Legal Project Management

I didn’t expect my last post about applying a project management approach to legal work to spark such a strong response - but I completely understand why. The challenges in-house legal teams face are universal, regardless of company size, industry, or location: ❌ Misalignment between legal and business teams ❌ Missed deadlines due to a lack of planning ❌ Confusion around roles and responsibilities between legal and other teams ❌ Clients expecting more than we can deliver ❌ Burnout from overloaded teams and unclear priorities ❌ Struggling to manage external law firms without clear guidelines ❌ Delayed responses from other departments Legal work often feels like a constant scramble, right? And that’s exactly why I’m such a strong proponent of Legal Project Management (LPM). I realized that by incorporating LPM principles into legal work, we can turn that chaos into something structured, predictable, and manageable. So, here are the most basic LPM principles I believe every in-house legal team can benefit from: 📌 Define objectives & scope Establish clear business objectives upfront Document what’s in and what’s outside of scope Describe assumptions (but always confirm them upfront!) Create formal scope statements for key matters 📌 Break down activities & timelines Implement Work Breakdown Structure (WBS) Break project into smaller, manageable tasks Map dependencies and critical paths Set clear milestones and deliverables 📌 Assign roles & responsibilities Deploy RACI (Responsible, Accountable, Consulted, and Informed) matrix for all projects Define decision rights and escalation paths Establish clear accountability frameworks Make sure that other stakeholders understand what is legal responsible for and what is not 📌 Plan & manage budgets Set matter-specific budgets for external legal spend Track spend against forecasts Monitor external counsel costs Use billing guidelines for external law firms 📌 Identify & mitigate risks Create risk registers (not only for “legal” risks but also for “project” risks) Assess probability and impact Develop risk management strategies Monitor both legal and project risks 📌 Structure communication Establish regular stakeholder updates Create communication protocols (how and to whom do you report progress, issues and risks) Use technology to report project progress Set clear reporting lines 📌 Control change management Document change requests Assess impact on scope/timeline Update project baselines Now, I want to hear from you: How are you bringing more structure into your legal work? Are you applying any of the LPM principles in your work?

3 Workflows I've Automated for in-house teams. ① Ask Legal ② Procurement ③ Contract Review (not just the review!) 1. Ask Legal [or any department for that matter 🤷🏼♀️] You've heard me talk about legal teams and knowledge management. Long story short, your legal team is answering the same 20 questions over and over 😵💫 A simple way to save a CHUNK of time answering questions from the business (enabling them to go faster) ALL while having complete control & keeping a human in the loop? ↪️ Set up an 'Ask Legal' bot in your comms platform. ↪️ Sync it with your knowledge base (e.g GDrive/Notion/Sharepoint). ↪️ Set up your custom instructions (Want it to tag Bob on privacy questions only, specifically on a Tuesday? No problem).  ↪️ Don't want the answer to go straight out to the business without reviewing it first? Cool, turn on co-pilot mode. The result? 60-80% fewer repetitive queries. Your team focuses on the high value things that need a human lawyer. 2. Procurement Businesses have 100's of tools, but when departments don't speak to each other you end up with duplicate tools & subscriptions 😭 💵 🚽.  What if there was a way for the business to find out in <1 minute if there was a tool available that covered their needs, before needing to spend some hard secured department budget? Moreover, what if I told you, they could kick off the internal procurement process from the comfort of your comms platform? Team member : “Do we already have a tool for X?” in Slack/Teams ✅ Bot checks knowledge base (policies, procurement tool). ✅ If a match is found, it shares the approved tool & owner to contact. ✅ If not, the bot can ask the user for more info and direct them with next steps to kick off the procurement process from inside Slack/Teams. Ensuring your users ACTUALLY follow the process, without adding friction. Did I just see your CFO cry tears of joy? 3. Third Party Vendor Contract Review & Project Management Getting AI to redline a contract (as a first pass) is a huge win, but there's still the other pieces of the process missing, like: 🤷🏼♀️ The business figuring out IF legal review is even needed (according to company policy). 📨 The business actually submitting the contract to legal. 😩 Managing review capacity within the legal team. 🖥️ Getting the legal team to log & update the PM tool. The list never ends. Legal reviews only what actually needs their eyes, turnaround times improve, and the business stops pinging the team for “update pls?” in Slack : ) TLDR; Most legal teams are drowning in admin work that could be automated. I've built all of these using simple processes and tools (that I've found most businesses have). You also know I love a good Figma flow. So I’ve built them for all three of the above (see a sneak peak below). Want the entire thing? Comment "FLOWS" and I'll send them over. Also, tell me what you want to see - more of the above or step-by-step how-to build videos?

Not going to lie - I have a handful of failed legal tech implementations and legal tech projects under my belt. If you're in legal ops and you haven't had the same happen to you, you likely haven't been doing it long enough. My biggest lesson? Don't overlook the importance of change management. Whether you're tackling a CLM implementation or shifting the way legal services are delivered at your company, change management is going to be key to the success of any legal operations initiative. Here are a few change management specific tips I've learned along the way: - Focus on the people We all know it at this point - legal professionals are resistant to change. You have to make sure you're not only explaining the why but also proactively addressing concerns before they arise. - Know how you're going to measure success You can't show quantifiable impact without knowing what success looks like. Ensure you have a clear definition of what success looks like - including what KPIs and KRIs you'll track, how you'll track them, and where the data is going to come from. - Don't skip UAT and Training It's easy to assume that because you understand something it's going to be easy and intuitive for everyone else. Being neurodivergent, I know that's rarely the case. Even for smaller initiatives, ensure you run a UAT group and build training materials that are right sized for the project (and support folks of all different learning types) - Take feedback as a gift and use it to iterate Legal ops is not set it and forget it. Don't wait until you've hit your KRI(s) for success - you should be leveraging feedback loops during the change management process to actively identify friction points and refine the change strategy as you go. Fellow legal ops pros - what else would you add? #legaloperations #legalops #legalinnovation #legaltech

Here’s something I wish I had started doing as a law firm associate: using checklists for project intake. Too often, when a project is handed over, details get missed, and questions go unanswered, leading to confusion, frustration, write-offs, and avoidable mistakes. Part of the problem is that senior lawyers usually aren’t trained in assigning work effectively. That’s how you end up with emails being forwarded with directives like: “pls handle” or "pls fix." A checklist can help a junior lawyer who is unclear on a request gain clarity. It can also help a senior lawyer become more thoughtful and consistent in how work gets delegated. Atul Gawande writes about this in The Checklist Manifesto (one of my favorite business/productivity books). Gawande is one of my favorite authors, generally. He is an orthogonal thinker in the best sense of the term—someone who looks across disciplines, borrows ideas from other fields, and applies them in practical ways. He writes as a surgeon, but his insights apply well beyond medicine. One of his core points is that in complex environments, problems arise because complexity overwhelms the human brain. Important steps get skipped, assumptions go untested, and small omissions create bigger problems downstream. That idea applies just as much to legal work as it does to surgery or aviation. A simple checklist can make legal project intake cleaner and reduce the odds that important details slip through the cracks. Here are a few helpful prompts: When? Make sure you are clear on the deadline. If there is a filing deadline or a date by which something has to go to a client, when does the assigning lawyer need to see a draft? Clarify what is meant by “ASAP” or “COB.” Who? Who is the audience? Is it an internal memo? Is it going to the client? Is the client a lawyer or a business person? This matters because it helps ensure the work product strikes the right tone and includes the right level of detail. What? What are the client’s work product preferences? Lots of detail and citations? A short list of practical conclusions? Also, what is the scope of the assignment? Spend a few hours and report back on initial findings, or go deep and try to reach a final answer? Why? Why does this matter? What is the context, and how does what I am doing fit into the bigger picture of the representation? Are there other issues I should be on the lookout for? Clarity comes from asking good questions. A checklist helps make sure those questions actually get asked. Create a checklist for the types of projects you commonly work on. It is a simple habit, but it can make a significant difference. You will feel more organized, work will move more smoothly, and fewer details will slip through the cracks.

When Project Engineers Treat Contracts as “Somebody Else’s Job” Too many project engineers proudly own the drawings, specs, and schedules—yet treat the contract as background noise. The result? Beautiful technical solutions wrapped in avoidable claims, change orders, and disputes. Industry studies consistently show that unclear scope, poor documentation, and misunderstood risk allocation are among the top causes of construction disputes—not bad engineering. When we ignore the contract, we’re effectively managing only half the project. Contract administration is not “legal stuff for others.” It’s about: • Understanding scope, deliverables, and risk allocation • Knowing notice requirements for delays and changes • Documenting decisions, RFIs, and site instructions • Protecting relationships and the project’s bottom line The best project engineers I’ve worked with read the contract as carefully as the drawings. They know which clauses govern time, payment, quality, and disputes—and they use that knowledge to prevent problems, not just react to them. If you’re a project engineer, here’s your challenge: Next project, highlight the key clauses that affect your day-to-day decisions (scope, changes, delays, documentation) and manage them as rigorously as your technical tasks. Because in modern projects, technical excellence without contract awareness is a liability. #ProjectManagement #ConstructionManagement #ContractAdministration #ProjectEngineer #RiskManagement #ClaimsAvoidance #LeadershipInConstruction

Understanding the Statement of Work (SOW): Your Project's Blueprint A Statement of Work (SOW) is like a blueprint for a project. It lays out the foundation for what needs to be done, who will do it, and when it needs to be finished. But a well-drafted SOW is more than just a document – it's a strategic tool that can save time, money, and headaches. Why is a SOW important? ✳ Clarity: It ensures everyone involved is on the same page about project goals, deliverables, and expectations. ✳ Risk Mitigation: By clearly defining the scope, it reduces the chances of misunderstandings and disputes later on. ✳ Cost Control: Outlining project deliverables and timelines helps manage budgets effectively. Key Elements of a Strong SOW: ✳ Project Objectives: Clearly define the project's goals and desired outcomes. ✳ Scope of Work: Detail the specific tasks, deliverables, and responsibilities of each party. ✳ Timeline: Establish clear deadlines and milestones for project completion. ✳ Payment Terms: Outline payment schedules, invoicing procedures, and any applicable payment milestones. ✳ Acceptance Criteria: Define how the deliverables will be evaluated and accepted. ✳ Change Management: Outline procedures for managing project changes and modifications. ✳ Intellectual Property: Address ownership of intellectual property created during the project. ✳ Confidentiality: Protect sensitive information shared during the project. ✳ Dispute Resolution: Outline the process for resolving conflicts or disagreements. Ensuring Legal Compliance: A well-drafted SOW not only outlines project requirements but also protects your interests legally. Ensure your SOW: ✳ Complies with Applicable Laws: Adhere to relevant contracts, labor, and intellectual property laws. ✳ Includes Clear Indemnification Clauses: Protect your company from potential liabilities. ✳ Addresses Termination Rights: Clearly outline conditions for terminating the agreement. ✳ Incorporates Force Majeure Clause: Account for unforeseen circumstances beyond your control. By following these guidelines, you can draft SOWs that not only streamline your projects but also protect your business interests. Do you have any specific questions about drafting SOWs? Let's connect! #SOW #projectmanagement #contract #business #legal #compliance

If you've ever struggled with long-drawn-out projects or wished for a more responsive way to deal with ever-changing legal landscapes, I'd like to introduce you to something called the Agile Process. Though originally designed for software development, this methodology can be a real game-changer for our legal profession! 🚀 Here's a practical look at what it entails and how we can adopt it: 1️⃣ Sprints: Break down a complex case or project into smaller, manageable 'sprints.' Work intensively on these short phases and review progress regularly. It makes large tasks more manageable and allows us to adjust if needed quickly. 2️⃣ Daily Stand-ups: A brief daily meeting where everyone in the team updates what they're working on and any obstacles they face. This ensures alignment and immediate support where it's needed. 3️⃣ Client Collaboration: Regular check-ins with clients ensure that you're on the same page and allow adjustments based on real-time feedback. This helps in avoiding any last-minute surprises. 4️⃣ Retrospectives: After each phase or sprint, the team reflects on what went well and what could be improved. This ongoing learning process ensures continuous growth and adaptation. 5️⃣ Digital Tools: Utilize tools like project management software tailored for Agile (like Jira, Trello) to keep everyone on track. It can also facilitate document sharing and collaboration between legal teams, clients, and other stakeholders. 6️⃣ Cross-Functional Teams: Build diverse teams with various areas of expertise. It enhances collaboration and ensures that different aspects of a case or project are considered from all angles. The Agile Process is not just a buzzword – it’s a practical approach to managing our work more efficiently and responsively. It could mean faster case resolutions, higher client satisfaction, and a more cohesive working environment. If you've already used Agile in your practice or if you're curious to learn more, I'd love to hear from you. Let's embrace this modern approach and drive our profession forward! #law #generalcounsel #digitaltransformation #technology -------- 💥I am Olga. 🔺Providing tips for in-house lawyers. 🔺Educating about disruptive technologies. 🔺Delivering keynotes on the intersection of business, law, and tech. Like this post? Want to see more? 🔔 Ring it on my Profile Follow #DailyOlga 🔝 Connect with me 🔝 Subscribe to Notes to My (Legal) Self newsletter

"Legal is slowing us down." I've heard that statement more times than I can count. But after years of working with legal teams, I've come to believe we're asking the wrong question. Legal isn't slow because lawyers enjoy saying "no" or delaying decisions. They're careful because every decision carries consequences. A contract approved today could become tomorrow's dispute. A missed clause could create financial exposure. An outdated policy could lead to compliance issues. When the business asks legal to move faster, it's rarely a simple request. Sales wants contracts reviewed before the quarter closes. Procurement needs vendors onboarded quickly. HR needs immediate guidance on policy questions. Compliance needs clarity on changing regulations. Leadership expects faster turnaround while keeping legal costs under control. At the center of all this sits the legal team, balancing speed with responsibility. That balance is what makes legal work fundamentally different. Reviewing a contract isn't just about summarizing a document. It's understanding obligations, identifying unusual risks, checking approved playbooks, comparing fallback positions, confirming governing law, protecting privileged information, using the correct policy version, and knowing when an issue needs human judgment. That's why generic AI isn't enough. Legal teams don't need a tool that simply generates polished answers. They need technology that removes repetitive work without removing control. This is where Legal SLMs create real value. They can efficiently handle structured, repeatable tasks such as clause classification, obligation extraction, contract metadata, legal request routing, NDA reviews, and document summaries. But legal decisions should never rely on model knowledge alone. Every recommendation should be backed by the right contract, policy, regulation, playbook, or approved legal guidance. That's where retrieval, verification, and human review become essential. The model accelerates the work. Evidence supports the conclusion. Lawyers apply judgment where it matters most. That isn't replacing legal professionals. It's giving them the leverage to keep pace with growing workloads while maintaining the standards their organizations depend on. The goal isn't simply faster legal work. It's safe speed. The kind of speed that legal teams, business leaders, and customers can all trust. How is your legal team balancing the growing demand for faster turnaround with the need for accuracy and defensibility? 🌐 Learn more about LuMay AI: https://www.lumay.ai 📅 Book a demo: https://booknow.lumay.ai #LegalOps #LegalAI #GeneralCounsel #ContractReview #EnterpriseLegal #LegalTech #AITrust

I haven't seen anyone talk about this. But the No.1 reason I have seen legal issues happen... It is because of a simple fact. Miscommunication. That's it. That's all there it is. -> Miscommunication leads to misunderstandings. -> Misunderstandings lead to disputes. -> Disputes lead to legal issues. I read a lot of case laws on the commercial/contract side. And they could all have been easily avoided had the parties communicated properly. Now you might be wondering, why does this happen? Couple of reasons: • Assumptions are made. One party assumes the other knows what they mean. But the other party might have a different interpretation. • Expectations aren't clear. One party expects certain features or services. But if it's not documented, it's just an expectation, not an agreement. • Deliverables aren't defined. What exactly is being delivered? Are the deliverables defined in detail? • Deadlines aren't realistic. Are the timelines realistic? What happens if deadlines aren't met? Now lucky for you, if you want to avoid this. There are a couple of steps I recommend. I normally share this with my clients. 1) Clearly define the scope of the project. Outline what is included and what is not. Example: "The website will include a homepage, about page, contact page, and blog section. E-commerce functionality is not included." 2) Specify each deliverable. Provide details for each one. Example: "The homepage will feature a hero image, a brief introduction, and links to the about and contact pages." 3) Set realistic deadlines. Include buffer time for revisions. Example: "The homepage design will be delivered by August 1st. The about and contact pages will follow by August 10th. The blog section will be completed by August 15th." 4) Be clear on how and when you'll communicate. Regular updates and check-ins. Example: "Weekly status calls every Monday at 10 AM. Daily progress updates via Slack." 5) Be clear about payment schedules. Include milestones and due dates. Example: "50% upfront, 25% upon delivery of the homepage, 25% upon final approval." 6) Define how changes will be handled. Include a process for approving and documenting changes. Example: "Any changes to the project scope must be submitted in writing and approved by both parties. Additional charges may apply." Once you start doing this, you remove a lot of "assumptions" from the contract. Point is - don't leave anything to chance. Because miscommunication can kill a project. I have seen it happen. Tldr: -> Assumptions can cost you. -> Clarity can save you. -> Document everything. That's all -- ✍️ Have you ever lost a project because of miscommunication? 📌 Web Agencies, if you need a good contract that properly communicates your offerings, then DM me the word "CONTRACT" and let's talk #Startups #Founders #Contract #Law #Business #website

Most in-house legal teams don’t run on systems. They run on judgment, memory, and vibes. That works, until it doesn’t. ❌When someone goes on leave. ❌When work scales overnight. ❌When leadership wants speed and compliance. Suddenly, everything breaks at once. Templates don’t fix that. Neither do new tools. You need something deeper... A layered architecture that makes Legal predictable, teachable, and resilient. Here are the five layers of a modern Legal OS: 1️⃣ Identity Layer (who owns what) ↳ Define what Legal owns, supports, approves, and advises. 2️⃣ Process Layer (how work moves) ↳ Map intake, triage, approvals, handoffs, and “done.” 3️⃣ Logic Layer (when and why decisions happen) ↳ Codify risk thresholds, escalation rules, and decision trees. 4️⃣ Prioritisation Layer (what happens first) ↳ Design systems for focus, delegation, and balance. 5️⃣ Governance Layer (how it stays alive) ↳ Assign owners, update cycles, training, and version control. When you start running Legal like a system: ✅Problems become design issues. ✅Delays become workflow issues. ✅Burnout becomes a prioritisation issue. And improvement becomes inevitable. 📘 Detailed guide is now live on my newsletter (link in bio). 💾 Save this post. ♻️ Share it with a colleague.