If you’ve been waiting for a new post, congratulations on your patience. If you haven’t noticed I disappeared for two and a half months, congratulations on your healthy relationship with email.
The last post went out August 6. It is now October. In blogging years, that’s roughly a geological era.
I’m not going to write a “sorry for the delay” post. Nobody asked for one, and apologizing to a mailing list for not emailing it is the most performative thing I could do this week. What actually happened is a management problem, and I’m the manager.
There is no schedule, on purpose
I’ve never had never had a posting schedule. No “I aim for Tuesdays,” no “weekly, ish.” I’ve sat through enough planning meetings to know what a promised cadence turns into: a calendar full of slots and a person filling them with whatever can be produced by Thursday. Output goes up, quality goes down, and everyone calls it consistency.
I’d rather publish something I mean than something I scheduled. The price of that is gaps like this one.
I had plenty to say. That was never the problem.
I didn’t run out of ideas. The list is long, some of it is angry, some of it is useful, and a few are both, which is my favourite category. A sample of what’s sitting in the pile:
“Your Jira Board Has 400 Tickets and Three of Them Are Real”
“Please Stop Putting ‘Rockstar’ in the Job Posting”
“The Reorg Is Not About You, But You’re Getting a New Manager Named Dale”
“Why Is Every ‘Quick Sync’ Forty-Five Minutes?”
“Nobody Has Ever Read the Onboarding Doc, Including the Person Who Wrote It”
Ideas were never the bottleneck. Sitting down and doing it was.
Busy is real. So is “don’t wanna.”
I’ve been busy, and not in an impressive way. Among other things, my oldest started university in September, and apparently a kid leaving home generates a surprising amount of paperwork, money transfers, and staring at a quieter house. By the end of the day, what’s left isn’t the kind of attention writing needs.
If you manage engineers, you know the shape of this: a to-do list full of things that matter, a calendar full of things that are urgent, and the two have never met. Writing landed in the same pile as the retro you keep skipping and the career conversation that gets bumped for the outage. I wrote a whole playbook on running those properly, and I still skip them.
The other half is less flattering. Some evenings I had the time. I had a coffee, a blank page and a list of good ideas, and I looked at all of it and thought “nah.” No blocker, no good reason. I’d love to call it a creative reset, but it was just don’t wanna, the same one your best engineer has at 4 p.m. on a Thursday. That isn’t a character flaw, it’s information. Maybe they’re tired, maybe the task is badly defined, maybe they’re a person and not a throughput machine. A manager who treats every one of those as a performance problem ends up with a team that looks productive right up until people start leaving.
What I’d tell a manager (and myself)
Same advice, applied late to the one person I actually manage:
Work out whether it’s “can’t,” “won’t” or “shouldn’t right now.” They look identical from the outside and need different responses.
Don’t fake momentum. A fake schedule gets you fake output, and I’d rather you hear from me rarely than hear filler.
Put the important, non-urgent thing on the calendar before the urgent stuff eats it. Mine is now a recurring block I’m allowed to ignore.
Stop apologizing for things that aren’t wrongs. A gap is just a gap.
Bottom line
It’s easy for me to say no schedule, no guilt. Nobody’s paying me and nobody’s waiting. A lot of people leading teams have a cadence because someone upstream demanded one, and they’re quietly drowning in it. If your rhythm produces output you’re not proud of, question the rhythm first.
I’m still here, I have things to say, and I don’t know when the next one is coming.


The misclassification cuts in the other direction too. Reading a don't-wanna as a performance problem is the error you name, and it ends with people leaving. Reading a real performance problem as a don't-wanna is quieter: you keep offering patience to someone who needs a clear standard, and the standard can start dissolving in front of the whole team. The three labels earn their place because they force the question before the response; the part I'd watch is picking one and never revisiting it.
Well put, my newsletter has been on pause for over a year. I'll get back to it eventually. "Don't wanna" is a good enough reason.