Back to homepage

Our favourite eggs to break · 03

Product strategy & roadmap reset.

A full roadmap feels like progress. But when the busiest teams are shipping features customers didn't ask for, while the deals that matter keep stalling on the same gaps, the roadmap has become a list of commitments rather than a strategy.

Sound familiar?

  • A roadmap shaped by whoever shouted loudest last quarter: a big customer, a sales escalation, a competitor's launch.
  • Lots of delivery activity, but little measurable change in adoption, retention or win rates.
  • Features nobody can bring themselves to retire, each with a small but vocal set of users.
  • Product and sales telling different stories about what's coming and why.
  • Engineering capacity consumed by keeping old commitments alive rather than building what's next.
  • A product strategy document that exists, but doesn't actually change any decisions.

Why it happens

Enterprise software is especially prone to this. Large customers carry real weight, every deal comes with requests attached, and saying “no” feels like losing revenue. Over time the roadmap fills with promises, and the product drifts towards being a collection of features rather than a coherent answer to a problem.

Stopping work is the hardest egg to break. Every item on the roadmap has a sponsor, and questioning it means a difficult conversation. So the list keeps growing, and the team's focus keeps thinning.

What it's really costing you

  • Engineering effort spent on work that doesn't move the business forward.
  • Slower progress on the capabilities that would actually win and keep customers.
  • Growing complexity that makes the product harder to sell, support and change.
  • A team that's busy but losing confidence in where the product is going.

How we break this egg

  1. Get close to the customer again

    Talk to customers, prospects, sales and support to understand the problems people are really paying to solve, not just the features they request.

  2. Look hard at the portfolio

    Review what's being built and maintained against the value it creates, and surface the work that should stop, shrink or change direction.

  3. Make the trade-offs explicit

    Turn priorities into clear choices with the reasoning attached, so leadership, sales and engineering can see what's in, what's out, and why.

  4. Reset and embed the roadmap

    Rebuild the roadmap around outcomes, and put a lightweight discovery and prioritisation rhythm in place so it stays honest.

Tell us about your egg.

What's stuck, and what's been “done that way” for too long? We'll come back to you within one working day.