Every S2P transformation starts with the same confidence. The business case is approved. The platform is selected. The implementation partner is onboarded. The Gantt chart looks immaculate.
And then reality arrives.
Not in the technology. Not in the process design. In the people, the competing agendas, and the assumptions nobody thought to document. Change Impact Assessment — CIA — is the discipline that maps this territory before you walk into it blind. In most transformations, it is either skipped entirely or performed as a tick-box exercise weeks after the decisions it should have informed have already been made.
That is not a project management failure. It is an architectural one.
What Change Impact Assessment Actually Is
CIA is not a change management form. It is a structured diagnostic that answers three questions an S2P transformation cannot afford to leave ambiguous:
- Who is affected, and how materially?
- What behaviours, roles, and ways of working must change — and by when?
- Where is the organisation's genuine capacity to absorb that change?
Done properly, it surfaces the uncomfortable gap between what the programme assumes and what the organisation can actually deliver. Done poorly — or not at all — that gap surfaces anyway. Just later, and at greater cost.
Why It Gets Skipped
Three reasons, consistently.
First, timeline pressure. CIA feels like preparation. Programmes are rewarded for execution. The two are in constant tension, and preparation loses.
Second, scope myopia. Transformation leaders focus on the platform and the process. The human system — roles, incentives, reporting lines, informal power — is treated as an implementation detail rather than a design constraint.
Third, overconfidence in adoption. There is an enduring belief that if the system works and the training is delivered, people will follow. They won't. Not reliably. Not without understanding what is changing for them specifically and why it matters.
What It Costs
The consequences are predictable precisely because they repeat. Adoption stalls. Workarounds proliferate. The old process runs in parallel with the new one — quietly, informally, and at significant cost to the efficiency gains the business case promised. Benefits realisation slips. The programme is declared complete while the transformation quietly fails in the background.
This is not a technology problem. It was never a technology problem.
What Good Looks Like
A rigorous CIA is completed before detailed design begins — not after. It maps impact at role level, not function level. It distinguishes between populations who need to change behaviour and those who need to change mindset. It gives the programme a realistic view of change capacity and sequencing risk.
It is, in short, the document that makes every subsequent workstream more honest.
Before your next S2P programme moves past mobilisation, ask this: can you name the five roles most materially impacted by this transformation — and articulate specifically what changes for each of them? If the answer takes more than a working session to produce, your Change Impact Assessment is overdue.
What did your last S2P transformation not plan for?