vvek

Set an appetite, not an estimate: fixed time, flexible scope for work that keeps growing

Basecamp's Shape Up idea of an appetite: decide how much time an idea is worth first, then shape the solution to fit. How a small team can try it.

Most teams know the feeling. Someone asks, "How long will this take?" You give a number, the work begins, and the number turns out to be a polite fiction. The task grows, the date slips, and nobody is sure whether to cut something or extend.

Basecamp's free book Shape Up suggests changing the question before the work starts. This article explains the idea, which they call an appetite, and shows how a small team can use it without adopting the whole method.

Estimate versus appetite

The book puts it neatly. An estimate starts with a design and produces a number. An appetite starts with a number and produces a design.

With an estimate, you work out what to build and then ask how long it needs. With an appetite, you decide how much time the idea is worth and then ask what version fits.

That second question is a business and product decision, not a technical one. "Is this worth two weeks of a small team?" is something a person can answer honestly. "Will this take twelve days or fifteen?" is something nobody can answer honestly before the design exists.

The sizes they use

For a standard team of one designer and one or two programmers, Shape Up sets appetites in two sizes:

  • Small batch: one to two weeks.
  • Big batch: a full six-week cycle.

If an idea does not fit into six weeks, the advice is to narrow the problem, or to split off a meaningful part that does fit. Not to stretch the cycle.

These numbers suit their setup. Your team may be different, and you can pick your own sizes. What matters is having a small, fixed set of them, so that everyone shares the same vocabulary.

Fixed time, variable scope

Once the appetite is set, the deadline does not move. The scope does.

This sounds like a slogan, but it changes behaviour day to day. When time is fixed and something takes longer than hoped, the question becomes "what can we leave out?" instead of "how much later will it ship?". The book gives a small example from the author's own writing: with one week left, they cut an extra section so they could still spend time fixing typos.

A fixed box also forces the team to separate the core of the work from the nice-to-haves. Early on, nobody knows which is which. Under time pressure, it becomes obvious quickly.

The book makes a point that is easy to overlook: "good" is relative to constraints. A solution is good in relation to how much time it is worth spending. An elaborate answer to a small problem is not an excellent solution. It is a poor use of the time.

Narrow the problem first

An appetite only works if the problem is well understood. The book encourages you to move from "What could we build?" to "What is really going wrong?" and to find the specific point where today's workflow breaks.

Two stories from the book show how much this can save:

  • A request for a six-week overhaul of permissions turned out to come from one incident: someone archived a file and it disappeared for everyone. A warning on the archive action fixed it in a day.
  • A request for a calendar became simpler when the team asked when a customer wanted one. The real need was to see free spaces, not to rebuild everything a calendar does.

And sometimes, if you cannot pin the problem down and it is not critical, the sensible answer is to walk away from it for now. Saying so openly is much cheaper than starting a project nobody can finish.

How a small team can try it

You do not need cycles or a new tool. Here is a gentle way to start.

  1. Write the problem in a few sentences, as something that went wrong for a real person. Not a solution.
  2. Pick an appetite. For example one week, two weeks, or "not now". This is the step that takes judgment.
  3. Sketch a solution that fits. If you cannot see one, narrow the problem or split it.
  4. Start, with the end date visible to everyone.
  5. Cut scope, not the date, when you find the work is bigger than hoped. Keep a short list of what you dropped and why.
  6. Look back briefly at the end: was the appetite right?

Tip

Keep a visible list of "things we cut". It turns scope reduction from a quiet failure into a recorded decision, and good items on it become the next piece of work.

Pairing it with other habits

An appetite fits well with things you may already do:

  • Release control. If scope can shrink late, you want a way to ship the finished part without exposing the unfinished part. Feature flags are a good fit.
  • Written decisions. When you cut something, write a short note about why. An architecture decision record is a light format for it.

When it works less well

Be honest about the limits. A fixed appetite is a poor fit for:

  • Work with hard external requirements, such as a legal change with a date and a fixed scope. Here scope is not variable.
  • Deep unknowns. If nobody knows whether something is possible, spend a short, explicit amount of time finding out. That research can itself have an appetite.
  • Maintenance and support, which arrive unpredictably. Reserve some capacity for them rather than pretending they do not exist.

Also, the method asks leaders to accept a smaller outcome rather than a later one. That takes some trust, and it is worth discussing before the first attempt.

One small experiment

Next time someone asks for an estimate, answer with a question: "How much time is this worth to us?" Then see how the conversation changes. In my experience, it moves from defending a number to designing something that fits, which is the part people wanted to do anyway.

Sources

Keep reading

A short email when we publish. Confirm once, unsubscribe any time.