An organisation can have a policy for almost everything.

It can document how projects should be managed, how decisions should be approved and how concerns should be reported. It can introduce checklists, templates, codes of conduct and detailed instructions for maintaining quality.

On paper, the organisation may appear exceptionally well prepared.

But work does not take place on paper.

It happens within relationships, deadlines, pressures, habits and unequal distributions of power. People interpret what leaders say, but they also notice what leaders do. They learn which procedures are genuinely important, which can be ignored and what happens to anyone who slows the work down by raising a concern.

A checklist may describe what should happen.

Culture teaches people what is actually expected.

When the two contradict each other, culture usually wins.

The Written Process and the Real Process

Most organisations have at least two versions of every important process.

The first is the official version.

It appears in the handbook, contract, project plan or quality framework. Responsibilities are clear, the sequence is logical and every important safeguard has its place.

The second is the process as people actually experience it.

Perhaps the official procedure requires a thorough review, but the deadline allows no time for one. Perhaps employees are instructed to ask questions, yet senior colleagues respond impatiently when they do. A community consultation may be required, but the budget and direction have already been decided before participants are invited.

The official process communicates the organisation’s stated intentions.

The real process reveals its priorities.

This does not mean written procedures are useless. Without them, people may have no shared standard at all. But a procedure cannot protect quality, fairness or safety if the surrounding culture makes following it difficult.

The first step towards improvement is therefore honest observation.

What happens in practice?

People Learn From Consequences

Organisational culture is often discussed through values.

A business may say that it values collaboration, inclusion, creativity, wellbeing or accountability. These words can be meaningful, but people decide whether to believe them by observing consequences.

If someone raises an emerging risk and is thanked for protecting the work, that teaches one lesson.

If they are treated as negative, difficult or disloyal, it teaches another.

If a manager admits uncertainty and asks for help, people learn that honesty is acceptable.

If leaders conceal their own mistakes while publicly emphasising accountability, people learn that accountability applies differently according to status.

If careful work receives little recognition while rushed delivery is consistently rewarded, people learn that speed matters more than quality.

The repeated consequences surrounding behaviour gradually become the culture.

What leaders reward becomes important.

What they tolerate becomes normal.

What they punish becomes dangerous.

A Checklist Cannot Correct a Contradictory Incentive

Imagine an organisation introduces a final quality checklist.

Before any report is sent to a client, the team must confirm that the facts have been checked, the correct version is attached and accessibility requirements have been considered.

The checklist is sensible.

But the organisation also rewards employees according to the number of projects completed each month. Deadlines are set without allowing time for review. Managers praise people who respond immediately and complain when checking delays delivery.

The checklist and the incentive are now in conflict.

Employees must choose between following the stated procedure and meeting the expectation that appears to determine how their performance is judged.

Some may complete the checklist without completing the checks. Others may regard it as an administrative obstacle. Over time, ticking the boxes becomes separate from protecting quality.

The failure does not necessarily lie with the individuals.

The organisation designed one process and rewarded another.

Compliance Can Become a Performance

A procedure can create the appearance of responsible practice without changing the conditions that made the procedure necessary.

Forms are completed. Attendance is recorded. Boxes are checked. Approved language appears in reports.

The organisation can demonstrate that a process took place.

But did the process achieve its purpose?

A consultation may attract participants without giving them meaningful influence. An equality policy may exist while informal networks continue determining who receives opportunities. A wellbeing survey may collect concerns that leaders have no intention of addressing.

This is procedural performance: the visible signs of compliance without the deeper change those signs are supposed to represent.

It is dangerous because it can reassure the organisation that the problem has been solved.

The existence of a record becomes evidence of success, even when the experience of the people involved suggests otherwise.

Good governance must therefore ask two questions:

Did the required process happen?

Did it produce the intended protection, participation or improvement?

Culture Lives Between the Rules

No procedure can anticipate every situation.

Work involving people, communities and cultural contexts always contains circumstances that require interpretation. Someone must decide when an exception is justified, how a principle applies and what to do when two responsibilities conflict.

This is where culture becomes particularly influential.

When the written rule is incomplete, people rely on what they understand the organisation to value.

If the culture respects evidence, people are more likely to investigate before deciding. If it values accessibility, they will notice barriers that a standard checklist has missed. If it values trust, they may pause before taking an action that technically complies with the procedure but could damage an important relationship.

Culture provides direction when the rules run out.

This is why values must be demonstrated through decisions, not merely displayed as statements.

Informal Workarounds Are Evidence

When an official process is difficult to use, people create workarounds.

They keep their own spreadsheet because the shared system is unreliable. They contact one trusted person rather than follow the formal approval route. They save documents privately because the folder structure is confusing. They avoid reporting smaller problems because the reporting procedure is too burdensome.

Workarounds are often treated as misconduct or resistance.

Sometimes they are.

But they can also reveal where the official system does not match the realities of the work.

A workaround may indicate that:

The process contains unnecessary steps.

Responsibilities are unclear.

The technology is unsuitable.

The official route takes too long.

People do not trust the response they will receive.

The system was designed without input from those expected to use it.

Following the procedure creates another form of risk.

Accessibility needs were not considered.

The people doing the work possess knowledge the designer lacked.

Leaders should not automatically approve every workaround. Informal methods can introduce serious risks of their own.

But they should investigate why the workaround exists.

Punishing the behaviour without understanding its cause may remove the visible evidence while leaving the underlying problem untouched.

Power Determines Who Can Question the Process

Not everyone experiences a procedure from the same position.

A senior leader may view an approval process as a useful safeguard. A junior employee may experience it as a barrier that prevents them from using their judgement.

A funder may regard a reporting framework as proportionate. A small community organisation may experience it as an administrative demand that absorbs limited capacity.

A consultation designer may believe that every participant has been given an equal opportunity to speak. Some participants may know that challenging the dominant view could affect their future access, reputation or relationship with the organisation.

Culture influences who feels entitled to question a process.

People with secure positions, established relationships or recognised expertise may be able to request exceptions. Others may feel that following the process silently is the safest option, even when they can see that it is producing harm.

A culturally intelligent review must therefore ask:

Who can challenge the procedure without negative consequences?

Whose interpretation is treated as authoritative?

Who is expected to adapt?

Who receives exceptions?

Whose additional labour keeps the process functioning?

Who carries the risk when the system fails?

Are people able to appeal or seek another route?

A process is not fair merely because the same instructions are presented to everyone.

Fairness also depends on whether people have the power, access and support required to use the process successfully.

Participation Must Begin Before the Procedure Is Finished

Processes are often designed by leaders, consultants or specialists and then introduced to the people expected to use them.

Those people may receive training or an opportunity to comment, but the fundamental structure has already been decided.

This limits what their participation can change.

Someone who performs a task regularly may understand difficulties that are invisible from a management position. A community partner may recognise cultural or historical implications that an external designer cannot see. A person with an access requirement may identify barriers that become obvious only through lived experience.

Participation is most valuable when it happens early enough to shape the process.

This does not mean every decision must be made collectively. Organisations still need clear ownership and accountability.

It means that relevant knowledge should enter before the design becomes difficult to change.

Ask the people closest to the work:

What makes the task difficult?

Where are errors most likely?

Which steps protect quality?

Which steps create little value?

What do people currently do when the process fails?

What information is missing?

What would make the procedure easier to follow?

Who may experience the process differently?

Which exceptions should require human judgement?

The people using a system are not simply its recipients.

They are a source of intelligence about how it functions.

Leaders Must Follow the Processes They Sponsor

A procedure quickly loses credibility when senior people treat it as optional.

If everyone must record decisions except the founder, the organisation has not created a shared decision record. It has created an administrative requirement for people with less authority.

If expenses require approval while senior leaders bypass the process, the rule communicates hierarchy more strongly than financial responsibility.

If managers expect employees to respect working-hour boundaries but continue sending urgent messages late at night, the lived expectation will override the written wellbeing policy.

Leadership exemptions can occasionally be necessary. Different responsibilities may require different processes.

But unexplained privilege damages trust.

Leaders should be willing to demonstrate the behaviour they expect, explain legitimate differences and accept scrutiny when the system does not work.

A culture of accountability cannot be created by people who position themselves outside it.

Psychological Safety Makes Procedures Useful

Checklists and reporting systems depend on people being willing to communicate honestly.

A team may be required to pause before an important action and confirm that everyone is ready. But if junior members are afraid to contradict a senior colleague, the pause may become ceremonial.

Everyone confirms.

The concern remains unspoken.

Psychological safety allows someone to say:

“I do not understand.”

“I think we may be using the wrong information.”

“This process is creating a barrier.”

“I made a mistake.”

“I believe we should stop and check.”

These statements protect organisations.

They reveal uncertainty while it can still be addressed.

Psychological safety does not mean that every concern is correct or that decisions must wait until everyone agrees. It means that people can contribute relevant information without fearing humiliation or retaliation.

A procedure that invites challenge requires a culture that permits it.

Review the Friction, Not Only the Failure

Organisations frequently review processes after something has gone seriously wrong.

By then, the cost may already be substantial.

A more useful approach pays attention to smaller signs of friction:

Repeated confusion

Delayed approvals

Missing information

Frequent exceptions

Duplicate records

Work completed outside official systems

People avoiding responsibility

Complaints that never reach formal reporting

The same questions being asked repeatedly

Tasks that depend on one unusually knowledgeable person

These are not always minor administrative irritations.

They may be early evidence that the written process and working culture are moving apart.

Regular review should ask both what failed and what almost failed.

The near miss may reveal the system more clearly than the final outcome.

Build the Culture Around the Purpose

An effective checklist begins with a clear purpose.

What is it trying to protect?

Accuracy? Accessibility? Trust? Safety? Financial control? Informed participation? A client commitment?

When people understand the purpose, they can use the process intelligently. They are better able to distinguish essential safeguards from unnecessary administration and recognise situations in which the standard procedure may be insufficient.

Leaders can strengthen alignment by:

Explaining why each important process exists

Removing steps that do not serve its purpose

Allocating enough time and resources to follow it

Rewarding the behaviour the process requires

Inviting feedback from users

Recording and reviewing justified exceptions

Responding constructively when concerns are raised

Applying appropriate accountability across levels of authority

Measuring outcomes, not only completion

Revising the procedure when conditions change

The objective is not perfect compliance.

It is dependable practice.

The Real Procedure Is What Happens Under Pressure

Almost any organisation can follow its values when work is calm, resources are available and no important interests are threatened.

Culture becomes visible when there is pressure.

What happens when the deadline is close?

Does the quality check remain important?

What happens when evidence challenges a senior person’s preferred decision?

Is honest disagreement still welcome?

What happens when accessibility requires additional time or expense?

Does inclusion remain a commitment?

What happens when a community raises an uncomfortable concern?

Is participation still meaningful?

The answers reveal whether the process is part of the organisation’s culture or only part of its documentation.

A checklist can remind people what to do.

A culture determines whether they believe they are truly expected, permitted and supported to do it.

Strong organisations need both.

They need clear processes that protect essential standards and a working culture that makes those processes credible.

The goal is not to produce more documents.

It is to create an organisation in which the written commitments and everyday behaviour tell the same story.