Trust Is the Cheapest Form of Organisational Infrastructure

There is a curious thing about trust in business. Everyone agrees it matters, but almost nobody budgets for it. We budget for systems, governance, controls, assurance, project offices, dashboards, risk committees, and increasingly sophisticated methods of checking whether other people have done what they said they would do. Then we call trust a “soft skill.”

This is rather odd.

Low trust is expensive. It turns a five-minute decision into a forty-five-minute meeting. It converts judgment into approval chains. It creates duplicate checking, defensive emails, carefully worded minutes, unnecessary escalations, and the magnificent corporate phrase “just to cover ourselves.” Every additional control may be rational, but many are invoices for missing trust.

High trust does something economically useful. It lowers the cost of cooperation.

That makes trust particularly important for the Business Improvement Lead, because improvement requires people to do unusually uncomfortable things. They must admit that the current system does not work. They must expose problems before they know the solution. They must allow outsiders into areas where they have expertise, status, and history. They may need to abandon practices they helped create. Occasionally, they must say in a meeting, “Actually, I think we got this wrong.”

No methodology can make that psychologically cheap.

Trust can.

The Problem: Improvement Starts by Making People Slightly Unsafe

Business improvement has a built-in paradox. We arrive promising to make things better, but the first thing we often do is destabilise what people already know.

We question the process. We examine performance. We ask awkward “why” questions. We map workarounds. We expose variation. We ask teams to experiment. We challenge assumptions that may have been protecting someone’s professional identity for fifteen years.

Then we are surprised when people become cautious.

This is where trust becomes operational rather than sentimental. People do not resist only because they dislike change. They assess the social risk of participating in it. Can I tell this person what really happens? Will my words be used against me? Is this another consultant who will disappear after producing a deck? Does the improvement lead understand my work or merely their methodology? If I admit that our process is held together by spreadsheets and favours from Karen in Finance, will someone decide that I am the problem?

Trust answers these questions before any process map can.

It is also subject to psychology. Confirmation bias means that once someone decides an improvement lead “doesn’t understand the business,” every mistake becomes evidence. The halo effect works in the opposite direction: an early demonstration of competence or empathy can influence how later actions are interpreted. First impressions are not always fair, but organisational life has never promised fairness to project teams.

This means the Business Improvement Lead is not merely managing tasks. They are continuously producing or destroying evidence about whether they can be trusted.

At CoEcosystem, we help organisations improve not only the mechanics of work but the human conditions that allow people to expose problems, experiment safely, and learn together. Learn more at CoEcosystem’s website.

A Better Framework: The Trust-to-Improvement Loop

Trust should not be treated as something you either have or do not have. It can be built through repeated experiences. For improvement work, four elements matter particularly: credibility, safety, reciprocity, and visible progress.

Explore the Trust-to-Improvement Loop in our video/community discussion.

1. Earn Credibility Before Asking for Vulnerability

People rarely trust a Business Improvement Lead because of the title. They trust evidence.

Credibility starts with competence, but competence is not the same as arriving with answers. In fact, arriving too quickly with answers is often a wonderful way to demonstrate that you have not understood the question. Credibility comes from asking intelligent questions, understanding operational detail, keeping commitments, admitting what you do not know, and being useful early.

Authenticity matters here. People have surprisingly good detectors for performative empathy. “Thank you for sharing your journey” means very little if the next slide ignores everything they just said.

The best improvement leads listen in a way that changes what they do next. That is empathy with consequences.

2. Make Truth Less Expensive

Psychological safety is frequently misunderstood as making everyone comfortable. It is almost the opposite. It is making uncomfortable truth safe enough to express.

Improvement needs bad news. It needs people to say the metric is misleading, the new system is making work harder, the customer workaround is actually sensible, or the executive sponsor’s preferred solution does not address the problem. If those statements are socially dangerous, the organisation receives a sanitised version of itself.

Low-trust organisations therefore develop an interesting problem: they become very good at reporting and very poor at knowing.

Trust-related social interactions are associated with biological processes involving stress regulation and neurochemicals such as oxytocin, but it is unhelpful to pretend that trust can be reduced to one hormone. The practical neuroscience is simpler: when people perceive threat, cognitive resources are diverted toward protection. When the environment feels sufficiently safe, more attention becomes available for learning, reasoning, collaboration, and experimentation.

The Business Improvement Lead therefore has an unusual job: reduce the interpersonal cost of telling the truth without reducing the standards of performance.

3. Build Reciprocity, Not Dependency

Trust strengthens when people experience improvement as something done with them rather than to them.

This is why good improvement leads resist becoming the cleverest person in the room. If every answer comes from the improvement team, the business may become dependent while politely calling it capability uplift.

Reciprocity works differently. The improvement lead contributes method, pattern recognition, challenge, facilitation, and outside perspective. The operational team contributes context, practical knowledge, history, and judgment. Each side has something the other lacks.

This also changes followership. People follow more willingly when following does not mean surrendering intelligence. Good leaders create direction without creating helplessness. They make it easier for people to contribute, challenge, and eventually lead without them.

The test of a successful improvement lead is therefore slightly uncomfortable: when the project finishes, can the organisation improve without needing you quite so much?

4. Create an Early Win People Can Feel

Trust grows through evidence, and early wins are evidence.

The mistake is choosing an early win because it looks impressive on a steering committee slide. The better early win is something people can feel in their work. Remove a pointless approval. Eliminate duplicate entry. Fix a customer irritant. Simplify a report. Resolve a frustration the frontline has complained about for years.

A small improvement that saves ten minutes every day may create more trust than a grand transformation milestone that nobody outside the program office understands.

This is behavioural economics in miniature. Humans disproportionately value what is immediate, visible, and personally experienced. A promised benefit in eighteen months competes badly against a working printer today.

Celebrate these wins too. Not with forced corporate fun involving matching T-shirts, but by making the progress socially visible. Show people that speaking up produced action. Recognise the people who helped. Share what changed and why. Enjoyment matters because positive experiences become part of the emotional memory of change.

Early wins are not merely outputs. They are trust deposits.

A Practical Example: The Team That Stopped Telling the Truth

Imagine a Business Improvement Lead entering an operation with poor customer outcomes and a growing backlog. Management believes the frontline needs stronger discipline. The frontline believes management has ignored capacity problems for years. Previous improvement programs have produced workshops, actions, and very little visible change.

The new improvement lead could begin with the standard machinery: process maps, performance data, interviews, governance, and an action register. All useful. But in a low-trust environment, the outputs may be technically correct and behaviourally useless.

So they start differently.

They spend time observing the work and asking where the process creates unnecessary effort. They avoid immediately correcting people. They notice that staff repeatedly re-enter the same customer information across two systems. Everyone knows it is wasteful. Nobody expects it to change.

The improvement lead chooses this as the first problem.

Within two weeks, the team redesigns the handoff and removes much of the duplicate entry. It is not the largest issue in the operation. It does not solve the backlog. It may barely excite the steering committee.

But the frontline notices.

Something important has happened: telling the truth produced a useful result.

The next workshop is different. People disclose more. One team member explains why cases are deliberately held before escalation. Another admits that a KPI encourages staff to clear easy work first. A manager acknowledges that teams have learned to avoid decisions because previous mistakes were publicly criticised.

The quality of information improves because the quality of trust improves.

Now the organisation can work on the real system.

One approach would describe the first intervention as a small process improvement. The better interpretation is that it changed the price of honesty.

See how we teach this approach inside the CoEcosystem Academy.

The Real Shift

The Business Improvement Lead is not simply a process expert, facilitator, analyst, or change practitioner. At their best, they are a temporary architect of trust.

They enter systems where people have histories with one another, where previous changes have left emotional residue, where status matters, where teams remember promises leaders have forgotten, and where apparently irrational behaviour may be a perfectly rational adaptation to low trust.

Their task is not to become universally liked. Trust and popularity are different things. Sometimes trusted improvement leaders must challenge, disagree, expose uncomfortable evidence, and say no. Authenticity matters precisely because empty positivity eventually destroys credibility.

Trust grows when behaviour is consistent. During the storming phase, this means staying curious when conflict appears rather than becoming defensive. During norming, it means reinforcing clear behavioural expectations. During performing, it means stepping back enough for teams to own the work. During transition or adjourning, it means acknowledging contributions and preserving relationships rather than disappearing once the project code closes.

The best improvement leaders also understand that change should contain some enjoyment. Serious work does not have to feel grim to be legitimate. Shared wins, humour, visible progress, and moments of collective pride strengthen social bonds. Fun is not the opposite of performance. Sometimes it is evidence that people finally feel safe enough to stop performing seriousness.

The larger lesson is that trust reduces organisational friction. It makes information travel faster, reduces defensive behaviour, allows judgment to operate, and makes experimentation less threatening. It creates the conditions in which Lean, Agile, process redesign, data, AI, and every other improvement method can actually work.

Without trust, an organisation compensates with control.

With trust, it can rely more heavily on judgment.

That is not soft management. It is a different economic model of coordination.

Further Reading

If this idea resonates with you, these books are useful companions for going deeper.

1. The Trusted Advisor, David H. Maister, Charles H. Green and Robert M. Galford. This is particularly useful for consultants and improvement leads because it explores how credibility, reliability, intimacy, and self-orientation shape trusted relationships.

2. The Speed of Trust, Stephen M. R. Covey. The central argument is commercially useful: trust changes the speed and cost of coordination. It provides a helpful lens for seeing trust as an operational issue rather than merely a cultural aspiration.

3. The Culture Code, Daniel Coyle. A practical exploration of how successful groups create belonging, safety, and shared purpose through small interpersonal signals and repeated behaviours.

4. Give and Take, Adam Grant. A useful examination of reciprocity and how different patterns of giving, taking, and matching shape collaboration, influence, and organisational relationships.

5. The Five Dysfunctions of a Team, Patrick Lencioni. A simple but memorable model connecting absence of trust with fear of conflict, weak commitment, avoidance of accountability, and inattention to collective results.

6. The Fearless Organisation, Amy Edmondson. One deliberately repeated recommendation from earlier in this series because psychological safety is directly relevant here: improvement requires people to surface mistakes, concerns, and uncertainty before those problems become expensive.

Discussion Question

What would people in your organisation tell you about the way work really happens if telling the complete truth carried no social or career cost?