Four Buckets: Read Your Week Back to Yourself

Most business owners cannot tell you where their week went.

Not because they stopped paying attention. Because the week was forty small things, and small things leave no mark. You remember the two hard conversations. You do not remember the thirty-eight times you opened something, decided it did not matter, and closed it.

That missing thirty-eight is where the week actually goes. And you cannot hand off work you cannot see.

So here is the exercise. Something reads your week back to you and tells you which parts needed you and which parts never did.

The four buckets

Every item from your last seven days lands in exactly one of these. Not two. The forcing is the point, because the work that hides is the work that gets to be a little bit of everything.

• 1. Only me. Needs my judgment, my relationships, or my name on it.
• 2. A person's job. Needs judgment, but not mine.
• 3. A machine's job. Repeats, has rules, and hurts me when I skip it.
• 4. Should not exist. I do it out of habit and nobody would notice if it stopped.

Bucket three is the money. Bucket four is the mirror.

The prompt

Paste this into an agent that can reach your calendar and your task list. It will interview you first, then go pull the week itself.

You are my operations advisor. You are blunt and you do not flatter me.

Before you do any work, ask me these one at a time and wait for each answer:
- Which calendar should you read, and on which account?
- Where does my task list live?
- Should you read my sent mail for the same seven days?

Then pull my last seven days yourself. It will be messy. Do not ask me to
tidy it. If you cannot reach something, name the missing connection and tell
me what to connect. Never guess, and never work from an earlier session.

Sort every item into exactly one of four buckets:

1. ONLY ME - needs my judgment, my relationships, or my name on it.
2. A PERSON'S JOB - needs judgment, but not mine.
3. A MACHINE'S JOB - repeats, has rules, and hurts me when I skip it.
4. SHOULD NOT EXIST - I do it out of habit and nobody would notice if it stopped.

For each item, give the reason in six words or less.

Then tell me:
- The one item in bucket 3 costing me the most, and why you picked it.
- The one item in bucket 4 you are most confident about, and what happens
  if I stop doing it.
- One thing I put in bucket 1 that you think I am wrong about.

End with one sentence: what my week says about what I actually believe
my job is.

How to run it

It will ask what it can reach before it starts. Answer that part properly. A gap it knows about costs you nothing. A gap it guesses at costs you the whole exercise.

Do not tidy anything first. The mess is the data. If you clean up your calendar before running this, you are grading a version of the week that did not happen.

The six-word reason limit is not decoration. It stops the answer turning into a paragraph of hedging per item, and it forces a real call on each one. If a task needs three sentences to justify sitting in bucket one, it is not in bucket one.

Bucket four is why this is worth ten minutes

Bucket three is satisfying. You find the report you rebuild every Monday, the follow-up you retype from scratch, the numbers you pull into the same shape every time. Those are real, and they are fixable.

Bucket four is different. Bucket four is the work you do because you have always done it. A dashboard nobody reads. A check nobody has failed in two years. A meeting that exists because it existed last quarter.

Nobody has ever sent me the same bucket four answer. That is the part I would actually read yours for.

Then pick one thing

One item. Not the list. Take the single thing from bucket three that cost you the most this week and write it down properly, precisely enough that somebody else could make it run without you.

That written page is the thing a machine gets built from. Not a good intention, not a note in your head. A page with a trigger, the inputs, the rule, the exceptions, and what happens when something is missing.

The prompt that walks you through writing it is on the tool page below, next to this one.