Chapter 18 · Part 5: Growth

The Integrated Playbook

“Plans are worthless, but planning is everything.”

— Dwight D. Eisenhower

Three years later

Three years after her first Monday on the train, Maya Smith sat in the same quarterly business review with Ambermoor Health that had been on her overnight digest that first morning. The meeting was different now.

Ambermoor’s chief nursing officer opened with her own numbers: the share of high-risk patients with a confirmed owner within 24 hours had held above 85 percent for a year across seven hospitals. Missed first follow-ups had fallen. The finance team had used Brindlepath’s outcome report to show the board what avoided readmissions were worth. The navigators, she said, no longer spent their mornings on the phone trying to find out who owned whom.

Then she asked about the future. Could the discharge-plan drafts cover more patients? Could specialist offices see the handoff too? Could Brindlepath help with the health plan’s members as well as the hospital’s patients?

None of those questions was answered by a single feature, a single framework or a single chapter of this book. Each one touched the problem worth solving, the strategy and positioning, the numbers, the team, trust, customers, partnerships and AI. That is the nature of product leadership: the pieces only work when they work together.

This last chapter pulls the playbook into one picture, offers a practical rhythm for running it, and closes with some thoughts about the job.

One system, not seventeen chapters

Each chapter of this book covers one part of the work. In practice, they form a single system, where decisions in one area shape every other.

Some of the connections Brindlepath lived through:

  • The problem shapes the business. Choosing post-discharge ownership over scheduling (Chapter 2) made a value-based price possible (Chapter 6), because the value was measurable in avoided readmissions.
  • Strategy shapes the team. The not-doing list (Chapter 4) freed a third of engineering capacity, which funded the reliability work (Chapter 5) and the integration platform (Chapter 7).
  • Economics shape the product. Discovering that custom integrations made small customers unprofitable (Chapter 6) led to the standard connector (Chapter 16), which made partnerships possible (Chapter 15).
  • Trust opens markets. Treating security and accessibility as product requirements (Chapter 11) shortened every sales cycle that followed (Chapter 13).
  • Customers close the loop. A customer success manager’s early warning (Chapter 14) revealed a data problem that became a product fix, and a renewal became an expansion.
  • AI raises the stakes on everything. The discharge-plan agent (Chapter 17) depended on the integrations, the evaluation discipline, the trust practices and the team habits built over the previous three years.

When you face a decision, ask which other parts of the system it touches. Most product mistakes come from optimizing one part while ignoring the rest.

The four pillars, revisited

Chapter 1 described four pillars of product leadership. Looking back, each runs through the whole playbook.

Market understanding is not a phase. It begins with problem discovery and continues through every customer conversation, field visit, cohort analysis and renewal.

Financial insight is not a budget exercise. It informs which problems to solve, how to price, what to build, how to scale and which partnerships to pursue.

Customer-centered innovation is not a design department. It is the habit of every team member who watches users work and measures whether the product actually helped.

Trust and responsibility is not a compliance review. It is built into every requirement, every release, every AI feature and every partnership.

A product leader strong in all four, and able to connect them, is rare and valuable. Most of us are stronger in some than others. Know your weakest pillar and work on it deliberately, or hire people who are strong where you are not.

An operating rhythm

Frameworks are only useful if they are used regularly. The following rhythm, adapted from what worked at Brindlepath and in teams I have led, puts the playbook into practice.

Weekly. Customer conversations for every product trio. Review of input metrics and health scores. Team planning and decision log updates. Thirty minutes of customer feedback review with customer success.

Monthly. Product review of outcomes against the roadmap. Review of AI feature quality and cost. Partner integration health check. A field visit for at least one trio.

Quarterly. Roadmap and capacity allocation review. Portfolio review with stage-appropriate measures. Business reviews with key customers. Launch reviews for anything released in the quarter. Retrospective on how the team is working.

Yearly. Strategy refresh: diagnosis, guiding policy, actions and the not-doing list. Vision check. Pricing and packaging review. Horizon allocation for the year ahead.

The rhythm matters more than the exact meetings. Without it, urgent work crowds out important work, and strategy becomes something you write once a year and forget.

Your first 90 days as a product leader

Many readers will use this book when starting a new product role. A practical plan for the first 90 days, drawn from Maya’s experience and my own:

Days 1 to 30: listen and learn.

  • Meet every member of the product, design and engineering teams one to one.
  • Talk to at least ten customers, including some who left or said no.
  • Spend time where the product is used, as Lena did in Chapter 12.
  • Learn the numbers: revenue, margin, retention, cost to serve, as in Chapter 6.
  • Read the existing strategy, roadmap and backlog, and the last year of decisions, if anyone wrote them down.
  • Change very little.

Days 31 to 60: diagnose and align.

  • Write your diagnosis: what is working, what is not, and the hardest problem the product faces.
  • Test it with the leadership team, the product team and a few trusted customers.
  • Identify one or two quick wins that demonstrate progress and build trust.
  • Clean up the backlog, as Maya did in Chapter 5.

Days 61 to 90: decide and communicate.

  • Write the one-page strategy, including the not-doing list.
  • Agree on the North Star and input metrics.
  • Rebuild the roadmap around outcomes.
  • Set the operating rhythm.
  • Tell the story, repeatedly.

Common mistakes

Optimizing one part of the system. A brilliant feature that the economics cannot support, or a strong strategy that the team cannot deliver, fails just as surely as a weak one.

Collecting frameworks. Frameworks help only when they are used regularly, by the whole team, to make real decisions. A rhythm matters more than a library.

Changing everything in the first month. New leaders who reorganize, rewrite the strategy and rebuild the roadmap before they understand the product lose the trust they need later.

Forgetting to look at the results. Plans are useful; results are what count. Build the habit of checking whether what you did made the difference you expected.

The job, honestly

Product leadership is a strange job. You are accountable for outcomes you cannot directly control. You have authority over very little and influence over almost everything. You are expected to be right about the future while knowing that much of what you believe is wrong. You spend your days choosing what not to do, and disappointing someone with almost every choice.

It is also one of the best jobs in business. You get to understand people’s problems deeply, assemble talented teams to solve them, and see the results in the lives of the people you serve. In healthcare, that can mean a patient who gets the call she needed, from a navigator who knew she was his, because a team made a hundred careful decisions about how that should work.

AI will keep changing how the work is done. Agents will take on more of the gathering, drafting, analyzing and monitoring. The tools in this book will evolve. But the core of the job, understanding people, choosing well, building trust and owning the outcome, will remain human for a long time. The best product leaders of the next decade will be the ones who use every tool available to do that core job better, and never confuse the tools with the job.

I hope this playbook helps you do it.

Final checklist