From Delivery to Product Leadership: Six lessons I wish I’d learned sooner

A few years ago, I traded delivery plans and burndown charts for product vision, discovery, and P&L ownership. I assumed it would be all strategy and big ideas. It wasn’t. It’s influence, ambiguity, and saying “no” - often.

Today I lead a product and a cross-functional team. None of it came from a slide deck, it came from messy, real-world practice. Here are six lessons I wish I’d learned sooner.

Lesson 1 - Your job isn’t great ideas

I used to think Product Management was about having great ideas. They knew the market, the clients, the competitors so obviously they knew what to build. They were my one-stop shop for requirements.

Spoiler alert: Product leadership is not “be brilliant on demand.” It’s “be ruthless about which bets deserve oxygen.”

The power of no

Great ideas are plentiful, capacity isn’t. Most of the job is saying no to good ideas. You’ll never have enough people, time, or runway. Inputs will flood in from customers, support, sales, execs, and your own team. The question isn’t “Is it good?” It’s “Does it advance the strategy and the metric now?”

Data beats dopamine

“Customers will love it” isn’t a prioritisation criterion. Love matters, but so do activation, adoption, onboarding drop-offs, retention, expansion, time to value, conversion (especially in freemium), NPS, revenue, and cost-to-serve. Often the right move is a boring improvement that quietly moves the number.

Keep it tied to business goals. Choose the metric that matters. Write testable hypotheses. Validate (or kill) fast and cheap. Start by trying to break the idea. If it survives, earn the right to invest.

Deliver the smallest version that kills the core problem, then make it pretty. Speed plus learning beats polish without proof.

Pro tip: Keep a living Not Now List. It’s not a graveyard, it’s a guardrail. When a shiny “quick win” appears, compare it against what you’ve already deprioritised. If it won’t move the metric more than what’s on deck, pass. Spoiler: it’s never as quick as it looks.

“Product leadership is not ‘be brilliant on demand.’ It’s ‘be ruthless about which bets deserve oxygen.’”

Piotr Opałacz, Head of Product @ Lenvi

Lesson 2 - Deadlines aren’t the enemy. Misalignment is.

Planning is my home turf - scope, timelines, risks. So I pointed that engine at strategy. I ran discovery, lined up the vision, mapped users and competitors, wrote the hypotheses, tested them, and picked a direction.

The ambush meeting

Then I polished the deck and unveiled it in a Big Meeting. Cue the tackle. Senior stakeholders bring their own incentives and agendas. Strategy will never feel as “objective” as a delivery plan, everyone has an opinion. Suddenly there are competing objectives, I’m defending my work, and misalignment has already landed.

The suspicious easy yes

Worse than tackle? A frictionless yes. If leadership waves it through, either I’ve cracked a miracle or no one’s really engaged. Misalignment bites later.

Pre-wire instead

Work offline with the right stakeholders while the plan is still forming. Ask for input early. Let them co-author, not judge from the jury box. Do the same with the team - formal buy-in may be optional; practical buy-in isn’t.

Lesson 3 - Strategy isn’t a slide deck, It’s a daily habit

I finally won buy-in from senior stakeholders and the team. Strategy approved. Presented. Two weeks later a teammate said they didn’t know what the strategy was. How? They were in the room. They listened. They weren’t the problem - my format was. The truth: I was living the strategy, they were living the sprint.

The penny dropped: you can’t expect people to memorise a deck. They have to feel the strategy in how we work. Re-running the presentation isn’t the fix. It’s like company values, printing them on a wall and quizzing people once a year won’t make them real. People copy what leaders do, not what leaders say.

Keep referencing the strategy in the work. New feature on the roadmap? State which outcome it moves and how we’ll know. Killing a feature after hypothesis validation? Show the evidence and the metric it failed to shift.

Say no with alignment, not attitude

You’ll say “no” more than you think. When a strong idea doesn’t fit, say: “If our strategy were X, this would be first in line. It isn’t, so it’s Not Now.”

Let consistency do the heavy lifting

Do this consistently, and the team and execs will start narrating the strategy back to you. Trade-offs get easier. “You changed priorities again” turns into “Glad we found a better path and skipped the noise.” That’s strategy moving from slide to habit.

Lesson 4 - Celebrate impact, not feature releases.

Inspiring slides about outcomes feel great - for you. For the team, they’re background noise. They won’t change how the team works. Action will.

Stop celebrating the launch

We finally ship a shiny feature, it hits production, hands slap for high-fives. Premature. That ritual teaches “the job ends at release”. Later telling people the metrics moved (or didn’t) is too late - the reward was already paid out at “feature delivered”. That hardens the belief that their job is to build features and mine is to have ideas.

Celebrate the result

You don’t celebrate picking lottery numbers or buying the ticket. You wait to see if it wins: Do the same with product: we cheer when activation climbs, onboarding drop-offs fall, conversion nudges up, retention holds, NPS lifts, or cost-to-serve drops. Not before.

Switch the ceremony. Praise the smallest shippable that proves (or kills) a hypothesis. Read the scoreboard together. When we tie applause to outcomes, the team plays to score - not just to ship. Change what you celebrate and you change the game. Now the whole team plays to win, not just to release.

Lesson 5 - P&L plays by different rules in product

In projects, you log time, invoice, move on. In product, the lens is team utilisation over time and whether that spend translates into value. You generated £1m on project work that cost you half of it last year? Great - until you realise you spent more than £1m on the team doing those projects. Idle capacity and context switching are real costs. A portfolio can look healthy on paper, but if unallocated time didn’t move product outcomes, you’re losing money.

The bespoke money trap

The big trap in B2B, a big client waves a fat cheque for a custom feature. Who can resist? Project P&L smiles, Product P&L cries. You ship Franken-features that slow future delivery and make the product harder to sell. Opportunity cost is the kicker: you booked revenue, but you also missed prospects or expansions because you deprioritised core capabilities.

Rule of thumb: if the request aligns with strategy or is already on the roadmap consider bringing it forward as a funded bet. If it’s off-strategy, say no.

Don’t fear the “no”

Worried about upsetting a customer? Shipping a one-off may make someone happy now, but people change on the client side. That custom becomes maintenance debt when new stakeholders expect market-standard features. If it doesn’t fit the strategy, it won’t age well. Protect the product.

Kill “requirements”, find the problem

Say “yes,” and you’re on a bumpy road to the next trap: “requirements.” Don’t mistake them for the problem statement - they’re usually a proposed solution, often shaped by an overcomplicated process. Step back. Identify the real problem, then design the simplest, most universal product-level solution - one that other customers can use and that won’t complicate future enhancements.

Lesson 6 - Making the jump (If you’re in delivery Today)

Want the product path? Act like product before the title. Startups and scale-ups are easier: blurry boundaries, too much work, not enough people. Enterprises play by different rules: earn your way in, then stick.

Eat your own dog food

Use the product. If it’s B2C, become a customer and try a competitor for contrast. If it’s B2B or niche, get a demo environment and do the jobs-to-be-done. Learn the problem it solves and the benefits it creates. Opinions earn weight when they’re grounded in clicks, not decks.

Sit where product decisions happen

Backlog refinement, triage, sales calls, discovery sessions - the good stuff. Ask “what outcome are we buying?” not just “what’s the estimate?”. In B2B, listen in on sales calls and discovery/implementation sessions; they’re gold for understanding real requirements (and for spotting bespoke traps).

Bring market signal

Ask how competitive analysis is done and offer support. There’s never enough. If it’s missing automation, set up simple AI-powered monitoring for competitor moves and industry news.

Follow the money

Think like an entrepreneur, not a project manager. Get close to Product P&L (not just project/portfolio P&L) to see how the business actually works.

Speak outcomes, not ceremonies

Stakeholders don’t care about Agile rituals, they care about results. Talk hypotheses, efficient experiments, benefits realisation, and measurable improvements. Shipping impact > being 100% Scrum-Guide aligned.

Get your foot in the door

Build a reputation for being product-focused. Cover for someone on holiday, take the “close to product” role on a new project, help elicit real product requirements. You may slide into a hybrid role and be first in line when a product opening appears.

Pro tip: make your intent known. Build relationships with the product team. Don’t play the know-it-all. Don’t teach - support. That’s the difference between “here they go again” and “loop them in - they’re a huge help”.