Design Pattern · September 2026
Work Origin and Incentive map
Find whether work serves the outcome or was created by a rule, incentive, boundary, or information failure.
Under the pillar Unbundling Work, Credentials, and Liability
Inputs
A recurring burden, governing rules, contracts, payment terms, organizational boundaries, and affected parties.
Method
Classify the work as outcome intrinsic, safety, legal, reimbursement, contractual, defensive, coordination, reconstruction, reporting, vendor imposed, cost shifting, or obsolete.
Output
A disposition of retain, assist, automate, redesign, renegotiate, or remove with an owner.
Boundary
Institutional friction can be protective. Classification does not prove that a burden is waste.
Stop
Stop automating when the root cause can be removed more safely or cheaply.
Put this to work
Work Origin and Incentive map application record
Apply Work Origin and Incentive map to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A work origin and incentive map application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
Do not infer that a task can move merely because it can be described.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.