Technical founders often build software that is architecturally elegant and commercially irrelevant. The instinct to solve interesting engineering problems is a strength in engineering teams and a liability in product teams. Learning to think in outcomes — what does the customer achieve, not what does the software do — is the most important mental shift a technical founder can make.
Jobs to Be Done: The Right Unit of Analysis
The Jobs-to-Be-Done (JTBD) framework, popularised by Clayton Christensen, reframes product development around the progress a customer is trying to make in their life or work — not the features they request. When a hospital administrator asks for "a better search function," the job they are hired to do is "find the right patient record before the doctor enters the room." These are different problems with very different solutions. JTBD forces you to ask "why" repeatedly until you reach the underlying motivation, which is where differentiation actually lives.
Outcome-Driven Roadmaps
A feature roadmap answers "what are we building?" An outcome-driven roadmap answers "what should be measurably true after we ship?" Instead of listing features, define desired outcomes ("reduce time-to-diagnosis by 30%") and then identify the smallest set of features that would produce that outcome. This changes the conversation from scope estimation to experiment design — and it gives engineers the context they need to make better technical decisions autonomously.
The best product leaders I have worked with never ask "can we build this?" They ask "if we build this perfectly, does the business meaningfully improve?" Those are very different questions.
Discovery as a Practice
Product thinking is not a one-time exercise — it is a continuous discipline. Schedule weekly customer interviews. Not usability tests, not surveys — actual conversations about the problems customers are struggling with right now. Keep a shared insight repository where engineers and designers can read raw interview notes. When the whole team understands customer problems at a visceral level, product quality improves without additional process overhead.
