Expand the definition to include process and Self-Service

Technology can accelerate a good process, but it cannot rescue a broken one. Many technology requests in Legal are so broad that no solution can truly meet the brief. "We need a system to manage all matters" or "we need AI for contracts" sounds decisive, but it hides the real work: defining which workflows matter most, what success looks like, and who will run the process once the tool exists.

Before drafting specifications, it helps to map the work as it actually happens: how requests arrive, how they are triaged, where they stall, how long review cycles take, and what information is missing when a file starts. Only then can a team identify the smallest set of requirements that would make a tool useful rather than decorative.

Corporate law departments often wait for IT or sourcing teams to write requirements, evaluate vendors, and run implementation. That can take a long time, and the end product still may not fit Legal's operating reality. At the same time, few lawyers have the time - or training - to act as product owners for systems like matter management, document automation, or analytics.

A practical way through this is to narrow the scope and build basic capability. Define one or two use cases that matter (for example: standardising intake and triage, improving visibility into workload, or reducing cycle time for a common contract type). Assign clear ownership. Build simple internal standards for how the work will be recorded and routed. Some departments use short skills check-ins to understand technology proficiency inside the team and across external providers, so training and support can be targeted where it will actually stick.

Even the best ideas fail when a team is buried in backlog and interruptions. If yesterday is never soon enough, improvement work gets squeezed out. The fastest way to create traction is to start with three or four changes that have immediate impact and do not depend on new tools.

Common examples include tightening intake channels, introducing triage rules, building simple templates and playbooks for repeat requests, and shifting routine tasks to the right roles. These moves are not glamorous, but they reduce noise, create breathing room, and give the team proof that change is possible.

What gets measured gets done. If innovation is treated as optional, it will always lose to urgent files. Traction improves when the department defines a small set of indicators that reflect value rather than activity - for example: time protected for strategic work, cycle time for common requests, intake volume by channel, and delegation by task. Make improvement part of objectives and protect time for it, so the team is rewarded for building better processes - not just for being fast and available.

With clearer rules for engaging Legal, more self-service, and less senior time spent on routine matters, teams create room for meaningful improvement and higher-value work. Innovation does not have to be complicated - it needs to be designed into the workflow.

• Bucket the last month of work by effort level and value: strategic projects, complex matters, routine advisory, administrative support.
• Publish a one-page "When to Call Legal" guide that clarifies triggers, thresholds, and expected lead times.
• Define intake rules in plain language: who can submit requests, through which channels, and what information is required.
• Pick the top 5 recurring requests and build simple templates, playbooks, or self-service guidance to handle them faster.
• Track a small set of workflow metrics monthly (cycle time, strategic hours protected, delegation by task) and adjust as you learn.