Brief your AI tasks in your sharpest thinking hours, and review the output in your steadier, lower-stakes hours. Briefing is the creative, high-judgment part of delegation, so it deserves your best energy. Reviewing needs attention, but not your peak firepower.
Most of us do this backwards. We dump a vague request into a chatbot first thing, then try to fix the mess when we're already fried. Here's the system I use to line each stage of delegation up with the energy it actually needs.
Why delegation has three energy costs, not one
When you hand a task to an AI, you're really doing three separate jobs. Each one taxes a different kind of energy.
- Brief — deciding what you want, why, and what "good" looks like. This is the expensive one. Pure judgment.
- Assign — writing the instructions and kicking off the work. Mechanical, once the thinking's done.
- Review — checking the output against your intent, then accepting it or sending it back. Needs focus, not invention.
Treat these as one blob and do them all at 4 p.m., and the briefing suffers most. A weak brief is the biggest reason AI output disappoints. You didn't get a bad robot. You gave it a tired brain's version of the request.
The playbook: map each stage to a slot
Step 1: Find your three energy zones
You don't need a fancy audit. For three days, jot one word an hour: sharp, steady, or spent. The pattern shows up fast. Most people find one clear peak (often mid-morning), a reliable plateau, and a predictable slump.
Name them:
- Sharp — your hour or two of clearest thinking.
- Steady — competent and focused, but not inventive.
- Spent — low fuel, easily distracted.
Step 2: Batch your briefs into your sharp hour
This is the move that changes everything. Instead of briefing tasks the moment they pop into your head, collect them through the day and write the briefs together in your sharp window.
Why batch? Because good briefing has a warm-up cost. Once your head is in "define the outcome" mode, writing five briefs is far cheaper than writing one brief five separate times. You reuse the mental posture.
A strong brief answers a few questions before you ever type a prompt. What's the real outcome? Who's it for? What does done look like? What should the AI absolutely not do? Get those clear on paper first, and the prompt almost writes itself.
Step 3: Assign on autopilot
Assigning is the low-judgment step, so it goes anywhere convenient — the tail of your sharp block, or the top of a steady one. The thinking's already done. You're just turning your brief into instructions and pressing go.
This is where a consistent structure earns its keep. When every brief follows the same shape, turning it into an assignment is copy, adjust, send. No fresh decisions.
Step 4: Review during steady, never spent
Reviewing feels easy, so people shove it into the slump. Bad idea. Review is where you catch the subtle stuff: the confident paragraph that's slightly wrong, the tone that's off, the instruction the AI quietly ignored. That takes real attention.
Put reviews in your steady zone. Read the output against the brief you wrote, not against a vague memory of what you wanted. When it misses, you'll usually spot exactly which line of the brief was thin. Then you fix the brief, not just the output.
Step 5: Protect the brief hour like a meeting
The whole thing collapses if your sharp hour gets eaten by Slack. Block it. Treat briefing as the most valuable 30 to 45 minutes of your delegation day, because it is. Everything downstream inherits its quality.
A day in practice
Here's how a mapped day looks:
- 9:30–10:15 (sharp): Write four briefs for the day's delegated work. Define outcomes and guardrails.
- 10:15–10:30 (sharp tail): Assign all four. Fire them off.
- 1:30–2:15 (steady): Review two that came back. Accept one, send one back with a fixed instruction.
- 4:00 (spent): Nothing that matters. Maybe file or archive. No briefing, no judgment calls.
Notice you never make a real decision when you're spent. That's the point.
The shortcut, if you don't want to build it from scratch
Building this rhythm by hand works. But keeping the brief, assign, and review stages consistent day after day is where most people drift. If you want the structure ready to go inside Notion, I built The AI Delegation Pack: Brief, Assign, and Review to hold each stage in its own space, so you can batch briefs in your sharp hour and run reviews later without losing the thread. It's the honest shortcut to the system above.
FAQ
What if I only have one good hour a day?
Spend all of it on briefing. That's the highest-leverage stage. Push assign and review into your steady and slump hours. They tolerate lower energy far better than briefing does.
Can't AI just fix a vague brief itself?
Not reliably. AI fills gaps with assumptions, and its assumptions aren't yours. A clear brief written in your sharp hour beats any amount of tired back-and-forth cleanup.
How is this different from just writing better prompts?
A prompt is one line of the process. This is about when you do the thinking versus the checking. You can have a great prompt and still get poor results because you wrote it in a slump. Timing is the missing variable.
How long before I see a difference?
Usually within a week. Once briefs land in your sharp hour, the output improves fast, and reviews get shorter because there's less to fix.