Key Concepts
Task description vs. task as run: Every task has two versions: the one you would describe and the one that happened the last time you did it. An agent works from what you provide, so whatever you give it is what it will run.
Hidden step: A step you perform without noticing. The real number of steps is typically three to four times higher than the number a person first gives.
Exception: A sign that a decision got made and never got written down. Each one you surface becomes either a rule you can hand over or a point where the agent stops and returns the task to you.
Quick Reference
How to write down a task
- Recall the last time you ran it, not how you would describe it
- Write it one step at a time, including parts that feel too obvious to mention
- Check each verb for hidden steps
- Check before the work begins and after it ends
- Turn every exception into a rule or a stopping point
Where steps go missing
- Verbs: One verb carries several operations. “Compare the two pages” hides four: open two things, look for one specific kind of change, judge whether it is meaningful, and note the ones that are.
- Before the work begins: The first thing you open, such as a dashboard you glance at or a thread you scan for changes. It is an input, and the agent needs it.
- After the work is done: Small cleanup, such as updating a tracker, saving a copy as this month’s baseline, or marking something complete. It feels like an afterthought, and it makes the next run possible.
What to do with an exception
- Make it a rule: for example, what to do when the export comes back two days short
- Make a rule to hand the work back: the place where the agent stops and gives the task back to you because you would rather look at it yourself
Example: the weekly visibility report (11 steps as described)
- Export the data
- Open last week’s spreadsheet
- Copy it across and compare the columns
- See which pages dropped
- Search the prompts you track
- Look at who is showing up now that was not there before
- Read their pages
- Decide what matters
- Write the summary
- Post it to Slack
- Update the spreadsheet for next week
Benchmark: Wispr Flow
- Situation: Head of growth running all of marketing alone, with around 100 newsletter placements live in a given month. Admin was eating 10 to 20% of everyone’s week.
- Task as described: negotiate, sign a contract, write copy to spec, drop a tracking link, analyze, repeat
- Approach: built against the steps underneath each verb, not the description
- System: the contract goes in as a file, the CPM is checked, and the audience is researched. If price or fit looks weak, he is told before any copy is written. If the deal goes ahead, copy is written in Wispr’s voice and tracking links are built. Every step runs against performance data from every newsletter Wispr has run.
- Result: the system carries all 100 sponsorships a month
Notes
- The “walk away from a bad deal” step was missing from the three-line version of Matt’s job because it does not feel like part of running sponsorships. It was an exception written down as a rule.
- You cannot hand over work you cannot describe.