Technology First vs. Needs First

Marty Cagan responds to a debate sparked by Don Norman's essay arguing that big societal innovations are driven by technology first and needs later, which Norman frames against heavy upfront user research. Cagan says the framing is an oversimplification: Norman's point applies mainly to revolutionary innovations, while most product work is incremental. For most interesting innovations, he argues, product, design and engineering collaborate in parallel to find solutions that are valuable, usable and feasible. He describes the many outcomes of product discovery, from feasibility surprises to pivots, and concludes that the real lesson is to avoid over-researching while treating innovation as a shared effort.

01Key takeaways

• Avoid spending months on research before considering whether a solution is technically feasible.
• Write a quick problem definition or opportunity assessment to frame the need without locking in a solution.
• Bring engineers into discovery early, since they often find feasible approaches teams assumed were impossible.
• Test ideas with users early, because reactions reveal which needs are met, which are not, and when to pivot.
• Treat innovation as a parallel collaboration between product, design and engineering aimed at solutions that are valuable, usable and feasible.

02Key sections

Norman's argument and its misreading

Norman's 'technology first, needs last' essay is aimed at revolutionary inventions and at dogmatic up-front research, and is often oversimplified. Cagan thinks the core point is valid but has confused many readers.

Need and technology arrive together

Cagan cites FedEx, TiVo and the iPad as examples where a long-standing need met a newly feasible solution. These were driven by solving real problems, not by technology research waiting for a use.

The value and limits of up-front research

Heavy formal research before building is rarely worthwhile, since the hard part is finding a feasible, usable solution rather than understanding the need. A brief problem statement or opportunity assessment still helps open up alternative approaches.

What product discovery actually produces

Discovery can validate the need but reveal infeasibility, show weak demand or entrenched resistance, expose overly complex solutions, or trigger a pivot. Most often it leads to iterative refinement toward a solution that is valuable, usable and feasible.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.