Build Down From Why, Or You’re Just Building Features

Most product visions get written backwards: the feature list comes first, and a mission statement gets bolted on afterwards to make it sound inspiring.

The Ladder of Needs flips that order. It has three rungs, read from the bottom up: Why does your product do the job, How does it do the job, and What job does it do. It combines two established ideas: Clayton Christensen’s Jobs to Be Done, the observation that customers "hire" a product to do a job and "fire" it if it does that job badly, with Simon Sinek’s Start with Why. Read bottom-up, the ladder becomes a filter for every new initiative on a roadmap: is this a genuinely new What, an improvement to How you already do the job, or an extension that only makes sense because it strengthens the Why underneath it.

The instinct is to start at the top of the ladder, define the feature, ship it, and worry about the vision statement later, once there’s something to point at.

The broader research behind Jobs to Be Done makes a specific case against exactly this instinct: most companies now hold more customer data than ever, yet a McKinsey poll found that 94% of executives were dissatisfied with their own innovation performance. The reason, according to the researchers, is that most of that data shows correlation rather than the causal "why" behind a purchase.

The proof is a Detroit condominium developer targeting downsizing retirees. Demographic data, focus groups, and a full cost-benefit analysis of every feature told the company almost nothing useful. Bay windows tested well and changed nothing. What actually explained who bought and who didn’t only surfaced through interviews aimed squarely at the job being hired, and it turned out to be the family dining table. A missing feature didn’t block buyers. They were blocked by the anxiety of giving up a piece of furniture that represented their family’s history. Once the company understood that, it redesigned the units to fit a table, added moving and storage services, and raised prices by $3,500. While the wider market fell 49% during the 2007 downturn, that business grew 25%. None of that came from a better feature. It came from correctly answering "Why" before touching "How" or "What".

Design at Scale™ places the same discipline at the top of its own Method for the same reason. Our Mission Statement sits ahead of the five-pillar Framework in the Book, not as decoration but as the rung on which everything else rests. Our Journal asks the individual version of the identical question under "On Purpose": what are you after, and how can design help you get there, before it ever asks what you're going to build. Applied to Design at Scale™ itself, the ladder reads cleanly. The top rung, What, is the growing library of SPY resources this section produces: research foundations, fit-checks, ideation tools, vision boards. The middle rung, How, is the documented Framework itself: Proposition Shaping, Design Shaping, Refinement, Product Delivery, Integration, a synchronised, transparent operating flow rather than a loose collection of habits. The bottom rung, Why, is stated plainly after reviewing 274 design methods: to close the gap between exploration and delivery, so teams stop reinventing processes by trial and error and start scaling on a compounding system. Every SPY piece published so far is a What resting on that same Why, which is exactly the test worth applying to whatever gets written next.

"We already have a mission statement, isn't this the same thing"

It is the most common objection. A mission statement is usually written once and framed on a wall. The ladder is a working filter you apply to every new initiative, asking which rung it actually sits on, not a plaque nobody rereads after the launch party.

"This feels like philosophy, not delivery"

Is the second, and the Detroit story answers it directly. Correctly identifying why produced a $3,500 price increase and 25% growth against a falling market. Few outcomes are less philosophical than that.

"Our team already knows why we exist"

Is the third. Knowing it privately and using it as a live filter for roadmap decisions are different things. Ask five people on the team to state it in one sentence and see how many versions come back.

The ladder only works when read from the bottom up. Skip straight to What and you've built a feature list dressed up as a vision. Start with Why, prove it the way Moesta proved his with real evidence of the job being done, and How and What follow logically rather than needing to be invented afterwards.

Next time you frame a new initiative, place it on the ladder before you scope it:

— a new What,
— a better How,
— or something that only exists because it strengthens the Why.

If you can't answer that, that’s where Supply starts. More at designatscale.co/spy.

REFERENCES

• Ulrich, C. (Kit), "A surprisingly simple technique for a rockstar product vision: The Ladder of Needs"
• Christensen, C., Hall, T., Dillon, K., Duncan, D.S., "Know Your Customers' Jobs to Be Done," Harvard Business Review, September 2016
• Design at Scale™ Book & Journal (internal)

SUMMARY

• The Ladder of Needs reads bottom-up: Why (root cause) → How (method) → What (feature/output), combining Jobs to Be Done with Start with Why.
• Most innovation efforts fail not for lack of data but for mistaking correlation (customer traits) for causation (the actual job being hired).
• The Detroit condo case is hard proof: understanding the real "why" (anxiety over a family dining table) drove a $3,500 price increase and 25% growth, even as the market declined 49%.
• Applied to Design at Scale™ itself: SPY resources are the What, the Framework is the How, and closing the exploration-to-delivery gap (274 methods reviewed) is the Why everything else rests on.
• The ladder is a working filter for every new initiative, not a one-time mission statement exercise.

https://www.figma.com/community/file/1383945468342308213/das-the-ladder-of-needs