Executing Legal Ops initiatives on time, on budget, and on scope — project management methodology, portfolio governance, and the First 90 Days playbook for new Legal Ops leaders.
---
## Why Legal Needs Project Management
Legal departments routinely manage complex, multi-stakeholder initiatives: CLM deployments spanning six months and three business units, panel rationalisation programs that touch every practitioner, compliance programme implementations with external audit gates, or data governance transformations that reshape how the organisation approaches risk. These initiatives differ fundamentally from the day-to-day work of legal service delivery. They are temporary, goal-specific efforts with defined budgets, stakeholder coalitions, and completion criteria.
Without structured project management discipline, these initiatives drift. Scope expands as stakeholders add requests. Timelines slip by 20%, 40%, or more as dependencies surface midway through. Budgets overrun because no one is tracking incremental costs. The business becomes sceptical of Legal Ops’ ability to execute. The legal leader’s credibility erodes.
Legal Project Management (LPM) is a discipline that brings predictability and accountability to these high-stakes initiatives. It borrows from proven methodologies — the initiation and planning rigour of traditional PMI frameworks, the iterative feedback loops of Agile, and the stakeholder transparency that builds coalition. The result is a structured yet flexible approach to delivering legal innovation on time and on budget.
A companion tool for structuring legal project initiations is the **LPM Project Charter template** (see Appendix A). This template guides you through the critical early conversations: stakeholder identification, success criteria definition, scope boundaries, and risk pre-emption.
## Legal Project Management (LPM) Methodology
The LPM lifecycle comprises five integrated phases. Each phase produces specific outputs and gates that protect you from silent scope creep and unmanaged risk.
### Phase 1: Initiation
**The Objective:** Establish a shared understanding of why the initiative exists, who it serves, what success looks like, and what constraints exist.
**Key Outputs:**
- **Project Charter:** A one-page agreement signed by the GC (or relevant sponsor), the project owner, and key stakeholder representatives. It states the business case, success criteria, scope boundaries, and known constraints (timeline, budget, resource constraints).
- **Stakeholder Map:** Visual identification of all parties who will be affected by or contribute to the initiative. Categorise them as sponsor, core team, active supporters, passive stakeholders, or potential resisters. For each category, define the engagement strategy — how you will keep them informed, engaged, and supportive.
- **Success Criteria:** Measurable, observable statements of what successful completion looks like. For a CLM deployment: “100% of commercial contracts stored in CLM, with metadata 95% complete and obligation-tracking alerts configured. User adoption rate of 80% among legal and commercial teams within 60 days of go-live.” Avoid vague criteria like “system is implemented” or “team is trained.”
**Why It Matters:** The Project Charter is a forcing function for the hard conversation you need with your sponsor before you commit resources and timeline. It surfaces hidden assumptions (the CFO assumes a 3-month timeline; you know it will take 6 months), reveals competing stakeholder priorities, and creates accountability for scope boundaries. A well-executed charter prevents 90% of the mid-project conflicts that derail timelines.
### Phase 2: Planning
**The Objective:** Build a detailed roadmap with milestones, dependencies, resource allocation, and risk mitigation strategies. Planning is the most under-invested phase in legal initiatives; it is also the phase that yields the highest return on time invested.
**Key Outputs:**
- **Scope Statement:** A document that explicitly defines what is IN scope and what is explicitly OUT of scope. This clarity prevents the classic scope creep conversation: “But surely the system should also do X?” The scope statement answers it: “X was evaluated and deliberately deferred to Phase 2 of the roadmap.” Scope statements feel bureaucratic; they are invaluable.
- **Work Breakdown Structure (WBS):** A hierarchical decomposition of all work required. For a CLM deployment: initiate a WBS that captures requirements gathering, configuration, data migration, user training, change management, and go-live support. Break each element into granular work packages (e.g., “requirements gathering” becomes “interview 12 legal users,” “interview 8 commercial users,” “document current contract workflows,” “identify SLA requirements”).
- **Timeline & Milestones:** A month-by-month (or week-by-week for shorter initiatives) roadmap with major milestones. Milestones are gates — decision points where the team assesses whether to proceed, pivot, or stop. A typical CLM timeline: Month 1-2 (requirements and design), Month 3-4 (configuration and data migration), Month 5 (user training and change management), Month 6 (pilot go-live), Month 7 (full rollout and support). Each milestone includes an exit criterion (e.g., “configuration complete and validated against 30 test cases”).
- **Resource Allocation Plan:** Who will do the work? Which internal team members will be released from day-to-day work to dedicate time to the initiative? Which external resources (vendors, contractors, agencies) are required? Allocate people, not just roles. “We will need a project manager” is insufficient; “Sarah Chen will be project manager at 60% allocation from Month 1-7” is actionable.
- **Risk Register:** A living document that identifies known risks (what could go wrong), assesses probability (will this likely occur?) and impact (how severe if it does?), and proposes mitigation strategies. For a CLM deployment, risks include: “Legacy matter data is not clean, and data migration will take 40% longer than estimated” (mitigation: conduct a data quality audit in Month 1, set realistic expectations with the sponsor). Another common risk: “Key technical stakeholder will be unavailable for a month due to another priority” (mitigation: identify a secondary technical contact, schedule their involvement early, document their decisions in writing).
- **Communication Plan:** A schedule of who will be told what, when, and by whom. A monthly steering committee update for the sponsor. Bi-weekly stand-up updates for the core project team. Monthly town halls for the broader user community. Written updates to all stakeholders after each major milestone. Transparency prevents surprises — and surprises are project killers.
**Why It Matters:** Planning takes time upfront, which feels inefficient when momentum is high and everyone wants to begin. The discipline saves you from compounding errors downstream. The WBS prevents you from forgetting critical work. The risk register surfaces the known unknowns and reduces nasty surprises. Resource allocation forces you to make hard trade-off decisions about competing priorities *before* the initiative bogs down.
### Phase 3: Execution
**The Objective:** Deliver the work outlined in the plan with disciplined tracking and course-correction.
**Key Practices:**
- **Agile Sprints for Legal Tech:** For technology-heavy initiatives (CLM, e-discovery platforms, legal analytics tools), organise execution into 1-2 week sprints. Each sprint includes a planning session, daily 10-minute stand-ups to surface blockers, and a retrospective to refine the next sprint. Sprints create visibility into progress and reveal obstacles early enough to course-correct.
- **Weekly Status Reporting:** Produce a one-page status update every Friday (or at a defined cadence). Report: what was completed this week, what will be completed next week, any blockers, any changes to timeline or budget. The status report is a communication tool, not a compliance document. Write it for the sponsor’s inbox, not a filing cabinet.
- **Milestone Tracking:** As each milestone approaches, conduct a structured “gate review.” Did we achieve the exit criterion (e.g., configuration validated against 30 test cases)? If yes, proceed to the next phase. If no, what is the variance, what is the cause, and how will we address it? This discipline prevents you from proceeding into Phase 4 (training and rollout) when Phase 3 (configuration) is incomplete — a common source of go-live chaos.
- **Budget Tracking:** Allocate a monthly budget ceiling for the initiative. Track actual spend against budget weekly. If you are tracking to spend 10% over budget by Month 3, you have time to adjust before Month 6. If you discover a 20% budget overrun in Month 6, it is too late to adjust. Regular budget tracking gives you visibility and control.
- **Scope Change Management:** When a stakeholder requests a change — “Can the system also do X?” — do not say yes or no informally. Document the change request. Assess its impact on timeline and budget. Discuss with the sponsor. Decide: does this change go into the current phase or into Phase 2? Is it worth the timeline delay or budget increase? This discipline prevents “scope creep” — the steady accumulation of additions that turn a 4-month project into a 9-month project.
**Why It Matters:** Execution discipline differentiates projects that deliver on time from projects that don’t. The daily stand-ups surface blockers before they become catastrophic. The milestone gates prevent you from compounding errors downstream. Budget tracking gives you control. Scope change management protects you from creep.
### Phase 4: Monitoring
**The Objective:** Maintain visibility into progress, budget, and risk status. Identify variance from plan early. Escalate and resolve issues before they become showstoppers.
**Key Practices:**
- **Status Reporting to Sponsor:** Monthly steering committee meetings where you update the sponsor on progress, budget, risks, and any decisions required. The agenda is always the same: three slides. Slide 1: milestone status (are we on track?). Slide 2: budget status (are we on budget?). Slide 3: risks and decisions (what could derail us, and what do we need from you?).
- **Stakeholder Satisfaction Pulse:** Mid-way through the initiative, conduct brief “pulse check” interviews with key stakeholders. Are they still aligned on the objectives? Do they have concerns about the direction? Are there silent resisters? Early identification of misalignment allows you to course-correct. Silent resistance discovered at go-live is disastrous.
- **Schedule Compression Analysis:** If the initiative is tracking to slip, analyse whether the timeline can be compressed through additional resourcing, parallel workstreams, or scope adjustment. Can we move from sequential phases to overlapping phases? Can we hire a contractor to accelerate data migration? Or do we accept the timeline slip and re-baseline the plan? This analysis is realistic: some timeline slips are inevitable, and better to plan for them than to pretend the original date is recoverable.
**Why It Matters:** Initiatives do not stay on track without active monitoring. The steering committee updates keep the sponsor informed and aligned. The pulse checks surface misalignment before it becomes resistance. The schedule compression analysis gives you options when reality diverges from the plan.
### Phase 5: Closure
**The Objective:** Formalise completion, capture lessons, and prepare for ongoing operations and benefits realisation.
**Key Outputs:**
- **Go-Live Readiness Checklist:** Before declaring the initiative complete, answer: Are all configurations completed and tested? Are all users trained? Are support resources in place? Is the business prepared to operate the new system? This checklist prevents premature declarations of victory that lead to post-launch chaos.
- **Lessons Learned Document:** Conduct a structured retrospective with the core project team and key stakeholders. What went well? What would we do differently? What did we learn about how our organisation executes change? Document five to seven key findings and attach them to the project record. The next project manager will thank you for this clarity.
- **Handover to Operations:** The project team dissolves, but the system, process, or capability must be sustained. Create a transition plan: who will own the system going forward? What training do they need? What documentation is required? A CLM system handed over without a dedicated owner quickly degrades. Handover discipline prevents post-launch decay.
- **Benefits Realisation Plan:** Did the initiative deliver the benefits outlined in the Project Charter? Conduct a structured assessment 3 months and 6 months post-launch. For a CLM deployment, have obligation tracking alerts reduced risk? Has contract cycle time improved? Have users adopted the system? Document the realised benefits and the gaps. This data informs future initiatives — and justifies future investment in the legal function.
**Why It Matters:** Closure discipline creates institutional memory. The lessons learned document informs the next project. The benefits realisation assessment proves the value of the investment and builds the business case for future initiatives. The handover plan prevents post-launch decay.
## Portfolio Governance
A mature legal function simultaneously manages multiple concurrent initiatives: a CLM deployment (Months 1-6), a panel rationalisation (Months 2-8), a compliance program launch (Months 3-9), and data governance design (Month 1-3 planning). Without portfolio-level governance, these initiatives compete for scarce resources, sponsors become overwhelmed by steering committee proliferation, and the organisation loses sight of the interdependencies between initiatives.
Portfolio governance is the decision-making framework that allocates resources across multiple initiatives and ensures they are sequenced and paced for organisational absorption.
### The Capability Portfolio
Conduct an annual portfolio review. List all Legal Ops initiatives — active, planned, and proposed. Categorise them:
- **Run (Maintenance & BAU):** Sustaining existing systems and processes. CLM system maintenance, external counsel panel management, contract intake administration. These activities are necessary but non-discretionary.
- **Grow (Capability Enhancement):** Initiatives that enhance existing capabilities. Expanding CLM from commercial contracts to employment contracts. Deepening analytics to include matter profitability. These initiatives have clear scope and defined stakeholders.
- **Innovate (New Capability):** Initiatives that create new capabilities. Legal analytics where none existed. AI-assisted contract drafting. These initiatives carry higher risk but unlock significant value.
Allocate your resources across the three categories. A common allocation: 70% to Run, 20% to Grow, 10% to Innovate. The allocation reflects your organisation’s risk appetite and strategic priorities. Some years, the allocation might be 60% Run, 30% Grow, 10% Innovate if you are pursuing aggressive transformation. Other years, 80% Run, 15% Grow, 5% Innovate if the priority is stability.
### The Impact vs. Effort Matrix
For each initiative in the Grow and Innovate categories, map it onto a 2x2 matrix:
**Low Effort** \| **High Effort** \|
\| ————— \| ——————————————— \| ——————————————————————– \|<br>\| **High Impact** \| **Quick Wins** — execute in current year \| **Strategic Projects** — multi-year initiatives with staged delivery \|<br>\| **Low Impact** \| **Nice-to-Haves** — defer or resource lightly \| **The “Not Yet” List** — revisit in future planning cycles \|
This visual forcing function clarifies where to concentrate resources. Quick Wins (high impact, low effort) are your first candidates — they deliver value quickly and build momentum. Strategic Projects (high impact, high effort) are your multi-year bets; you will need to sequence them carefully and commit sustained resources. Nice-to-Haves get deprioritised. The “Not Yet” List is explicitly deferred — not killed, but not resourced today.
### Resource Allocation Across the Portfolio
Identify your scarcest resource — typically, experienced people who can lead initiatives. Map out their allocation across initiatives:
- **Sarah Chen** (Senior Legal Ops Manager): CLM project manager (60%), panel rationalisation sponsor (20%), data governance steering committee (20%).
- **Marcus Williams** (Legal Ops Analyst): Compliance program data integration (100%).
- **Amelia Patel** (Process Specialist): Legal intake process redesign (40%), training for CLM and compliance programs (40%), documentation and knowledge base (20%).
This explicit allocation prevents over-commitment (which leads to burnout and quality degradation) and clarifies trade-offs. If Sarah is 60% allocated to CLM, she cannot take on a new data governance project. If Marcus is fully allocated to compliance program data integration, the CLM data migration will need to be resourced externally.
### Sequencing and Dependencies
Map the initiative timeline and dependencies. Some initiatives are prerequisites for others:
- Data quality audit (Month 1) must precede CLM data migration (Month 3-4).
- Contract process standardisation (Month 1-2) must precede CLM configuration (Month 3-4).
- External counsel panel rationalisation (Month 2-8) should complete before CLM contract value reporting rolls out (Month 6), so that the value reporting reflects the final panel.
Sequencing discipline prevents the common mistake of launching initiatives in parallel that should be sequential. It also reveals opportunities for phased delivery: instead of rolling out CLM to all five business units at once (Month 6), phase it: Unit A (Month 6), Unit B (Month 7), Unit C (Month 8). The phased approach reduces implementation risk and improves adoption quality.
### Governance Cadence
- **Annual Portfolio Review** (typically October/November): Assess all active, planned, and proposed initiatives. Reprioritise based on business strategy changes. Agree on the resource allocation for the coming year.
- **Quarterly Steering Committee**: Each active initiative reports on progress, budget, and risks. The sponsor (typically the GC or CFO) hears a consolidated view and makes any necessary decisions about sequencing, resourcing, or scope.
- **Monthly Initiative-Level Reviews**: Within each initiative, the project manager conducts monthly reviews with the core team and initiative sponsor.
Portfolio governance prevents resource overcommitment and ensures initiatives are paced for organisational absorption. It also provides the discipline to say “not yet” to good ideas — which is far harder than saying yes, and far more important for execution quality.
## The First 90 Days: A Playbook for New Legal Ops Leaders
When a new Legal Ops leader joins an organisation, the first 90 days are disproportionately important. Stakeholders form their assessment of the role’s value within the first quarter. The GC, CFO, and business leaders are asking: Does this person understand our business? Are they connected to our priorities? Will they deliver tangible results, or is this another staff function?
A structured 90-day plan answers these questions and builds momentum. This playbook divides the 90 days into three phases, each borrowing from a proven methodology: **Design Thinking** for discovery, **Lean Startup** for strategy, and **Agile** for execution. The phases are sequential — each builds on the outputs of the prior phase.
### Days 1-30: Design Thinking (Discovery)
### The Objective
Understand the current state with empiricism, not assumption. Gather data on how the legal function actually operates, where it creates value, where friction exists that slows business outcomes, and what the rest of the business perceives about the legal function.
### The Empathy Interview Circuit
Schedule 30-minute interviews with every key stakeholder who interacts with the legal department. The target list:
- **GC / Chief Legal Officer:** Strategic priorities, pain points, political landscape, budget constraints
- **CFO / Finance Director:** Views on legal spend, accruals quality, budget forecasting reliability
- **Head of Sales / Commercial:** Contract cycle time experience, legal bottleneck perceptions
- **Head of HR:** Employment law support quality, policy maintenance, tribunal preparedness
- **Head of IT / CTO:** Technology stack, integration points, data governance, security requirements
- **Head of Procurement:** Vendor management overlap, billing systems, ALSP relationships
- **2-3 lawyers on the legal team:** Day-to-day workflow reality, tool frustrations, process pain points
- **2-3 paralegals / legal support:** Administrative burden, system gaps, knowledge access
The interview format is structured but conversational. Three core questions drive every conversation:
**“What does legal do well for you?”** This reveals the function’s perceived strengths and existing value that must be protected during any transformation.
**“Where does legal slow you down?”** This surfaces opportunities for improvement — and the answers will cluster around predictable themes: contract turnaround time, approval workflow complexity, responsiveness timelines, and self-service capability gaps.
**“If you could change one thing about how you interact with legal, what would it be?”** This is the diagnostic gold. The single-change question forces prioritisation and reveals the highest-impact improvement opportunity.
### The Dark Data Audit
While conducting interviews, simultaneously audit the legal function’s data landscape. “Dark data” is the institutional information that exists but is inaccessible, unstructured, or unknown:
- **Matter data:** Where is it stored? Is it in a matter management system, spreadsheets, email folders, or individual lawyers’ personal files?
- **Contract data:** How many active contracts exist? Where are they stored? Is metadata (party names, key dates, value, governing law) structured and searchable?
- **Spend data:** Is external counsel spend tracked centrally with standardised coding? Or is it distributed across individual cost centre budgets with no aggregation?
- **Knowledge assets:** Where do templates, playbooks, and policy documents live? When were they last updated? Who owns them?
The Dark Data Audit produces a heat map of information accessibility: what you can find, what you know exists but cannot access, and what you suspect exists but cannot confirm. This heat map directly informs technology and data strategy in Phase 2.
The empathy interviews serve a dual purpose. They gather intelligence, and they build relationships. Every stakeholder you interview in Month 1 becomes an ally who feels heard and invested in the outcome. This political capital is essential — you will need it when proposing changes that disrupt established habits in Month 3.
### Deliverable: The Discovery Report
At the end of Day 30, produce a concise (5-7 page) Discovery Report summarising:
- Key themes from stakeholder interviews (anonymised where appropriate)
- The Dark Data heat map
- The top 5 pain points by frequency and impact
- Initial observations on the maturity baseline against best practice frameworks
- A preliminary list of “Quick Win” candidates — improvements that are high-impact, low-effort, and achievable within 60 days
Share this report with the GC. It demonstrates rigour, establishes a shared fact base, and creates accountability for the strategy phase that follows.
### Days 31-60: Lean Startup (Strategy)
### The Objective
Translate discovery findings into a prioritised strategy and roadmap. Define what to do, what not to do, and in what sequence.
### Strategy Formulation: The Priority Matrix
Map every identified opportunity and pain point onto a 2x2 matrix:
**Low Effort** \| **High Effort** \|
\| ————— \| —————————————– \| ————————————————– \|<br>\| **High Impact** \| **Quick Wins** — execute in Days 61-90 \| **Strategic Projects** — roadmap for Months 4-12 \|<br>\| **Low Impact** \| **Efficiency Gains** — batch and schedule \| **The “Not Yet” List** — sequence for later phases \|
The Priority Matrix is a communication tool as much as a planning tool. Showing the GC and CFO that you have systematically evaluated opportunities and consciously decided what not to pursue builds confidence in your judgment.
### Strategic Deferral: The “Not Yet” List
The “Not Yet” list is the most underappreciated output of the strategy phase. It explicitly names initiatives that will be pursued after Months 1-12 rather than immediately, and explains the sequencing logic. Common “Not Yet” candidates include:
- Technology deployments that require process design first (CLM after contract processes are mapped and optimised)
- Enterprise-wide rollouts that benefit from pilot validation first (organisation-wide AI deployment after a controlled proof of concept proves value)
- Projects inherited from prior leadership that do not align with current strategic priorities
- Vendor relationships that carry political importance but lack economic justification
Documenting the “Not Yet” list protects the Legal Ops leader from scope creep and provides a defensible basis for sequencing initiatives effectively. It communicates strategic discipline: you have chosen which battles to fight first.
### Process Mapping Sprint
Select the top 2-3 processes identified in Phase 1 and conduct the process mapping exercise described in Chapter 10. The output is a documented “as-is” and a proposed “to-be” for each process, with a clear articulation of the time, cost, or quality improvement the redesign will deliver.
### Technology Assessment
Based on the process maps and the Dark Data Audit, assess whether existing technology is under-utilised (a common finding) or whether new technology is genuinely required. The assessment framework:
**1. Do we already own a tool that does this?** Many legal departments have technology licences that are partially or entirely unused. Check existing licences before issuing RFPs.
**2. Can we solve this with configuration, not acquisition?** Often, the existing tool can be configured or extended to address the requirement. A SharePoint site with a decision tree may fully address the knowledge base need without requiring a dedicated platform.
**3. If we need new technology, what is the minimum viable deployment?** Start small. A CLM pilot with one contract type and one business unit proves value faster and at lower risk than a full enterprise rollout.
### Deliverable: The 12-Month Roadmap
At the end of Day 60, present a 12-month roadmap to the GC and, ideally, the CFO. The roadmap should contain:
- 3-5 Quick Wins to be delivered in Days 61-90
- 2-3 Strategic Projects to be scoped and initiated in Months 4-6
- The No-Go list with rationale
- A preliminary budget (or resource request) for Months 4-12
- Success metrics for each initiative
### Days 61-90: Agile (Execution)
### The Objective
Deliver visible, measurable results. The Quick Wins identified in Phase 2 are the vehicle.
### Quick Win Selection Criteria
A genuine Quick Win meets all four criteria:
- **Visible:** The improvement is noticed by stakeholders beyond the legal team
- **Measurable:** The benefit can be quantified (time saved, cost reduced, satisfaction improved)
- **Achievable:** It can be delivered within 30 days with existing resources and authority
- **Low-risk:** Failure does not create a worse situation than the status quo
### Common Quick Wins
**Standardised NDA template and self-serve workflow.** If the organisation processes more than 50 NDAs per year and lawyers are reviewing each one individually, a standardised template with a self-serve intake form can be deployed in 2-3 weeks. The visible impact — business users getting NDAs in hours instead of days — is immediately noticed by the commercial team.
**Legal intake portal.** Replace the multi-channel request chaos (email, Slack, phone, hallway) with a single intake form that categorises, routes, and tracks requests. Achievable with existing tools (Jira, ServiceNow, or even a well-structured Microsoft Form) within 2-4 weeks.
**Spend dashboard.** Aggregate existing e-billing or invoice data into a single visual dashboard showing spend by firm, practice area, and matter type. Even a basic Excel or Power BI dashboard, produced in 1-2 weeks, transforms the CFO conversation from “we think we spent about \$X” to “here is exactly where the money went.”
**Outside counsel billing guideline enforcement.** If OCBGs exist but are not actively enforced, select the three most common violations, communicate the enforcement standard to panel firms, and begin flagging non-compliant invoices. This can be done manually as a bridge to automated e-billing enforcement.
### The Feedback Loop
Agile execution requires a tight feedback loop. For each Quick Win:
- Define the success metric before launch
- Measure weekly during the 30-day execution window
- Conduct a brief retrospective at the end: what worked, what didn’t, what to adjust for the next initiative
- Communicate results to stakeholders explicitly — do not assume they will notice
Quick Wins are strategically selected, rigorously executed initiatives that build early credibility and momentum. Quality matters as much as speed. Each well-executed Quick Win raises the standard for future initiatives and reinforces the Legal Ops brand as one that delivers measurable results. Execute fewer wins, but execute them to a high standard.
## In the Trenches
**The 90-Day Turnaround**
Anika Singh was hired as the first-ever Head of Legal Ops at a 600-person Australian professional services firm. The legal team of four lawyers operated with minimal technology infrastructure (Microsoft Office only), no documented processes, and spend visibility limited to annual budget allocation. The GC who hired her set a clear expectation: “The CEO expects us to demonstrate the value of this role within the first quarter.”
Anika ran 18 empathy interviews in her first three weeks. The most consistent theme: the sales team waited an average of 11 days for contract turnaround, which translated to lost sales cycles. The Dark Data Audit revealed a significant asset: 2,400 contracts existed in a shared drive but lacked structured metadata, obligation tracking systems, and template standardisation — a foundation ready to be organised and leveraged.
Her 12-month roadmap included a CLM deployment (Strategic Project, Month 6), a panel rationalisation (Strategic Project, Month 8), and a legal analytics programme (Strategic Project, Month 10). Her No-Go list explicitly deferred AI tools until the data foundation was in place.
For her Quick Wins, she chose three: (1) a standardised services agreement template with pre-approved deviation ranges, deployed through a simple Word template with a one-page user guide; (2) a legal intake form on Microsoft Forms, connected to a shared Planner board for queue visibility; and (3) a monthly spend summary sent to the CFO, built from manually aggregated invoice data.
The services agreement template alone reduced average contract turnaround from 11 days to 4 days for standard deals. The intake form gave the legal team visibility into its queue for the first time — and revealed that 30% of incoming requests were duplicates or could be resolved with a policy FAQ (which became the foundation for a knowledge base in Month 5). The CFO received her first-ever monthly legal spend report and, in Anika’s words, “looked at me like I had performed a magic trick.”
The CEO renewed the Legal Ops mandate at the 90-day review. The role was made permanent, and the budget for the 12-month roadmap was approved.
## Checklist
- **Schedule your first five empathy interviews this week.** Start with the GC, CFO, and Head of Sales. Use the three core questions. Take notes, not recordings — the informality builds trust.
- **Start the Dark Data Audit.** Open your legal team’s shared drive, matter management system, or email archive and answer: Can you find every active contract? Can you determine total external spend for last quarter? Can you locate the current version of every template? The gaps you identify are your data strategy priorities.
- **Draft your Priority Matrix.** Even before completing all interviews, begin mapping what you already know about pain points onto the 2x2. This gives you a working hypothesis to test and refine as you gather more data.
- **Identify one Quick Win you can deliver in 30 days.** It should meet all four criteria: visible, measurable, achievable, and low-risk. Commit to it, resource it, and communicate it. Your credibility depends on delivering at least one tangible result before Day 90.
- **Establish a portfolio governance rhythm.** If you are managing multiple concurrent initiatives, schedule your first quarterly steering committee review. Clarify the resource allocation across Run, Grow, and Innovate work. Document the “Not Yet” list explicitly.
## Suggested Reading
- [PMI Standards and Guides](https://www.pmi.org/pmbok-guide-standards)
- [PMI - What Is Project Management?](https://www.pmi.org/about/learn-about-pmi/what-is-project-management)
- [Agile Manifesto](https://agilemanifesto.org/)
- [PRINCE2 Methodology (AXELOS)](https://www.axelos.com/certifications/prince2-project-management)
- [Prosci - Change Management Resources](https://www.prosci.com/resources)