One team, different badges at Arden Manufacturing
Arden Manufacturing runs 24/7 operations across five countries with 2,000 IT users. Its SIAM ecosystem comprises an internal service integrator, an internal service desk, and three providers for infrastructure, SAP application support, and field services. Staff turnover in the shared service desk is 25% a year. There are 1,200 knowledge articles, but an audit found 40% are outdated or duplicated. Provider staff say they are discouraged from sharing knowledge because 'knowledge is our value'. After each severity-1 outage, the monthly operational review becomes a blame session; providers bring contractual evidence to prove they met SLA. Continuous improvement ideas come almost exclusively from the integrator. The COO has demanded a 'one team' culture and better knowledge sharing, but the contracts still reward individual provider SLA attainment and contain no collaboration measures. The SIAM lead has one quarter to show progress without renegotiating the master contracts.
1. Recommend practical cultural integration mechanisms that can work within the existing contracts. Explain why each mechanism addresses a specific behaviour in the setup.
Read the worked answer
Culture will follow daily practices and incentives, not a values campaign. Within the existing contracts, I would use five mechanisms.
First, a joint service desk queue and shared shift rota for severity-1 triage. This reduces the 'badge' boundary at the point where handoffs fail and gives staff a shared task identity.
Second, blameless post-incident reviews with a fixed format: timeline, contributing factors, actions and owners, with no contractual evidence allowed in the review. This directly addresses the blame sessions and separates learning from commercial claims.
Third, cross-provider communities of practice for SAP, infrastructure and field services, meeting monthly with rotating chairs. This gives provider staff a legitimate forum to contribute beyond their contract.
Fourth, joint onboarding and a shared knowledge standard. New starters from all providers learn the end-to-end service, not only their tower. Knowledge articles have named owners and review dates.
Fifth, visible leadership behaviour: the SIAM lead and provider account directors co-chair the operational review and open with end-to-end performance, not individual SLA defence. The COO should attend occasionally to signal that 'one team' is not a side initiative. These mechanisms are low-cost and do not require contract renegotiation.
2. Redesign the measurement and incentive approach so that collaboration is rewarded rather than punished. Include specific measures and how they would be introduced without reopening the master contracts.
Read the worked answer
The current contracts reward individual SLA attainment, which punishes collaboration when helping another provider increases local cost. I would introduce a collaboration scorecard alongside the existing SLAs, not instead of them, using a contract change note or governance schedule rather than a full renegotiation.
Measures should include: knowledge contribution and freshness (percentage of articles reviewed on time, reuse rate, duplicate rate); handoff quality (acceptance within OLA, rework rate, missing information); joint improvement (number of cross-provider actions completed, not just raised); end-to-end restoration contribution; and service desk turnover and new-starter competency.
The scorecard should be discussed at the monthly operational review and reported to the SIAM board. It should influence noneconomic recognition first: awards, case studies and preferred-partner status. If the contracts allow, a small portion of variable margin or renewal评分 can be linked after two quarters of baseline data.
The key design rule is to avoid measuring collaboration through surveys alone. Behavioural measures such as handoff rework and knowledge reuse are harder to game and closer to the outcome the COO wants.
3. What are the main risks of this cultural integration programme, and how would you mitigate them in the first quarter?
Read the worked answer
The first risk is that 'one team' becomes a slogan while contracts continue to reward siloed behaviour. Mitigation: pair every cultural mechanism with a visible operational change, such as the shared severity-1 queue, and report collaboration measures at the same forum as SLAs.
Second, provider staff may share knowledge and then see it used against their commercial position. Mitigation: define knowledge licensing and use rights in a simple schedule, and keep post-incident reviews explicitly non-contractual. If providers fear exploitation, knowledge sharing will stop.
Third, the programme may create meeting overhead without changing decisions. Mitigation: limit new forums to two, give each a decision or action output, and retire any forum that does not produce actions within two cycles.
Fourth, high service desk turnover may undermine joint training. Mitigation: create a lightweight onboarding module and buddy system that survives turnover, rather than relying on one-off workshops.
Finally, the SIAM lead may be blamed if culture does not change in one quarter. Mitigation: agree leading indicators for the quarter, such as review format compliance, knowledge owner assignment and handoff rework baseline, rather than promising a cultural transformation in 90 days.