The Detail Dial
Calibrate how prescriptive a shaped plan is to the builder's seniority — more detail lifts juniors, less frees seniors.
- Difficulty
- Easy
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 90%
How much implementation detail to put into a shaped plan is not a fixed rule but a dial you turn based on who's on the build team. More detail makes a junior engineer far more successful and prevents them hiding that they're lost; less detail gives trusted seniors room. Counterintuitively, the dominant real-world failure is too little detail, not too much — and if a builder insists on owning the fundamental approach, the fix is to bring them into shaping, not to strip detail out.
Origin
Ryan Singer's practical answer to the common PM fear that detailed shaping turns engineers into 'code monkeys.' Drawn from his consulting with Shape Up teams of varying seniority, contrasted against Basecamp's all-senior teams that needed very little detail.
Core principles
- 01The right amount of detail is a dial set by the builder's seniority, not a universal standard
- 02The dominant real-world failure is not enough detail, not too much
- 03Juniors won't ask when lost — they hide it, and it blows up later; guidance prevents that
- 04Give people 'bigger shoes to grow into' by dialing detail back as trust builds
- 05If a builder wants to own the approach, put them in the shaping session rather than removing detail
How to run it
- 1
Read the build team's seniority
Before deciding how prescriptive to be, look at who will actually build it — a junior needs a suggested approach; a proven senior with a track record and your trust can be given far less.
Watch out Prescribing schema-level implementation to a senior engineer ('here's how I want you to implement the database change') rightly makes them bristle — 'who are you?'
- 2
Dial detail up for juniors
For a junior builder, add guidance: 'we're going to do this, and I'd suggest approaching it like this.' It makes them successful and lets them learn how an expert approached the problem.
Pro tip Detail also protects you from the silent failure where a junior who doesn't know how won't ask — because they don't want to reveal they're lost — and it blows up late.
- 3
Dial it back to grow people
On later projects, deliberately give less detail to see how the person handles more responsibility — bigger shoes to grow into. For stellar, trusted talent, leave things out from the start.
- 4
If they want the approach, bring them into shaping
When a builder feels they should own the fundamental approach decisions, don't solve it by removing detail — invite them into the shaping session to play the technical role, using their strengths at the right moment.
Pro tip The goal is to put each person where their strengths apply and give them both maximum creativity and maximum clarity.
In the wild
When a junior is on the build team and a senior is in shaping, adding 'I'd suggest approaching it like this' makes the junior far more likely to succeed. Left without guidance, a junior who doesn't know how won't ask — they hide being lost, and it surfaces as a blow-up later in the project.
→ With guidance the junior succeeds and learns the expert's approach; on a later round the detail can be dialed back to stretch them.
Common mistakes
Assuming detailed shaping means 'code monkey' work
PMs fear that specifying detail insults engineers, but the amount of detail is a dial keyed to seniority — for juniors, more detail is empowering, not demeaning, and its absence is the more common failure.
Stripping detail out when a builder wants the approach
If a builder wants to own the fundamental approach, removing detail from the plan doesn't help — the right move is bringing them into the shaping session to play the technical role.
Is it for you?
Best for
PMs and leads shaping work for mixed-seniority teams who worry about either over-prescribing to seniors or under-supporting juniors.
Not ideal for
All-senior, high-trust teams (like Basecamp's) that consistently succeed with minimal detail — the dial just stays low.
From the transcript
“the dominant failure case that I see in the real world is always again and again not enough detail”
“the amount of detail that the team is going to feel helps them is a dial that we can turn that depends on who on…”
“a better solution would be to actually bring them into the shaping and have them play that technical role in the shaping session”
From the episode
A better way to plan, build, and ship products
Ryan Singer (creator of “Shape Up,” early employee at 37sign