The grills are cold, the leftover potato salad situation is under control, and somewhere out there a dog is finally coming out from under a bed. The holiday weekend is winding down, which means it’s Sunday, which means it’s time for the weekly accounting.

This was a strange and useful week. The year hit its midpoint on Tuesday night, I ran my halftime audit, I read a book that rearranged some furniture in my head, and I spent a holiday thinking harder about freedom than I have in a while. Out of all that, three lessons made the cut. As always, these aren’t theories I collected. They’re things the week actually charged me tuition for.

Lesson One: The Scoreboard Doesn’t Care About Your Story

I sat down last weekend to score the first half of my year, and I want to tell you about the fifteen minutes before I opened the spreadsheet, because that’s where the lesson lives.

In those fifteen minutes, I had already graded the half in my head. I gave myself something like a B plus. Busy season, lots of momentum, a few things slipped but circumstances, you know how it is. The narrative was smooth and reasonable and mildly flattering, the way narratives tend to be when you’re both the author and the subject.

Then I opened the actual numbers, and the numbers told a different story in a couple of places. Not a catastrophic one. Just a different one. The newsletter operation graded out exactly as well as I thought, because I track it obsessively. But my time data showed I’d spent far more hours in reactive mode than my B plus story had accounted for, and two projects I’d been describing as almost done for months were, by any honest measure, not done and not moving. My story had them at ninety percent. The scoreboard had them at zero, because the scoreboard only counts finished.

Here’s what I actually learned, and it’s subtler than just measure things. The gap between my story and my scoreboard wasn’t random. It was concentrated exactly in the areas where I don’t keep numbers. Wherever I track, my self-assessment was nearly perfect. Wherever I don’t track, my self-assessment inflated like a parade balloon. Which means the inflation isn’t a character flaw I need to feel bad about. It’s a structural feature of untracked work. The story expands to fill the space the data doesn’t occupy.

The fix isn’t to become a harsher judge of myself. I spent years being a harsh judge and it produced nothing but noise. The fix is to shrink the untracked space. If something matters enough to be in my plan, it now matters enough to have a number attached to it, because I’ve seen what my brain does with the ones that don’t.

I see the same pattern constantly in consulting work, by the way, which is probably why it was so uncomfortable to catch in myself. Ask an owner how their marketing is going and you’ll get a story. Pretty good, we’ve been posting more, things feel like they’re picking up. Ask them for the number of qualified conversations that marketing produced last month and the room gets quiet. It’s never because they’re dishonest. It’s because feel is the only instrument they’ve got on the dashboard, and feel always reads a little rosier than the fuel gauge. The businesses that grow aren’t run by better storytellers. They’re run by people who got tired of being surprised by their own numbers and did something about it.

Lesson Two: You Don’t Need a New Plan, You Need a Smaller One

After the audit came the planning, and this is where I caught myself doing the thing I always do. I opened a fresh document and started building the Second Half Master Plan. Sections. Sub-sections. Quarterly targets feeding monthly targets feeding weekly sprints. Within an hour I had something genuinely impressive-looking, and I was enjoying making it, which should have been my first warning.

Because here’s the pattern I’ve finally got enough reps to see. The elaborateness of my planning documents has historically been inversely correlated with how much of the plan actually happened. The prettiest plans I’ve ever built were for the halves that went nowhere. The stretches of my life where I actually built things ran on plans you could scribble on an index card. This isn’t a coincidence, and this week I think I finally understood the mechanism.

An elaborate plan is a way of experiencing the satisfaction of the work without doing the work. You get the dopamine of progress, the sense of order, the feeling of being someone who has it together, and it costs you nothing but an afternoon. The plan becomes a performance for an audience of one. And the more detailed the performance, the more it postpones the uncomfortable moment where you have to actually do the first ugly, unglamorous task on it.

So I deleted the master plan. What survived is one page. Three outcomes with numbers on them, one thing I’m saying no to, the weekly actions that feed each outcome, and the date of the next audit. It took twenty minutes and it was less fun to make, which I’m now treating as evidence that it’s the real one. If your second half plan is impressive, be a little suspicious of it. The plan isn’t the product. The plan is supposed to disappear into the work.

Here’s a test you can run on any plan, and it takes ten seconds. Read the first action item and ask, could I do this before lunch tomorrow? If the answer is yes, you have a plan. If the answer involves the word phase, or requires three other things to happen first, or starts with the word research, you have a document. Documents are lovely. I’ve made hundreds of them. But nothing in my life has ever been built by a document. It’s been built by whatever was small and concrete enough to survive contact with an ordinary Tuesday morning, when I was tired and the inbox was loud and the grand vision felt very far away. Plan for that guy. He’s the one doing all the work.

Lesson Three: The Wave Doesn’t Wait for You to Feel Ready

I spent the week reading Mustafa Suleyman’s The Coming Wave, which I covered properly in Friday’s Roundup. But there’s one lesson from it that kept following me around after I closed the book, and it earned its spot here because of a conversation I had this week that made it land personally.

I was talking with a business owner I’ve known for years. Sharp guy, good operator, runs a real company with real employees. AI came up, the way it always comes up now, and he said the thing I’ve heard a dozen times this year. I’m going to wait until it settles down a bit. Let them work the kinks out. Then I’ll figure out where it fits.

Six months ago I would have nodded along. It sounds prudent. It sounds like the responsible, measured take. But sitting there with Suleyman’s book fresh in my head, I finally heard the assumption buried inside it, which is that there’s a settled state coming, some future plateau where the technology stops moving and the manual gets written and the careful people can safely climb aboard. The entire argument of the book is that no such plateau is coming. The wave doesn’t crest and calm. It keeps building, and the gap between the people riding it and the people watching it compounds every single month.

Here’s the part that got personal. I realized I run the same waiting pattern, just in smaller ways. There are tools sitting in my own stack that I use at maybe a tenth of their depth, because really learning them would mean a few weeks of being clumsy and slow at something, and I’ve got a comfortable routine that works. Waiting until it settles down and I’ll go deeper when things slow down are the same sentence wearing different clothes. Both of them quietly assume a future that isn’t coming.

The lesson isn’t panic. Panic is just waiting with extra cortisol. The lesson is that readiness isn’t a feeling that arrives before the reps. It’s a capacity that gets built by them. My pattern with AI stays the same as it’s been all year, I create, AI critiques, I refine, but this week put a new floor under it. One workflow rebuilt before Labor Day, clumsiness included, feelings of readiness not required. The wave’s coming either way. I’d rather meet it with calluses.

For me, the workflow I picked is my research process for these very newsletters. Right now it’s a patchwork of open tabs, half-organized notes, and my own memory, and it eats a chunk of every week that I’ve simply stopped noticing because it’s always been there. That’s the tell, by the way, if you’re looking for your own candidate. The best workflow to rebuild isn’t the one that annoys you most. It’s the one you’ve stopped seeing, the one that’s become part of the furniture. Annoyance at least gets your attention. The invisible stuff just quietly collects rent, year after year, and nobody ever audits the landlord.

The Thread Running Through All Three

Every Sunday I try to find the thread, and this week it’s not hard to spot. All three lessons are about the difference between the comfortable version and the true version. The comfortable story versus the scoreboard. The impressive plan versus the small one. The prudent-sounding wait versus the clumsy rep. In each case, the comfortable version flatters you and costs you the second half. The true version stings for about a day and then starts paying you back.

And I want to name something about that sting, because I think it’s where most people bail. The discomfort of the true version is front-loaded. You feel it immediately, right there in the moment you open the real numbers or delete the pretty plan or fumble through the new tool like a rookie. The cost of the comfortable version is back-loaded. You don’t feel it today. You feel it in December, all at once, when the year closes and the gap between what you told yourself and what actually happened comes due with interest. Same total price, roughly. Completely different payment plans. The whole game, as far as I can tell, is training yourself to prefer the front-loaded bill.

Six months left in 2026. That’s twenty-six weeks, twenty-six Sunday editions, twenty-six chances to close the gap between the story and the board. I don’t plan on wasting many of them.

Go easy on yourself tonight. Tomorrow we build.

One step, one day. Grace over guilt.

— Dan Kaufman