“You’ve got to start with the customer experience and work back toward the technology.”
Steve Jobs delivered this principle while answering a difficult question at Apple’s 1997 Worldwide Developers Conference, soon after returning to a company with a confusing product line and serious strategic problems. He contrasted two approaches to innovation. One begins with an impressive technology and searches for a way to sell it. The other defines the benefit a customer should receive, then chooses and integrates technologies capable of producing that result. For Jobs, strategy required deciding what meaningful experience Apple could provide before celebrating any particular technical capability.
Working backward creates a practical filter. Customers rarely experience a component, protocol, or organizational chart in isolation; they encounter the speed, clarity, reliability, and emotional coherence of a complete journey. Starting there can expose tradeoffs that a feature list hides. A powerful function that adds friction may deserve removal, while an unglamorous improvement in setup or support may transform the product. The method also forces engineering, design, operations, and marketing to share an outcome rather than optimize separate pieces.
Customer focus is not the same as obeying every stated request. People can describe frustrations and desired outcomes more easily than they can specify an unfamiliar solution. Jobs’s formulation leaves room for invention because teams work back from an experience, not from a literal feature poll. At the same time, intuition should not become an excuse to disregard evidence or exclude users whose needs differ from a founder’s own. Accessibility, privacy, serviceability, and long-term cost are part of the experience even when they are less visible during a dramatic product demonstration.
The idea remains useful wherever organizations are tempted to lead with a tool. Before adopting a new platform or adding artificial intelligence, leaders can describe the concrete change a customer should notice and the trust conditions that must hold. They can map the journey, identify the hardest moments, test a small solution, and connect each technical investment to a measurable benefit. Technology still expands what is possible, but possibility is not a strategy. Jobs’s sentence asks companies to make technical ambition answer to a human purpose. A written experience principle can help teams settle later disputes: which option reduces effort, communicates control, or preserves confidence? When tradeoffs are explicit, elegance becomes a disciplined decision rather than a matter of taste. Post-launch observation completes the loop. Real use often exposes a gap between the intended experience and the one customers actually receive.
Jobs made the statement at Apple’s 1997 developer conference while explaining how the company should choose among many possible technical investments.
Apple needed a clearer product direction, and he argued that customer benefits should organize decisions across technologies.
Begin with the outcome and complete journey a customer should experience, then select the capabilities required to deliver it.
This does not mean implementing every request; teams still need judgment, experimentation, and evidence to invent a coherent solution.
New tools make it easy to add features before anyone defines the problem those features should solve.
A shared customer outcome keeps design, engineering, operations, and support aligned around value instead of separate activity metrics.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.