Legacy Work Patterns
A field guide for recognizing work that belongs to a previous technological era
How to Read This Page
This is not a list of instructions. It is a perception tool.
Its purpose is to help you recognize which parts of modern work are artifacts of older constraints. Read it as a pattern-recognition guide, not a checklist. It complements the reference framework, which defines the maturity levels and transformation path.
Transformation begins when you can see legacy work while it is happening.
The Core Principle
Work that repeats without meaningfully changing inputs is not human work. It is a system that has not yet been built.
Why Legacy Practices Persist
Most outdated workflows were once necessary. They tend to survive because:
- they originally required human judgment;
- building systems used to be expensive or slow;
- improvisation was easier than design;
- organizations optimized for activity instead of leverage.
Those constraints no longer apply. What used to be necessary effort is now often unnecessary repetition.
Recognition Signals
You are likely looking at a legacy practice if the task:
- repeats the same steps regularly;
- involves copying or reformatting information;
- exists mainly to move data between tools;
- requires a person to "prepare" information that already exists;
- depends on memory instead of written structure;
- produces outputs from predictable inputs.
These signals do not mean something is wrong. They indicate an opportunity for redesign.
Common Legacy Patterns and Their Evolution
These examples illustrate the shift from human-executed work to system-executed work.
Reporting and Analysis
Manual reports assembled by hand
Live dashboards and AI-generated summaries
- numbers must be requested from someone;
- reports are rebuilt instead of refreshed;
- metrics live in slides instead of systems.
Information Gathering
Manually collecting and synthesizing information
AI aggregation from structured sources
- information exists but must be searched for manually;
- insights depend on who gathers the data;
- the same sources are consulted repeatedly.
Quality and Review
Humans repeatedly checking predictable conditions
Automated validation driven by scenarios
- reviews mostly catch formatting or obvious issues;
- the same feedback appears every cycle;
- errors are detectable by rules.
Content and Communication
Humans drafting routine material from scratch
AI drafts with humans refining judgment, tone, and intent
- first drafts follow predictable structures;
- writing time is spent assembling rather than deciding;
- content resembles previous versions.
Process and Coordination
Workflows that exist only in people's heads
Specified processes that systems can execute
- steps must be explained repeatedly;
- outcomes vary depending on who performs them;
- tasks stall waiting for someone to route or assign them.
Meetings
Recurring conversations without durable outputs
Asynchronous specifications and recorded decisions
- the same topics reappear;
- decisions are not documented;
- participants leave with different interpretations.
Engineering
Manual steps required for repeatable technical processes
Automated pipelines and spec-driven execution
- releases depend on someone remembering steps;
- similar problems are solved repeatedly;
- implementation precedes specification.
Maturity Spectrum
Work rarely shifts instantly. Most systems evolve through stages:
| Stage | Description |
|---|---|
| Legacy | Humans execute steps |
| Assisted | Tools help humans |
| Delegated | Systems execute steps |
| Designed | Humans design systems |
These stages map to the organizational maturity scale defined in the reference framework: Legacy and Assisted correspond to Level 1 (AI-Assisted), Delegated to Level 2 (AI-Integrated), and Designed to Level 3 (AI-Native).
Transformation is the steady movement from left to right.
What This Does Not Mean
Recognizing legacy work does not imply:
- humans become unnecessary;
- judgment is automated;
- creativity is replaced.
It means human effort shifts from executing tasks to designing systems.
Reflection Prompt
During your work week, notice moments when you are:
- repeating steps;
- moving information;
- formatting outputs;
- checking predictable conditions.
When you notice one, ask: Is this work, or is this a missing system?
Direction of Travel
This field guide will evolve as patterns become visible.
The goal is not immediate change. The goal is learning to see.
Transformation begins the moment you start recognizing legacy work in real time. Once you can see the patterns, the next question is what happens to the roles that performed that work — see Role Evolution.
← Back to home · The reference framework · Employee guide · Glossary