11. Team-wide discovery

§The third pillar corrects a picture most founders carry without noticing: that discovery is something the product person does, alone, and reports back. It is not. Every seat in a company is a different window onto the same customer, and the view from any single window is partial.

§ 11.1What each slice sees#

§Engineers see two things nobody else can: what is technically possible that the customer would never think to ask for, and what is technically impossible that the customer assumes is trivial. Both are discovery findings. A model that can now do in a second what took a human an hour is an opportunity an engineer notices first. A feature that would need data the company cannot legally hold is a constraint an engineer notices first.

§Support hears the struggle in the customer's own words, before it has been translated into a feature request. The phrasing of a confused email is problem-space data of a purity no interview reaches, because the person was not trying to be helpful; they were trying to get something done and could not.

§Sales hears the objections and the comparisons: what the buyer is using now, why they hesitate, what they think the competitor does better. Half of Product Discovery's mature-market work happens in sales calls whether or not anyone writes it down.

§Designers notice patterns across users that any single user cannot see in themselves: the three people who all hesitated at the same screen, the workaround everyone invents independently.

§ 11.2Why the connection is the hard part#

§Marty Cagan and Teresa Torres both arrive at the product trio, a product person, a designer and an engineer doing discovery together, for exactly this reason: the slices only become insight when they meet. A finding from support that never reaches the engineer stays a complaint. An engineering observation that never reaches the person talking to customers stays a possibility. The trio is a structure for forcing the meeting.

§At a startup of one to five there is no trio and no need for one. The slices are in one or two heads. That is the advantage the original guide named directly: if you are a team of two or one, you already have all the insights; you just have to connect them. The founder who spent the morning in a sales call and the afternoon fixing a bug holds both windows. The question is whether they set the two views next to each other or file them separately.

§ 11.3Connecting them on purpose#

§Three habits do it. First, one place where everything lands: not a support tool and a sales tool and an engineering tool, but one document or channel where a customer's confused email, a lost deal's reason and an engineer's "we could actually do this now" sit in the same list. Second, a weekly moment when the owner reads that list looking for the pattern across slices, not within one. Third, the discipline of writing the connection down when it appears: "support says X, sales says Y, the engineer says Z is now possible, therefore." That sentence is discovery.

§ 11.4The solo founder's version#

§For one person, team-wide discovery means refusing to let the roles inside your own head stop talking to each other. The you that took the support call and the you that is about to write the prompt are the same person, and the whole advantage of that is lost if the call is forgotten by the time the prompt is written. Write it down. The same list, the same weekly read. One head, all the windows.

§Part III is done. Part IV turns from what holds discovery up to how the person doing it should think.