Sunday, August 23rd, 2026

SUNDAY LESSONS | THE 3 THINGS I LEARNED THIS WEEK

Three lessons from seven days with no highlight reel, no crisis, and nothing worth posting about. Which turned out to be the useful part.

This was a nothing week.

No launch, no emergency, no big win, no disaster. I restored a bunch of routines that had gotten thin, ran a debrief, took the walks, did the rehab, showed up for the work. If you asked me Friday afternoon what happened this week I'd have struggled to give you a headline.

And then I sat down to write this and found three things worth keeping, which is more than I've gotten out of some of the dramatic weeks.

Here they are.

I spent Monday morning waiting for momentum to show up.

That's not a figure of speech. I actually sat at my desk with a coffee and a blank block on the calendar and waited to feel like doing something, because that's how I've understood momentum for most of my working life. Momentum is the state where the work pulls you instead of you pushing it. And when you're in it, everything's easy, and when you're not, you wait.

Monday I waited until about eleven. Nothing came.

What broke the stall wasn't inspiration. It was going back to the calendar from six weeks ago, before the push started, and just doing what was on it. Outreach block at nine. Content block at ten thirty. Pipeline review Thursday. The stuff that had been running on rails before I let a big project cannibalize the schedule.

By Wednesday things felt normal again. Not because I'd found motivation. Because I'd rebuilt the structure that had been generating the feeling I mistook for motivation in the first place.

That's the lesson, and I want to be precise about it. Momentum isn't upstream of your systems. It's downstream. The feeling of being in motion is a byproduct of having a baseline that runs whether or not you're inspired. When the baseline thins out, the feeling goes with it, and then you sit around waiting for a feeling that can't come back until you rebuild the thing that was producing it.

Which means the fix for a stalled week is never a mindset fix. It's an inventory question. What was running six weeks ago that isn't running now?

Almost always there are three or four things. Almost always you can name them in under two minutes. And almost always putting one of them back is enough to start the flywheel again, which is a much smaller ask than manufacturing enthusiasm from nothing.

The thing that makes this hard to see is that when the baseline is running well, momentum feels like a personal quality. It feels like drive. You start to believe you're a person with good energy, and you build a whole self image on it. Then a big project eats the schedule for six weeks, the baseline thins out, the feeling goes away, and now it doesn't read as a structural problem. It reads as a character problem. You think you've lost something in yourself.

You haven't lost anything. You dismantled the machine that was producing the output and then judged yourself for the output dropping.

I've spent entire months in that misdiagnosis. Reading books about discipline when what I actually needed was to put three recurring blocks back on a calendar. The books weren't wrong. They were just answering a question I didn't have.

I'd add one caveat, because I don't want this to read as pure mechanics. There are weeks where the baseline is running fine and you still feel flat, and those weeks are usually about something other than work. But you can't diagnose that until the structural stuff is ruled out, and most people skip straight to the emotional explanation because it's more interesting. Check the boring cause first.

I learned this one the expensive way, which is how I learn most things.

A couple weeks back I ran a call that ended in complete agreement. Everybody on board, nobody pushing back, done twenty minutes early. I remember thinking it was one of the better calls I'd had all month.

This week the bill came due. Two people had gone off and built toward two different interpretations of the same sentence, and about ten days of work had to be reconciled.

Nobody did anything wrong. That's the part I want to underline. There was no bad actor. We'd agreed on a phrase that was general enough to hold multiple meanings, and every person in that room heard the meaning that made sense from where they were sitting, and every one of them was reasonable.

Here's what I actually learned, and it goes beyond the meeting.

Agreement is easy to produce. If you want a room to agree, all you have to do is keep the language abstract enough. Talk about improving communication, being more strategic, focusing on quality, moving faster. Nobody argues with those. Everybody nods. You get consensus in about four minutes and you've bought absolutely nothing.

Alignment is expensive to produce. Alignment requires somebody to say the specific thing, and the specific thing always has a cost. It excludes options. It steps on somebody's assumption. It makes at least one person in the room mildly uncomfortable. That discomfort is not a bug in the process, it's the price of the product, and if you never pay it you never get the product.

So the practical thing I'm now doing, and it's almost embarrassingly simple, is that I don't let a meeting end on a phrase. Whatever we agreed to, somebody other than me says it back in their own words, out loud, and we compare. If it matches, we're done and it took thirty seconds. If it doesn't, we just saved ourselves two weeks.

Ran it three times this week. It matched once.

Once out of three. And these are people I've worked with for a while, in a small operation where I would have told you communication wasn't a problem. That number is the whole lesson.

The broader version, which I'm still sitting with, is that I've spent a lot of years reading the absence of conflict as evidence that things were fine. In business, in friendships, in the relationships where it matters most. Quiet is not the same as settled. Sometimes quiet means settled. Sometimes quiet means somebody stopped bothering to tell you. Those two states look identical from where I'm standing, and I've historically assumed the good one.

Assuming the good one is comfortable. It's also how you end up surprised by things you had every opportunity to see coming.

I ran a debrief this week on the thing I published last Sunday. Ninety minutes, four questions, written answers.

Question one is always what actually took the time, versus what I thought would take the time. And this is where I got humbled.

My internal story was that the writing was the hard part. Two months of circling it, drafting, deleting, rewriting. That's what it felt like from the inside, and if you'd asked me before I looked, I'd have said eighty percent of the effort went into the words.

The data said otherwise. The actual time was spent on formatting, on production, on the assembly and distribution mechanics of getting a thing from a document into six places. The writing itself was a fraction of it. The rest was logistics I'd never bothered to systematize because I'd been telling myself a story in which the writing was the whole job.

Two months of quietly believing something the numbers would have corrected in about fifteen minutes.

That's the lesson, and it's not really about time tracking. It's about the general category of things you can avoid indefinitely as long as you never look directly at them.

You can outrun a lot. You can outrun a conversation for years. You can outrun a decision by staying busy enough that you never have a quiet hour to make it in. You can outrun the state of your pipeline by only checking it when the news is likely to be good.

What you cannot outrun is the compounding. The thing you're avoiding doesn't sit still while you avoid it. It accrues. And when you finally turn around and look, you're not dealing with the problem you had. You're dealing with the problem plus every month of interest since.

The mercy in this, and there is one, is that looking is almost always cheaper than you expect. Fifteen minutes with the actual numbers corrected a story I'd been carrying for two months. Ninety minutes of debrief gave me a build list that'll make the next one meaningfully easier. The thing I dreaded looking at was smaller than the dread.

That's been true for essentially everything I've ever avoided. The avoidance was heavier than the thing.

Doesn't mean it's easy. Means it's worth it, and there's a difference.

What I've started doing about it is small and I'd recommend it. One number a week. Not a dashboard, not a review process, not some elaborate scorecard I'll abandon in three weeks. One number, picked specifically because I've been avoiding it, looked at directly on a Thursday afternoon whether or not I want to.

Some weeks the number is fine and I've been carrying dread for nothing. Some weeks it's worse than I thought and I get to start fixing it two months earlier than I otherwise would have. Either outcome beats not knowing. And after a few rounds of it, the dread starts to lose its grip, because you've built enough evidence that looking doesn't kill you.

That's the whole mechanism. Not courage. Repetition until the thing stops being scary.

Three lessons out of a week where nothing happened.

Momentum lives in the baseline, not in your head. Agreement is cheap and alignment isn't, and you can tell them apart by asking one question. And the things you're avoiding are collecting interest whether or not you're looking at them.

None of that is new information in the abstract. I've read versions of all three. What made this week useful was that each one showed up attached to something specific that cost me something, which is the only way a lesson actually installs.

If you're heading into a week that looks flat, that's not a bad week. That's the week where the real infrastructure either gets built or doesn't, and nobody's watching either way.

Pick one thing. Put it back on the calendar. Ask somebody to say it back to you. Look at one number you've been avoiding.

That's plenty for a Sunday.

One step, one day. Grace over guilt.

— Dan Kaufman