Academy 03 Assign

One decision, one owner, one date

Assignment is where most operating systems quietly break. A decision with two owners has none, and a decision without a date is a preference.

Competency

Accountability design

Objective

Leave this lesson able to attach a single named owner and a real due date to every scored decision, and to spot shared ownership before it costs you a week.

Where this sits

The loop, with this stage lit.

  1. 01Signal
  2. 02Score
  3. 03Assign
  4. 04Execute
  5. 05Verify
  6. 06Remember

Comes in from

Score

This stage

Assign

Leave this lesson able to attach a single named owner and a real due date to every scored decision, and to spot shared ownership before it costs you a week.

Hands off to

Execute

Composite Utah service-business examples of this loop running end to end: Read the composites

Why it matters

  • Shared ownership feels collaborative and behaves like abandonment. Nobody is embarrassed when nothing happens.
  • A due date is what converts a scored priority into work that competes for real hours.
  • The escalation path has to be written before it is needed, not invented during the failure.

How to run it

  • Name one human. Not a team, not a channel, not a role in the abstract.
  • Set a date the owner agrees to out loud. If they cannot, the effort score was wrong.
  • Write the escalation rule: what happens, and who hears about it, if the date passes.
  • State the boundary. What the owner may decide alone and what has to come back for review.
  • Write what a helper or system may do on the owner's behalf, and what it may not.
  • Store the assignment where both the office and the field can see it.

Evidence it ran

  • A record showing one named owner per decision.
  • A due date the owner accepted.
  • A written escalation rule with a second name on it.

Competency pulls

The skills this stage draws on, written in our own words and taught against a real decision in your shop.

  • Human and machine team design, where each side has a named job.
  • Delegating narrow work to a helper with a defined boundary.
  • Reusable skills, so the same job is done the same way twice.
  • Shared workspace habits, so the assignment is visible to more than one person.

Watch lesson

The recorded walkthrough for this stage is not published yet. When it is, it plays here. Nothing is hidden behind it, the written lesson above is the full lesson.

Take the lesson with you

The whole written lesson as a one file sheet you can print for the shop wall or the truck.

Your progress

Without a seat, progress is kept in this browser only. Take a seat and it is saved to your record instead.

0/6 stages done

Take a seat