Know Why. Know How. Then What?

The chapter walks through the practical work of identifying the Why-How-What stack for an organization, starting from where most organizations actually live: knowing the What clearly and the How partially.

The method Sinek describes is reverse-engineering. Start with the What — the products, the outputs, the visible behavior — and ask what they have in common when the organization is at its best. The commonality is not the product itself; it is the underlying belief or method that produced the product and that distinguishes it from competitors. Iterate the question until the underlying Why emerges.

The chapter is honest that the work is uncomfortable. Many organizations discover, on doing the exercise, that they do not have a coherent Why — their products and outputs do not share a common belief, and the variation is explained by ad-hoc strategic decisions rather than by purpose. The discovery is itself useful because it makes the strategic problem visible, but it is not the pleasant exercise that purpose-statement workshops are usually marketed as.

The deeper claim is that Why is not invented; it is discovered. Organizations that invent a Why and impose it onto their existing What produce branding mismatches that customers and employees can detect. Organizations that discover their genuine Why — the one that already explains their best historical decisions — produce alignment that requires no enforcement because it was always there.

The reverse-engineering method runs from the visible to the underlying: list the What's the organization is proudest of, then ask what they share that competitors' What's do not. The shared quality is rarely the product itself; it is the belief or approach that produced it. Sinek is insistent that the Why is discovered, not invented — it already exists in the organization's best decisions and most-aligned products, and the work is excavation rather than authorship. A useful Why, he argues, is phrased as a statement of contribution and impact: the difference the organization seeks to make and the effect that difference has on the people it serves, not a description of the product or the market. Once articulated, the Why is tested against history: does it explain the decisions that worked and the ones that felt wrong? A Why that fits only the press release fails the test. The chapter's deliverable is the full Why-How-What stack, ordered correctly, so that future decisions can be checked against the purpose rather than improvised against the quarter.