article-time-estimate-icon

5 minute read

6 ‘must dos’ for speeding up Legal Tech adoption

Matt Pollins

Matt Pollins

6 must do's
In this article

    These days, if you’re a lawyer who hasn’t been affected by the disruption of Legal Tech in delivering legal services, you’ve been trying really rather hard to avoid it.


    As Legal Tech vendors proliferate in the market, as in-house Corporate teams receive increasing pressure to do more with less and as law firms continue to invest in their ever-maturing suite of innovative services, this disruption is not just an interesting trend. It is an inevitability. It’s also a huge investment, drawing on precious time and energy, sparse resources, and, often, the lawyer-client relationship. And so it becomes the responsibility of all lawyers and business teams to arm themselves with a robust strategy for the swift adoption of Legal Tech in their organisations. For the sake of time and value as much as for keeping themselves relevant and successful.


    But, as everyone will admit, the path to adoption of Legal Tech is slow. It’s a battle as prevalent in small legal departments as it is in the magic circle. The same challenges exist for both. To name a few:

    • Lawyers are busy people and the work will always come first.
    • It’s harder to learn a new way of working than it is to carry on doing what you know.
    • Technology often solves some, but not all of the problems lawyers face.
    • There simply aren’t enough successful examples out there to influence adoption.

    What lessons have we learned during the COVID-19 pandemic? We’ve witnessed an unprecedented acceptance of new, and pre-existing, technologies and different working methods since March 2020 to enable a virtual lifestyle – across all industries. In legal, video conferencing software, e-signature tools, mobile apps, and digital workflow tools have irreversibly blended into everyday working habits. These have all been taken up without the luxury of time for intricate internal decision-making, gentle onboarding, and dispersed adoption. It’s been a matter of urgency, and everyone has had to do it.

    But must it really take a pandemic to get everyone using their current tech stack or to roll out new technologies that may just solve fundamental challenges and keep everyone’s pockets happy? We’ve all proven we can adapt more quickly than we might expect. And we’re running out of excuses when it comes to Legal Tech.

    So what can Legal Tech vendors, lawyers, and the business professionals supporting them do to encourage quicker adoption? While you could of course take away all the other options available to users, as COVID-19 did, there are some other moves that you can make to clear the way.

    1. Clearly define and communicate the problem to solve.

    Identifying and proving the business problem is the first hurdle. All too often, this critical first step is mishandled – with catastrophic consequences. A complex task, ‘the business’ attempts to solve the problems that they perceive to exist without thoroughly integrating lawyers into the discovery process – whether that’s due to lack of engagement, a persuasive individual in need, or a comprehensive list of assumptions. This is not an easy path to organisational adoption.

    As Simon Sinek has observed, ‘true innovation is solving a real problem’ and for adoption to really take hold, the technology must have a direct benefit to its users. It requires Legal Tech teams to spend time with lawyers, to understand the ways in which they operate, and to get to the heart of the key challenges that they face – well in advance of their search for a solution. Once a solution has been found, they must clearly communicate the day-to-day impact that it will have and the problems that it solves. The quality of this communication will hugely influence the likelihood of adoption.

    2. Build the right Project Team.

    Assigning sole responsibility for the successful rollout of any technology to one individual is like asking someone to assemble Ikea furniture on their own. It’s much harder than it looks! For each new implementation, you will need a Project Team. At a minimum, this might consist of:

    • At least 1 lawyer, who is active on legal matters and has been with the business for a minimum of 2 years. This person knows what it’s really like in practice and will be the best person to advise on how things are done and what really counts to the user.
    • A Project Lead, who is dedicated to delivering the solution and has suitable influence at the organisation. At a law firm, this might be a leader in Innovation, Digital Transformation, Knowledge, or even Legal Tech. For in-house teams, this might be a Legal Operations Manager or Information Technology Lead.
    • Depending on the size of the organisation, a trainer is ordinarily responsible for teaching lawyers and other business users how to operate the organisation’s tech stack. This is critical to merging workflows with current technologies and advising on current best practices.

    This team should work together to come up with a plan and really get to grips with what the lawyers are being asked to do, well ahead of onboarding. Which leads nicely to my next tip.

    3. Have a plan. And stick to it.

    It’s no use tackling adoption without a game plan, no matter the size of the organisation. Here are some of the key factors to consider:

    Is it a mandatory rollout (for example due to expiring software) or a recommended one? This will dictate your timeline.
    What is the scope of adoption? It doesn’t have to cover every feature of the solution. Clearly identify what is in and out of scope.
    What are your adoption targets in year 1 and year 2? Be aggressive, get numbers down on paper, and put the onus on the users to deliver them. This will drive you towards success.
    Can they do it on their own or do they need training? Consider the parties involved and the variety of training options you may need to make available. Think about the impact on your timeline.
    Does it really make sense to onboard everyone at once? Some of the best results come from small, quick wins that prove the success of the solution. This gives you time to identify challenges and overcome them before any damage can be done. Pick a discreet group of enthusiasts to pilot the solution thoroughly and make them feel part of something special. Better yet, overwhelm them with genuine incentives.
    Once you’ve agreed to your plan, do your best to work together and see it through. It will almost certainly change and deadlines will move. But if you use it as your anchor to keep you on the straight and narrow, you’re more likely to achieve your adoption goals.

    4. Take risks and fail fast.

    When video conferencing became the new normal in 2020, we forgave each other (and the tech) immediately for challenges that arose during the course of meetings, and we continue to do so. Whether it’s user error or feature shortfalls, the expectation for virtual meetings is low and a truly smooth experience can be unusual. But we laugh it off, we adapt and we do better next time. If anything, it’s brought us all closer. At Lupl, our bespoke ‘You’re on mute!’ paddles have become a highly sought-after commodity with customers across the globe due to the universal issues that we all continue to face with chatting away to an audience while on mute.

    If we took the same attitude with Legal Tech solutions, we’d take up the use of the tools much faster. Project teams tightly control the approach to onboarding for fear of the impact of a poor experience on users and of wasting their time. I don’t blame them – I would too. But if users could be as agile as they have been with video conferencing, they’d be receptive to failures and become part of the growth of the tech and, consequently, of their organisation.

    If we all waited until everything was perfect, tried and tested (which, let’s face it, it can’t be – there are too many variables from one organisation to the next), we’d still be using fax. It’s up to lawyers on every side of the fence to take risks, embrace failure, and do better quicker by learning from their experiences. Project teams, particularly Project Sponsors, should encourage their users to put their foot down and fail fast. It’ll pay dividends.

    5. Celebrate your successes!

    It’s a simple thing that’s often underestimated. When something goes well, tell everyone else about it! Plaster it over your intranet, write it up in a newsletter, take over weekly meetings, put together a video short…spread the good news and encourage those who might be falling behind.

    6. Collaborate with your vendor.

    If you’re not quite hitting your adoption targets or you’re coming up against challenges, speak to your Vendor. It’s likely that they’ll have ideas and ways to support you. They may even have specialist expertise in-house that could transform your path to adoption. For example, at Lupl we have specialist PMP and Legal Project Management professionals that can provide upskilling workshops to complement our platform.

    Furthermore, vendors themselves benefit enormously from hearing about the adoption challenges that users face, as they navigate their never-ending development journey. You’ll be doing each other a service.

    Final Thoughts…

    Rallying the adoption of Legal Tech is hard. But you can make it so much easier for yourself with an organised strategy, the right team, and a ready usership. It’s tricky enough to get past all the obstacles of procurement when taking on technology. Legal Tech teams must take a positive, forward-thinking, and faster-paced approach to adoption in order to meet the expectations of the market and to realise the vast investment of their time and money more speedily. This includes preparing and persuading lawyers to be involved from the outset and to get their hands a little dirty.

    Set yourself up for success right from the beginning and work towards measurable, achievable goals. We know that the users can do it, we have the evidence to prove that now. Empower them, incentivise them and make them responsible for taking on the task of adoption. If it solves a core business need, there’s no longer any need to roll out at a snail’s pace.

    In this article

      More legal tech insights we think you'll love

      The cost of over-dependence on AI

      AI saves us time, boosts productivity, and lets us do...

      # Lupl Workstream Design Principles: A Practical Guide to Legal Project Management for Lawyers Legal project management works when your setup is simple, ownership is clear, and statuses are unambiguous. This guide shows how to turn existing processes and checklists into a lean, reliable Workstream. Lupl is the legal project management platform for law firms, making it easy and intuitive to apply these principles. It also supports moving your work from Excel, Word tables, or if you are transitioning from Microsoft Planner, Smartsheet, or Monday. You will learn what belongs in a Workstream, a Task, or a Step, and which columns to use. If you want practical project management for lawyers, start here. **Excerpt:** Legal project management works when ownership, dates, and statuses are clear. This guide shows lawyers how to turn checklists into Lupl Workstreams with the right columns, Tasks, and Steps. Use it to standardize project management for lawyers, reduce follow ups, and move matters to done. --- ## How to organize your work with Workstreams, Tasks, and Steps Workstreams, Tasks, and Steps are three different types of objects in Lupl. They form a simple hierarchy. Workstreams contain Tasks. Tasks may contain optional Steps. This hierarchy aligns with standard project management. In project management, you break work into projects, deliverables, and subtasks. Lupl adapts this for lawyers by using Workstreams, Tasks, and Steps. This makes it easier to map legal processes to a structure that teams can track and manage. * **Workstream.** Use when you have many similar or related items to track over time. Think of the Workstream as the table. * Examples: closing checklist, court deadlines, pretrial preparation, regulatory obligations, due diligence, local counsel management. * **Task.** A high level unit of legal work. A key deliverable with an owner and a due date. Tasks are the rows. * Examples: File motion. Prepare Shareholder Agreement. Submit Q3 report. * **Step.** An optional short checklist inside a single Task. Steps roll up to the parent Task. * Examples: Draft. QC. Partner review. E file. Serve. ### Quick test * If it can be overdue by itself, make it a Task. * If it only helps complete a Task, make it a Step. * If you need different columns or owners, create a separate Workstream. --- ## Do you need to track everything in Lupl Not every detail needs to be tracked in a project management system. The principle is to capture what drives accountability and progress. In Lupl, that means focusing on deliverables, not every micro action. * Use the level of detail you would bring to a weekly team meeting agenda. * Position Tasks as key deliverables. Treat Steps as optional micro tasks to show progress. * Example: You need client instructions. Do not add a Task for "Email client to request a call." Just make the call. If the client approves a key deliverable on the call, mark that item Approved in Lupl so the team has visibility. --- ## Start with the Core 5 columns Columns are the backbone of a Workstream. They define what information is tracked for each Task. In project management terms, these are your core metadata fields. They keep everyone aligned without overcomplicating the table. Keep the table narrow. You can add later. These five work across most legal project management use cases. 1. **Title.** Start with a verb. Example: File answer to complaint. 2. **Status.** Five to seven clear choices. Example: Not started, In progress, For review, For approval, Done. 3. **Assignee.** One named owner per row. If you add multiple assignees for collaboration, still name a primary owner. 4. **Due date.** One date per row. 5. **Type or Category.** Show different kinds of work in one table. Example: Filing, Discovery, Signature, Approval. **Priority.** Add only if you actively triage by priority each week. If added, keep it simple: High, Medium, Low. --- ## Add up to three Helper columns Lupl includes a set of pre made columns you can use out of the box. These allow you to customize Workstreams around different phases or stages of a matter. They also let you map how you already track transactional work, litigation, or other processes. Helper columns are optional fields that add context. In task management, these are similar to tags or attributes you use to sort and filter work. The key is to only add what you will update and use. Pick only what you will use. Stop when you reach three. * Party or Counterparty * Jurisdiction or Court * Phase * Approver * Approval, status or yes or no * Signature status * Risk, RAG * Amount or Number * External ID or Client ID * Document or Link * Docket number * Client entity **Guidance** * For Task Workstreams, prefer Approver, Approval, Risk. The rest are more common in Custom Workstreams. * Aim for eight columns or fewer in your main table. Put detail in the Task description, attachments, or Steps. --- ## Simple rules that keep your table clean Consistency is critical in project management. A cluttered or inconsistent table slows teams down. These rules ensure your Workstream remains usable and clear. * Only add a column people will update during the matter. If it never changes, set a default at the Workstream level or set a default value in the column. * Only add a column you will sort or filter on. If you will not use it to find or group work, leave it out. * If a value changes inside one Task, use Steps. Steps show progress without widening the table. * Keep columns short and structured. Use Description for brief context or instructions. Use Task comments for discussion and decisions. Link to work product in your DMS as the source of truth. * One accountable owner per Task and one due date. You can add collaborators, but always name a primary owner who moves the Task. If different people or dates apply to different parts, split into separate Tasks or capture the handoff as Steps. * Add automations after you lock the design. Finalize columns and status definitions first. Then add simple reminders and escalations that read those fields. --- ## Status hygiene that everyone understands Status is the single most important column in project management. It tells the team where the work stands. Too many options cause confusion. Too few cause misalignment. In Lupl, keep it simple and consistent. * Five to seven statuses are enough. * Use one review gate, For review or For approval. Use both only if your process needs two gates. * One terminal status, Done. This is the end state of the Task. Use Archived only if you report on it or need it for retention workflows. --- ## When to split into multiple Workstreams In project management, it is best practice to separate workstreams when workflows, owners, or audiences diverge. Lupl makes this easy by letting you create multiple Workstreams for one matter. Create a new Workstream if any of the following are true. * You need a different set of columns for a chunk of work. * Ownership or cadence is different, for example daily docketing vs monthly reporting. * The audience or confidentiality needs are different. **Signal** * If half your rows leave several columns blank, you are mixing processes. Split the table. --- ## Decision tree, three quick questions Use this quick framework to decide where an item belongs. This is the same principle used in task management software, adapted for legal workflows. 1. Is this a list of similar items over time, or a discrete phase of the matter * Yes. Create a Workstream. 2. Can it be overdue by itself, and does it need an owner * Yes. Create a Task. 3. Is it a step to finish a Task and not tracked on its own * Yes. Create a Step. --- ## Common mistakes to avoid Many project management failures come from overdesigning or misusing the structure. Avoid these mistakes to keep your Workstreams lean and effective. * Wide tables with many optional columns. Keep it to eight or fewer. * Two columns for the same idea, for example Status and Phase that overlap. Merge or define clearly. * More than one approval gate when one would do. It slows work and confuses owners. * Mixing unrelated processes in one table, for example signatures and invoice approvals. --- ## Build your first Workstream Building a Workstream is like setting up a project board. Keep it light, pilot it, then refine. Lupl is designed to let you do this quickly without heavy admin work. 1. Write the Workstream purpose in one sentence. 2. Add the Core 5 columns. 3. Add at most three Helpers you will use. 4. Define clear Status meanings in plain words. 5. Set defaults for any value that repeats on most rows, for example Jurisdiction. 6. Add two light automations, a due soon reminder and an overdue nudge. 7. Pilot for one week and adjust. --- ## Where this fits in legal project management Use these principles to standardize project management for lawyers across matters. Keep structures consistent. Reuse column sets and status definitions. Your team will find work faster, reduce follow ups, and close loops on time. --- ### On page SEO helpers * Suggested title tag. Lupl Workstream Design Principles, Practical Legal Project Management for Lawyers * Suggested meta description. Learn how to design lean Lupl Workstreams for legal project management. Get clear rules for Tasks, Steps, statuses, and columns to run matters with confidence. * Suggested URL slug. legal-project-management-for-lawyers-workstream-design

      Lupl Workstream Design Principles: A Practical Guide to Legal Project Management for Lawyers

      Learn why large‑firm lawyers are ditching Excel checklists for dynamic,...

      Do AI Agents Have An Identity? Notes from InfoSec Discussions

      Agentic AI is in its early phases but advancing fast....