How to Train a Legal Team on New Software

Aug 26

11 min read

Most failed software implementations in law firms are not failures of software. The system works as specified, the data migrates acceptably and the vendor performs its obligations, yet within a few months the fee earners have gone back to their old habits and the new platform is used only by the person who selected it. The usual cause is that legal software training was treated as a single event at the end of the project rather than as a programme that begins before purchase and continues well after go-live.

Lawyers are a demanding audience for training. They are accustomed to being the person who knows the answer, they bill their time in small units and they perceive time spent learning a system as time taken from fee-earning work. They are also, quite properly, cautious about anything that touches client confidentiality, deadlines and the accuracy of the record. A training programme that ignores those realities will be attended grudgingly and forgotten quickly. One that respects them, by being short, role-specific, tied to real matters and visibly endorsed by the partners, has a far better prospect of changing behaviour.

This article sets out a practical method for planning and delivering legal software training in a firm of any size, from a sole practitioner adopting a first system to a multi-partner practice replacing an established one. It addresses the preparation that precedes training, the structure of sessions for different roles, the handling of resistance, the support available after go-live and the means of measuring whether the training has worked. The emphasis is on procedure and on the trade-offs a firm must make with limited time and attention.

Why legal software training fails

It is worth identifying the common causes of failure, because each suggests a design principle for the programme. The first is timing. Training delivered weeks before go-live is forgotten; training delivered weeks after is irrelevant, because users have already devised workarounds. The second is generality. A tour of every feature, delivered to a room containing partners, associates, secretaries and accounts staff, teaches none of them what they need to do on Monday morning.

The third cause is the absence of a defined standard. If the firm has not decided what must be done in the new system, for example that every new matter must be opened there, that all time must be recorded there and that all correspondence must be saved there, then users will treat the system as optional. The fourth is a lack of visible sponsorship. If the senior partners continue to circulate documents by email and ask for paper files, the message to everyone else is clear. The fifth is a failure to provide help at the point of need. A user who cannot remember how to attach an email to a matter at five o'clock on a Friday, and who has nobody to ask, will revert to the old way, and the habit may not return.

Preparing the ground before any training begins

Define what the firm expects people to do

Before designing a single session, the firm should write down, in plain terms, the working rules that will apply after go-live. These are not features; they are obligations. Examples include opening every matter in the system before work begins, recording time contemporaneously, filing every incoming and outgoing document to the matter, and obtaining client signatures through the system's signature function. Each rule should have an owner and, where possible, a date from which it applies. The training then becomes the means of teaching people how to comply with rules the firm has already adopted, which is considerably easier than persuading people to use a tool they do not yet understand the purpose of.

Map roles and tasks

A law firm contains several distinct user groups, and their needs differ substantially. Partners and supervising attorneys-at-law need to review matter status, approve bills, check deadlines and supervise junior colleagues. Associates and fee earners need to open matters, record time, draft and save documents, manage tasks and communicate with clients. Legal secretaries and paralegals need to manage correspondence, calendars, document assembly and filing. Accounts staff need to generate and reconcile bills, record receipts and manage client account entries. A receptionist or intake administrator may need only to record enquiries and conflict checks.

For each group, the firm should list the ten or so tasks that account for most of its daily use. Those tasks form the syllabus. Features that fall outside them can be left for later, or for self-directed learning, and the group should not be burdened with them in the first sessions.

Appoint champions and a project lead

Every implementation benefits from a project lead with the authority to make decisions, and from one or two champions drawn from the user groups themselves. A champion is a colleague who learns the system early, becomes the first point of contact for questions and gives feedback on what is working. Champions should be chosen for credibility and patience rather than seniority, and their time should be recognised in the allocation of work. In a firm with few people, one person may combine the roles, but the roles should still be named.

Prepare a realistic environment

Training on an empty system, or on invented matters that bear no resemblance to the firm's work, is of limited value. Where possible, the firm should prepare a training environment containing anonymised or fictional matters that mirror its real ones: a conveyancing file, a litigation file with a hearing diary, a corporate matter with a document set, and a client with several matters. Users learn faster when the scenario is familiar, and the trainer can demonstrate the particular workflows of the firm rather than abstract features. Firms must take care not to place real client data in any environment used for demonstration to a wider audience than those entitled to see it.

Designing the training programme

Sequence the learning

A sound programme moves through four stages. The first is orientation, in which all staff learn why the firm is changing, what will change in their working day and what the timetable is. The second is role-based instruction, delivered in small groups, concentrating on the core tasks identified for each role. The third is supervised practice, in which users perform real work with a champion or trainer available. The fourth is consolidation, which occurs some weeks after go-live and addresses the problems that have actually emerged.

The table below illustrates one way a firm might allocate effort across those stages. The proportions are a planning suggestion rather than an industry standard, and they should be adjusted to the complexity of the platform and the experience of the staff.

Stage	Purpose	Format	Principal audience
Orientation	Explain the reasons for change and the working rules	Short briefing led by a partner	Everyone
Role-based instruction	Teach core tasks for each role	Small group workshops with exercises	Role groups
Supervised practice	Build confidence on live work	Floor-walking, drop-in sessions, champions	Everyone
Consolidation	Fix problems, introduce further features	Short refresher sessions	Role groups and individuals

Keep sessions short and task based

Sessions of between forty-five and ninety minutes tend to hold attention better than half-day lectures, and they are easier to fit around hearings and client appointments. Each session should have a single stated objective, such as "open a matter, conflict check it and issue an engagement letter for signature", and should end with each participant having done it. Demonstration by the trainer should be brief; most of the time should be spent with participants performing the task themselves. Written step-by-step guides, tailored to the firm's own procedures and kept short, should be circulated afterwards so that users can refer to them when the trainer is not present.

Use the firm's own matters and vocabulary

Generic training materials use generic terms. A firm that calls its files "matters" and its fee earners "attorneys-at-law" will find that users engage better when the materials use the same words. Where the system uses terminology that differs from the firm's, the training should state the equivalence clearly, and the firm should consider whether the system can be configured to match its own language. The same principle applies to forms and templates: training on the firm's own engagement letter, its own conflict check form and its own bill layout is more persuasive than training on a sample.

Provide different depth for different people

Partners rarely have time for lengthy classroom sessions, and a partner who feels exposed in a group of juniors may withdraw. Short, private sessions of perhaps thirty minutes, focused on the dashboards, approvals and reports the partner will actually use, are often more effective. Equally, staff who are comfortable with technology should be given the opportunity to explore beyond the core syllabus and to act as local experts, while staff who are anxious should be offered extra practice and reassurance without embarrassment.

Addressing resistance and anxiety

Resistance to new software is not a character defect; it is usually a rational response to perceived cost. Users fear that the system will slow them down, that they will make mistakes in front of colleagues, or that it will expose how they work. In legal practice there is an additional concern that technology may introduce risk, particularly to confidentiality and to the accuracy of deadlines. A training programme should respond to each concern directly rather than dismiss it.

Where users fear a loss of time, show how the new workflow removes duplication, for example by drafting from stored client details rather than retyping them.
Where users fear error, explain the safeguards in the system, such as access permissions, audit trails and version history, and allow practice in an environment where mistakes carry no consequence.
Where users doubt the purpose, ensure that a partner explains the commercial and professional reasons, including improved supervision, better recording of time and a more reliable record of advice given.
Where users resist because the old method works for them, identify which steps of the old method the firm can no longer accept, and be clear that the working rules are not optional.

The firm should also listen. Early users often identify genuine weaknesses in configuration, such as a field that is mandatory but unnecessary or a workflow that requires too many steps. Adjusting the system in response demonstrates that feedback is valued and removes real obstacles to adoption.

The role of leadership

No amount of training compensates for inconsistent leadership. The partners must follow the working rules themselves and must be seen to do so. They should open their own matters in the system, record their own time and request information from the system rather than from a secretary. They should refuse to accept paper or emailed work that bypasses the process, politely redirecting colleagues to the correct method. In reviewing files, they should expect to find the record complete in the system and should treat omissions as a supervision matter.

The partners should also set aside the time that training requires. A programme scheduled for lunchtimes and evenings communicates that learning is an afterthought. Protected time during the working day, with fee-earning targets adjusted accordingly during the training period, communicates the opposite. The cost is real, and the firm should budget for it as part of the cost of implementation rather than treating it as free.

Support after go-live

Floor-walking and drop-in sessions

In the first two weeks after go-live, a trainer or champion should be physically or virtually available throughout the working day, ready to resolve small problems before they harden into resentment. Drop-in sessions at fixed times, where anyone may bring a question, allow users to ask for help without feeling that they are interrupting.

A simple route for questions and issues

The firm should designate a single channel for questions, whether a shared mailbox, a chat group or a log kept by the project lead. Each question should be recorded, answered and, where it indicates a gap in the training or the documentation, used to improve them. Recurring questions are evidence that a step is unclear and should prompt either a revised guide or a configuration change.

Quick reference material

One-page guides for the most common tasks, kept in a location every user can reach, reduce the burden on champions and shorten the time to competence. Short recorded demonstrations of core tasks, made by the firm's own people using its own matters, serve the same purpose and can be used to train new joiners later. The guides should be reviewed whenever the system or the firm's procedures change, because outdated instructions generate more frustration than none.

Measuring whether the training has worked

Attendance at sessions is not evidence of competence, and a user who has attended a session has not necessarily changed behaviour. The firm should decide in advance what it will measure and should do so at defined intervals, such as two weeks, six weeks and three months after go-live. Useful indicators are largely observable from the system itself and from the firm's own records.

The proportion of new matters opened in the system rather than elsewhere.
Whether time is being recorded daily or in arrears.
Whether correspondence and documents are being saved to matters, assessed by sampling a small number of live files.
Whether bills are being generated from the system without manual reconstruction.
Whether tasks and deadlines are being diarised in the system rather than in personal calendars.
The nature and number of support questions, and whether they are diminishing or changing in character.

The firm should supplement these measures with short conversations with users. Asking what they find difficult, what they still do outside the system and why will yield information that no usage report supplies. Where a pattern emerges, for example that a particular group still keeps a separate spreadsheet of deadlines, the firm should investigate why and respond with additional training or a change in configuration, not with exhortation.

Onboarding new joiners and sustaining capability

A programme that trains the existing team well but ignores later arrivals will see standards decay within a year. The firm should incorporate system training into its induction for every new joiner, with a short role-based session in the first week and a check, perhaps a month later, that the new person is following the working rules. Recorded demonstrations and the written guides described above make this inexpensive.

The firm should also review capability periodically. Platforms evolve, and new features may offer real benefits, but they will be adopted only if users learn of them. A brief regular session, perhaps once a quarter, in which a champion shows one improvement or one underused feature, keeps the system valued and prevents the gradual narrowing of use that afflicts many firms. Firms that charge per user for software often find that the cost of adding staff discourages broad access, which in turn limits who is trained; where pricing is per firm with unlimited users, as Legalytech's is, the firm can train every member of staff, including part-time staff and support personnel, without considering the marginal cost of a further licence.

Managing risk during the transition

A change of system is also a period of heightened professional risk. Deadlines may be diarised in two places, or in neither. Client money entries may be made in the old and new systems inconsistently. Documents may be saved in the wrong matter. The training programme should address these risks explicitly. Users should be told clearly which system is the system of record from the go-live date, how outstanding items from the old system will be transferred, and who is responsible for verifying that limitation dates and other critical deadlines have been carried across correctly.

It is prudent for a firm to run a short period of parallel checking for critical matters, in which a supervising attorney-at-law compares the new system's diary entries against the old for matters with imminent deadlines. Training should also cover the basic security practices that accompany the system, including password hygiene, the use of multi-factor authentication where available, the correct assignment of permissions and the handling of client information on personal devices. The firm should record that this training took place, since regulators and insurers increasingly expect firms to demonstrate that staff are trained in the handling of confidential data.

Practical next steps

Write the firm's working rules for the new system as a one-page list of obligations, and obtain partner approval of it.
List the user groups and the ten principal tasks for each, and use those lists as the syllabus.
Appoint a project lead and at least one champion, and allocate protected time to both.
Build a training environment using fictional matters that resemble the firm's real work.
Schedule short, role-based sessions in the weeks immediately before go-live, and a second round soon after.
Arrange floor-walking support and a single channel for questions during the first two weeks.
Prepare one-page guides and short recorded demonstrations for the most common tasks.
Decide the measures of adoption and review them at two weeks, six weeks and three months.
Add system training to the induction of every new joiner.

How practice management software supports the process

Training is easier when the system itself is organised around the way a firm works: matters, clients, documents, tasks, billing and signature in one place, so that a user learns a single environment instead of several. Legalytech provides a cloud practice management platform of that kind for solo and small firms, and its structure allows a firm to build its training around a small number of coherent workflows and to monitor adoption from the same records its staff already use.

This article is provided for general information only and does not constitute legal advice. Practitioners should consult the rules of their own jurisdiction and regulator.