The trust question behind every sign-off process

There's a pattern we see often when a team brings us in to help them build a clearer way of working. On the surface, the brief is about creating a shared guide, a process, or a document that sets out the rules of how things get done, and both leaders and staff agree on the need for that clarity.

Underneath that agreement is an issue of trust.

Leaders worry that staff might unknowingly create risk for themselves, for the organisation, and for its reputation, so they ask to see and approve almost everything personally. Staff experience that same sign-off process as inconsistent and hard to predict, because two ideas of similar merit can get different outcomes depending on the day or on reasoning that's never quite spelled out. Over time, staff stop investing emotional effort in ideas, because an idea that gets blocked without a clear explanation feels like wasted effort.

Each side has formed a story about the other. Leaders see staff's frustration with sign-off as ingratitude towards a process designed to protect them. Staff see leaders' sign-off habits as a need for control. Neither side intended to create the situation they're now in and both sides care deeply about the work the team produces.

Making the reasoning visible

This gap tends to close once each side's reasoning becomes visible to the other.

When we ask leaders to write down the actual criteria they use to approve or reject something, many discover their own decisions have been less consistent than they assumed. The criteria were mostly based on instinct, which is part of why decisions could feel different from one occasion to the next.

When we ask staff to list everything that could go wrong if they worked without sign-off, and then ask how much of that risk they would personally be willing to carry, the usual answer is very little. That exercise tends to change how staff see the sign-off process, and many come to see it as a layer of protection they hadn't previously valued.

The real foundation

That's the real foundation for any guide worth having. A guide built after both sides have seen their own blind spot earns genuine commitment, because everyone involved had a hand in shaping the logic and can see why each rule exists.

This is why, before we help teams come up with documented ways of working, we spend time understanding the dynamics underneath the brief. We speak to people beyond whoever commissioned the work, and we build in time after the main sessions to check the new ways of working are actually working well.

The guide itself matters, but the shared understanding that produces it tends to matter even more.

Our Deliver module includes several applications that help teams map out processes and improve the flow of the way they work.