Every leader I’ve coached in thirty years, from a squad bay in the Marine Corps to a Fortune 500 boardroom, asks some version of the same question: how do you actually build trust? Not define it. Not measure it, though I’ve written a separate guide on how to measure trust for that. Build it. Where does it start, and what does the process from nothing to something actually look like?
My answer is the Tsunami Wave Theory. It’s the proprietary framework underneath everything else I teach, and it’s the one idea I’d want a podcast host, a keynote booker, or a reader picking up my book for the first time to understand before anything else. This article is the full explanation: what the wave is, where it starts, how it moves through a real team, and what makes it stop.
The idea, in one sentence
Trust is not a binary event. It’s a behaviorally activated flow state, ignited by small, repeated acts that ripple outward until they become unstoppable.
That single sentence carries the whole model. Most leadership advice treats trust like a light switch: either the team trusts you or it doesn’t, and the job is to flip the switch with a big enough gesture, a values offsite, a heartfelt all-hands, a mission statement redesign. The Wave Theory says the opposite. Trust behaves like water. It starts as a single, almost invisible disturbance, and it only becomes a wave through repetition, not through size.
Why the metaphor alone doesn’t work
I’ll say the quiet part first, because it’s the biggest risk in writing about this: a wave is a nice image and a useless management tool unless you can point to the exact behavior underneath every stage of it. I’ve watched consultants build entire keynotes on “ripples of change” that evaporate the second someone asks, “okay, but what do I do on Tuesday?”
So every stage in this article gets tied to something you could watch happen on an actual Tuesday afternoon, in an actual conference room or Slack thread. If a stage can’t survive that test, it doesn’t belong in the model. That’s the standard I hold my own frameworks to, and it’s the standard I’d ask you to hold anyone else’s to as well.
Trust as a flow state
The starting point isn’t a trust theory at all. It’s flow theory, the psychological state described by Mihaly Csikszentmihalyi: full immersion, energy, and intrinsic motivation, produced by a specific set of conditions, chiefly a balance between challenge and skill, clear goals with immediate feedback, and a sense of control over the task at hand. Csikszentmihalyi built that model studying artists, surgeons, and rock climbers, not trust. I’m borrowing the mechanism, not the credit for discovering it.
What I noticed, across thirty years of watching teams either come together or come apart, is that trust builds under the same conditions flow requires. It starts small. It compounds with consistency. It needs enough challenge to matter and enough clarity to feel safe. Those four ingredients, consistency, challenge, clarity, and connection, are already baked into the twelve behavioral building blocks I use to operationalize trust, which I’ve documented in full in the TrustFlow Methodology, Academic Edition. This article is about the mechanism that moves a team through those building blocks, not the blocks themselves.
In practice, this means trust isn’t something you announce. It’s a state a team enters through repeated, specific behavior, the same way a musician enters flow through repeated, specific practice, not through a single inspired night.
Micro-Trust Activations: the ripple effect
Trust doesn’t begin with grand gestures. It begins with acts small enough that most leaders don’t think to count them:
- Showing up when you say you will
- Owning a mistake without shifting blame
- Giving credit freely, especially when no one is checking
- Following through on micro-promises, the small commitments nobody would notice if you broke
- Holding space for a difficult conversation instead of rescheduling around it
Each of these is what I call a Micro-Trust Activation, an MTA. They’re the entry points into TrustFlow, and they carry a disproportionate weight relative to their size. An MTA behaves like a pebble dropped into still water. One ripple, on its own, changes nothing you can measure. But drop enough pebbles in the same spot and the ripples start to overlap, then reinforce each other, then move as a single current.
Here’s what that looks like on an actual Tuesday. A product manager tells her team on Monday she’ll have a decision on scope by end of day Tuesday. Tuesday at 4:45, she doesn’t have full clarity, but instead of going quiet until she does, she posts in the team channel: “Not ready yet, here’s what I still need, you’ll have it by Thursday morning.” That’s an MTA. It cost her nothing but a moment of discomfort admitting she wasn’t finished. It also just taught five people that her word means something even when the news isn’t good.
The four stages: from ripple to tsunami
Repeated MTAs don’t just add up. They move through four distinct stages, each with its own dominant trust dimension. This is the wave’s actual shape.
| Stage | TrustFlow state | Dominant trust dimension |
|---|---|---|
| 1 · Micro-Ripple | Self-awareness | Functional trust |
| 2 · Trust Current | Relational alignment | Relational trust |
| 3 · Momentum Surge | Team synchronization | Behavioral trust |
| 4 · Trust Tsunami | Organization-wide trust culture | Blind trust (high vulnerability) |
Stage 1 · Micro-Ripple: self-awareness
The wave starts with one person noticing their own behavior. The product manager above, in the moment she decides to post an honest update instead of going dark, is at Micro-Ripple. Functional trust is the dimension in play: can this person do what they say they’ll do. Nobody else on the team has necessarily noticed yet. The ripple exists, but it hasn’t reached the shore.
Stage 2 · Trust Current: relational alignment
The ripple becomes a current when it starts to run in a predictable direction that other people can feel. This is the stage where a teammate starts noticing the pattern: “She always tells us when she’s behind, even when it’s not good news.” That noticing is relational trust forming, the shift from “can you do the job” to “can I read you accurately.” A current in real water is invisible from the surface but it moves everything drifting in it. Relational trust works the same way: it’s not announced, but it starts steering how people talk to each other.
On a Tuesday, this shows up as a colleague starting to loop that product manager into a decision earlier than the process technically requires, because they’ve started trusting her reaction more than they trust the formal review cycle.
Stage 3 · Momentum Surge: team synchronization
A current strong enough, sustained long enough, becomes a surge, the stage where the team starts to move as one unit instead of a set of individuals coordinating around each other. Behavioral trust is now the dominant dimension: not just “can I read this person” but “do I understand how they’re wired, and am I adjusting how I lead and communicate with them because of it.”
The Tuesday version of Momentum Surge looks like a stand-up meeting where a normally quiet engineer flags a risk in front of the whole team before being asked, because the team has built a track record of receiving bad news without punishing the messenger. That’s synchronization. The team has internalized a shared behavior, not just observed one person’s.
Stage 4 · Trust Tsunami: organization-wide culture
The final stage is what I call the Trust Tsunami Effect: a behavioral wave big enough that it no longer depends on any one person sustaining it. Blind trust is the dimension here, meaning high vulnerability trust, the willingness to follow someone’s judgment in a high-stakes moment even without full visibility into their reasoning. This is not trust given lightly. It’s trust earned across every stage before it, and it shows up as culture rather than as individual behavior.
At this stage, a new hire joins the team and, within a few weeks, is doing the same things the founding members do: naming mistakes early, giving credit publicly, following through on small commitments, without ever being told to. That’s the tsunami. It’s no longer a set of individual choices. It’s the water everyone is standing in.
Why the conditions for flow matter here
Csikszentmihalyi’s conditions for flow map directly onto what makes each stage of the wave possible, and this is where the metaphor earns its keep instead of just decorating a slide. A team can’t reach Momentum Surge if the challenge is either too high, so people freeze, or too low, so nobody bothers engaging. It can’t sustain Trust Tsunami without clear goals and fast feedback, because ambiguity is exactly what breaks a current back down into disconnected ripples. And no stage survives without a sense of control: Micro-Trust Activations work because they’re self-directed and repeatable, something a person can choose to do again tomorrow, not a mandate handed down from HR.
This is also where the distinction between reward-driven behavior and what researchers Richard Ryan and Edward Deci called an autotelic system matters. In an autotelic system, people engage not because of an external reward but because the activity itself becomes the reward. Once a team reaches Momentum Surge, giving credit or naming a mistake early stops feeling like a sacrifice and starts feeling like how this team simply operates. That shift, from cost to identity, is the clearest sign the wave is real and not performative.
What stops the wave
Waves die the same way they’re born: through repetition, or the lack of it. A single broken commitment doesn’t sink a team’s trust. A pattern of them does, because the moment people stop being able to predict your behavior, they start hedging against it instead of building on it. Hedging looks like copying extra people on emails as cover, withholding a concern until it’s safe, or quietly building a workaround instead of raising the issue. Those are the countermoves people make when the current has gone still.
The second, more common killer is substitution: a leader performs the big gesture, the trust-themed offsite, the new values poster on the wall, and skips the small, unglamorous repetition that actually moves water. Grand gestures don’t compound. They spike attention for a week and fade, because nobody experiences a poster as a Micro-Trust Activation. The wave only moves on repeated, specific behavior, not on announcements about behavior.
How to start one on a real team
You don’t need authority, a budget, or a program to start a ripple. You need one Micro-Trust Activation you’re willing to repeat.
- Pick one MTA, not five. Closing a loop you said you’d close, naming a mistake before someone else finds it, or handing credit to whoever actually did the work. One behavior, done consistently, moves more than five behaviors done once.
- Do it visibly. Not performatively, just where the team can see it happen. A ripple nobody notices doesn’t compound.
- Repeat it on the same trigger. Same meeting, same kind of update, same moment each week. Consistency is what turns a ripple into a current; randomness never does.
- Watch for the second person. The moment someone else on the team starts doing the same MTA without being asked is the moment you know the current has formed. That’s the real signal, not a survey score.
- Protect it under pressure. The behavior will get tested exactly when it’s least convenient, a missed deadline, a bad quarter. Whether it survives that test determines whether the team reaches Momentum Surge or drifts back to still water.
This is also the practical bridge to how I coach teams to measure the process, which I lay out step by step in how to measure trust: score the specific behaviors, not the feeling, and you’ll know whether the wave is actually moving or whether you’re just hoping it is.
Frequently asked questions
What is the Tsunami Wave Theory of trust?
It is Jeff Morris’s model for how trust builds: not as a single event but as a behaviorally activated flow state, ignited by small, repeated acts called Micro-Trust Activations. Each activation behaves like a pebble dropped in still water. Repeated, the ripples combine into a wave that moves through four stages, from one person’s self-awareness to an organization-wide trust culture.
What is a Micro-Trust Activation?
A Micro-Trust Activation, or MTA, is a small, specific, repeatable act of trust: showing up when you said you would, owning a mistake without shifting blame, giving credit freely, following through on a micro-promise, or holding space for a hard conversation. None of these require authority or a program. Each one is an entry point into TrustFlow, and each one is small enough to do today.
How long does it take for trust to compound?
There is no universal clock, because compounding depends on repetition, not calendar time. What moves the wave is consistency: the same Micro-Trust Activations showing up in the same moments, week after week, until the team stops noticing them as effort and starts expecting them as normal. That shift from noticed to expected is the signal that a ripple has become a current.
What stops the wave?
Inconsistency stops it fastest. One broken micro-promise does not sink a team, but a pattern of them collapses the wave back to still water, because people stop predicting your behavior and start hedging against it. The other common killer is a leader who performs the big gesture, the offsite, the values poster, without the small, unglamorous repetition underneath it. Trust does not compound on spectacle.
How do you start a trust wave on a real team?
Pick one Micro-Trust Activation you can do this week without asking permission: closing a loop you would close, naming a mistake before someone else finds it, or handing credit to whoever actually did the work. Do it in front of the team, do it again next week, and watch for the moment someone else starts doing it too. That second person is the wave, not the metaphor.