Most procurement organisations love SOPs.
They look solid.
They feel controlled.
They signal seriousness.
And yet, when things actually go wrong,
people don’t open SOPs.
They remember stories.
________________________________________
What really happens on the ground
Picture a field supervisor standing at a collection point.
It’s hot.
Farmers are waiting.
A truck is late.
Quality is borderline.
No one says:
“Let me check Clause 4.3.2.”
What they think instead is:
“Last time this happened, what went wrong?”
That memory is not procedural.
It is narrative.
________________________________________
SOPs explain what. Stories explain why.
SOPs are excellent at:
• defining steps,
• setting boundaries,
• assigning responsibility.
They are terrible at:
• handling ambiguity,
• managing pressure,
• or teaching judgement.
Stories do the opposite.
A story explains:
• why a shortcut failed,
• why a decision backfired,
• why a well-meaning action caused harm.
Judgement is learned through consequence — not instruction.
________________________________________
How people actually learn governance
People don’t learn governance by reading rules.
They learn it by:
• watching outcomes,
• hearing what happened to others,
• and imagining themselves in similar situations.
A farmer remembers:
“That buyer who rejected late lost everyone next season.”
A staff member remembers:
“That supervisor who delayed payment had no suppliers left.”
A manager remembers:
“That one exception destroyed the whole system.”
These are governance lessons — transmitted through stories.
________________________________________
Why SOP-heavy systems collapse under stress
Under stress:
• attention narrows,
• time compresses,
• and memory takes over.
SOPs require:
• calm,
• time,
• and clarity.
Stress removes all three.
Stories survive stress because they are compressed wisdom.
________________________________________
Stories travel where SOPs never reach
SOPs stay in folders.
Stories travel through:
• WhatsApp,
• tea breaks,
• phone calls,
• and warnings disguised as advice
“Wahan mat karna jo pichhle saal hua tha.”
That sentence has more governance power
than a 20-page manual.
________________________________________
Stories preserve ethics when rules fall short
Rules cannot cover every situation.
Stories fill the gaps.
They teach:
• restraint when rules allow excess,
• empathy when rules permit harshness,
• patience when rules allow speed.
Ethics live in these gaps.
Governance that ignores stories
becomes technically correct and morally hollow.
________________________________________
Why this book avoids checklists
This book intentionally avoids:
• rigid templates,
• exhaustive checklists,
• and universal formulas.
Not because they are useless —
but because they create false confidence.
Real procurement is messy.
Stories prepare people for mess — not perfection.
________________________________________
Stories also reveal patterns
One story is an anecdote.
Ten similar stories are data.
Patterns emerge:
• where systems break,
• which behaviours repeat,
• and which decisions hurt most.
This is how lived governance evolves —
not through audits, but through accumulated experience.
________________________________________
SOPs still matter — just not alone
This is not an argument against SOPs.
SOPs:
• protect consistency,
• support training,
• and enable scale.
But SOPs must be anchored in stories.
Otherwise, they are followed mechanically
and abandoned emotionally.
________________________________________
A simple learning governance test
Ask this:
“If I remove all SOPs tomorrow, would people still know how to act responsibly?”
If the answer is no,
the system hasn’t taught judgement — only compliance.
________________________________________
Why this chapter matters
Many procurement systems believe they are governed
because they have documents.
They are not.
They are governed when:
• people anticipate consequences,
• act responsibly under pressure,
• and choose dignity over convenience.
Stories make that possible.
________________________________________
What comes next — and what ends here
With this chapter, the doctrine is complete.
What follows is not more content —
but reflection.
Because governance is not something you finish writing.
It is something you keep practising.
