SOAP changes with every case.
You have probably heard of SOAP. Simple Object Access Protocol: machines talking to each other in structured, polite XML. Orderly. Predictable. Nothing like the projects in these books.
In SAP SOAP, every protagonist finds their own SOAP. The same four letters, different words. Never handed over at the start. Found the hard way, somewhere in the middle of the case.
Alex’s SOAP
From Death by Spreadsheet: a data migration a week from go-live, and one spreadsheet that claims to be the single version of truth.
Every migration project has spreadsheets. One of them started as a quick extract and quietly became the single version of truth. Everybody trusts it, nobody owns it, and every team keeps its own copy, each version its own gospel. Alex’s SOAP is not about banning the spreadsheet. It is about building things properly, so the spreadsheet never has to carry the truth on its own.
-
Structured. Chaos spreads exponentially. Structure slows it down.
-
Open. Silence is lethal. Say it in the meeting. Not after it.
-
Aligned. Nodding is not agreeing. Pretending to agree is the slowest form of sabotage.
-
Purified. Sooner or later everything needs a good scrub. Data. Process. Your ego.
Amy’s SOAP
From Death by Workaround: a live system nobody fully understands, and one person who holds all the keys.
Every organisation has a Max. The one who fixes it overnight, every time, so nobody ever has to ask why it broke. Every workaround starts as temporary, and every temporary fix needs someone to keep it alive. Amy’s SOAP is not about replacing Max. It is about a system that no longer needs any one person to keep it breathing.
-
Stabilise. Not fix. The bleeding stops. That is all you can promise.
-
Ownership. Weight distributed. Keys shared. When one person becomes the system, that is not expertise. That is exposure.
-
Accountable. Decisions remain visible. Traceable. Not blamed. Addressable.
-
Protected. Some knowledge destroys more than it heals. You carry it carefully.
Priya’s SOAP
From Death by Email: fourteen tickets, an empty castle, and a VAT specialist on holiday. Case 3, under investigation.
Every organisation has a Frank. The one who knows how it really works. Frank builds a castle of knowledge, and the organisation helps him dig the moat. Priya’s SOAP is not about storming the castle. It is about what an organisation looks like when it no longer needs one.
-
Shared. Not the secret. The knowledge. Three people in a closed room is just a smaller castle.
-
Official. In the ticket, or it didn’t happen. Nobody covers. Nobody guesses.
-
Auditable. A trail anyone can follow. Who knew. What they knew. When.
-
Proven. Checked, not inherited. Traceability is a claim. Not evidence.
Why the SOAP meaning changes
Every case looks at the same company from a different angle. Where you stand decides what you see, and what you see decides what SOAP has to mean.
Alex sees Sapura as a project manager. A new system is on its way in, and the risk is building the old mess into it. Her SOAP is about getting the foundations right before go-live.
Amy sees it as a functional consultant. The system is live, and the risk is that one person has quietly become it. Her SOAP is about spreading the weight before it breaks someone.
Priya sees it as a business analyst. The knowledge sits in someone else’s inbox, and the risk is that it goes wherever they go. Her SOAP is about making knowledge outlast the person who holds it.
Same company. Same four letters. Three different meanings. The letters stay because the problem underneath stays: people under pressure, and systems that remember every shortcut. Amy puts it best. Not a methodology. A survival mechanism.