Changing and Improving SCS Example Statement (750 Words)

SAs chief operating officer of a national organisation with 6,500 staff and over two million customer interactions a year, I inherited a portfolio of 14 separate change projects, most running late and none joined up. Customer satisfaction was falling, staff change fatigue was real, and the organisation was spending around £30 million a year on projects that nobody could confidently describe as succeeding. Each project had its own branding, its own governance and its own definition of progress, which made honest oversight almost impossible. The board had limited confidence in delivery, and our sponsoring ministers were openly asking questions about value for money.

TThe chief executive asked me to reset the entire portfolio. My task was to turn 14 competing projects into one coherent transformation programme with clear benefits, honest sequencing and visible leadership, while keeping daily services running throughout. I was personally accountable to the board and to our sponsoring department for both the savings and the service improvements. I set the tone personally: the reset needed credibility more than another glossy document.

AI started by listening: in six weeks I met every project team, the customer service centres handling the consequences of change, and the finance team tracking the spend. I commissioned a rapid independent review of all 14 projects against the same simple test: what customer or staff outcome does this deliver, by when, and how will we know. Five projects could not answer convincingly, so I recommended to the board that we stop them, releasing £8 million and, more importantly, 90 skilled people. Stopping projects was politically hard, so I presented the evidence project by project and gave each sponsor the chance to challenge it; two convinced me with data and were saved on merit, which showed the process was genuine. I rebuilt the remaining nine projects into one programme with a single outcome map agreed by the whole executive, so every initiative had a visible line to customer experience, staff capability or cost. I published that map internally, so anyone could challenge where their work fitted and why. I simplified governance from seven overlapping boards to one delivery board that I chaired monthly, with a standard one-page report replacing the 60-slide packs that had hidden problems rather than surfaced them. I introduced a citizens' panel of 40 service users who reviewed plans before we built anything, and their input changed two designs fundamentally, including a digital service that assumed smartphone access our customers often lacked. I insisted we kept non-digital channels properly staffed, because transformation that abandons the most vulnerable customers is not improvement. I renegotiated our largest supplier contract, moving from a fixed specification to outcome-based milestones, and I brought testing in-house after the review showed we had outsourced our ability to spot failure early. I invested in our own people, creating a change-practitioner development scheme so capability stayed when contractors left. Midway through, I rotated the programme leadership so fresh eyes challenged my own assumptions, and I asked the audit committee to review benefits honesty, not just delivery confidence. When middle managers disengaged, sensing the programme was an executive hobby, I moved decision-making for local changes to regional level and required senior sponsors to spend one day a month in the teams their projects affected. I reported benefits publicly every quarter, including the projects that were off track, and I never re-baselined a target without explaining why, which rebuilt trust with staff who had learned to distrust good-news reporting. I set up a reverse-mentoring scheme pairing executives with frontline digital champions, which changed several executive assumptions about how staff actually worked. One mentoring pair redesigned our appointment letters, cutting avoidable customer calls by a fifth. Two years in, I led a formal strategy refresh with the board, dropping one major workstream the evidence no longer supported and reinvesting in the two that were outperforming.

RWithin three years, customer satisfaction rose from 61% to 84%, digitally completed transactions grew from 12% to 58%, and annual running costs fell by £14 million. The programme returned its full investment 18 months ahead of schedule, staff absence fell for the first time in five years, staff change-fatigue scores improved by 21 points and internal promotion into change roles doubled, and our quarterly reporting approach was adopted by two partner organisations. The strongest signal of success came when the organisation handled an unexpected surge in demand, 40% above normal volumes, without service failure, because the processes and people were finally built to adapt rather than built to cope.