Command the Machines
0 / 5
6
BAND II · MONEY
Week 6 of 12 · LE LOCLE · 992 m

Win Back the Hours You're Already Paying For

You're already paying for these hours. This week you get them back.

Month one returned your own hours — the dashboard has the number. This week the machine does it to the payroll: where the team's hours actually go, the reply backlog cleared on one drive, the two-day relay collapsed to one approval, the inbox that sorts itself before you sit down — and on Friday, the one-page charter that changes what "doing the work" means in your company.

Not your desk? This week's moves work on any desk: find the hours you're paying for · clear a backlog by talking · make approving the new doing.

Today · one task

Give the prompt above your calendar, the email threads you're on, and two minutes of voice about the three processes you suspect eat the most time. Circle the three biggest. Save it as THE HOUR AUDIT.

In week one you found out where YOUR time goes. Today the same honest page gets written about the hours you're paying everyone else for — and three reclaim targets get names.

You'll have: THE HOUR AUDIT — three processes, three estimated hours-per-week numbers, and your reclaim targets for the rest of the week, named.

  1. Give the press what you can see. Your own calendar's meetings with the team, the threads you're copied on — plus two minutes, voice, on the three processes you already suspect are eating hours (the weekly report, the quote run, the chasing).
  2. Read the page it builds: each process, the steps inside it, and an estimated hours-per-week number — labelled as the estimate it is.
  3. Circle three. Those are this week's reclaim targets: Wednesday collapses one, Thursday returns the morning hour, Friday changes the operating rule. Save as THE HOUR AUDIT.

Build my team's hour audit. Sources: my calendar and the mail threads I'm part of, plus what I've just described out loud. Give me one page: (1) the recurring processes you can see the team running — one line each on the steps involved; (2) an estimated hours-per-week number for each, marked plainly as an estimate; (3) the three where drafting by machine and approving by human would return the most hours, and why. No advice beyond that, no judgement of people — processes only. I'll pick the targets.

COPY

Rescue — Numbers feel off? They're estimates from what the machine can see, and the page says so. Circle the three biggest anyway — twenty percent wrong about the right target still wins the week.

Did you get this done?

Three processes named, each with an hours-per-week number attached.

Want more — Want sharper numbers? Ask two team members for the same two-minute voice note you gave in week one — their lists plus yours turns estimates into a map.

The targets have names now. Tomorrow starts small — with the email you've been avoiding all week.

Today · one task

Record one hands-free voice note on the drive: a name, your reply, next name, next reply. The prompt splits it, drafts every message, and queues them. When you arrive, tap send — dreaded one first.

In week three, sixty seconds of voice wrote a whole proposal. Today the same muscle takes a bigger job: not one email — the entire reply backlog you owe, cleared on one drive.

You'll have: THE BACKLOG RUN saved — one continuous voice note becomes every reply you owe: split, drafted in your voice, queued in order, sent tap by tap on arrival.

  1. On today's drive or walk, run the backlog — one voice note, hands-free. Say the recipient's name, then talk the reply; next name, next reply. Start with the dreaded one. Decisions, not dictation — messy is fine, the names are the dividers.
  2. The press below splits the ramble into the batch: each message separated by name, drafted in MY VOICE, subject lines on, queued in the order you spoke them.
  3. Arrive, read down the queue, tap send — tap, tap, tap. The dreaded one goes first. Each tap keeps your name honest; the queue is why one drive now clears what used to follow you into the evening.

Above is one voice note covering several replies I owe. Split it by recipient — I said each name before each item. For every item, draft the message I'd actually send in MY VOICE: keep my decisions exactly, lose the rambling, land the difficult parts clearly and kindly, one plain next step each, subject line included. Queue them in the order I spoke them, the dreaded one first. Drafts only — nothing sends until I tap. And if an item turns out to be a decision I haven't actually made yet, don't dress it up: put it at the bottom of the queue, flagged "decide first."

COPY

Rescue — Drafts blurred into each other? You skipped the names. The recipient's name before each item is the divider — "To Pete:… To Sarah:…" — rerun the note with names and the batch splits clean.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

One drive cleared five or more owed replies — drafted on arrival, sent by your taps.

Want more — Now give the run to your two busiest managers — their commutes are backlog too, and Friday's charter makes draft-then-approve official for everyone. The backlog notices within a week. Company-wide, it notices within a month.

The backlog noticed. Tomorrow: the handoffs — the places where work stops and waits for a human to notice it.

Today · one task

Take the slowest relay from your audit — work passed hand to hand. Write down its steps, then run the prompt above the next time it starts: one pass, one approval, out.

Somewhere in your company, work is being passed hand to hand like a baton — drafted, reviewed, formatted, forwarded — and the passing takes longer than the work. Today one of those relays dies.

You'll have: one relay from yesterday's audit collapsed into a single pass: the whole package drafted in one go, one human approval at the end.

  1. Pick the relay. A relay is work passed hand to hand — drafted by one person, checked by another, formatted by a third, sent by a fourth. Take the slowest one from THE HOUR AUDIT and write its steps down: who touches it, and what each person actually adds.
  2. Run it once, for real. The next time it starts — this week's report request, today's quote enquiry — paste that trigger and your step list into the press below. The whole package comes out in one pass: drafted, formatted, send-note included.
  3. One approval, then out. The person who used to be the last step reads it once and approves. Time it against what the relay used to take.

I'm collapsing a relay. Here's how it works today: {the steps, who touches it, what each adds}. Here's the live trigger: {paste it}. Produce the ENTIRE finished package in one pass — the drafted content, formatted the way the final step expects it, plus the one-line send-note to whoever receives it. Where the old relay's steps existed to add judgement, list those judgement points at the top as questions for the approver — the approval replaces the relay, it doesn't skip the thinking.

COPY

Rescue — Output missed what one relay step used to add? That step was carrying judgement, not formatting. Name it — "the review step checks margins against the price list" — and run again. The relay's wisdom moves into the order.

Did you get this done?

The old two-day relay finished in under an hour — with one human approval.

Want more — Show the person who used to be the bottleneck, not the person who used to start it. When the reviewer sees they've become the approver — same authority, a tenth of the time — the pattern sells itself.

One relay down. Tomorrow: the biggest relay of all — the one in your inbox.

Today · one task

Run the prompt above on the last twenty-four hours of your inbox, right now. Read the three that need you first, then the drafted replies waiting in the queue. Save it as THE INBOX PRESS.

The first hour of your day belongs to your inbox — sorting, triaging, typing the same polite replies. From tomorrow, you open it and the sorting is already done.

You'll have: THE INBOX PRESS saved — inbox labelled and prioritised, routine replies drafted into a queue, and the three mails that genuinely need you, surfaced.

  1. Run the press below on today's inbox, right now. Watch it work in front of you: labels on, priorities set, the routine replies drafted, the three that need your actual brain pulled to the top.
  2. Read the three, then the drafts. The three are your morning. The drafts are a queue — approve and send the good ones yourself, edit the near-misses, ignore the rest. Nothing goes anywhere without your tap.
  3. Save it as THE INBOX PRESS. Tomorrow morning, run it before the coffee's done — and when you're ready for it to be waiting before you wake, the schedule is one tap away.

Sort my inbox from the last 24 hours. (1) Label everything: needs-me, routine, reading, noise. (2) Surface the THREE that genuinely need my judgement, with one line each on why. (3) For the routine ones, draft replies in MY VOICE into a queue — short, warm, done. You label and draft ONLY: you never send, you never delete, you never archive. Every draft waits for my tap. If something looks important but you're unsure, put it in needs-me — too careful is the right kind of wrong.

COPY

Rescue — Mail still locked behind IT from week one? This lesson is waiting on one click — chase the 1.3 note today; it's worth the nudge, because this is the lesson that pays for the whole connection.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

Inbox sorted, at least three replies drafted and waiting — nothing sent, nothing deleted.

Want more — The morning schedule is the natural upgrade: sorted before you wake, drafts queued with the sunrise. Powers stay exactly as written — label and draft, never send, never delete. The Roll records it either way.

The morning hour just came back. Tomorrow it becomes policy — one page that changes what "doing the work" means here.

Today · one task

Draft the charter from this week's wins, spend ten minutes editing it into your own words — then convert one person today: their next task drafted by machine, approved by them, timed.

Everything this course has built runs on one quiet rule: machines draft, humans approve. Today that rule stops being your habit and becomes your company's operating system — on one page, live by tonight.

You'll have: THE APPROVAL CHARTER — one page: which work machines draft, which humans approve, and how fast approval turns around. And one team member who ran one real task the new way today.

  1. Draft the charter with the press below. It reads your week — the audit, the collapsed relay, the inbox queue — and drafts the page: what machines draft here, what humans approve, what machines never touch, and the turnaround a draft can expect.
  2. Edit it as the owner, not a committee. Ten minutes, your pen. The words matter — "approving IS the work" is a sentence your company will quote back to you.
  3. Convert one person, today. Pick one team member and one task from the audit. They run it draft-first — machine drafts, they approve — and you both time it. When it beats doing it by hand, the charter has its first believer.

Draft THE APPROVAL CHARTER for my company — one page, plain words, in MY VOICE. Sections: (1) THE RULE — machines draft, humans approve; approving is the work now, and it carries the same authority signing always did. (2) WHAT MACHINES DRAFT HERE — from this week's audit and builds: {name the processes}. (3) WHAT HUMANS ALWAYS DO — judgement calls, anything leaving the building, anything touching money, people or promises. (4) WHAT MACHINES NEVER HOLD — spending, sending, deleting: never all together, mostly not at all. (5) TURNAROUND — a draft waits hours, not days; an approval is a decision, not a queue. Make it a page a good person reads once and understands forever.

COPY

Rescue — Team member's run took LONGER than by hand? First runs carry setup. Time their second run of the same task tomorrow — the charter's claim is about the pattern, and the pattern shows up on run two.

Did you get this done?

The charter exists, edited in your words — and one person's draft-then-approve run beat doing it themselves.

Want more — Put the charter on the shelf and give the Oracle a copy — from today, "what's our policy on AI drafting?" has a cited answer. Week 9 redraws the org chart on this page's foundation, and Week 12 hands over power on its rails.

Week six is in. The hours have names, the dreaded email writes itself on the drive, one relay is dead, the inbox sorts itself — and the way your company works has a new operating rule, on one page, with your name under it. Next week: money.

Week 6

The payroll works differently now.

Five for five. Three reclaim targets named with numbers, the entire reply backlog cleared on one drive home, a two-day relay collapsed to one approval, an inbox that sorts itself before coffee — and a one-page charter that makes approving the new doing, with its first convert already timed. The hours you were already paying for started coming home this week.

0 of 5 done

The week's quiz · seven questionsNO PASS MARK · IT TEACHES
Continue → Week 7