The Dual-Track Playbook Keep discovering. Keep building.
Most solo builders swing between shipping everything and researching everything. Both end the same way: a year of effort and little that changed. This guide shows how to run both streams at once, so what you build is what was worth building.
You are not short of effort. You are short of evidence.
You build continuously. The list is full, things ship, your evenings are busy, and after two quarters remarkably little has changed. Or you stop to be rigorous, research for weeks and ship almost nothing. Both come from one belief: that discovering and building take turns. Once you believe it, discovery always loses, because only building has a visible cost to stopping. And AI has made it cheap to build the wrong thing beautifully.
None of them is "talk to users".
Pure output ships a lot of confident work with no reliable link to results. The cost is not the work you did. It is the work you could have done instead.
Insight you never ship decays, because markets move. Building is how discovery gets validated. A conclusion you never shipped is a hypothesis with better manners.
Building comes in units and asks whether you built it well. Discovery is irregular and asks whether it should exist at all. Forced into one list, discovery looks permanently overdue.
Building is the most expensive way to test an assumption. Every idea killed in two conversations is a month of evenings sent somewhere with better evidence.
Alone, doubt has nowhere to go. A discovery track turns an anxious loop at eleven at night into a question with a cheap test and a date.
Did the thing you shipped produce the outcome you predicted? Measuring it is how you get better at predicting. Shipping and moving on repeats the same errors.
Two streams, one person.
Not a research phase and not a build phase. A way to keep one small stream of listening running the whole time, protect it from the week you feel behind, and send only what earned its evidence into your evenings.
Five parts, in order.
Six mechanisms, each a specific failure it prevents, and the honest limit: your capacity is fixed, and a discovery track can become a place to hide.
Both tracks are yours, assumptions go in discovery and not features, what validated means, the time you protect, and what makes an idea graduate.
Start from the riskiest assumption, choose the cheapest test that could change your mind, talk without leading, kill things visibly, and timebox each question.
What graduates and why, keeping building fed, spotting a starving track, closing the loop after shipping, and keeping the boundary light.
Before you start, running discovery, and the handoff and the loop. Each line is a box you either can or cannot tick.
Nine ways dual-track turns into vocabulary. All of them are failures of protection and follow-through, not of method.
Take the idea you most want to build and list what must be true for it to work. Rank by how damaging it would be to be wrong. Test the dangerous one, not the convenient one.
Name it, put it in the calendar, and decide now what happens when you feel behind. "I do discovery when I have time" means no discovery.
Decide what result counts as a no, and whether you would really stop. If you would not, skip the test and build. A test you would ignore only buys false confidence.
- You already run a one-person business and want to scale it without hiring a team.
- You can build almost anything in a weekend and need help choosing what deserves one.
- You are willing to kill ideas and record why.
- You want a method with checkboxes, not motivation.
- You want a research programme or a licence for indefinite discovery.
- You want a promise that every idea you test will work.
- You expect discovery to cost nothing. It costs some of your building time, by design.
- You plan to test only the things you already intend to build.
Never let the listening reach zero.
The most expensive thing you can do with your evenings is build the wrong thing beautifully. You will not avoid it by being careful, because it feels like the most focused you have ever been. The protection is structural: two conversations a week, a written record, and a rule about what would make you stop.
Luis Gonçalves
Twenty years in digital product development. Led the agile transformation at Nokia. Teaches at Porto Business School. Has spent the last decade working with founders across Saudi Arabia, Portugal, Brazil, and the broader emerging-market startup ecosystem.
He calls himself the Dark Entrepreneur because he believes the founder world is allergic to honesty. No success theater. No highlight reels. Just the real work that has to happen.