Product Model · Reading List

3 books that explain
why the product model works

Moving from a feature factory to an empowered product organisation isn't just a process change — it's a different way of thinking about teams, discovery, and delivery. These three books form the intellectual foundation.

Team Topologies Transformed Continuous Discovery Habits
🏗️
Structure your teams right Team Topologies shows how to organise for fast flow
🎯
Give teams real ownership Transformed explains the product operating model
🔁
Make discovery a daily habit Continuous Discovery Habits turns it into practice
01 — Team Design
Team Topologies
Matthew Skelton & Manuel Pais
How you structure your teams determines what software you can build — and how fast you can build it.
Key Ideas
1
Conway's Law is a design tool
Your architecture mirrors your org chart — always. Use this intentionally: design your team structure to produce the architecture you want.
2
Cognitive load sets team boundaries
Each team can only effectively own what fits its cognitive capacity. Overloaded teams slow down and produce poor quality — split the domain, not the effort.
3
Stream-aligned teams are the default
Most teams should be aligned to a flow of business value. Everything else — platform, enabling, subsystem teams — exists only to serve them.
Core Framework
The 4 Team Types
Every team in your org should map to one of these four — no exceptions.
1
Stream-aligned: owns a product or service flow end-to-end
2
Platform: reduces cognitive load for stream teams
3
Enabling: temporarily upskills other teams
4
Complicated subsystem: manages specialist complexity
"Organisations should be designed for adaptability and flow, not for static efficiency."
02 — Product Model
Transformed
Marty Cagan
The definitive guide to what a real product organisation looks like — and how to get there from where most companies are today.
Key Ideas
1
Feature teams vs. product teams
Feature factories execute stakeholder requests. Real product teams own the problem — not the backlog. The difference is accountability for outcomes.
2
Outcome over output
Shipping features is not progress. The measure that matters is whether those features change behaviour and move business metrics.
3
The transformation starts at the top
No team can operate in a product model if leadership still thinks in roadmaps. Executives must change how they fund, direct, and evaluate product work.
Core Framework
The Four Product Risks
Every solution must pass four tests before it's worth building.
1
Value: will customers actually choose this?
2
Usability: can they figure it out on their own?
3
Feasibility: can the team build it today?
4
Viability: does it work for our business?
"The best product companies don't build what stakeholders ask for. They solve the problems stakeholders care about."
03 — Continuous Discovery
Continuous Discovery Habits
Teresa Torres
Knowing you should talk to customers is easy. Building the weekly habit that makes discovery a team sport — that's what this book teaches.
Key Ideas
1
Discovery is a team habit, not a phase
Quarterly user research is too slow and too late. Talking to customers weekly — every week — keeps the whole team grounded in real human problems.
2
Opportunities, not solutions
Most teams jump from business outcome straight to solutions. The Opportunity Solution Tree forces you to map the problem space first, then explore solutions.
3
Test assumptions, not ideas
Every solution rests on a stack of assumptions. Identify the riskiest one, design the cheapest possible test, and run it before writing a single line of code.
Core Framework
The Opportunity Solution Tree
A visual map that connects desired outcomes to the opportunities and solutions that serve them.
1
Outcome: the business metric the team owns
2
Opportunities: customer needs, pains, and desires
3
Solutions: ideas that address the opportunity
4
Experiments: the fastest way to test each solution
"If we want to build products that create value for our customers, we need to develop the habit of continuous discovery."

Ready to make the shift?

These three books, read together, give your team a shared language and a clear picture of what good looks like. Start with Transformed for the why, Team Topologies for the structure, and Continuous Discovery Habits for the daily practice.