Why the Workshop is two days, not five

The Discovery Workshop is two days. Founders who book it sometimes ask whether it could be longer — three days, a full week, two weeks broken into sessions. The shorter answer is no, and the longer answer is the subject of this essay.

I want to walk through the reasoning, because the structure isn’t arbitrary and the structure matters more than most founders expect.

This is one of the design decisions I get asked about most often, and one I’ve thought about most carefully. The honest answer is operational, partly cognitive, partly a reflection on what constraint produces in service-design. None of those reasons are obvious; all of them are load-bearing.

The operational reason

The operational reason is that discovery quality is constraint-shaped.

A short engagement forces prioritisation. We can’t map everything in two days, so we have to map the things that matter most. The diagnostic that ships at end of Day 1 is the sharpest version of the diagnostic precisely because we didn’t have time to dilute it with second-tier observations. The roadmap that ships at end of Day 2 is the most actionable version of the roadmap precisely because we had to commit — we couldn’t defer.

A longer engagement loses this. Three days creates room for the diagnostic to drift sideways into territory that’s interesting but not load-bearing. Five days creates room for the team to second-guess earlier conclusions, which is sometimes useful but mostly produces revision-without-improvement. The work that benefits most from constraint suffers most from extra time.

I’ve watched discovery engagements in adjacent firms run for two weeks and end with less actionable output than ours produces in two days. The pattern is consistent enough that I treat it as a design parameter, not an accident.

The cognitive reason

The cognitive reason sits behind the operational one.

Founder attention degrades reliably after the second working day on a single problem. Not because founders are inattentive — most founders running businesses at the 4-to-25-person stage have proven attention discipline. The degradation happens because the problem space changes shape under sustained focus. After two days inside a brand-and-operations diagnostic, the founder’s mental model has shifted; the questions that felt sharp on Day 1 feel familiar on Day 3; the patterns the founder identifies on Day 4 are partly real and partly artefacts of fatigue.¹

This isn’t a moral failure. It’s an operational reality. Sustained attention on a single complex problem reliably degrades quality after about 48 working hours. The cognitive research on attention-fragmentation goes back decades; the application to professional services is straightforward.

Two days is calibrated to the work the founder can do well. Five days is calibrated to the hope that more time produces more value — which the research doesn’t support.

2-day vs 5-day output

The output difference between a 2-day Workshop and a 5-day workshop is visible.

A 2-day Workshop ends with a locked diagnostic — the founder can explain it to their team in 60 seconds. The roadmap is sequenced for the next 12 weeks; each milestone has a documented success criterion. The founder closes Day 2 with energy left for the next 90 days of work.

A 5-day workshop ends with an iterating diagnostic — the team is still adjusting on Day 5 because the constraint never forced commitment. The roadmap covers multiple quarters but at lower specificity, because the team had room to be ambitious without having to commit. The founder closes Day 5 having spent the cognitive budget the engagement was designed to preserve.

Two days is calibrated to the work; a week would be calibrated to hope.

That’s not theoretical. It’s the difference between an engagement that produces a usable artefact and one that produces an aspirational document. The Workshop’s job is the usable artefact. The structure protects that.

Constraint as quality

The two-day calibration is part of a broader pattern in how we design engagements.

The Build tier is three months, fixed price. Not nine months. Not “we’ll see how long it takes.” Three months is the duration the work calibrates to, and the price reflects the work, not the team’s hourly rate. The Partnership tier is monthly with a 90-day cancellation notice — not annual contracts, not autopay-lock-in. Ninety days is the time required to hand a system back cleanly when the founder decides to in-house it.

Each of these constraints is calibrated, not punitive. We’re not making the engagement difficult; we’re aligning the duration with what the work needs. Most agencies use longer engagement structures because longer structures bill more hours. Most agencies use ambiguous duration because ambiguity creates room for scope creep. We use specific, short, fixed durations because the work itself benefits from the constraint.

The pattern is service-design discipline. Founders who recognise it from inside their own businesses — the same way constraint sharpens product decisions — are usually the founders we work best with.

If two days doesn’t suit your situation, the Discovery Call is the right place to say so. We can walk through the reasoning together; if the constraint is wrong for your business, we’ll be honest about it and point you toward better-fit alternatives.

If it does suit your situation — and it suits most founders running brand-and-operations at 4-to-25 staff — the Workshop is where the work begins. Two days, fixed price, refund on non-delivery. The structure is the same way the rest of the engagement is structured: calibrated, not punitive; specific, not arbitrary; sharp, not maximal.

Most of the founders I work with appreciate the structure once they’re inside it. The shape of the engagement matches the shape of the work the engagement does. That’s the discipline.

— Kenny