Case Study: Strategic Thinking Under Pressure
- Lucille Tut
- Apr 30
- 3 min read
TL;DR This case study demonstrates how prioritising transparency and commercial data allowed us to untangle technical complexity, descope low-value work and successfully secure a critical milestone that saved the client millions in legacy costs.
The Context
We were managing a large, bespoke enterprise application with thousands of users. After years of incremental growth the system had become highly complex.  The objective was to complete a critical final phase of work that would unlock significant cost savings (£2m per month) and enable the success of a much larger, multi-million-pound programme.
The Bottleneck
Early progress had been rapid but as we reached the final, most complex requirements, momentum stalled. We were hit by a perfect storm:
Increasing Complexity The remaining tasks had deep technical and policy dependencies.
Operational Load The teams were balancing third-line support with heavy development.
Decision Fatigue Stakeholder sign-offs were slow and shifting policy requirements necessitated frequent reworks.
The Turning Point: Radical Transparency
It became clear the original deadline was unrealistic.  In delivery, the hardest conversation is often the most necessary one.  We chose total transparency over "hoping for the best."
We told the client early that the date wouldn't be met.  While no one likes bad news, managing expectations early is the only way to maintain trust.  This honesty allowed us to hit "pause" for a few days to re-plan properly - time that proved to be a vital investment in our eventual success.
Using Data to De-risk
We stripped the programme back to basics. Using performance metrics, we identified low-volume use cases that were consuming a disproportionate amount of development and testing time.
By analysing the data, we proved that some features didn't require a complex technical solution immediately. We moved these to manual or hybrid processes.  This wasn't just a tactical win - it was a significant financial one.
The Commercial Reality of Complexity
The cost of pushing every minor use case through a digital pipeline is often hidden, but, in this instance, the figures were stark:
Direct Delivery Costs At a conservative estimate of £25k per use case for development and testing, the financial overhead for end to end digital low-volume journeys was significant.
Operational Drag Each new digital journey adds roughly £15k–£20k in annual BAU costs for maintenance and infrastructure.
The £2m Monthly Penalty Most critically, including these edge cases would have extended the deadline by up to two months (possibly more). This would have delayed the decommissioning of legacy systems that were costing the organisation £2m per month in upkeep.
By descoping the "noise" we didn't just save on development; we protected the business from millions in avoidable legacy costs.
Untangling the Complexity
The project had become conflated. Related problems were being treated as dependencies, causing steering groups to go in circles.
We stepped in to break these problems down into isolated workstreams.  We acknowledged the links between tasks but strictly parked anything that wasn't a showstopper.  By enforcing this focus, we stopped the team from being overwhelmed by the scale of the task and got them focused on the immediate next steps.
The Outcome
The strategy worked.  By clearing the noise and focusing on the core functionality, we unblocked the path to the programme's ultimate goal.  We delivered all agreed changes to production safely and incrementally.
Breaking the back of the most complex cases allowed the final phase to move with much greater pace.  Ultimately, we secured the critical milestone, unblocking the wider strategic programme and delivering the long-term value the client required.
Lessons for the Next Phase
Transparency as a Delivery Tool Difficult conversations aren't a sign of failure; they are a project requirement. Being honest about timelines allows for pragmatic re-planning rather than a panicked rush.
Technology is the "How," not the "Why" Not every business problem requires a line of code. Sometimes a process change is faster, cheaper, and more effective than a technical build.
Think Beyond the Deadline It is vital to look at what the product looks like after you reach the goal. Is it supportable? If a feature costs more to maintain than the value it generates it is a liability, not an asset.
The Cost of "Completion": True delivery leadership is about recognising the opportunity cost.  Every hour spent on a low-value feature is an hour stolen from a critical business goal.
Conclusion
Successful delivery isn't just about dogged determination; it’s about having the courage to challenge the plan when the facts change. By balancing technical expertise with commercial reality, we didn't just meet a deadline - we delivered a sustainable, cost-effective solution that allowed the client to move forward with confidence.