At first, building LowFlow mostly meant one thing: making the product work. Then another question came up. What good is a solid product if no one knows it exists?
I had already worked on the journal, the desktop app, the customer journey, the real-world tests and the control tools. But there was still another system to build around LowFlow: its visibility.
Not with a big ad campaign. Not by trying to be everywhere. By gradually building entry points.
The site became the central point. The blog is where I can tell how LowFlow was built, and also explain why certain decisions were made.
Search engines then let those pages exist beyond my own posts. Google first. Then Bing. And behind Bing, other engines can discover the content too.
Social media plays a different role. Facebook isn't the product. It isn't even where I want to store LowFlow's whole story. It mostly serves to create a first encounter. A short post. An image. A few lines. Then a link to the site. The important content stays with LowFlow.
Little by little, I understood that visibility had to be built exactly like the rest of the project: one piece at a time. The site. The blog. The search engines. The share previews. The social networks. And soon the videos.
The product had become a system. Now I had to let people find it.