article-time-estimate-icon

4 minute read

Coordinating Chaos: Project Management’s Critical Role in the AI Age

Shreyas Sriram

Shreyas Sriram

In this article

    An associate can now generate a first draft of a document in minutes with a generative AI. A marketing manager can create dozens of campaign variants instantly. A developer can deliver code at twice the pace with AI pair-programming. Productivity gains of this scale are routine. Research shows that business users complete 66% more work on average with AI support, while developers finish twice as many projects per week when assisted by AI.

    Yet the productivity surge has a catch. Faster cycles and more outputs create complexity. Tasks splinter into micro-components, and coordination becomes the true bottleneck. One report found that while 68 percent of developers save more than 10 hours weekly using generative AI, many do not feel more productive because of organizational obstacles. Nearly half reported losing those hours again due to fragmented workflows, poor cross-team collaboration, and difficulty accessing information.

    These issues aren’t specific to developers, just the most visible in their case because the data is easier to measure. Knowledge workers across law, consulting, finance, and operations face the same barriers, but their productivity losses are harder to quantify.

    The implication is clear: while AI speeds up execution, without proper orchestration, the outcome is chaos, redundant work, and lost potential.

    The Productivity Boom and Its Limits

    Generative AI is transforming throughput across industries. Customer service agents resolve more cases. Writers create more content. Analysts generate richer reports. This pace of improvement compresses decades of efficiency gains into months. Yet most of these AI-powered tasks are fragments of larger workflows. Coding, for example, represents only 16 percent of a developer’s workweek and drafting is just one part of what a lawyer works on each day. The rest is planning, reviewing, documenting, and coordinating. These are areas where AI contributes little and where the cracks now show.

    The initial excitement of AI-driven speed often shifts to the realization that more drafts and analyses can slow teams if no one integrates them. Atlassian’s survey found only 6 percent of engineering leaders believed AI had significantly increased overall productivity. This pattern emerges across industries: raw output without effective orchestration fails to deliver meaningful results.

    Coordination, Orchestration, and Visibility

    Coordination is no longer back-office administration. It is at the center of competitive advantage. AI can generate endless outputs, but only humans can decide which outputs matter and how they fit together. Project management, once considered overhead, is now the skill that determines whether organizations convert activity into results.

    Managing in this context requires new layers of judgment. Who sets the right prompts? Who ensures quality? Who aligns AI-generated documents, campaigns, or reports with the broader strategy? These responsibilities fall on project leaders in title or in function. As HBR observed, teams must be viewed as a mix of humans and algorithms. The project manager becomes the connective tissue, bridging technical speed with strategic coherence.

    Soft skills move to the foreground. AI reduces routine work, leaving human leaders to navigate ambiguity, rally stakeholders, and motivate teams. Portfolio-level visibility becomes critical as executives seek to oversee dozens of AI-driven initiatives in parallel. Those firms that institutionalize project management discipline will scale what works and stop what does not far faster than their peers. Those that fail will drown in AI outputs with little to show for it.

    Legal Transformation

    No industry highlights this dynamic more clearly than law. Once considered resistant to change, the legal sector is now a laboratory for AI-driven workflows. Surveys show 84% of lawyers believe generative AI can increase efficiency, with analysts estimating 44% of legal tasks are candidates for automation .

    Leading firms are treating AI adoption itself as a managed project. DLA Piper was the first major firm to roll out Microsoft Copilot across its practice, embedding it into everyday drafting, analysis, and presentation workflows. They paired deployment with rigorous testing, training, and change management. Lawyers were not left to improvise with new tools. Instead, internal project teams tracked quality, accuracy, and risk, and ensured everyone understood both capabilities and limitations. This is not experimentation but structured implementation.

    Legal Project Management (LPM) has risen alongside these changes. Firms now employ project managers and process experts to coordinate attorneys, technologists, AI models, and clients. LPM ensures timelines and budgets stay intact, outputs are translated into client-ready insights, and human judgment steers the process. Gartner has projected that 80 percent of project management tasks could be automated by 2030, a figure many doubt. What is not in doubt is that project managers will increasingly shift from task management to leadership roles centered on judgment, communication, and risk.

    The lesson extends beyond law. AI adoption in any sector must be treated as a project, with clear objectives, phases, accountability, and risk controls. Firms that skip these fundamentals discover errors, ethical issues, and failed rollouts. Those that treat AI as a disciplined change initiative capture real value.

    New Tensions in the AI Workplace

    As AI takes over more tasks, project leaders face new challenges. Accountability blurs. If an AI system generates a flawed analysis, is that a technology error or a management lapse? Leaders must learn to treat AI tools like junior colleagues, reviewing their output critically and contextualizing it before action.

    Cultural gaps are widening. Executives often push “AI everywhere” strategies while frontline teams struggle with the day-to-day friction of implementation. Atlassian found 63% of developers believe leadership does not understand their challenges. Project management becomes the translation layer, surfacing realities from the ground and aligning them with strategy.

    Workforce development is also shifting. Junior analysts who once learned through repetitive tasks now rely on AI for much of that work. Without redesign, this risks creating a generation of professionals with shallow experience. Leaders must intentionally redesign roles to ensure learning, mentorship, and growth continue. Otherwise, AI will hollow out the talent pipeline.

    Motivation is another challenge. HBR research shows AI increases productivity but can reduce intrinsic motivation, leaving employees less engaged. The task for project managers is to keep work meaningful, rotate responsibilities, and highlight the purpose behind outputs. Emotional intelligence and leadership matter more as machines take on routine execution.

    The Future of Project Leadership

    The age of AI requires a new model of project leadership. Project management is becoming the operating system of modern organizations. It integrates technology, human effort, and strategy into coherent execution. The mechanics of management will change, but the need for human coordination, judgment, and empathy will only intensify.

    AI accelerates change. It enables more projects, faster cycles, and higher stakes. This amplifies the value of leaders who can integrate technology into the larger human endeavor of business. The paradox is simple: the more we automate, the more critical the human factor becomes. Coordination, vision, and empathy—what we might call the “taste” of good leadership cannot be automated. They are the differentiators.

    Organizations should ask not only how they will use AI, but how they will manage everything AI unleashes. Those that invest as much in coordination as in automation will convert potential into performance. Those that do not will discover that no algorithm can compensate for muddled direction. In this new era, project management is not overhead. It is the decisive skill that turns AI’s speed into strategic success.

    In this article

      More legal tech insights we think you'll love

      Legal matter dashboards for partners: clarity across matters and teams

      Partners manage growing volume and complexity. Lupl gives live matter...

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