The problem before the product
I generate more ideas than I can responsibly build. For years I moved them between notebooks, Apple Notes, Evernote, OneNote, and Notion. Those tools could capture a thought, but capture was not the real problem. The difficult part was deciding which ideas described something worth solving and what I would need to learn before committing months of work.
yFocus was an early product concept for that gap. Its purpose was not conventional task management or personal productivity. It was intended to help a maker refine an idea faster and validate it before the idea quietly turned into a roadmap.
The intended workflow
The product direction separated enthusiasm from evidence. A useful path through yFocus would move a concept through a small number of questions:
- What human problem do I think I have noticed?
- Who experiences it, and what do they do today?
- Which assumptions must be true for this idea to work?
- What is the smallest interview, prototype, or experiment that could challenge those assumptions?
- What did I learn, and should I continue, change direction, or stop?
The point was not to produce a polished pitch. It was to create enough structure that a founder could distinguish a genuinely useful opportunity from an idea that was merely enjoyable to imagine.
Why it stayed a concept
yFocus reached the prototyping and proposition stage, but not a public product. The holding page invited people interested in refining ideas faster to get in touch while the wider workflow was still being shaped.
That status is part of the case study rather than something to hide. A product about validation should be allowed to validate itself before becoming another large build. At the same time, I was working on Observer, Airproxy, and other experiments; yFocus had to compete for attention under the same constraints it was meant to help clarify.
The useful outcome
The project sharpened how I approach new products even without becoming one itself. I now separate an idea repository from an evidence process. Notes are useful for remembering possibilities; validation requires contact with the people, constraints, and behaviour surrounding the problem.
yFocus also reinforced that deciding not yet is a legitimate product decision. The cost of a weak idea is rarely the afternoon spent sketching it. It is the momentum, infrastructure, and identity that accumulate after building begins and make an honest change of direction harder.