Tuesday, August 18th, 2026

TUESDAY TACTICS | YOUR WEEKLY OPERATING BRIEF

Everybody plans the big push. Almost nobody plans the week that comes after it. Here's the protocol that keeps your momentum from quietly leaking out the back of the building.

I shipped something on Sunday that had been sitting in my drafts folder since June. Turned forty seven on Saturday, published the piece I'd been circling for two months, and by Sunday night it was out in the world doing whatever it was going to do.

Monday morning I sat down at my desk at 5:40 and accomplished roughly nothing until lunch.

Not because I was fried, although I was. Because I genuinely didn't know what came next. I had spent weeks building toward a specific date, and the date came, and then it was Monday and the thing that had been organizing my entire calendar was gone. There was no ramp on the other side. Just a flat stretch of week with nothing pulling me forward.

If you've ever finished a launch, closed a big client, wrapped a project you'd been grinding on for months, or hit any kind of milestone you'd been building toward, you already know this feeling. And if you're like most operators I talk to, you've probably chalked it up to being tired and moved on.

It isn't fatigue. It's a design flaw. And it's costing you more than you think.

Here's what actually happens when you run a big push.

For however many weeks, your calendar has an organizing principle. Everything you do is either directly serving the push or waiting until the push is over. Decisions get easy because there's an obvious filter. Does this move the thing forward or not? Yes, do it. No, park it. Your focus is borrowed from the deadline, and deadlines are excellent lenders.

Then the deadline clears, and the lender wants the lens back.

Now you've got an empty calendar, a depleted operator, and a giant pile of parked decisions that all became urgent the second the push ended. That's not a recipe for a strong week. That's a recipe for opening seventeen tabs, answering emails you should have delegated, and telling yourself you're "catching up" while your revenue engine sits idle.

I've watched myself do this enough times to stop pretending it's a character issue. The trough is predictable. Anything predictable can be designed around. And the operators who actually compound over years are the ones who treat the week after the push as a scheduled part of the push, not as leftover space.

So here's the protocol I've been running, refined by the fact that I violated most of it on Monday and paid for it.

The single most expensive habit in small business is finishing something and immediately starting the next thing without extracting anything from what just happened.

You paid for that information. You paid in hours, in stress, in the stuff you didn't do because you were doing this instead. The lesson is sitting right there and it has a shelf life of about four days before your memory sands off all the useful edges and leaves you with a vague sense that it "went okay."

So block ninety minutes. Not two hours, not a whole afternoon, because you'll never do it. Ninety minutes, within four days of finishing.

Four questions. That's the whole debrief.

First, what actually took the time? Not what you thought would take the time. What did. If you're tracking your hours you'll have the answer already, and if you're not, this is the argument for starting. I've been using Rize for a while now, mostly because it doesn't require me to remember to start a timer, which is the reason every other time tracker I've tried ended up abandoned inside a month. The value isn't the pretty charts. It's that when I sit down to run a debrief I don't have to reconstruct the week from memory, and my memory is a liar with an agenda.

Second, what did I do by hand that a system should have handled? Every push surfaces the same three or four manual tasks you swore you'd automate last time. Write them down. Not "automate my workflow." Write down the specific task, the specific trigger, and the specific output. That's the difference between a note and a build ticket.

Third, what did I say yes to that I shouldn't have? This is the uncomfortable one. Pushes are when your boundaries get tested, and most of us fold at least twice. Naming it now is how you don't fold in the same place next time.

Fourth, what would have made this 20 percent easier? Not 100 percent easier. Twenty. Small enough that you'll actually build it before the next push.

If your work happens on calls, the debrief gets a lot easier when you have transcripts to look at instead of vibes. I run Fathom on client calls and go back through the summaries during the debrief. Half the time the thing that cost me the most was said out loud in week one and I blew right past it.

Here's the mistake I make every single time, and it's the one I want you to avoid.

After a push, the temptation is to immediately announce the next push. It feels productive. It feels like momentum. It's actually just running from the discomfort of not having an organizing principle, and it guarantees you never rebuild the underlying operation.

Your baseline is the set of things that happen every week whether or not you're inspired. The outreach. The follow up. The content. The invoicing. The pipeline review. During a big push, most of those get thinned out or dropped entirely, and nobody notices because the push is generating enough noise to cover the silence.

Then the push ends and you find out your pipeline has a hole in it shaped exactly like the six weeks you weren't prospecting.

So before you commit to anything new, spend one week restoring the baseline. All of it. Every recurring block back on the calendar, executed at the normal level, no heroics. It will feel slow. It will feel like you're wasting the momentum. You're not. You're paying down the debt the push created, and if you skip this step you'll carry that debt into the next quarter and wonder why everything feels harder than it should.

One week. That's it. It's the cheapest insurance you'll ever buy.

I want to be careful here because "rest" has become a content category, and most of what gets written about it is either permission slips for avoidance or productivity advice wearing a robe.

Recovery is not the absence of work. Recovery is the deliberate reduction of decision load so your judgment comes back online.

That's a real distinction and it changes what you actually do. If recovery meant "no work," you'd take Monday off and feel worse on Tuesday, which is what usually happens. If recovery means "fewer decisions," then the move is to run a light week on rails you already built. Same wake up. Same first block. Same walk. Fewer new inputs, fewer new commitments, nothing that requires you to invent anything.

I'm about three weeks into rehab on a meniscus tear, and one thing that's carried straight over from the knee work into the business is that recovery has a protocol. Nobody tells you to just rest the knee. They tell you exactly what to do, how many, how often, and what pain level is acceptable. It's structured. It's boring. It works.

Business recovery should look the same. Five miles with Sheldon in the morning, three at night, and by the time I'm back at the desk the thinking is already done. That's not a wellness tip. That's where most of my actual work happens, and it's the first thing that disappears when a push takes over.

Most people automate the doing. Very few automate the starting.

The starting is where the leak is. You come off a push, you sit down, and there's no clear first move, so you invent one, and the one you invent is almost always email. That's forty minutes gone before you've touched anything that matters.

So build the re-entry. In Make I've got a scenario that fires on Monday morning and drops a single card into my board with three things on it, pulled from the parked list I built during the push. Not a dashboard. Not a project plan. Three things. The whole point is that the first decision of the week is already made before I sit down.

The same principle applies anywhere your operation restarts after a gap. Client onboarding, content cadence, follow up sequences. If the restart depends on you remembering, the restart is optional, and optional things stop happening in exactly the weeks you need them most.

If you're wrangling a handful of AI tools to do the drafting and summarizing inside those workflows, Galaxy is what keeps me from paying five separate subscriptions to five separate companies for the privilege of switching tabs.

Let me make this concrete, because frameworks are cheap and calendars are honest.

Tuesday morning, ninety minutes, debrief on the piece I published. Four questions, written answers, saved where I'll find it in October when I do this again.

Tuesday through Friday, baseline restoration. Every recurring block back where it belongs. Outreach at the normal number, not the ambitious number. Content produced on the normal schedule. Pipeline reviewed on Thursday like it always is.

No new commitments until Monday the 24th. None. If somebody wants something from me this week and it isn't already on the calendar, the answer is next week, and I've got a saved reply that says exactly that in a way that doesn't burn the relationship.

And one build. Exactly one. From the debrief list, the single highest leverage automation, scoped small enough that it ships by Friday. Not a platform. Not a rebuild. One thing that makes the next push 20 percent easier.

That's the week. It's not impressive. Nobody's making a documentary about it. But three months from now the difference between me and the version of me who skipped this will be measurable in the pipeline, and that's the only scoreboard I care about.

The reason most people don't run this protocol isn't that they don't know about it. It's that the week after a push is the week your identity has nothing to hold onto.

When you're pushing, you know exactly who you are. You're the person building the thing. The work does the identifying for you. Then the thing ships, and you're just a guy at a desk on a Tuesday with an ordinary week in front of him, and that's genuinely uncomfortable if your sense of self is riding on being in motion.

So people manufacture the next emergency. They start the next push before they've absorbed the last one. They stay busy because busy feels like being someone.

I've done it for years. It works right up until the moment it doesn't, and then you're forty seven, sitting at a desk on a Monday morning, realizing you've built a business that requires you to be in crisis in order to function.

The fix isn't discipline. The fix is having something to be when you're not pushing. A baseline you're proud of. Standards that hold on ordinary weeks. An operation that runs at a decent level whether or not you're on fire about it.

That's the actual work. The pushes are just the parts that get photographed.

Pick your most recent finished thing. Launch, project, client engagement, whatever. It doesn't have to be recent. It just has to be finished and undebriefed, which for most of you is all of them.

Block ninety minutes before Friday. Run the four questions. Write the answers down somewhere permanent.

Then look at your calendar for next week and ask whether it contains a baseline or just a bunch of reactions. If it's reactions, fix one block. Just one. Put the recurring thing back where it belongs and defend it for seven days.

You don't need a better push. You've proven you can push. You need a better week after, because that's the week that decides whether the push compounds or evaporates.

One step, one day. Grace over guilt.

— Dan Kaufman

Tools I use and trust. If you sign up through these links I may earn a small commission at no extra cost to you. I only recommend things I actually use.

Make.com — Automate your workflows without writing code

Rize.io — Time tracking that shows you where the week actually went

Fathom.video — AI meeting notes that actually capture what matters

Galaxy.ai — All your AI tools in one place

Beehiiv — Where serious newsletter operators publish