Slow time to market

It takes months to get from idea to release

Slow time to market shows up at release, when a feature arrives late, but it builds up along the whole path: in the approvals before a line is written, in the hand-offs between teams, in releases grouped into big batches. One wait creates another, because work waiting for another team lands in the next batch, and a bigger batch waits longer.

Book a call

Does this sound familiar?

  • A feature reaches users after the reason we asked for it has already changed.
  • The code has been ready for days and is waiting for a review, a test round or the next release window.
  • Before anyone writes a line, the idea goes through several approvals and sits in the backlog.
  • A small change stays in the queue because it has to find room in another team’s plan.
  • Competitors get to similar features first, even though our team is no smaller than theirs.

Where does the time between idea and release come from?

Coupled code forces teams to pass features to each other and to group releases. The waits before any code is written have a cause of their own, and they are the easiest to overlook.

  1. Work waits before it even starts

    Part of the delay builds up before a line is written: the idea waits for a decision, an approval, a place in the backlog. It doesn’t show in development measures, and that is exactly where it is worth starting to measure.

  2. You release rarely, in big batches

    A feature that goes out all at once waits for the last of its parts to be finished, and picks up risk and coordination with every extra week. A feature delivered in increments, each already in production, shortens the wait and brings forward feedback from users.

  3. Every feature crosses several teams

    If teams are divided by technology or by component, a feature changes hands several times and at each hand-off waits until the other team has time. To avoid coordinating too often you end up grouping releases, while teams organised around parts of the product can take a feature through on their own.

  4. The code has no boundaries that hold

    When the parts of the system depend on each other, even a small change touches other teams’ code and forces a joint release. Until the boundaries of the code and those of the teams coincide, moving people around leaves the waits where they are.

What changes when work flows from idea to release

A feature goes out in small pieces, each already in production, and whoever asked for it sees the first result while the rest is under way. The team knows where work stops because it measures it, and discusses it with data in hand.

Responding to a competitor or a customer request becomes a choice you make when needed, and the next step is decided by watching how users use what has just shipped. The team gets faster without working any harder, because the path is shorter.

Let’s start with a feature that arrived late

We retrace that feature’s route from idea to release with you, and mark the points where it waited.

We use your data to respond to your request. Read our Privacy Policy.