Building and Discovery:How to Split Your Time as a Solo

To split building and discovery, pick a fixed share of your week for discovery, name it, and book it like a client call. Then protect it when you feel behind, because that is exactly when it gets eaten. The number matters less than the fact that it exists and survives a bad Tuesday.

How to split your time between building and discovery

"I'll do proper research once this release is out."

You've said it. In good faith. Every week. And every week the release was almost out, and then there was another release.

Here is why. Building has a visible cost to stopping. A feature half shipped, a customer waiting, a bug open. Discovery has no such cost. Nobody chases you for the conversation you didn't have. So when time runs short, discovery loses. Not sometimes. Every time.

The fix is not more willpower. The fix is a split between building and discovery that exists on paper before the week starts.

The split is a decision, not a ratio

People want me to hand them a number. Sixty-forty. One day a week. Mornings.

I won't, and here is why. Your number depends on your business, your stage and how much of the next quarter is a known improvement versus a guess. Anyone who gives you a universal ratio is selling a template.

What I will say is this. Whatever number you pick, three things must be true:

• It is a number, not a feeling. "Some time" is zero.
• It is planned around. Other work flexes. This doesn't.
• You know what happens to it when you feel behind.

That last one is the test. Say it out loud: "When I'm behind, discovery time gets ___." If your honest answer is "cut", you don't have a split. You have a wish.

"I do discovery when I have time" means no discovery. There is never time. That is not a bad month. That is the permanent condition of working alone.

Free guide · 21 pagesDiscovery and delivery, one person.The Dual-Track Playbook: how to keep discovering while you keep building.Get the free guide →

Your capacity is fixed, and small

Let's be straight about the arithmetic. There are no two teams here. One person holds both streams. So every hour of discovery is an hour of building you won't do.

There is no version of this where discovery is free.

That's the price. It is also the point, because building is by far the most expensive way to test an assumption. For you, expensive means evenings, and evenings are the only budget you can't top up. An hour spent answering "will anyone want this" is cheap next to a month spent finding out the hard way.

So you're not losing hours. You're buying a cheaper way to be wrong.

Give building and discovery each their own clock

Here is where most people break the practice. They put everything on one list, with one cadence and one definition of done.

Building runs in units with a predictable length. It asks: did I build it well? Discovery is irregular. Some questions resolve in an evening. Others take a month. It asks: should this exist at all?

Force both onto the same task list and discovery items sit there looking permanently overdue. They look like they're failing. They aren't. They are behaving normally, on a different clock.

Separate lists. Separate clocks. Same person, same week. Once you accept they run at different speeds, running them together becomes possible.

Put the questions on a calendar, not a to-do list

A to-do list is where discovery goes to die. Items drift down, get reworded, get postponed with a clear conscience.

A calendar is harder to lie to. So give discovery a recurring slot and a deadline for each question. Not "look into pricing". Instead: "By Friday I will know whether people from my target group do X, and I'll decide on Friday."

That is a timebox. Set it before you start. Discovery expands to fill the time you give it, and it always feels responsible to learn a little more. A date stops that. At the end you decide with what you have. Even if the decision is "I still don't know, and this is the one thing I'd test next".

If you want ideas for what goes in the slot, cheap tests and honest conversations are the two best uses of it. A small stream of listening that never reaches zero. Two conversations a week is a perfectly respectable stream.

Keep the buffer small

Now the awkward part. Building needs a steady supply of validated work. Discovery can't deliver on a schedule, because questions don't resolve on demand.

The way through is a small buffer. Enough validated work queued that you're never blocked waiting. Not so much that you're approving things just to fill the queue.

And when the buffer runs dry? Do not lower the bar. Take maintenance. Take a known improvement. Fix the thing that's been annoying you for a month. The moment you start promoting weak ideas to keep the build side busy, you are back to being a feature factory of one, with extra ceremony.

Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →

Connect the slot to the quarter

A protected slot with no direction turns into wandering curiosity. Interesting, unfocused, useless on a Friday afternoon. So tie it to this quarter's goal. The goal says what should be different. Discovery looks for the routes that might get you there. Building makes the ones that survive. This also kills a worry I hear a lot: that a fixed goal leaves no room to explore. It's the opposite. A goal framed as a result, not a pre-decided feature, is what permits discovery. If you find a cheaper route to the same result, that is a win, not a deviation from the plan.

What the first week looks like

Don't redesign your whole schedule. Do this instead.

1. Choose your share and write it on the calendar as a recurring block.
2. Create a separate list for questions. Phrase each one as a risk or an assumption, never as a feature.
3. Give the top question a date to decide.
4. Write one line: what I do with this block when I feel behind. Make the answer "I keep it".
5. Put the monthly check in the calendar now, before you forget.

That's it. You are not adding a process. You are adding a boundary around a stream of work that otherwise gets squeezed out.

Check building and discovery once a month

Starvation is gradual. Each step feels reasonable. That is why you need a direct question on a date.

Once a month, ask two things. What did discovery decide this month? What did I ship?

One blank month happens. Two in a row is the signal. Act on it.

Free guide · 21 pagesDiscovery and delivery, one person.The Dual-Track Playbook: how to keep discovering while you keep building.Get the free guide →

Watch the failure in your direction

I should warn you about the other side. Some of you will read all this and fall in love with the conversations.

Discovery is more comfortable than building. Nobody's code breaks. Nobody's deploy fails. You get to feel thoughtful. If you notice you prefer talking to shipping, ask yourself one question: am I learning, or hiding?

Both tracks must produce something that changes what happens next. A discovery slot that ends without a decision is just a coffee. If this sounds like you, the post on common dual-track mistakes covers it.

Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →

Frequently asked questions

What share of my week should go to discovery?

There is no universal figure. Choose one that fits your stage and how much of your plan is still guesswork, write it down and protect it. A smaller share that survives every week beats a bigger one that never happens.

Should I do building and discovery on the same day?

You can. They run at different rhythms, so what matters is that each has its own list and its own definition of done. If mixing them on one day keeps pushing discovery to the end, give it a fixed slot instead.

What do I do when a deadline eats my discovery time?

Decide in advance. Write down what happens to the allocation when you feel behind, because that moment is when it normally vanishes. If you skip it once, make it up or note it, and check whether it is turning into a habit.

How do I know the split is working?

Each month ask what discovery decided and what you shipped. If either answer is blank two months running, one track is starving and the split needs fixing.

Is it a problem if discovery tasks look overdue?

Only if they live on the build list. Discovery has its own clock, so keep its questions on a separate list with their own dates. Otherwise normal behaviour in building and discovery looks like failure.

The full method, with the checklists, is in The Dual-Track Playbook, a free 21-page playbook.