Updated 28 October 2026
Growth changes what a business asks of its teams. A product becomes a portfolio. A single channel becomes several. Customers expect the parts to work together, even when different teams built them.
The operating model can lag behind that change. Responsibilities, systems and decision rules that worked for one product become harder to use across several. Teams work hard, yet the customer experience becomes inconsistent and delivery commitments keep slipping.
Four patterns worth investigating
Tools multiply while work stays disconnected
A team buys software to solve a real problem. Another team does the same. Over time, customer information, reporting and workflows become fragmented. People compensate by copying data, reconciling records and negotiating handoffs.
The useful question is where the work breaks between tools and teams. Replacing every application is rarely a sensible starting assumption. Understand the information, ownership and connections the journey needs.
Ambition grows faster than capacity
Each product roadmap may look reasonable in isolation. Together, the roadmaps can depend on the same engineering specialists, designers, operations staff or decision-makers. Commitments compete for capacity that has already been allocated elsewhere.
Make those dependencies visible before promising another date. Leadership needs to decide what matters most, what can wait and which ongoing responsibilities must be protected.
The customer promise outruns operational support
A polished interface can make a request simple to start while leaving it difficult to fulfil. Customers experience the whole service, including support, exception handling and the transitions between products.
Trace the promise through to completion. Examine who receives the work, what information they need and what happens when the standard path fails. Customer experience and operating design need to inform the same decision.
People inherit a change they cannot use
New technology often changes responsibilities and expectations. If the decision rights, skills and measures remain unclear, people have to improvise. Apparent resistance may reflect a practical problem with the new way of working.
Include the people doing and supporting the work in the investigation. Give them clear responsibilities, appropriate support and a way to feed operational learning back into the design.
An illustrative example
Consider a business with two products, each with its own onboarding process. A customer using both must repeat information, and support teams cannot easily see where the customer is in the journey. Each product team has an onboarding improvement on its roadmap, drawing on the same small group of specialists.
This is an illustrative scenario, not a client case. Improving the two screens separately might leave the underlying problem untouched. The business needs to decide which information and capabilities should be shared, which product requirements are genuinely different, who owns the cross-product journey and how the work fits the available capacity.
Close the gap with a specific decision
Start with evidence about the customer or business consequence. Map the relevant work across boundaries, test the causes and distinguish useful variation from avoidable friction. Then agree the selected change, its owner and a sequence the business can absorb.
The 8S framework helps examine the connections between Systems, Speed, Service, Scale, Synergy, Stability, Sense and Spirit. Its purpose is to support a sound decision, with evidence gaps made clear.
Explore Stravus assessments and strategy design to understand how we help leaders connect the customer experience with the operating model behind it.