You cannot be neutral about your own roadmap

The portal worked. The agreement about it did not

An 8 to 10 week sprint, September 2025. A €5B global machinery company. One senior analyst and two analysts, 20+ stakeholder interviews and 3 workshops. Capability: Customer Experience.

The client had launched a customer portal to streamline project delivery, and adoption stayed limited. Three causes sat behind that: an unclear vision, fragmented stakeholder input, and no structured prioritization.

This was not a software fault. The portal ran. What was missing was an agreed answer to what the portal was for, and that gap reached the customer as fragmented communication, especially about new features. A customer who is told three different things about one portal by three teams learns to wait and see.

Internal teams were at full capacity, with no bandwidth to consolidate feedback or align around shared goals. Left alone, the client faced slow adoption, low customer buy in, and missed opportunities to scale digital project delivery.

Everyone was right, and that was the problem

A €5B machinery company knows its customers and its own portal better than we do. It employs product managers, digital leads and customer teams who have worked on this for years. Domain knowledge was not the gap. On this engagement we brought none the client did not already hold.

Capacity was part of the problem, but capacity alone does not explain a stall of this kind, because the missing pieces were not hard to find. They sat with people who would have given them to anyone who asked.

The harder half is that every group holding a piece also held a stake. Product, digital and the customer teams each had a reasonable view of what the portal should do next, and each view carried consequences for that group's own plan. Consolidating those views is an arbitration rather than a research task, and nobody with a stake in the outcome can run one, however senior they are and however fairly they mean to behave. A ranking produced inside one of the three groups reads as that group's position whatever evidence sits behind it, and the other two read it that way at once.

So the honest answer to "why did we not do this ourselves" is that on the content they could have, and in a sense they did. Every fact in the result came from their own people and their own customers. What internal time and seniority do not produce is a party with nothing to win from which feature goes first.

A disagreement became a decision with a basis

What that enables. The client can hold a feature argument against two written tests instead of against seniority, and a group that loses a round can see why it lost. That is what makes a roadmap survive its first month. It can also tell its customers one story about the portal, which it could not do before.

The client's own summary, from the VP, Project Management: "The team helped us cut through internal uncertainty and build a more customer-driven view of what the portal should become".

One figure is published here, and two are left out

One figure is published, with the qualifier the record carries. 5 critical challenge areas identified and prioritized. It counts what the sprint produced, so it reports a deliverable rather than an outcome.

Two further figures are left out. One states a percentage for faster alignment in portal feature decision making, the other a percentage for an efficiency gain in cross team collaboration. Neither carries a qualifier, and neither says what it was measured against. Faster than what, and measured when. A sprint that ends at an agreed roadmap has no before and after period to measure a decision speed across, so we cannot show either number. A percentage a reader cannot trace is worth less than the sentence explaining its absence.

Source. Every figure in this article comes from the SprintlyWorks engagement record for Accelerating Customer Portal Adoption and Alignment, a €5B global machinery company, September 2025, an 8 to 10 week sprint with 20+ stakeholder interviews and 3 workshops. Clients are described and never named. The consolidated map, the prioritized features and the 3 year roadmap are the scope the sprint was set to deliver, and are reported here as scope rather than as measured outcomes. Where a figure is identified or modelled rather than banked, this article says so.

Buy the room once, then hold it yourselves

We put one senior analyst and two analysts on one defined question for 8 to 10 weeks. You get the fieldwork, the analysis and the handover, and you keep the method, so the second time the question comes round you do not need us in the room.

If your teams each have a confident and different answer to what something is for, that is the shape of problem this sprint is for. Write to rahul.abhisek@sprintlyworks.com and we will tell you on the first call whether it is worth the time. If a sprint is the wrong instrument, we will say that instead.