“If you ever tell an engineer at Intuit which features you want, I'm going to throw you out on the street.”
Tell Engineers the Problem, Not the Features
From Trillion Dollar Coach: The Leadership Playbook of Silicon Valley’s Bill Campbell (Schmidt, Rosenberg, and Eagle, HarperBusiness, 2019). Campbell coached Steve Jobs through the Apple turnaround, Eric Schmidt, Larry Page, Jeff Bezos, Sheryl Sandberg, and many others, and never wrote a book himself. The volume that captures his principles was assembled posthumously by three Google executives he had coached, drawing on interviews with more than eighty people he had worked with, three years after his death from cancer in April 2016. The line itself is from his Intuit years in the mid-1990s, when he was CEO and the company was expanding into banking. A newly hired product manager handed his engineering team a feature list; Campbell, witnessing the meeting, finished the rebuke with: “You tell them what problem the consumer has. You give them context on who the consumer is. Then let them figure out the features.”
The instruction sits inside a long product-management tradition: Clayton Christensen’s “Jobs to Be Done,” Marty Cagan’s “missionaries, not mercenaries” framing already in this collection, the broader discovery-driven approach. A feature list is a hypothesis about a solution, and handing it to engineers as a spec closes off the search before they have the context to widen it. Engineers given a problem can find a better solution than the one the PM walked in with. Engineers given a feature list can only ship it.
What makes Campbell’s version distinctive is the threat. Most writing on this principle is polite. Campbell ran the room: do this once and you are out. Without an enforcer, the default reverts to feature lists within a quarter, because they are easier to write and easier to manage against.