That's probably the simplest test of whether a system is any good.
Lots of processes work when everyone is calm, focused and has plenty of time. That isn't the hard bit. The hard bit is whether the same process still works on a messy Monday when someone is off sick, three things have gone wrong and nobody has read the documentation properly.
Those are the days that reveal the system.
Not the perfect days.
The bad ones.
I think this is where we often overestimate people and underestimate design. We assume people will remember the right steps, name things properly, update the tracker, check the dashboard and tell the right person at the right time.
Sometimes they will.
Sometimes they won't.
Not because they're lazy or careless, but because they're human.
Good systems reduce the chance that one tired person can quietly break the whole thing.
They make the right action easier, the wrong action harder and the important information visible.
Where my thinking is today
A good system shouldn't need perfect behaviour to work.
If it does, it isn't really a system.
It's just hope with a process document attached.