Human intelligence applied to the architecture of work.
Work, redesigned for people.
For a century, more of the capacity a job supplies meant more human hours. It doesn't anymore.
Most organizations are still designed as though it does. Ai can now perform, accelerate, or augment meaningful portions of productive work. Yet jobs, departments, headcount models, management systems, and the workday itself remain largely organized around human hours.
Human Workday studies what happens when the architecture catches up.
Ninety-nine years on an architecture designed for factory floors. The hundredth is when the drawing changes.
The different question
Ai capability is outrunning the organizations meant to use it.
Most organizations ask
How do we add Ai to the jobs we already have?
Human Workday asks
What work actually needs to exist now? And only then — who or what should perform it?
Every organization already has a Work Architecture™. It determines what work exists, how it is organized, where decisions sit, what capacity performs it, where accountability lives, and how work becomes coherent human roles. 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.
The method
Don't start with the job. Start with the work.
Take inherited jobs and workflows apart into meaningful work units.
- INTAKE
- SOURCING
- SCREENING
- EVALUATION
- INTERVIEWING
- DECISION
- OFFER
- ONBOARDING
Determine the strongest defensible capacity for each unit.
- HUMAN
- Ai
- SYSTEM
- HYBRID
- EXTERNAL
- INTAKE SYSTEM
- SOURCING Ai
- SCREENING HYBRID
- EVALUATION HUMAN
- INTERVIEWING HUMAN
- DECISION HUMAN
- OFFER HUMAN
- ONBOARDING HYBRID
Illustrative allocation — the method decides per organization. Not every capacity source appears in every architecture.
Don't leave humans with whatever technology didn't take. Build coherent human work around judgment, accountability, relationships, capability, development, and outcomes.
- Retained
- Evaluation, interviewing and the hiring decision stay human, with the contested cases in screening.
- Widened
- Backward into capability, succession and internal mobility, which the inherited job did not carry at all. Forward into governing the selection stack — a duty that barely existed before, and one that grows as more of the funnel is delegated to Ai and system capacity.
- 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.
Inherited role → Work units → Capacity → Coherent work → Talent & Capability Lead
The residue of delegation is not a job.
Decomposition without recomposition is just Taylorism with better technology.
Work gets measured. People don't.
Human Workday decomposes work, not human beings. It does not treat people as optimization variables, reduce human worth to productivity, or assume that everything technically automatable should be automated. The unit of analysis is the work. The object of design is the architecture. The human being remains a human being.
See it applied
Departments reimagined.
Theory is cheap. Architecture should produce something you can run.
People
Inherited jobs decomposed. Work allocated across human, Ai, system, hybrid, and external capacity. Human work recomposed. Roles redesigned.
Explore PeopleInformation Technology
Same discipline. Different work. Different capacity. Different architecture.
Explore IT IN PREPARATIONFinance
Same discipline. Different work. Different capacity. Different architecture.
Explore Finance IN PREPARATIONSame method. Different answers.
The method doesn't prescribe the answer. Five inherited HR jobs produced materially different architectural conclusions:
The method doesn't prescribe the answer. The work reveals it.
Working drafts. Destination titles are hypotheses to be tested against a work inventory, never recommendations — the method also preserves the inconvenient conclusions: keep the job unchanged, use fractional capacity, externalize the work, or find that a standalone role is not justified.
The human consequence
Architecture changes the workday.
Declared fictional — "Renata" is a construct for illustration; no real person or organization is depicted.
Before — HR Generalist
- Policy questions. Nineteen more by noon.
- I-9 corrections.
- Enrollment problems.
- Verification letters.
- Manager chasing.
- Interruptions.
- The consequential employee investigation waits until 4:00.
- Notes are being finished at 6:30.
After — People Partner
- Systems handle routine questions.
- Ai prepares and synthesizes.
- Renata verifies the delegation.
- Her time concentrates around credibility interviews, manager coaching, consequential interpretation, organizational patterns, and decisions requiring human judgment.
"The redesign did not remove the weight of the job. It removed the nineteen interruptions between her and doing it well."
That's the Human Workday.
Enterprise implications
Capacity before headcount.
Stop beginning with the org chart. The question isn't "how many people do we need?" until we've answered: "what work exists, and what capacity should perform it?"
TRADITIONAL GROWTH → HEADCOUNT → JOBS → TASKS
HUMAN WORKDAY REQUIRED OUTCOME → WORK → CAPACITY → HUMAN REQUIREMENT
Ai can inherit execution. It cannot inherit accountability.
As machine execution increases, accountability doesn't disappear. It moves.
- Who approved the delegation?
- Who validates the system?
- Who handles exceptions?
- Who owns the consequential decision?
- Who can stop the architecture?
Machine execution does not eliminate human accountability. It relocates it.
Rigor
We don't ask you to trust the diagram.
Every consequential architectural claim should be challengeable.
Don't just read it. Run it.
Proof that the method produces Work Architecture a practitioner can run, not commentary about one. Worked examples, templates, checklists, job descriptions, architecture records, and implementation tools.
Don't copy our architecture. Run the method against your work.
The institution
An institute that happens to build software. Research precedes product.
- Software may eventually instrument the discipline. It does not define the discipline.
- Commercial convenience does not override evidence.
- Product requirements do not override constitutional constraints.
- Ai capability does not determine what humans ought to delegate.
Follow the work. No newsletter. No nurture sequence. No sales funnel. Receive an email only when Human Workday publishes or materially revises research, a standard, a constitutional provision, or a worked architecture.