The Same System, Two Outcomes
Give an identical CRM platform to two firms. Assume these two firms have similar use cases and the exact same training and onboarding process. One will have users logging in daily, data flowing regularly, and reports that leadership can rely on — for the most part. The other will have a system that users don’t go into unless they’re forced to, inconsistently populated records, and a running joke about “the CRM nobody uses.” The difference isn’t the software sitting between them — it’s what happens after go-live, and specifically, who in the organization treats adoption as their job. In the firms that succeed, that’s rarely one person. A leader sets the expectation, and front-office tech works alongside the teams to make it real.
If the tool itself were the deciding factor, we wouldn’t see this split. We’d see proportionately poor results from poor tools and good results from good ones. Instead, we see firms succeed with software that has real rough edges, and we see firms fail with software that’s genuinely well designed. That’s not a UX story. That’s a management story.
No Tool Survives an Empty Driver’s Seat
The most expensive, most sophisticated platform on the market is worthless the moment users decide it’s optional. And users will decide it’s optional unless someone actively decides otherwise on their behalf. Adoption doesn’t happen by osmosis, and it doesn’t happen because the system is good enough to sell itself. It happens because someone in the organization sits in the driver’s seat — constantly reminding, pushing, following up, and refusing to let old habits reassert themselves in the first ninety days, which is when almost every rollout is actually won or lost.
This isn’t a training problem you solve once at launch. It’s an ongoing management discipline. The manager owns the expectation, but the front-office tech team usually has the clearest view of whether it’s being met. Someone has to notice when a team reverts to spreadsheets. Someone has to ask, in a Monday pipeline review, why a record hasn’t been touched in three weeks. Someone has to make it clear, repeatedly, that this is how the firm operates now — not a suggestion, not a pilot, not a “when you get a chance.” It’s not fun or easy to constantly nag, remind, cajole, and encourage people to start new habits — I know this from experience — but if you take that person out of the equation, even the best-designed system will quietly die of neglect.
The Virtuous Cycle Has to Be Built, Not Assumed
Here’s where a lot of firms get the sequencing backwards. They wait for users to see the value of the system before asking them to invest in it — and that value never arrives, because the system only becomes valuable once enough people are consistently inputting information. Adoption isn’t something users opt into after they’re convinced. It’s something leadership has to force into existence before the payoff is visible and hold in place until the payoff shows up on its own.
That’s the virtuous cycle: input creates output, output creates trust, trust creates more input. Someone just has to prime that pump, because on day one there’s nothing in it for the user yet. The easiest place to prime it is with a team that already has its own reason to want the system to work. Their early results give everyone else a reason to follow. The salesperson entering notes into a system with no history gets no benefit from doing so — until six months later, when that same system can tell them everything about a relationship without a single phone call. This matters even more as firms layer AI on top of their systems. AI can only work with what’s been captured, so a team that skips the system gets weaker answers, and the blame lands on the tool all over again. Getting from the empty system to the useful one is not a UX journey. It’s a management job, and it’s usually a thankless one for the first two quarters.
The Weekly Pipeline Call
I once worked for a manager who ran exactly this kind of forcing function, whether or not he thought of it that way. We held a weekly pipeline call with the institutional sales team, built entirely around a report pulled straight from the CRM. If an opportunity wasn’t logged in the system, it wasn’t on the report. And if it wasn’t on the report, it wasn’t discussed on the call — no airtime, no visibility, no chance to talk through a deal in front of the team and get help pushing it forward. And salespeople generally do not like to be left out of the group conversation, especially when their pipeline looks weak without critical inputs!
Of course, people had to be reminded to keep their data updated. People are busy and easily distracted, but they knew the cost of non-compliance was immediate and personal: your deal simply didn’t exist that week. Our manager never gave a lecture on data hygiene. We built a process where good data was the price of admission to something people already wanted — a seat at the table where deals got discussed, coached, and helped along. Log it, and you got visibility and support. Skip it, and you got neither.
That one habit did the work of a reward system and an accountability system at the same time, and it cost nothing to build beyond a decision that the report would only ever reflect what was actually captured in the CRM. Notice that it took two things: a manager who made the call matter, and a report people could trust.
How to Drive Technology Adoption & Excellence
For Business Leaders
If adoption is a people problem, the fix isn’t a better feature — it’s a job description. Business leaders, and the managers who report to them, have to:
Lead. Use the system visibly and reference it in every relevant conversation, so it’s understood as the single source of truth, not a side project run by IT.
Prompt. Build adoption into the rhythm of the business — pipeline reviews, shared KPI dashboards, weekly standups — rather than treating it as a one-time training event that gets checked off and forgotten.
Reward. Make the benefit of good data visible and attach it to something people already care about, whether that’s a faster answer in a partner meeting or credit for a well-documented deal. People love to see their name trending on the leaderboard.
Hold accountable. Treat incomplete or stale records the same way you’d treat any other unfinished piece of work — as a performance issue, not a technology complaint. If you’re itching for a fight, tie compliance to compensation, and if someone doesn’t meet their sales goals, at least they can show their documented effort in the CRM notes.
For Front-Office Tech
Business leaders set the tone, but they can’t sit next to every user, and they shouldn’t have to. That’s where the front-office tech team comes in. The teams that do this well work through three steps, in order.
1. Find the managers and teams who are motivated to change. Look for the ones with their own reason to switch, whether that’s a pipeline they can’t see or a report they’re tired of rebuilding every quarter. Self-interest moves people faster than a mandate, and an early win from a willing team does more to convince the rest of the firm than any training session.
2. Work with them well past rollout. Partner with those managers on more than the launch plan. Monitor usage week by week and hold 1:1s with users to learn what’s working, what’s in their way, and where they’re slipping back to spreadsheets. Those conversations surface problems long before a usage report does.
3. Roll up the good and the bad to the leader. Give the business leader an honest picture of where adoption is strong, where it’s stalling, and what could be made better. That’s what lets the leader fix real friction while staying committed to driving adoption. A leader who only hears good news can’t help, and one who only hears bad news starts to waver.
None of this shows up on a vendor’s feature list, because none of it is the vendor’s job. It’s the buyer’s, split between the people who set the expectation and the people who make it work.
The Uncomfortable Conclusion
Blaming the tool is easier than admitting a management gap, which is exactly why it’s the default explanation. But if two firms can take the same system and produce opposite results, the software was never the variable in question. The firms that get this right aren’t the ones with the friendliest interface — they’re the ones where someone with real authority decided that adoption wasn’t optional, and a front-office tech team did the unglamorous work of following through every week until it stopped needing enforcement at all.
The next time a rollout stalls, the right question isn’t “Why is this system so hard to use?” It’s “Who was supposed to be driving, and did they actually show up?”
Frequently Asked Questions About Technology Adoption
Why do technology rollouts fail at private markets firms?
Most rollouts stall because of what happens after go-live, not because of the software. When no one owns adoption, users decide the system is optional and go back to spreadsheets.
Who is responsible for technology adoption?
Two roles share it. A business leader makes adoption non-negotiable, and a front-office tech team, such as a CRM manager, platform team, or someone on the IR side, does the daily work of making it stick.
What can business leaders do to drive adoption?
Lead by using the system visibly, prompt usage through regular business rhythms, reward good data, and hold people accountable for incomplete records.
What should front-office tech teams do to drive adoption?
Start with managers and teams who are motivated to change, stay with them well past rollout to monitor usage and hold 1:1s, and report the good and the bad back to leadership.
How does AI affect technology adoption?
AI can only work with the data people capture. Low adoption leads to weaker AI answers, and the blame lands on the tool again.
