Career comparisons
eDiscovery jobs vs legal operations jobs: choose by operating layer
The useful distinction is no longer ‘technical eDiscovery’ versus ‘business legal ops’. Start with the workflow being controlled, then identify whether the role executes matters, runs a service, or changes the programme around it.
Start with the workflow, not the department name
eDiscovery roles are built around electronically stored information for litigation, investigations or regulatory work. Legal operations roles are built around repeatable legal-department services such as intake, contracts, spend, vendors, matter records, systems and reporting. Both can sit inside Legal Operations, use data and technology, and involve project or vendor management. The first test is therefore the workflow being controlled. Custodians, legal holds, preservation, collection, processing, review and production point to eDiscovery. Business requests, contract workflows, invoices, provider records, service metrics and department-wide adoption point to broader legal operations.
EDRM 2.0 makes the eDiscovery boundary clearer
The September 2026 EDRM 2.0 update keeps identification, preservation, collection, processing, review and production at the centre, while adding disposition as a core phase. It also places information governance underneath the model, groups early work as data acquisition, and treats analysis as continuous rather than a single late step. For candidates, that changes the job-description screen. Ask whether the role controls defensible data acquisition, iterative analysis, review decisions, production and post-matter disposition. A posting that only mentions general document systems or legal data is not automatically an eDiscovery role.
Separate execution, service ownership and programme change
Two eDiscovery roles can share the same lifecycle but carry very different authority. Matter execution owns scoping, holds, collections, transfers, workspaces, status and exceptions for active work. Service ownership adds standard procedures, access, vendors, quality controls, reporting and a dependable operating cadence across matters. Programme change adds roadmaps, integrations, platform choices, automation, evaluation methods, commercial decisions and senior reporting. This three-layer test also works in legal operations: compare running an intake queue with owning the intake service, then compare both with redesigning the department's service model.
Current in-house roles show where the paths overlap
Honeywell's current eDiscovery programme role is execution-led: intake and scoping, custodian identification, holds, preservation, collection, secure transfers, system records, standard procedures, chain of custody, tool administration and vendor coordination. Amazon's current programme-manager role starts from the same eDiscovery lifecycle but adds a technology roadmap, integrations, automation, AI evaluation, vendor strategy, standards and leadership reporting. Both are legal-operations roles in organisational terms. Their specialist unit of work is still discovery. The overlap is real, but the expected decisions and artifacts reveal the level.
Use the failure mode to classify hybrid postings
Ask what failure the role exists to prevent. Missed preservation, incomplete collection, uncontrolled data transfer, review defects or an incorrect production point to a discovery mandate. Lost requests, unreliable contract or matter records, invoice exceptions, poor adoption or weak department reporting point to a broader operations mandate. A hybrid role may genuinely carry both. In that case, map each responsibility to a trigger, data object, control, decision-maker and accepted output. Then ask whether the team, vendors and systems make both mandates credible rather than assuming a broad title means broad support.
Build evidence as a chain, not a tool list
For eDiscovery, a useful evidence chain might run from matter trigger and data-source identification through preservation, collection, quality control, review support, production and closure. State where you executed, checked, recommended or approved. For legal operations, trace a recurring service from intake through routing, system record, exception, handoff, reporting and improvement. In either path, name the artifact left behind: a collection log, chain-of-custody record, review protocol, production checklist, process map, requirements document, dashboard, training guide or change record. Tool knowledge matters when it proves a workflow and level of responsibility, not when it appears as an unsupported list.
Choose the next role with a five-line test
Write five lines for any vacancy: the event that starts the work; the data or record being controlled; the failure that matters; the decision you would own; and the artifact that proves completion. If the answers centre on matters, custodians, ESI and defensible delivery, compare your evidence with the eDiscovery layer the employer needs. If they centre on department services, spend, contracts, vendors or adoption, use the legal operations analyst requirements guide and legal operations career path. If the role changes systems or programmes, compare the legal technology implementation guide and legal AI operations guide. Then review current legal operations jobs or set a role alert using workflow terms, not only titles.