From Months Behind to Months Ahead:
A Real Turnaround Story
Not every project problem needs a new methodology. Sometimes it just needs someone willing to change how the room works.
A couple of years ago, I inherited a programme for a global bank that was, by every measure, in trouble. The project was running months behind schedule. Worse than the slippage itself was the atmosphere around it: a fortnightly governance call that had become a two-hour ordeal, with regional heads dialling in from every continent to vent frustration at me, who was unlucky enough to be presenting every time.
Eighteen months later, that same call was ten minutes long, ran once a month, and nobody was angry. The project was planning months ahead instead of scrambling to catch up. Here’s what actually changed.
Why the Old Calls Were Broken
The fortnightly call wasn’t really a planning meeting — it was a symptom. It existed because nobody trusted the status reporting between calls, so everyone showed up to interrogate the numbers live, in front of each other, across time zones. Two hours of that, every two weeks, and you get exactly what you’d expect: Defensive reporting, and decisions that still didn’t get made because there wasn’t time to make them properly.
The real problems weren’t visible in that room. They were sitting quietly between calls — in handoffs nobody owned, in risks nobody had flagged early enough to matter, and in a reporting structure that told people what had happened, not what was about to!
What Actually Changed
- Reporting moved from “meeting-driven” to “written-first.” Instead of status being presented live and debated in the room, I submitted a short structured update in advance — Bad news first!: blockers, progress, confidence level, and early risk signals. By the time the call happened, everyone had already read it. The call stopped being where information arrived and became where decisions got made.
- Client-side access to trackers. I also implemented client-side access to live trackers for those who needed it. So no matter the time zone, people who needed to know could check and see what is booked and for when, without needing to call me up at 2 am or vice versa.
- Ownership was drawn properly. A lot of the original chaos came from genuine ambiguity about who owned what across regional teams. We mapped clear ownership across every workstream and handoff point, so escalations went to a named person immediately instead of surfacing three weeks later as a surprise on a governance call.
- Planning shifted from reactive to forward-looking. Rather than reporting on what had already gone wrong, the written updates were built to surface what was likely to go wrong in the next four to six weeks. That’s the difference between firefighting and actually planning ahead — you can only plan ahead if your reporting is looking ahead too.
Put together, those four changes did the real work. The monthly call still happened — but by then it was a genuine review of a plan everyone already trusted, not a two-hour attempt to reconstruct what was going on from scratch.
Why This Matters for SMEs Too
You don’t need a global bank’s budget or team size to hit this same failure pattern. Any SME running multiple projects across sites, clients, or teams can end up with the same thing: status meetings that exist to compensate for reporting nobody trusts, and planning that’s always looking backwards instead of forward.
The fix scales down just as well as it scaled up. Structured, forward-looking reporting; clear ownership at every handoff; and a review rhythm that’s short because the hard work already happened in writing beforehand — that’s the same approach we use with clients today.
SSC Ltd brings senior project management experience — including large-scale programme turnarounds — to SMEs who need the same discipline without the enterprise overhead.
