Seven anonymised cases, explained simply: what was getting in the way, what changed and what teams noticed.
Case study
The digital portfolio had grown through successive additions: new initiatives, cross-team dependencies and old commitments that never quite closed. Each lead understood their…
Case study
A digital service used in healthcare had to handle critical information flows, sharp peaks in traffic and many dependencies between organisations. When pressure rose, an urgent…
Case study
A mid-sized operations team was under pressure to deploy AI quickly. Yet incoming requests, recurring reports and handovers were spread across email, spreadsheets and chat. The…
Case study
The team had grown, and so had its tools. Its ways of working had not kept pace. People moved quickly inside their own area, but handovers varied from one person to another,…
Case study
In a highly regulated activity, teams had to move quickly while keeping evidence of approvals and sensitive decisions. That evidence was scattered across several tools. Every…
Case study
In a growing services firm, useful precedents, procedures and configurations were spread across shared folders, conversations and personal habits. Finding the right answer…
Case study
A multi-site SME had allowed each location to adapt its access practices, workarounds and incident response. That autonomy helped day to day, but when a problem crossed sites,…