What changes when you become a project manager

Analysts are often measured by the accuracy and timeliness of their own work. Project managers are measured by whether the entire engagement works. That requires anticipating dependencies, identifying risk early and making sure that legal, technical and commercial expectations remain aligned.

The role therefore requires breadth. You do not need to be the deepest technical expert in every platform, but you must understand enough to ask the right questions and challenge unrealistic assumptions.

Build strong technical foundations first

Project managers should understand preservation, collection, processing, review, analytics and production well enough to recognise the effect of choices made at each stage. They need to understand data volumes, document families, metadata, search, privilege workflows, TAR, productions and common exceptions.

Without that grounding, it is difficult to estimate effort, manage suppliers or explain risk convincingly.

Develop scope and planning skills

Every project should begin with a clear understanding of objectives, data sources, custodians, deadlines, review requirements and deliverables. Project managers convert those inputs into a workable plan.

Practise breaking matters into workstreams, identifying dependencies, estimating volumes, assigning ownership and recording assumptions. Good planning is visible: stakeholders should know what will happen, when and why.

Learn budgeting and commercial awareness

Cost matters. Project managers should understand the main cost drivers in collection, processing, hosting, review and production. They should be able to identify when data reduction, targeted collection, workflow redesign or alternative resourcing could reduce cost without undermining defensibility.

More senior roles may involve pricing, statements of work, profitability and supplier negotiation. Commercial literacy therefore becomes part of professional competence.

Strengthen stakeholder communication

Project managers sit between lawyers, clients, reviewers, vendors, technical teams and sometimes regulators or investigators. Each group uses different language and has different priorities.

Strong project managers provide concise status updates, make risks explicit, document decisions and escalate early. They avoid both technical jargon and false simplicity.

How to gain project-management experience

You do not need to wait for a formal promotion. Volunteer to own a workstream, prepare status reports, coordinate a production, lead a quality-control exercise or manage a small review. Ask to participate in scoping calls and post-project reviews.

These assignments demonstrate that you can take responsibility for outcomes rather than only individual tasks.

What good eDiscovery leadership looks like

Good project managers create calm, repeatable delivery. They make priorities clear, support colleagues, challenge weak assumptions and maintain an audit trail. They also know when to bring in deeper legal, forensic or technical expertise rather than pretending to know everything themselves.

Professional development principle: Build transferable knowledge of the complete ESI lifecycle, then combine it with practical experience, quality discipline, communication and evidence of successful delivery.

Build your eDiscovery capability

Explore vendor-neutral certification, professional training and the wider eDiscovery Certification Council Knowledge Hub.

Explore Certifications Browse Training Courses

Editorial note: Published by the eDiscovery Certification Council as vendor-neutral professional guidance. Career requirements vary by employer, jurisdiction and role. This guide should be used alongside current job descriptions and relevant legal, regulatory and organisational requirements.