Nobody Wants Another Tool: How I Got an Entire Firm to Actually Use One

There is a particular silence that follows a software rollout announcement in an architecture firm. It is not the silence of excitement. It is the silence of all your once friendly co-workers, spread across all studios, collectively deciding to ignore you.

Mosaic was supposed to change how we worked. A firm-wide project management platform that would replace the patchwork of personal spreadsheets, disconnected time tracking, and the Monday-morning ritual of chasing down project status updates via email. Leadership bought it. An entire committee configured it. We announced it to the full firm with the kind of enthusiasm usually reserved for new espresso machines.

| Six weeks later, fewer than 12% of our project teams were using it consistently.

| The platform wasn’t broken. Adoption was.

The Spreadsheet That Wouldn’t Die

To understand the resistance, you have to understand what Mosaic was replacing. Not a competing software platform. Something far more entrenched: habit.

Project managers had spent years building personal spreadsheets, customized to their exact preferences, tracking budgets and hours in formats they trusted because they had built them with their own hands. Senior architects had workflows that predated the iPhone. Admin staff had the impression, that technology rollouts were not really about them.

Mosaic didn’t ask people to learn a new tool. It asked them to abandon a system they had created for themselves. That is a fundamentally different kind of ask, and it requires a critically different kind of strategy.

I didn’t know it at the time, but what I was about to build was a product adoption playbook.

The People Behind the Percentages

The first thing I learned is that “the firm” is not a monolith. When you peel back the org chart, you find four distinct groups of people, each with a different relationship to change.

The Champions. About 15% of the firm. Tech-forward project managers and younger staff who had already been poking around in Mosaic before the official announcement. They didn’t need convincing. They needed a role. I recruited them as peer trainers, gave them early access, and let their enthusiasm become contagious. In marketing terms, these were my internal influencers.

The Willing but Uncertain. The largest group, roughly 35%. Mid-level staff who genuinely wanted to use the new platform but froze at the login screen. They asked a lot of questions. They felt embarrassed about not knowing. They apologized for “bothering” me. This group didn’t need a sales pitch. They needed someone to sit next to them, walk through the basics without judgment, and hand them a one-page guide they could pin to their monitor. They converted fast. Fastest of any group.

The Skeptics. Around 30%, and overwhelmingly senior staff. Principals and senior project architects who had been running successful projects for 15 or 20 years without Mosaic and saw no reason to start now. Their resistance wasn’t a training problem. It was a messaging problem. They didn’t need to learn how to use Mosaic. They needed to understand why they should care.

The Disengaged. The remaining 20%. Mostly admin and support staff who had been excluded from the rollout conversation entirely. Nobody had asked them what they needed. Nobody had explained their role in the system. They were the smallest group, but the loudest source of friction when ignored.

I didn’t have a name for this framework at the time. I called it “figuring out who’s who.”

Saying the Right Thing to the Right Person

The firm-wide announcement we sent in Week 1 was a feature list. Here’s what Mosaic does. Here are the modules. Here’s the login link. It landed with the impact of a weather report for a city nobody lives in.

The breakthrough came when I stopped talking about the tool and started talking about the problem. Different problems, for different people.

To the principals, the message became: We cannot give clients real-time project visibility if our teams aren’t using the system that provides it. That was a language they understood: client expectations, competitive positioning, risk.

To the project managers: Mosaic replaces the three to four spreadsheets you’re maintaining per project with one live dashboard. Time savings. Fewer errors. Less email.

To the designers: Understand how your project fee is tracking before getting the scary ‘we are running out of fee’ email.  The promise of avoiding their stress triggers.

To junior staff: Get a leadership level glimpse at your projects status.

To admin and support: Three tasks. Five minutes of training. That’s your entire scope.

The shift was simple in hindsight. Benefit-led messaging outperformed mandate-driven announcements every single time. “You have to use this” generated compliance. “Here’s what this fixes for you” generated adoption. Those are two very different outcomes wearing the same clothes.

Building the Bridge, Not Just Opening the Door

It began with the Champions. Eight of them, across seventeen studios, given early access and a simple mandate: use it on your projects, tell me what breaks, and show your teams how it works. No formal title, no extra compensation. Just the implicit recognition of being trusted first.

Launch week was structured around respect for people’s time and self-image. Six training sessions, segmented by role, because a project manager’s relationship to Mosaic is fundamentally different from a designer’s. Quick-start guides that covered five tasks, not fifty. Drop-in office hours with no appointment required, because the people who needed the most help were often the least likely to ask for it.

In the weeks that followed, I tracked adoption by team, not by headcount. A firm-wide percentage is a vanity metric. What matters is which project teams have embedded the tool into their actual workflow and which are still running parallel systems. The teams that lagged got targeted follow-up. The teams that thrived became case studies.

|One studio cut their weekly status meeting time by 40% within a month. That story |traveled faster than any email I ever sent.

The Numbers

After six months, daily active usage across the firm had climbed from 12% to 78%. Thirty-four of forty active project teams were fully onboarded. Support requests had dropped by 60%. Project managers reported saving roughly three hours per week on tracking and reporting tasks that used to require manual consolidation.

These are real numbers, though not precise ones. We didn’t have a product analytics dashboard tracking activation funnels. We had login reports, training attendance logs, and the unmistakable shift in hallway conversations from “Do I have to use this?” to “Can Mosaic do this?”

If I could go back, I would segment the audience from day one instead of discovering the segments through three weeks of trial and error. I would track adoption with a formal dashboard from launch, not reconstruct it anecdotally after the fact. I would invest twice as much time in the “why” before ever mentioning the “what,” because too many people heard about the tool before they understood the problem it was solving. I would build a formal Champion program with visible recognition, not rely on the goodwill of volunteers. And I would include admin and support staff in the rollout plan from the very beginning. They were an afterthought in the original strategy, and they became the loudest point of friction because of it.

The Reframe

Here is the thing I did not fully understand until I stepped back from the work and examined it through a different lens: everything I did during the Mosaic rollout, I did without a playbook, without a title, and without realizing I was doing product marketing.

Audience segmentation. Persona-specific messaging. Phased enablement. Champion advocacy. Adoption tracking. Feedback loops. Iteration.

These are not IT skills. They are not training coordinator skills. They are Product Marketing Manager skills, applied internally instead of externally. The mechanics are identical. The audience is different.

Every SaaS company’s biggest post-sale challenge is adoption. I have been on the customer side of that challenge, leading rollouts, fighting the inertia of established workflows, and building the enablement programs that actually move the metric. That practitioner perspective, is something no amount of customer interviews can fully replicate.

I have lived the adoption gap. I have closed it. And I have learned, through the friction of real work with real people who did not want to change, that the best product in the world is worthless if nobody uses it.

---