The partners approved the budget. IT set it up over a weekend. Your team sat through two hours of training. And six months later, the matter management system is generating automated reminders that nobody reads, while everyone still tracks deadlines in a shared spreadsheet and chases instructions via WhatsApp.

You are not alone. Legal teams across South Africa — from boutique firms to large in-house departments — are sitting on software investments they cannot get their people to use. The subscription renews. The adoption does not.

This is not a technology problem. It is a stakeholder communication problem — and the hidden costs of that breakdown run deeper than most firms track. There is a structured way to fix it.

Lawyers are trained to be careful. Methodical. Risk-averse by disposition and by professional obligation. When something works — even imperfectly — there is a strong pull toward staying with it. The familiar spreadsheet may be inefficient, but it has not caused a missed prescription date yet.

New software is unproven territory. What if the system loses a file? What if the workflow does not map to how we actually run a matter? What if I cannot find something quickly when I am in court? These are not irrational fears. They are exactly the questions a careful practitioner should be asking.

Most technology rollouts do not answer them. They lead with features, not with benefits framed in legal terms. They hand training over to IT or to an external vendor who has never billed a client by the hour and would not know a practice direction from a practice note.

When your team pushes back on new software, they are usually not being obstructionist. They are doing what lawyers do: identifying risk, protecting their workflow, and defaulting to what they know works.

The fix is not more training sessions or a stern email from the managing partner. It is treating adoption the way you would treat any complex mandate — with a structured plan, clear stakeholder communication, and defined accountability. If you are planning a fresh rollout rather than rescuing a failed one, the fundamentals of managing that kind of change in a legal environment are worth reading first — we cover them in our post on legal tech rollout and change management.

Step 1: Diagnose the Real Resistance Before You Do Anything Else

Before you send another reminder or schedule another training session, find out specifically why your people are not using the tool.

This sounds obvious. It rarely happens. Most firms diagnose adoption failure as stubbornness, then respond with pressure. The actual reasons are usually more specific — and more fixable.

Run individual or small-group conversations with your team. Not a survey. A conversation. Ask three questions: What is your current workflow for the task this software is meant to handle? What specifically concerns you about the new system? What would you need to feel confident using it?

You will almost certainly hear the same three or four barriers coming up repeatedly. Common ones in legal teams: the system does not reflect how matters are actually structured in your practice; the training did not cover exceptions (and legal work is mostly exceptions); nobody explained what happens to files that were already mid-matter when the system went live.

Identify the real obstacles before you design a solution. You cannot fix a problem you have misdiagnosed.

Step 2: Translate Features Into Legal Outcomes — In Their Language

Software vendors sell features. Legal professionals care about outcomes. These are not the same thing.

“Automated task dependencies” means nothing to a litigator managing twenty active matters. “You will see, in one view, every outstanding instruction across all your files — and which ones are at risk of missing their deadline” means something.

When you re-introduce the tool to your team, frame every capability in terms of the work they actually do. Not generic productivity benefits. Specific ones: fewer write-offs because scope is captured upfront, fewer client complaint calls because status updates go out automatically, less time reconstructing a file at billing because the matter log builds as you go.

This is stakeholder communication applied directly to technology adoption. Your team needs to understand what is in it for their billings, their risk exposure, and their ability to run a matter cleanly — not what the software vendor’s marketing team considers a compelling selling point.

Step 3: Build a Re-Engagement Plan With Defined Milestones

A re-engagement plan is not a re-training schedule. It is a structured process that takes your team from where they are now to consistent working use — with specific milestones, a defined timeline, and named accountability.

Start with one use case, not the whole system. Pick the highest-value, lowest-friction workflow: often deadline tracking or matter status updates. Get everyone using it consistently for that single function before expanding.

Set a four-week milestone: everyone logs the agreed function on every new matter opened from a set date. No exceptions. At week four, review — what is working, what is breaking down, what needs to be adjusted.

Build in a feedback loop at weeks two and four. Not to accommodate resistance, but to catch genuine workflow gaps before they calcify into “the system does not work for us.”

By week eight, move to the next use case. Adoption compounds when each step builds on something already working.

Step 4: Appoint a Practice Champion — Not an IT Contact

The single most consistent difference between firms where legal team technology adoption holds and firms where it quietly collapses is the presence of a practice champion.

This is not an IT liaison. It is a practising member of your legal team — a senior associate or junior partner — who uses the system, understands the legal workflow, and serves as the first point of contact when colleagues hit a problem.

IT support is valuable for technical issues. But when a colleague says “I cannot figure out how to handle a matter that spans two practice areas,” they need someone who understands both the system and the legal context. A helpdesk ticket cannot give them that. A practice champion can.

Make the role explicit. Give the champion a small time allocation — even two hours a week is enough to maintain momentum and prevent the slow slide back to old habits.

Once your team is using the core functionality consistently, that is the right moment to look at what you can automate. Our post on legal automation quick wins covers where most legal teams see the fastest measurable returns once adoption is stable.

What This Looks Like in Practice

A mid-sized commercial firm invested in a matter management and billing system after years of running files on shared drives and email threads. Initial rollout: two vendor training sessions, followed by a firm-wide message asking everyone to migrate.

Three months in, fewer than a third of the team was using it consistently. The rest had quietly reverted to familiar workflows, and the partners were attributing it to culture.

Rather than forcing compliance, the managing partner ran brief one-on-one conversations with each practice head. Two issues surfaced repeatedly: the system’s matter structure did not reflect how the M&A team ran complex multi-stage transactions, and the litigators had no clear process for matters that changed scope mid-instruction.

They rebuilt the matter templates to reflect actual practice. They appointed a senior associate — someone the team already respected and went to with questions — as the internal champion. They ran a focused four-week re-engagement on deadline tracking only, nothing else.

Within ten weeks, adoption across the firm was above 85%. A software investment made eighteen months earlier, and largely written off, finally started delivering on what was promised.

Technology adoption in legal teams fails for predictable, fixable reasons. The software is rarely the problem. The approach to rolling it out almost always is.

If this kind of structured, practical approach to running a legal team resonates with how you think about your practice, the Applied LPM Course covers stakeholder communication as a dedicated module — grounded in how legal matters actually work, not adapted from generic change management theory.

Before committing to the full programme, I run a free LPM 101 introductory session where we unpack the core framework together. If unused tools, fractured workflows, or persistent communication gaps are costing your team billable time, it is worth an hour of your time to see whether a more structured approach would make the difference.

Register for the next LPM 101 session

Submitted by Pocket Advisor Legal Solutions