Every organization already has a Work Architecture™.
It determines what work exists, how the organization is structured around that work, who holds which decision rights, where capacity comes from, who is accountable when something goes wrong, and whether the resulting roles are coherent for the humans who hold them.
Some organizations design it deliberately. Most inherit it.
An organization without a Work Architecture still has one.
It is simply unowned. Work Architecture is the discipline of designing it deliberately.
Decompose. Decide. Recompose.
The method starts from work, not from the org chart. An inherited job is taken apart into the work units that actually make it up. Each unit is decided against the capacity that can defensibly supply it — a human, Ai, a system, an external provider, or some hybrid of those. Decomposition without the third step is just fragmentation: the units are deliberately put back together into a role a person can actually hold, coherently and accountably.
An inherited job, taken apart into the work units that make it up — before anyone asks who or what should do them.
Recruiter
- Intake
- Sourcing
- Screening
- Evaluation
- Interviewing
- Decision
- Offer
- Onboarding
Each unit assigned to the capacity source that can defensibly supply it — never assigned by default to whichever tool arrived first.
- HUMAN
- Ai
- SYSTEM
- HYBRID
- EXTERNAL
- Intake SYSTEM
- Sourcing Ai
- Screening HYBRID
- Evaluation HUMAN
- Interviewing HUMAN
- Decision HUMAN
- Offer HUMAN
- Onboarding HYBRID
Illustrative allocation — one example, not a specification. Not every capacity source appears in every architecture.
Not the leftovers reassembled. A role built on purpose around judgment and accountability, then widened with work the inherited job did not carry before.
Talent & Capability Lead
- Retained
- Evaluation, interviewing and the hiring decision stay human.
- Widened
- Capability, succession and internal mobility backward, which the inherited job did not carry at all. Governing the selection stack forward — a duty that barely existed before.
- Accountable for
- The hiring recommendation, named and recorded. The hiring manager still owns the hire.
- Stop authority
- May suspend any automated screen pending review.
Working draft, unratified — the Five HR Jobs series.
Decompose → Decide → Recompose
The residue of delegation is not a job.
Decomposition without recomposition is just Taylorism with better technology.
Capacity before headcount.
The traditional planning flow starts from growth and ends at tasks — it never asks what the work actually needs, only how many more of the current job to buy.
Traditional GROWTH → HEADCOUNT → JOBS → TASKS
Inverted REQUIRED OUTCOME → WORK → CAPACITY → HUMAN REQUIREMENT
Human Workday inverts the order. Start from the required outcome, decompose it into work, and decide its capacity configuration — human, Ai, system, external, or hybrid. Only once that configuration is decided does a number of humans get asked for at all. Headcount is not the question an organization starts with — it is what is left over once the required human contribution has been decided, not the number it plans backward from.
Capacity before headcount.
Accountability relocates.
Ai can inherit execution. It cannot inherit accountability.
When a machine takes over execution, the accountability that used to travel with the person doing the work does not disappear. It relocates — to whoever approved the delegation, whoever validates the system that now performs it, and whoever still owns the decision the work was for. A Work Architecture has to say who, by name or by role, before the delegation is made — not reconstruct it after something has gone wrong.
- Q1 Who approved the delegation?
- Q2 Who validates the system?
- Q3 Who handles exceptions?
- Q4 Who owns the consequential decision?
- Q5 Who can stop the architecture?
Machine execution does not eliminate human accountability. It relocates it.
The rules that bind how far any of this can go are public. Read the Constitution.
See the method applied.
The method reads clean in a diagram. It reads differently against five real jobs, redesigned in full.