There's a strange thing happening in organizations rolling out new digital workplace tools. The executives are excited about it, IT has tested it thoroughly, the early adopters are already finding clever uses for it, and then everything stalls. Not dramatically. Just... stops moving forward the way it should.
When you actually look at where the friction lives, it's usually not in the executive suite and it's not with individual contributors. It's in that weird middle layer of managers who run teams but don't run companies. The ones who have to actually use the tools while also making sure their people use them. The ones who get email from leadership saying "we're adopting Teams for all collaboration" and then have to figure out what that actually means for their daily standup, their status reports, their way of keeping tabs on what's happening.
The thing about middle managers is they're the first people who feel the actual friction of change. Not in theory, not in a pilot program. In their Tuesday morning when they're trying to run a meeting using the new tool and it's slower than the old way and three people are on mute by accident and someone's asking why they can't just use email like before. They feel it before anyone else.
What's interesting is that their skepticism or buy-in doesn't really stem from whether the tool is objectively better. It comes from whether the change makes their job harder or easier in the actual moment. A tool that requires them to learn a new workflow, duplicate information across systems, or manage adoption among their team gets resistance not because they're afraid of change, but because they're already managing fifteen other things and this is one more.
Organizations that actually move the needle on digital workplace adoption seem to get this. They're not just dropping the tool and expecting it to spread organically. They're treating middle managers as the actual audience for change, not as obstacles to work around. That means showing them specifically how it makes their job better. Not "this improves collaboration" but "you'll spend less time chasing people for status updates because it's all in Teams." Not "it's the future of work" but "your team doesn't have to context-switch between five apps anymore."
The other thing that matters is giving middle managers actual authority over how their teams adopt it. Not "here's the policy" but "here's what the company is moving toward, help us figure out what works for your specific team." Because middle managers know things leadership doesn't. They know which of their people will need extra support, which workflows are going to break, which processes were designed around the old tool for a reason.
When adoption stalls, people tend to blame the tool, or the team, or resistance to change. But a lot of the time what's actually happening is that middle management never really got on board because nobody made it worth their while. Nobody showed them what's in it for them. Nobody treated their skepticism as information instead of obstruction.
The irony is that middle managers probably spend more time in the actual digital workplace than anyone else. Executives have calendars that pull them out. Individual contributors might spend their day focused on their actual work. But middle managers are living in Teams, in email, in status updates, in the constant communication infrastructure. They're the ones who should be the toughest critics and the most valuable guides. Organizations that figure that out usually end up with adoption that actually sticks.