The week I planned and the week I had
2 min read
I meant to write this as a minute-by-minute diary of one week running QuickStaging. Then I went looking for the week and couldn't find it. There's no time log or journal, and no retro either. What I do have is a folder of plans and a commit log, and a gap between the two.
The plans
This summer I wrote three marketing plans in a row, each one smaller than the last.
The first had me spending eight hours a week to send 500 messages to real estate photographers. It lasted two days. The second cut that to two hours a week and 100 messages, and three weeks later the log showed zero messages sent.
The third was a two-hour weekly routine where I'd check the numbers, send a batch and follow up. I never ran it once.
The commit log
Over the same 23 days where I sent zero messages, I made 55 commits.
That's not unusual for me. QuickStaging has had commits every single month since February, 161 in the first month and never fewer than 47 since. Code is the part of the job I never have to talk myself into.
When I finally wrote down why, it came out as one sentence: every task that needs talking to strangers stalls at "draft ready", and every task that needs code gets finished.
Being honest about time
The next plan started with a sentence I wrote to myself: I can give four or five hours, but honestly, I'm going to get bored after a few days.
That reads like giving up, but it turned out to be the most useful line in the plan, because it changed what the plan was allowed to contain. If I'm going to get bored of any routine, the plan can't depend on one.
So there's no weekly manual check. A script emails me a snapshot of the numbers every Monday at 8 a.m., and if I ignore it, nothing breaks. Work comes in one-off blocks instead of habits, things I can finish in one sitting while I'm still interested. And wherever code can do the job, code does it. The outreach script picks leads, prepares a personal demo for each one and caps itself at 20 first emails a day. My part is approving each demo.
What a week actually looks like
Without a diary, the log is the most honest answer I have. A typical week is mostly building: a fix that came out of a customer complaint, a pricing change, an SEO cleanup. Somewhere in there is one small thing outside my comfort zone, done as a block rather than a routine, plus the Monday email, which I read with coffee.
No growth handbook would plan that week, but it's the one I actually keep.
If you're running something alone
Write down the plan you'd give a disciplined stranger, and next to it, what you did last week. If they don't match, I'd treat the second one as the real job description and plan around it.