To evolve from a culture that absorbed operational complexity to a system that could decide, measure and learn from it.
The company was not trying to fix a broken operation. It was trying to test whether an organisational model that had worked in a previous phase could still sustain service, capacity, cost and execution under a more complex and uncertain context. Functionally, the ambition was to create clearer governance, stronger planning routines, shared KPIs and a more explicit decision architecture. Emotionally, it meant giving the organisation permission to stop hiding difficult trade-offs behind effort, goodwill and the instinct to protect service at all times.
The organisation was aligned enough to keep moving, but not explicit enough to decide cleanly.
Teams were committed, connected and used to solving operational problems. But the model increasingly depended on people absorbing friction. Some departments acted as bridges between others, which helped coordination but also softened accountability. Decisions were discussed, shared and distributed, but not always owned with enough clarity. Service remained the natural answer to every exception, even when the cost of that answer was not fully visible.
The organisation was aligned enough to keep moving, but not explicit enough to decide cleanly.
- 01Why a previously transformed operating model can start losing effectiveness under higher complexity
- 02How a strong collaborative culture can unintentionally dilute decision ownership
- 03Why service at any cost only works when the cost is visible
- 04How Diagnosis separates tactical symptoms from structural decision frictions
- 05How data, thresholds, RACI, planning routines and Control Tower logic can become an operating architecture
- 06Why the next level of operational maturity is not more effort, but better decision design
The company operated a complex distributed supply chain connecting demand, planning, supply, platforms, transport and final service locations. The operating model had been improved in a previous transformation cycle, but the new context required a deeper review of whether its organisational structure, planning routines, analytical layer and decision rights were still fit for the level of complexity ahead.
The leadership question was not simply how to optimise logistics. It was whether the organisation could keep protecting service while making the cost, owner and consequence of each decision visible enough to learn from it. The Diagnosis became the starting point for a broader model definition exercise focused on decision architecture, data governance, planning and operating management.
Surfingvest worked as a strategic execution partner inside a broader delivery team, playing a central role in diagnostic structuring, operating analysis, synthesis of findings and the definition of a decision architecture for a complex distributed operation.
The engagement produced a structured model definition for a more scalable logistics decision system. It clarified the need for stronger governance, data-driven decisions, clearer accountability, planning protocols and a Control Tower logic capable of connecting service decisions with economic impact.
This should be treated as a diagnosis and model-definition outcome. No quantified financial outcome is available yet. Do not claim that the model was fully implemented, that KPIs improved or that savings were achieved unless later evidence confirms it.
Service is only a strategy when you know what it costs.
Protecting service can be the right decision. But when every exception is absorbed without knowing its cost, its owner or its long-term impact, service stops being a strategic choice and becomes a cultural reflex. The next level of operational maturity starts when the organisation can decide with the same commitment, but with better data, clearer accountability and a visible price tag.
The company had already gone through a significant organisational transformation several years before. That previous effort had improved the operating model and helped the business capture many of the more immediate efficiency gains. But the system was entering a different phase. The environment was more uncertain, operational capacity was harder to flex, and the cost of protecting service was becoming more difficult to absorb without stronger analytical discipline.
The Diagnosis revealed a mature operation with committed teams, a strong culture of collaboration and a high ability to keep service running. The problem was not lack of professionalism. The issue was that the model increasingly depended on coordination, informal negotiation and human effort to absorb complexity. Responsibilities were spread too widely, some departments operated as hinges between others, and the organisation did not always have one shared way to decide who owned a trade-off, what it cost and when it should escalate.
The central finding was not that service was the wrong strategy. Service can be the right strategic choice. But service at any cost only works when the organisation knows the cost. The work therefore focused on making the decision system more explicit: shared KPIs, a common source of truth, thresholds, escalation rules, economic models, a Control Tower logic and planning routines that could connect the business ambition with operational capacity.
The project moved beyond diagnosis into model definition. Instead of proposing an ideal redesign that the organisation might not absorb, the team worked from the constraints of the real business and defined a practical path: organisational model, data-driven decision architecture and operating management model. The result was a structured operating blueprint for decision-making, planning and execution, not a claim of completed implementation or measured financial impact.
Momentum: Several years earlier, the company had made a significant effort to transform and optimise a large part of its operating model. That work had created progress, but the context had changed. The new leadership question was whether the current structure still represented the best way to organise, plan and decide.
The Diagnosis was launched to understand the real operating model, identify the structural frictions behind daily tensions and define whether the next phase required a new organisational layer, a new decision system or simply better execution discipline. The work then moved into model definition, where different operating models were evaluated against cultural fit, analytical maturity and organisational feasibility.
Operating reality: The operation connected demand, planning, supply, platforms, transport and service locations. Each area understood its own reality and carried part of the operational pressure. But the system did not always work from a single accepted version of the truth, one shared KPI language or one clear protocol for deciding when a problem should be absorbed, automated, escalated or redesigned.
The operating model had cultural strength and technical capability, but the analytical and governance layer needed to become more central. Data could not remain a reporting layer. It had to become the layer through which the organisation decided.
Diagnostic read: The diagnosis showed a capable and committed organisation whose model had become increasingly dependent on human coordination, informal negotiation and reactive problem-solving. The main issue was not operational capability. It was the absence of a sufficiently explicit decision architecture.
The company did not need to care less about service. It needed to understand what each service decision cost, who owned the trade-off and how the system should learn from every exception.
Action path: The recommended path focused on building the operating layer the organisation was missing.
1. Define a clearer organisational model around control, optimisation and cross-functional governance.
2. Build a Control Tower logic able to connect planning, execution, incidents, reporting and learning.
3. Establish shared KPIs, thresholds and escalation rules so decisions could move faster and with less ambiguity.
4. Create economic models so service, capacity, forecast deviations, stock-outs, waste and supplier penalties could be translated into financial impact.
5. Redesign planning routines, RACI structures and operating sessions so the organisation could move from reactive coordination to governed execution.
6. Treat the model as progressive: first visibility and control, then prediction, then automation and prescriptive decision support.
What changed: The work did not stop at identifying frictions. It translated them into model options and then into a more practical operating architecture.
The engagement moved from Diagnosis into Model Definition. It clarified the need for a Control & Optimization role, a Control Tower logic, clearer RACI structures, planning protocols, KPI thresholds, economic models and a roadmap toward more data-driven operating management.
The project reframed the challenge from logistics optimisation to decision architecture. The question was no longer only how to improve the supply chain. It became how the organisation should decide when service, cost, capacity and accountability collide.