Reflecting on Apple's product culture under Steve Jobs, Camille Hearst argues Apple's craft/design-led approach — defining the narrative and messaging for a product before building its features — differed fundamentally from today's metric-driven product management, where features and roadmaps are typically derived from data and OKRs first.
She notes this narrative-first model is now being consciously re-imported by companies like Airbnb, suggesting it's resurfacing as a deliberate countertrend to purely metrics-driven PM.
When developing a product, consider drafting the narrative/messaging (what the product means to the user, how it will be talked about) before defining feature specs, as a way to keep the "why" ahead of the "what" — particularly for products intended to be flagship or brand-defining rather than incremental.
Fadell endorses writing the product's press release, or top-line customer story, before building — while rejecting the "backwards" label in "working backwards," comparing it instead to writing a script before shooting a film. Drafting the press release first forces early clarity on what the product actually is to a customer.
A press release can only carry three or four key features before it becomes, in Fadell's words, "gobbledygook" to a customer — so this practice doubles as a scope-cutting discipline. Cap a launch narrative at three to four headline features and cut or defer anything else, even if it's already been built.
Fadell argues technology-led teams default to describing products by their features (the what) while great storytelling explains why the product matters to a person's life (the why): "too many times when we're technology-led, we talk about the what. We don't talk about the why. And the why is where the storytelling is." Lead with the human reason a product matters before listing its features.
Two techniques he names for building that story: