Problems not Solutions
Build shared clarity around the customer, context, and progress worth making before settling on an answer.
Ask: What problem is worth solving, and for whom?
THINKING IN PRODUCT
A practical method for operational leaders and their teams to connect customer needs, strategic choices, learning, and delivery.
Build a system that turns ideas into success, concepts into cash, emergence into value
Explore the methodFor leaders taking responsibility for enduring product outcomes.
Set direction and make trade-offs.
Reduce uncertainty with evidence.
Create value, learn, and improve the flow.
THE WHOLE SYSTEM
Customers, teams, leaders, and partners shape the value a product can create.
Thinking in Product connects six shifts in judgment with three areas of practice. Leaders use the method to set direction, learn before costly commitments, and keep value moving through the whole system.
It brings established ideas from Design Thinking, Lean Startup, and Agile practice into a shared conversation without claiming those ideas as its own.
“Did we ship what we planned?”
“Did we make things better?”
SIX THINKING SHIFTS
These shifts guide how leaders and teams frame problems, make choices, learn, and adapt.
Build shared clarity around the customer, context, and progress worth making before settling on an answer.
Ask: What problem is worth solving, and for whom?
Connect strategy to observable change. Use desired outcomes to guide decisions and measures.
Ask: What needs to become meaningfully different?
Make assumptions visible, test what matters, and adjust before commitment becomes expensive.
Ask: What must be true, and how can we learn?
Make the cost of choice visible. Protect important work and defer what cannot receive attention now.
Ask: What will we reconsider, defer, or protect?
See customers, teams, channels, technology, economics, dependencies, and decisions as a connected system.
Ask: Where does value flow, and where does it stall?
Use repeated delivery, measurement, feedback, and adaptation to sustain value beyond launch.
Ask: What is the smallest useful next move?
THREE CONNECTED PRACTICE AREAS
The method is applied as one system. The techniques below are examples to choose from as the challenge demands.
Set direction, align stakeholders, and make explicit trade-offs.
Frame the problem and reduce uncertainty before investing heavily.
Coordinate teams, visualize work, and improve through feedback.
A QUESTION TO TAKE TO YOUR NEXT TEAM CONVERSATION
Start there. Then decide how you would know.
PRODUCT THINKING IS A TEAM PRACTICE
Better product decisions need leaders and teams who understand their responsibilities, work across boundaries, and stay accountable for outcomes.
Make strategic intent clear, resolve competing priorities and dependencies, and create the conditions for teams to take ownership.
Connect the product goal to the next decision. Bring customer insight, make priorities clear, and stay accountable for value over time.
Bring different skills to a shared problem. Explore solutions together, deliver in small increments, and learn from real feedback.
CO-CREATORS
Thinking in Product
Ewan O’Leary and Tanner Wortham co-created Thinking in Product for operational leaders, product owners, and teams learning to turn ideas into lasting value.
Tanner’s website · worth.amThe Thinking in Product baseline is by Tealshift LLC and Wortham, LLC and licensed under CC BY-NC-ND 4.0. It draws on established ideas including Design Thinking, Lean Startup, MVPs, Build-Measure-Learn, Agile, Scrum, Kanban, work-in-progress limits, and product operating models; those ideas remain with their respective originators.
LET’S START WITH YOUR CONTEXT
Thinking in Product is the method. Workshops, coaching, team kickoffs, and leadership forums are ways to apply it to your real challenges.