Skip to content
Period 5 / 12

The Five Practices, One Delegation Mindset

The frame: manage a new hire, not software

You're not learning to operate software. You're learning to manage a new hire: talented, tireless, fast, slightly overconfident, and very literal.

That's the whole frame for this module. Read the five practices below once, as a map (each one gets its own lesson, its own mechanism, and a live worked demo: a spreadsheet reconciliation with seeded mismatches, a contract folder turned into a renewals tracker, a monthly report that drafts itself). Nothing here is asserted without a demo behind it. This lesson is the map, not the proof; the proof starts at the next lesson and doesn't let up until practice five's report lands in your drafts folder, unsent, waiting for a signature.

Not one technical word among them

Every one of the five practices below is something already known about delegating well to a person. The tool is new. The underlying discipline is not.

The five practices, at a glance

Brief before you delegate

See the plan before any work happens. Misunderstandings are cheap when they're caught in a proposal and expensive once they're baked into a finished file.

One bounded job, not a mission

Inputs in hand, output defined, verifiable today. A vague mission stalls; a bounded job ships.

Demand evidence, not assurances

"Done" is a claim, not proof. The evidence (citations, control totals, an exception list) has to be part of what gets delivered.

Write the handbook once

Corrections compound instead of repeating. A rule written to a file survives every session; a rule spoken in chat evaporates with it.

Nothing ships without your signature

Automate the work. Never automate the accountability. Anything that reaches a client, the ledger, or a filing gets a human's approval first.

How the five connect

Each practice guards one point in the same handoff, from briefing the work, to bounding it, to checking it, to remembering the fix, to signing off on what leaves.

The five practices as one handoff

Not one technical skill among them

Quick check — Which of these five practices is a technical skill specific to AI agents?

Where this module goes next

Practice one is the same discipline as with any new hire: don't let them start before they've told you what they think the job is. That's where this module picks up next.

Continue to Lesson 05

Practice 01, with its mechanism (Plan Mode) and the ten-second correction that replaces a twenty-minute one.

Have a question about this lesson?

Reply here and it goes straight to Rod. Same as replying to one of his emails.