Instead, Ask: “Where Are We Accidentally Destroying It?”

When leaders talk about trust, the conversation often turns to communication.

How can we be more transparent?

How can we improve our messaging?

How can we better explain our decisions?

These are important questions. But they all assume the same thing: that trust is primarily created through communication.

I think that’s only part of the story.

In my last article, I argued that trust is fundamentally a design problem. Communication matters, but it exists within a much larger system of relationships, processes, technologies, policies, and everyday experiences.

If that’s true, then building trust requires more than crafting better messages.

It requires designing better experiences.

Every Interaction Is a Lesson

Organizations teach people what to expect.

Sometimes intentionally.

More often, unintentionally.

Imagine visiting two organizations that both describe themselves as “customer-focused.”

In the first, you immediately find clear directions, receive timely updates, and know exactly who to contact when you have a question.

In the second, you’re transferred multiple times, information is inconsistent, forms are confusing, and no one seems quite sure who owns the problem.

Both organizations may use identical language in their mission statements.

Only one communicates trust through experience.

Every interaction teaches people something.

Over time, those lessons become expectations.

Those expectations become trust—or mistrust.

A Simple Trust Audit

One of the easiest ways to identify opportunities for improvement is to conduct what I think of as a simple trust audit.

Instead of asking people whether they trust your organization, begin by examining the experiences you’ve designed.

Walk through one of your most common processes as though you were encountering it for the first time.

As you do, ask five questions.

1. Where does friction begin?

Where would a first-time visitor become confused?

What assumptions does your organization make that newcomers don’t yet understand?

Every unnecessary obstacle sends a message.

2. Where does information stop flowing?

Who has the information people need?

How easily can they access it?

When information becomes trapped within departments, software systems, or organizational silos, uncertainty grows.

3. Do your processes reinforce your values?

Many organizations proudly describe themselves as collaborative, responsive, or community-centered.

But do everyday experiences reflect those values?

Policies communicate.

Processes communicate.

Waiting communicates.

Consistency communicates.

4. Where are people compensating for weak systems?

One of the clearest signs of a design problem is when good people must constantly work around broken processes.

Employees create spreadsheets because software doesn’t communicate.

Citizens call multiple offices because responsibilities are unclear.

Volunteers rely on personal relationships because formal systems don’t work.

These workarounds often become invisible to leadership because dedicated people quietly keep the system functioning.

Heroic employees should be celebrated.

But they should never become the operating system.

5. What happens when one person leaves?

Healthy systems are resilient because knowledge, responsibility, and trust are distributed.

Fragile systems depend on a few individuals who “know how everything works.”

If losing one employee creates widespread confusion, you’ve identified a systems issue—not a staffing issue.

Small Improvements, Big Results

One of the encouraging aspects of systems thinking is that meaningful improvements don’t always require massive investments.

Sometimes trust grows simply because someone removed an unnecessary approval step.

Clarified confusing language.

Made information easier to find.

Assigned clear ownership.

Closed the communication loop.

Each of those changes may seem small in isolation.

Collectively, they reshape how people experience an organization.

A Design Ecology Perspective

One of the central ideas I’m exploring through Design Ecology is that every intervention changes the ecology of a human system.

We often think about design in terms of buildings, products, or technology.

But organizations are designed systems, too.

Every workflow.

Every form.

Every policy.

Every digital interface.

Every meeting.

Every conversation.

Each one influences how people interact with one another and with the institution itself.

Trust isn’t simply earned through good intentions.

It’s cultivated through consistently thoughtful design.

A Challenge for This Week

Choose one experience your organization creates every day.

It might be onboarding a new employee.

Responding to customer questions.

Scheduling appointments.

Processing permits.

Handling complaints.

Now experience that process yourself.

Not as the leader who understands how everything works.

As someone encountering it for the very first time.

Pay attention to every point of confusion, delay, contradiction, and unnecessary effort.

Then ask yourself one final question:

If we redesigned just one part of this experience, would people trust us a little more tomorrow than they do today?

That may be one of the most practical places to begin designing trust into your organization.