About This Episode
Lindsey Jayne spent 15 years moving through startups, scaleups, and ultimately the Financial Times, where she served as chief product officer. She started her career at the Government Digital Service — stumbling into product management, she says, by chasing someone down a corridor holding a MacBook that actually worked. She now works as an independent product adviser and coach, and she brings a rare combination of practitioner instinct and structural rigour to the conversation.
This episode is anchored in the defining tension of product management: accountability without authority. Product managers are responsible for outcomes they don't control. They can't make an engineer, a lawyer, or a sales team do anything — and the gap between what they're answerable for and what they can actually command is a primary source of burnout across the profession. Lindsey argues that the solution is not to close that gap through force but to navigate it through influence, and that the skills product managers already use with customers — curiosity, empathy, not assuming you know the answer — apply equally well to the stakeholders around them.
She also speaks frankly about what it looks like to lead a product function at a large, complex institution: establishing a board reporting cadence at the FT where none existed before, running product reviews borrowed from design critique to keep leaders connected to the work without running it themselves, and distinguishing between enthusiasm that is sustainable and enthusiasm that is quietly burning someone down. And on the question of landing a product — getting the people who matter to actually understand what has been built and why — she offers one of the episode's sharpest tests: if a junior user researcher a few weeks into the job cannot articulate the strategy, it isn't a strategy yet.
The conversation closes with something rarely discussed: how to tell your story clearly after a difficult exit, a toxic organisation, or a role that didn't go to plan. Lindsey's advice is practical and grounded, drawn from the coaching work she now does with product leaders at every stage of their careers.
Chapters
Key Takeaways
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. The friction it generates is a primary source of burnout across the profession.
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?
When Lindsey 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.
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. The matrix makes those decisions explicit rather than intuitive.
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 — and it falls to the leader to notice it before the person themselves does.
The format asks teams to bring a problem and work in progress — not a finished outcome — to a cross-functional leadership group. The group's job is to ask what options were rejected, what else might be tested, who else should be in the conversation. It keeps leaders connected to substance without the overhead of running the work.
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.
