How to build resilience in product - Lindsey Jayne (Product Advisor)

Lindsey Jayne is an independent product adviser and coach, and former chief product officer at the Financial Times. She began her career at the Government Digital Service, where she stumbled into product management by chasing someone down a corridor holding a MacBook that actually worked. What followed was 15 years moving through startups, scaleups, and ultimately one of Britain's most storied media institutions.

We discuss:
— Why product managers burn out — and why accountability without authority is at the root of it
— How to apply discovery skills not just to customers but to the stakeholders around you
— The influence/interest framework for stakeholder mapping and why it matters more than you think
— How to spot burnout signals in your team, including the ones driven by passion rather than pressure
— When and how to shift from individual contributor to product leader without losing touch with the work
— The product review as a format for cross-team problem solving borrowed from design critique
— What it really means to land a product — and why half the job is communication, not shipping
— How to tell a compelling story after a difficult company exit or a role that didn't go to plan

Chapters
00:00 — Introduction
01:08 — Lindsey's origin story: from a broken government laptop to product management
02:48 — Why product managers burn out: accountability without authority
05:34 — Influencing stakeholders using discovery skills
07:19 — What leaders can do to clear the way for their product teams
08:44 — Stakeholder mapping: the influence and interest framework
09:41 — Recognising burnout signals in your team at scale
11:16 — Balancing passion and sustainability: when enthusiasm becomes a pattern
14:16 — When to transition from individual contributor to product leader
16:24 — Product reviews and cross-team knowledge sharing
18:42 — How to communicate effectively with senior stakeholders
20:40 — Career-defining advice: you don't have to die on every hill
21:43 — Half your job is landing the product, not just building it
22:25 — The most common mistake junior product managers make
24:05 — How to tell your story after a difficult or toxic company exit


Key takeaways
— Accountability without authority is the defining tension of product management. Product managers are responsible for outcomes they cannot control directly. They cannot make an engineer, a lawyer, or a sales team behave in a particular way — and nor should they. Managing that gap through influence, not command, is the core skill, and the friction it generates is a primary source of burnout across the profession.
— Apply discovery to your stakeholders, not just your customers. The tools product managers use to understand users — curiosity, empathy, not assuming you already know the answer — work just as well on the people around you internally. Before trying to get someone on board with an idea, understand what is on their table. What were the three things in their diary before they met you?
— Demonstrate results consistently and in plain language. When Lindsay joined the Financial Times, the product team had never updated the board. Her first move was to establish a regular cadence: this is what we said we would do, this is what we did, what do you need? Done repeatedly, it builds the credibility that creates space for product work to happen.
— The influence/interest matrix is a practical tool for communication decisions. High influence, low interest is the most dangerous quadrant — someone who could sideswipe your work entirely but is not paying attention to it. Knowing where stakeholders sit determines what they need to know and how often.
— Sustainable enthusiasm looks different from burnout-driven overwork. It is fine for someone to be so excited about a piece of work that they cannot put the laptop down. It is a problem if that becomes a consistent pattern. The signal to watch for is whether the intensity is a burst or a rhythm.
— The product review borrows the best of design critique. Borrowed from design, the format asks teams to bring a problem and work in progress — not a finished outcome — to a cross-functional leadership group. The job of the group is to ask what options were rejected, what else might be tested, who else should be in the conversation. It keeps leaders connected to the substance of the work without the overhead of running it.
— Half the job is landing the product, not shipping it. A product is not done until the people who matter understand what has been built and why. Strategy exists only when a junior user researcher a few weeks into the job can articulate it clearly. Until then, it is not strategy — it is an internal document.