There’s a moment during an integration when you realize that having the right plan isn’t necessarily enough.
You’ve established the governance structure, mapped out the workstreams, aligned leadership on priorities, and built a roadmap for bringing two organizations together.
But despite all that planning, decisions are taking longer than expected. Teams are hesitant to adopt new processes. Employees are questioning changes that seem perfectly reasonable on paper.
Often, the issue isn’t the plan itself. It’s trust.
Trust in leadership. Trust in the decisions being made. Trust in unfamiliar systems and processes. And perhaps most importantly, trust between people who, until recently, worked for two entirely different organizations.
It’s one of the hardest parts of integration to measure, but one of the most important to get right.
You Don’t Need Every Answer
One thing I’ve learned through integration work is that uncertainty is unavoidable.
Employees want answers. They want to know how their roles will change, what the future organization will look like, and whether the ways they’ve worked for years are about to disappear.
And understandably, they want those answers sooner rather than later.
But the reality is that leadership is often figuring things out at the same time. Processes are still being evaluated, organizational decisions are still being made, and new information continues to surface.
There’s a temptation to hold off on communicating until everything is finalized. After all, nobody wants to share information that might change next week.
The problem is that when employees don’t hear anything, they tend to fill in the blanks themselves.
I’ve found that being upfront about what you know, what you don’t know, and what you’re working toward goes a lot further than trying to project certainty that doesn’t exist.
People don’t need leaders to have every answer. They need to believe they’re being told the truth.
Trust Is Built in the Follow-Through
It’s easy to underestimate how closely employees pay attention to the small things during an integration.
A leader promises an update by Friday. Does it come?
An employee raises a concern about a new process. Does anyone follow up?
A new system is introduced with the promise that it will make work easier. Does that actually happen?
Individually, these moments may seem insignificant. Collectively, they shape how employees feel about the entire integration.
The same goes for relationships between the two organizations.
People naturally trust what they know. They trust the colleagues they’ve worked alongside for years, the processes they’ve relied on, and the systems they’ve learned to navigate.
Asking them to move away from those familiar ways of working requires more than explaining why the new approach is better.
It requires giving them opportunities to experience that it’s better.
And when something doesn’t work as expected, acknowledging it and making improvements can do more to build credibility than pretending the transition has been seamless.
Trust Makes Everything Move Faster
There’s a practical side to all of this that often gets overlooked.
Low-trust environments are slow.
Decisions get escalated unnecessarily. Teams spend more time defending their positions than solving problems. People hesitate to share information or raise concerns because they’re unsure how it will be received.
And during an integration, those delays add up quickly.
When teams trust one another, the opposite happens. They’re more comfortable making decisions, challenging assumptions, and working through disagreements without questioning each other’s intentions.
That doesn’t mean every decision is popular or every change goes smoothly. It means people believe they’re working toward the same outcome, even when they disagree on how to get there.
And that shared confidence makes a tremendous difference when you’re trying to bring two organizations together.
The Takeaway
Throughout these Field Notes, we’ve talked about the importance of looking beyond Day 1, preserving institutional knowledge, understanding how people work, managing integration fatigue, and building a better operating model.
But there’s a common thread running through all of it. None of those things happen particularly well without trust.
You can consolidate systems, redesign processes, and create a unified org chart. But you can’t simply assign people a shared identity and expect them to embrace it.
That takes time, transparency, and consistent follow-through from leadership.
It’s when employees stop talking about “their company” and “our company” and start talking about “our business.”
Not because the org chart says they’re one organization, but because they’ve started to believe it.