Kevin Systrom, 2011

“The hard part is actually finding the problem to solve.”

Kevin Systrom explained this lesson in a 2011 Stanford eCorner conversation about Instagram’s beginnings. He and Mike Krieger wrote down the problems people experienced with mobile photos before narrowing their product to a simple solution. Teams often become attached to a capability, algorithm, or feature before proving that the underlying problem is frequent and meaningful. Problem discovery demands contact with behavior, competing alternatives, and the context in which a customer decides whether change is worth the effort. The business value of the line appears when it changes a real decision. It directs attention toward assumptions that routine can hide and invites a team to examine the system behind an outcome instead of treating the visible result as a complete explanation.

Founders can interview and observe users, rank problems by frequency and consequence, and test a narrow promise before building infrastructure. A good problem statement names the person, situation, obstacle, and current workaround without smuggling the preferred solution into the description. Application therefore requires an explicit mechanism: what should people do differently, what signal should move, and when will the team examine the result? Writing those elements down turns general agreement into a testable management practice.

Customers may describe symptoms rather than causes, and a large complaint does not guarantee a viable market. Discovery should examine willingness to switch or pay, distribution, regulation, and whether solving the problem creates harms or burdens elsewhere. Context matters because an idea that improves one situation can create harm in another. Leaders need boundaries, dissent, representative evidence, and a way to correct course. Accountability cannot be delegated to the quotation or the tool used to implement it.

AI makes solution production fast, which increases the danger of building impressive answers to weak questions. Teams that invest in problem selection, proprietary insight, and direct evidence can use rapid generation as leverage instead of mistaking output volume for product value. Before the next build cycle, ask the team to present three observed problems and the evidence for each, then choose the experiment that tests demand with the least irreversible work. The review should preserve what was known when the choice was made, document what changed, and share the learning beyond one team. Repeated with discipline, that cycle converts a memorable sentence into better judgment rather than another short-lived management theme. It also makes the cost of assumptions visible, allowing future teams to reuse proven knowledge while recognizing the point at which a different customer, risk, or operating environment requires fresh testing.