The new CRM launched in March. By September, half the sales team was still working off of a spreadsheet.
Nobody rejected the new system outright. Information Services had done real diligence, the platform was a genuine upgrade, and leadership had signed off on the investment. But the team that would actually live in that system every day had never been in the room when the decisions were made. Field configurations didn’t match how sales actually worked. Required fields made sense to finance while slowing down every single call log. Within a month, a few sales reps built their own workaround. Within three months, that workaround was the unofficial standard.
If you’ve watched a rollout stall like that, the diagnosis usually lands on training. Do more training sessions, draft a better onboarding guide, send a follow-up email reminding everyone to use the new tool. That almost never fixes it, because the problem was never a training gap. It’s a structural one that inhibits cross-functional collaboration.
Why Reframing Your Team as a System is a Game Changer
A Lack of Cross-Functional Collaboration Isn’t a Communication Problem
The instinct, when a rollout stalls, is to explain it better. Another training video. A cheat sheet. A reminder in the team meeting. These help at the margins. However, they rarely fix the underlying pattern because the underlying pattern isn’t confusion. It’s exclusion, and exclusion doesn’t respond to better documentation.
The team that is building or choosing a new information system is usually optimizing for a real, legitimate goal, like cleaner reporting, better forecasting, tighter compliance. The team using the system daily is optimizing for something equally real: closing deals fast, keeping momentum with a client, not losing time to friction. When those two teams never sit in the same room during the decision-making and selection process, the system ends up reflecting one team’s priorities while quietly undermining the other’s. No amount of explaining the tool afterward changes that.
Research on team boundary-spanning backs this up. A framework developed from qualitative data across more than 200 interviews and validated against 565 members of cross-functional teams found that how a team manages its activity across organizational boundaries shapes its outcomes as much as anything happening inside the team itself. In plain terms: the handoff itself is a real, measurable part of the work, not an administrative afterthought to it. Treating the seam between departments as unimportant is treating part of the work as optional. (Emondson & Harvey, 2017, as reported in ScienceDirect)
This is the distinction that separates the systemic team coaching from a change management workshop. A workshop teaches people to adopt a new process better. Systemic coaching asks a harder question upfront: who was actually in the room when this decision got made, and did it include the people who’d have to live with it?
The Stakeholder Gap: Why High-Performing Teams Keep Their Eye on Who They Serve
What Executive Teams Model, Everyone Else Inherits
Here’s the part most leadership teams don’t want to hear. Rollouts stall from the top just as often as they stall on the front line.
If your own executive team adopts a new planning process, a new reporting cadence, or a new decision-making structure without ever asking the people closest to the work whether it holds up in practice, you’re modeling the exact pattern you’re frustrated to see repeated below you. Middle managers watch how leadership handles change, and they calibrate accordingly. If leadership rolls out decisions without input and expects compliance, that becomes the norm everywhere else, whether anyone intends it or not.
This is why going “from silos to systems” has to start at the top, even when the visible friction is happening in a sales team six layers down. Training middle managers on change adoption while the executive team keeps making unilateral calls is treating a symptom while the source keeps producing more of it.
Transform your team into a high-performing powerhouse with team coaching.
Three Shifts That Actually Move the Needle
None of this requires a different vendor or a bigger budget. It requires a shift in who’s in the room and in what gets rewarded.
Shift 1: Name the seams, not just the silos. Most rollouts fail at the exact same seam: the point when the team that decides and the team that executes don’t actually talk. Before your next system, process, or policy rollout, ask plainly who will use this daily, and make sure at least one of them is in the design conversation, not just a subsequent training session.
Shift 2: Change what gets rewarded, not just what gets discussed. If the team building the system is measured only on the go-live date, they’ll optimize for delivering it on time, not for whether the people using it actually adopt it. Add adoption rate, not just launch date, to what leadership actually tracks.
Shift 3: Make friction visible on purpose. Most stalled rollouts survive because their cost stays invisible. A team quietly reverting to a spreadsheet looks like a minor workaround in the moment. Nobody’s tracking how often this happens across tools and processes. Once a team starts naming friction as it happens, instead of discovering it in an adoption report six months later, the pattern becomes impossible to ignore.
To illustrate, here’s a composite example, built from patterns I see across client engagements rather than in any single company. A mid-market logistics firm rolled out a new project management platform that operations had chosen and configured entirely on its own. Six months in, adoption sat below forty percent, and two departments were still coordinating by email.
When the executive team finally mapped the handoff, they found the same gaping seam behind every stalled rollout in the company’s recent history: whoever built the tool never interfaced with whoever had to use it. Their fix? Not a better tool. It was a standing rule that no system or process rollout moves forward without a working session including the actual end users, before configuration, not after.
Where to Start This Week
You don’t need to fix every process in your organization by Friday. You need one rollout, current or upcoming, where you can name who’s missing from the room. Pick the system, policy, or process that’s caused the most silent friction in the last year. Ask the people using it daily what actually happens when it doesn’t work, not what the training manual says should happen.
Silos aren’t a structure you tear down once and have fixed the problems they caused. Silos are a habit your system keeps defaulting back to unless something deliberately interrupts it. Addressing that interruption is the real work.
If you want a second set of eyes on where your own seams are breaking, that’s a conversation worth having. Schedule a free strategy session with me now.