Glossary
What is shaping?
Turning a raw request into something decidable: the problem stated apart from the proposed solution, the intended outcome, what is known versus assumed versus unknown, and a likely owner.
Shaping is not specification — it produces a decision input, not a build plan. A shaped demand can still be declined, and that is the point: the work of understanding happens while the requester still has the context, and before anyone's time is promised.
Shaping vs specification vs refinement
Specification describes how to build something that has been decided. Refinement prepares committed work for a team to pick up. Shaping comes before either, and before the decision itself: it produces enough understanding to decide whether the work should happen at all. A shaped demand may never be specified, because the answer may be no.
The word also appears in Basecamp's Shape Up method, where shaping roughs out a solution at a fixed appetite before a betting table decides. The spirit is close, but the sense here stops earlier: it deliberately keeps the problem apart from any solution, and its output is an understanding of the request, not a pitch for one way of meeting it.
How to shape a request
First, separate the problem from the proposed solution: ask what happens if nothing is done, and who notices. Second, state the intended outcome as something observable, so success can be recognised later. Third, sort what the request says into what is known, what is assumed and what is still unknown. Fourth, name the likely owner of the next decision. Then stop — sizing, sequencing and task breakdown belong to later stages.
Do it with the requester, soon after the request arrives, while they still have the context. A shaping question answered in a day costs a message; the same question discovered in week six of delivery costs the date.
Common mistakes
Restating the solution as the problem — "the problem is that we do not have SSO" describes a missing feature, not the need behind it. Shaping into a specification, which spends design effort on work nobody has agreed to. Shaping every request to the same depth, when a small fix needs a sentence and a strategic initiative needs a real conversation. And treating a well-shaped demand as already committed: shaping makes the decision possible, it does not make it.
Related terms
- Demand — A work request that has entered the delivery lifecycle — the unit a delivery governance system tracks from intake to decision.
- Clarification brief — A short artifact that separates what is known from what is assumed from what is still an open question, produced when a raw request is shaped into a demand.
- Demand management — The practice of deciding what happens to requested work — shaping raw requests into decidable demands, refusing or parking some on the record, and committing the rest against real capacity.
This definition comes from building DeliverySheet — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date.
$189/month per workspace, unlimited members. 7-day free trial — card required, cancel before it ends and you're not charged. I answer the support email myself.