Appetite and shaping

Basecamp's Shape Up replaces "how long will this take?" with appetite: how much time is this idea worth? Fixed time, variable scope. A six-week appetite means the team shapes a version that fits six weeks — or the pitch is rejected / reshaped — instead of estimating a fantasy and then slipping.

Why appetite works better than open-ended estimates for product work: estimates assume the solution is known. Early product work is mostly learning. Fixing the timebox forces the question "what version of this idea fits the learning budget?" instead of "when will the imaginary complete product be done?"

Walking through a shaped pitch

Before a cycle, someone writes:

• Problem and elements of a solution at the right altitude
• Rabbit holes called out (auth edge cases, migration, performance)
• No-gos — what is out of scope for this appetite
• Breadboard or rough UI flows without visual polish

Then a betting table chooses which shaped pitches get an appetite this cycle. Teams own execution inside the timebox; if scope threatens the deadline, they cut scope, not quality or sleep.

This pairs with estimation: estimates are still useful for relative cost inside a pitch, but the commitment boundary is the appetite, not a negotiated date for infinite scope.

When engineers estimate, ask for the Must-only estimate and the Must+Should estimate separately. Stakeholders who demand both the full list and the Must-only date are asking for a contradiction; make them choose.

From MVP to v1 without boiling the ocean

When signal is good, resist rebuilding everything "properly" at once. Sequence:

1. Automate the most painful manual step you repeated in concierge mode.
2. Harden trust paths (auth, billing, data deletion).
3. Widen from design partners to a slightly broader segment — not the entire TAM.
4. Add the second job only when the first job retains.

Each step still has an appetite and a learning goal. That is how wedges become products without skipping product–market fit.

Common mistakes

• Estimating infinite scope. The date slips; the idea never gets smaller.
• Shaping as pixel mockups or as vague epics. Wrong altitude on both sides.
• Cutting quality or sleep when the timebox is tight. Cut scope. That is the point.

Check yourself

A pitch cannot fit in a six-week appetite. What happens? Reject or reshape it. Do not accept a fantasy date for the full vision.

Must+Should is twice the Must-only estimate, and leadership wants both plus the short date. What do you do? Make them choose. Full list and Must-only date is a contradiction.

Key takeaways

• Appetite fixes time and varies scope; that matches product work, which is mostly learning.
• Shape before you bet: problem, rabbit holes, no-gos, breadboard.
• After a successful MVP, sequence automation, trust, a wider segment, then the second job.

Further learning

Shape Up (Basecamp) — free bookShape Up will help you break free of “best practices” that aren’t really working, think deeper about the right problems, and start shipping meaningful projects your team can celebrate.basecamp.com

Next: cutting scope without losing the aha.