ISO Projects Don’t Die From Complexity. They Die From No One Asking What Happened Since Tuesday.
Bodil Biering
Most ISO projects don’t fail because nobody understands the standard. They fail because nobody’s checking in on Tuesday to ask what happened since last Tuesday.
Our customer Haime’s CEO had been through this before. When we talked to him after his team got certified, he told us he’d had previous experience with ISO projects that never finished. Not “took longer than expected.“ Never finished. Started, staffed, budgeted for, and then quietly abandoned somewhere
That’s a common pattern at SMEs. Someone kicks off the compliance project with real intent. A folder gets created. A few policies get drafted. Then the day job takes over, the project has no natural deadline pressure, and it drifts until nobody mentions it in meetings anymore. The knowledge was never the problem. The accountability was.
What changed this time, according to the CEO, was the process and having a compliance coach involved to help get the team to the finish line. Not a dashboard. Not a smarter checklist. A person, checking in weekly.
Those check-ins made the team feel accountable and kept them moving forward. Combine that with a process built from clear steps and modules, plus support that actually responds quickly and doesn’t make you feel stupid for asking — and the project stops being something the team is theoretically working on and becomes something that’s actually progressing.
Software can hold your evidence. It can’t ask why nothing moved since last week. That still takes a human who’s expecting an answer.
