Chapter I
Shaping
Turning a raw problem into a pitch a team can bet on — concrete enough to build, rough enough to leave room.
Shaping happens before a team ever commits. It's the quiet work of taking a raw problem and giving it just enough definition to bet on — no more. The output is one thing: a pitch. Five parts, and by the end of this page you'll have built one, from problem to solution.
What makes this hard
Shaping asks three things that cut against normal product instinct. If they feel wrong at first, that's expected — watch for them as we go.
Stay off the solution.
The reflex is to start designing. Shaping starts from the problem and earns its way to a solution slowly.
Fix the time, not the scope.
You set how much time the problem is worth and hold it. The solution bends to fit the time — never the reverse. (Scope gets trimmed later, while building — not here.)
Kill ideas while they're cheap.
A bad idea caught on paper costs a minute. The same idea caught mid-cycle costs weeks. Paper is where ideas are supposed to die.
Here's where we're headed. A finished pitch has five parts, and one example will carry us the whole way: a calendar app whose users are drowning in it — every event shows at equal weight, so the day's few get lost in the many. That complaint is the raw problem, and right now it's the only part of the pitch filled in. The rest is what shaping produces.
Notice we began with a problem, not an idea for a feature. That's the first discipline. We don't yet know what we'll build — only what's wrong. Good.
The pitch we're shaping
The calendar is a wall.
Problem
Every event shows at equal weight, so the day's few get lost in the many.
Appetite
— set in Move 1 —
Solution
— shaped in Move 2 —
Rabbit Holes
— walked in Move 3 —
No-Gos
— drawn in Move 3 —
Move one
Set the appetite
Before thinking about solutions, settle one question: how much time is this problem worth? Not how long a fix would take — that question can't be answered yet and would balloon if it could. The answer is the appetite, and it's the reverse of an estimate. An estimate starts from a design and produces a duration. An appetite starts from a duration and constrains the design. You pick the number first, and then hold it.
Shape Up offers two sizes: a small batch (around two weeks) or a big batch (a full six-week cycle). For the calendar, two weeks buys only sorting — a filter, a reorder — and the problem is deeper than sort order. A whole quarter would mean rebuilding scheduling itself — an overhaul, for what's really just friction. So: a big batch, six weeks. That number is now fixed. Every solution from here has to fit inside it.
The pitch we're shaping
The calendar is a wall.
Problem
Every event shows at equal weight, so the day's few get lost in the many.
Appetite
Solution
— shaped in Move 2 —
Rabbit Holes
— walked in Move 3 —
No-Gos
— drawn in Move 3 —
Move two
Rough out the elements
Now the creative middle of shaping. Solutions get sketched at the level of elements — the parts of a solution and how they relate, not the pixels or the copy. Three ideas come to mind for the calendar, and instead of debating them in the abstract, each one gets a quick breadboard: a five-minute flow in words and arrows. Then the boards do the arguing. Two collapse as soon as they're on paper.
Fig. 1 · Three boards, one survivor
A separate priorities inbox
Its board needs a second place beside the calendar — a second thing to check and manage. It adds a list rather than taming the one they have.
Let users tag every event by importance
Its board fills up with affordances — tag, rank, re-rank — all worked by the user. It asks the user to do the very sorting the tool set out to do for them.
A focused day view
One new place, a couple of affordances, a line back. The only board that removes work instead of adding it. This one holds.
The technique
Breadboarding
The term is borrowed from electronics, where a circuit is wired up bare, with no casing. A breadboard writes a flow in three kinds of mark: places you can be (underlined), affordances you act on, and lines for where each leads. Nothing gets drawn — it's all words and arrows, and that's enough to tell whether a flow actually works.
Cheap enough to waste. A board takes minutes, so every idea can have one — and losing one costs nothing. Every option gets a fair look.
It surfaces the questions. Writing out places and affordances confronts you with questions you hadn't thought to ask — where does this live, how do you leave it, what happens next.
It can't argue about looks. With nothing visual on the page, the debate stays on how the idea works — not on how anyone happened to draw it.
The surviving board settles how the day view wires together — but not what it looks like, and for this idea the look is the substance. So the shape gets settled with a fat marker: "today, distilled" resolves in seconds into a short, ranked list, the day's few stacked with the most pressing on top. Only now is the solution actually decided — settled by the sketches, not ahead of them.
Fig. 2 · The fat marker sketch
The day's few events, stacked with the most pressing on top, plus a way back to the full calendar. It's deliberately too rough to be mistaken for a real design — what it finally looks like is up to the builders.
The technique
Fat marker sketches
A sketch made with strokes so broad that adding detail is impossible — a thick pen on paper, the fattest brush on a tablet. It's the tool for ideas that live in two dimensions, where the arrangement is the idea.
Some ideas are visual. When the 2D arrangement is the fundamental problem, a flow of words and arrows misses the point — you have to see where things sit.
Too thick to overcommit. You can settle the layout without settling the design. Wireframe fidelity would decide things shaping has no business deciding.
The pitch we're shaping
The calendar is a wall.
Problem
Every event shows at equal weight, so the day's few get lost in the many.
Appetite
Solution
A focused day view — Focus opens “today, distilled,” a short ranked list with a way back.
Rabbit Holes
— walked in Move 3 —
No-Gos
— drawn in Move 3 —
Move three
Walk it, then declare the no-gos
One move left, and skipping it is how confident pitches sink cycles. Walk through the solution in slow motion — how does a user actually get from start to end? — looking for a rabbit hole: a hidden depth that could swallow the appetite. This is de-risking: you're removing danger from the solution before anyone bets. A rabbit hole gets one of three treatments: patch it by making the hard design decision now, declare it out of bounds, or cut the piece entirely.
Walking the day view, the rabbit hole shows up fast: how does the tool decide which events matter? Doing that with real intelligence would mean building a recommendation engine inside a calendar — easily more work than the whole rest of the pitch. So we patch the hole and make the decision now: the list is ranked by a few simple signals. Whatever is soonest, whatever involves other people, whatever the user already marked important.
What we ruled out becomes a no-go, written into the pitch so no one wanders back into it. Naming what you won't do is the last act of shaping — it's what lets a team read the pitch and know exactly how far it goes.
The artifact
A shaped pitch
All five parts are filled. The complaint we started with is now a proposal any teammate can judge in a single read — bounded in time, solved at the level of elements, and de-risked before a week is spent.
Look back at what shaping never touched: how long it'll take, how to break up the work, what the screens finally look like. Those are the builders' to discover — inside the six weeks we fixed.
The pitch we're shaping
The calendar is a wall.
Problem
Every event shows at equal weight, so the day's few get lost in the many.
Appetite
Solution
A focused day view — Focus opens “today, distilled,” a short ranked list with a way back.
Rabbit Holes
No real intelligence — rank by simple signals: soonest, involves other people, marked important.
No-Gos
The pitch we're shaping
The calendar is a wall.
Problem
Every event shows at equal weight, so the day's few get lost in the many.
Appetite
— set in Move 1 —
Solution
— shaped in Move 2 —
Rabbit Holes
— walked in Move 3 —
No-Gos
— drawn in Move 3 —
Shaping's job was only to hand the builders a problem worth solving, a boundary they can trust, and enough of a solution to begin. Whether anyone actually builds it is a separate decision, made at the betting table — and that's the next chapter.
Terms from this chapter
Appetite
How much time a problem is worth. An estimate asks how long the work will take. An appetite asks how much time the problem deserves.
Elements
The parts of a solution and how they connect. The altitude shaping works at.
Breadboard
Places, affordances, and the lines between them. A flow proven in words before anything is drawn.
Fat marker
A pen too thick for detail — for settling arrangement without dropping into pixels.
Rabbit hole
A hidden depth that could eat the appetite. Remove it, decide it, or declare it out of bounds — before betting.
No-go
Something ruled out in writing — declared out of bounds so no one wanders back into it.