article-time-estimate-icon

6 minute read

Macro Impacts of Micro Innovations

Ab Saraswat

Ab Saraswat

macro impacts
In this article

    What an impressive panel we had on July 19th for Lupl’s Innovators of Law Series! If you missed the webinar, here are some insights from today’s panel.

    Today’s interactive conversation was aimed at demystifying how you can stack small wins that amplify throughout your entire organization. Kalina Leopold, our very own Senior Manager of Customer Success & Growth at Lupl, was joined by Catherine McPherson, Legal Technology Strategist at Barlit Beck LLP, and Nikki Shaver, CEO And Co-founder at Legaltech Hub.

    First, we asked our panel…

    What does innovation mean to you?

    The answers may or may not surprise you! Innovation is taking a new approach to solve a problem. Catherine noted that on a microlevel this means addressing something that doesn’t work anymore. In fact, simply asking the question, how can we make this work better, is in and of itself innovative. Innovation can be client driven, determined by the business or can be due to cultural changes, as we saw in the spring and summer of 2020.

    The first order of business is to define what innovation means to your organization – put it in concrete terms. Additionally, it’s important to note that how you frame the innovation is particularly important and it can mean different things over time. One way to do this is with McKinsey’s Three Horizons of Growth Model, described by Nikki Shaver.

    A great article by the Harvard Business Review describes the three time horizons in simple terms:

    • Horizon 1 Ideas provide continuous innovation to a company’s existing business model and core capabilities in the short-term.
    • Horizon 2 Ideas extend a company’s existing business model and core capabilities to new customers, markets, or targets.
    • Horizon 3 Is the creation of new capabilities and new business to take advantage of or respond to disruptive opportunities or to counter disruption.

    Innovation is about solving a problem in the present, and to do that one must also consider the future and how we can set ourselves up for success down the road.

    If innovation means doing things differently to produce a better outcome…

    How can we shift our perspective on innovation?

    The first step is to shift your thinking to active improvement and quality of service execution. Catherine advised that talent management is very important here. You can start by identifying subject matter experts within your organization and may need to repurpose certain roles / individuals to migrate their talents to things that may not have been anticipated. The thing is: innovation can happen anywhere. And as a result, Nikki pointed out, this is exactly why you need an innovation strategy. Include in this strategy a way to inform the organization regularly; to be effective and successful everyone needs to know their role and why that role is so important (in an outcomes-oriented way).

    Another steppingstone towards innovation is diversity. Insights coming from fresh eyes, or the newest members of the team, can spark creativity. Additionally, having a diverse team has proven time and again to be an effective tool towards successfully implementing change that improves quality of life for employees and clients! Kalina noted that humility, especially from leadership, is required from all team members to create an innovative environment. Humility in this case is the understanding that it’s okay if you are not the one who has the most brilliant idea, and it is crucial to allowing every team member to feel as though they can voice even the craziest of ideas!

    What can an organization do to drive innovation if there is none at a macro level?

    Our panelists agreed that you there are limitations to driving innovation from the bottom up – at some point you must get support and buy in from leadership. That said, there are many ways to drive innovation, even if you feel as though the organization you work for isn’t leading the charge. Here are just a few ideas that came out of the discussion:

    • Run a postmortem on a recent case or trial. Ask those teams what worked and what didn’t work. Not only will you glean insights from this feedback, but you will also instill in your teams a trend of considering workflow and logistics on future projects.
    • Do an innovation audit. This is a listening effort. Sit down with the attorneys and staff members you speak to the most and ask them open ended questions about their work, the bottlenecks, frustrations, pain points, etc. Take the data you retrieve and find the easy wins! If multiple teams or team members report the same pain point, you now have a brilliant starting place for an innovation opportunity.
    • Find out what’s going on the industry. Every time we go to a conference or networking event, we learn invaluable information about what is going on in our industry. Sharing those insights with your organization creates a knowledge base of your competitive landscape and trends in the industry.
    • Tap into FOMO. Now that you’re acutely aware of what others are doing in the space, tapping into the feeling of missing out (or being left out) has the power to keep competitive spirits alive as you move through your own innovation initiatives.
    • Foster support for legal tech strategy through leadership. Being open to ideas and creative an environment requires talent management, as we mentioned earlier. When creating an innovation strategy consider the people in your organization who can help. Perhaps there are 1-2 people can take on a leadership role for the innovation initiative? This allows leadership to maintain their responsibilities while empowering others in the organization.
    • Communicated TNTs. Tiny noticeable things can have a huge impact with less resistance because they enhance daily workflow rather than disrupting it. Host regular meetings with different staff members for a show & tell of what is working so others can see what solutions are there and help to create an innovative environment.
    • Look for Bright Spots. Dan and Chip Heath have written many books over the years, but one process stands out among the rest: finding bright spots. This is about identifying where things are working really well, find out why it’s working so well, and consider how to replicate that in other areas of the organization.

    As we look towards the future, said Nikki, one of the key indicators on whether a firm is an innovator is whether the lawyers have freedom to act outside the legal matter. There is always work that can drive revenue without being associated with a case or trial. New efficiencies within workflow have the power to streamline processes, allowing employees more time to do other, perhaps revenue generating work. And as we all know, this isn’t just a win for the business or support staff, this frees up bandwidth for those focused on billable hours too!

    When it comes to innovation, is it better to ask for forgiveness or permission?

    Overall, the panelists believe that asking for permission is the best way to go; however, if permission does not exist, wherever possible it is okay to take innovation into your own hands. Of course, this means respecting the privacy of the organization, following employee policies and brand guidelines.  

    Outside of the areas where you must get approval, there are many things you can do to drive micro innovations. Here are a few ideas to get you started:  

    • Pay your own way…if you can. We realize this is a less-than-desirable option and not accessible to everyone. But…if your organization doesn’t have a budget for conferences or networking events, that doesn’t mean you can’t go and pay on your own. You may even find that after you go and bring back all the juicy industry details to the team, your organization is willing to reimburse you for some or all the travel.
    • Find internal champions. Find those in the organization that have a louder voice than you and see if you can win their support. Listen to partners, managers, and those in leadership to hear what there interests are to see if align with the ideas you have. Perhaps you can get them to see the value in your creativity and set things in motion! Additionally, if the idea works (and sometimes even when it doesn’t), now you have powerful team members who can also take credit for the positive impact, increasing the chances they may help champion one of your ideas in the future.
    • It’s all about the business case. Create a business case that highlights the strategic value of your idea. How could this innovation save time or money? What problem does it solve? How does the opportunity cost match up to the implementation cost? These are all questions you should be able to answer if you want to pitch a new idea to the powers that be.
    • Engage early and often. Highlighting the positives is a great way to showcase why the new workflow, tech stack, or idea is useful and is already helping the organization. Describing the successes early can help people see the positive impact and lessen the aversion to change.
    • There will always be naysayers. Some skeptics will always be skeptical, and their opinions need to be controlled and isolated, as best one can. It is simply the nature of life that not everyone will be on board. Try not to listen to the negatives too much from people in your organization who you know poo-poo everything.

    Here is one last tidbit: Ask yourself if your organization is creating a space for all the “crazy” ideas – because you never know what may come of it!

    Connect with the panelists on LinkedIn!

    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....