Last week I said that if this conference didn’t force the creative ship, I owed myself an honest look at why.

The conference happened. The ship didn’t.

So here’s the honest look.

Monday through Wednesday at the CNI Spring 2026 membership meeting in Salt Lake City. Good room. Library and archives people were reckoning openly with AI: what it does to their collections, their mission, their jobs. A lot of the anxiety I hear in hallway conversations at my own institution was getting named on the main stage.

I came home with seventeen meeting notes, eight new signals, and the feeling of having been in a room where my questions were other people’s questions too. Those conversations are the reason I went.

And yet.

  • Peak Monday. Strong energy at altitude. Went to every session, took good notes, leaned into networking. The forcing function was working.
  • Wednesday gauntlet. Flew home Tuesday night. Wednesday was a seven-meeting day at the office. A commitment I’d made weeks ago was simply “survive Wednesday.” I did, but it ate whatever buffer I had left.
  • Friday, Saturday, Sunday. Blocks that were supposed to become a newsletter and two blog posts. Instead I ran my most thorough weekly review yet, spent a Saturday sprint iterating my daily operating system, and put five focused hours into a subscription-management audit that’s genuinely useful AND is now my new comfortable thing.

I closed the week tonight with a coaching session, and I finally said something I’ve been circling for a while: productive procrastination is blocking output, at a structural level. The story I’ve been telling myself (discipline, willpower, habit) was the wrong story.

The comfortable work in my life isn’t TV or doomscrolling. I seem to settle into building systems, iterating skills, processing information, running audits. It’s objectively productive. It ships commits. It makes my weeks more efficient. It creates real gains.

It’s also, increasingly, where I hide from the riskier output.

This past week was a case study. My operating-system infrastructure moved forward meaningfully: a weekly-review skill that now generates a coaching handoff, a timing-loop that back-dates activity transitions correctly, a weekly-conversation skill that properly handles a home walk-through. Useful and shippable, but none of it public.

Meanwhile, three drafts of a Newsletter are sitting on my laptop. A CNI Day 1 blog post, polished, never published. Day 2 never even written.

Here’s the thing I couldn’t see until tonight. “Relaunch Newsletter” has become a totem. Three weeks of slip made it the symbolic First Public Thing, and the stakes inflate every time I approach it. It’s unshippable because I’ve loaded too much onto it.

The fix is structural. So I made two decisions tonight.

Shrink the first ship. Newsletter is formally pushed to a couple weeks out. The target this coming week is a single merged CNI wrap-up post, out the door by Thursday. One piece, polish bounded. The idea is to rebuild the ship muscle on something lighter before loading “Newsletter” back on it. My own guiding principle answers this cleanly: ship, then iterate. Volume advances the conversation. Newsletter #47 will look nothing like #1, so stop treating #1 like it has to be definitive.

Freeze the systems lane. No skill iteration, no subscription-audit deep-work, no tweaks to the operating system, until the CNI wrap-up is up. The audit is legitimate work AND it’s the current avoidance vehicle. Both things are true at the same time. The freeze addresses the second without denying the first.

When the urge to iterate on a skill hits this week (it will, it always does), the replacement move is already decided. Capture the idea as a Signal and park it for post-ship week. Or open the blog draft and add a sentence. Or go for a walk, because sometimes that urge is really an energy signal wearing a creative mask.

A few things I’m actually watching:

  • Whether the CNI wrap-up actually ships by Thursday.
  • Whether the freeze holds, and what specifically tries to break it.
  • Whether sleep, steps, and a and eating habits come back after cracking this week under travel. Health cracked hard: sleep scattered, steps low, sugary treats.
  • Whether “reset and restore” as a tone for the coming week actually survives into Tuesday, or whether I perform ambition again the moment my battery recharges.

My AI life coach (a phrase I still can’t quite say casually) made an observation that stuck tonight: I named the Explore-to-Ship Leak and built a forcing function out of the conference. Turns out the forcing function was just one input among several. Travel fatigue, productive procrastination, and three weeks of accumulated symbolic weight all teamed up on it. It couldn’t carry alone what I asked of it.

I notice, writing this, that the post itself is a small ship. A weeknotes entry on a Sunday night, for people I mostly don’t know who read this site, is exactly the kind of thing the systems-work freeze is meant to protect space for.

That’s the piece I keep missing. My Signal Path framework has a visible output step that I keep treating as the final step instead of the constant one. Publish something small regularly as the system compounds in the background.

This week: the wrap-up post. Next week: probably these weeknotes again. Eventually: the newsletter, after it’s stopped being so “important.”