Since 1970, we have lost 3 billion birds in North America. Birds like the Snowy Owl are at increasing risk of extinction due to climate change. Birds are vital to healthy ecosystems - and their decline affects us all.

With over a century of conservation expertise, the National Audubon Society knows what it takes to protect the birds we love. And with your support today, we can.

Join us in protecting birds with a dependable, annual gift and we’ll send you our quarterly, award-winning magazine every year as our thanks.

Donate Now.

Happy Sunday.

The work week is over. The next one has not started yet. This is the small window I have come to value more than almost any other window on the calendar. It is the only time I get where I am not actively producing something or actively planning to produce something. It is the day I sit down and ask the question I do not ask often enough during the rest of the week, which is, what did I actually learn.

Not what did I do. Not what got shipped. What did I learn, and is the learning going to change anything about how I show up next week.

Three things landed this week. Some of them landed gently. One of them did not. Here they are.

I had a conversation early in the week that took a turn I was not expecting, and it ended up being one of the more useful conversations I had in a while.

The setup was familiar. Someone I work with was frustrated about a specific habit they keep trying to install and keep failing to install. We had been over it before. They knew what they wanted to do. They knew why it mattered. They had read the books, watched the videos, set up the systems. None of it was sticking, and the longer it did not stick, the more they were starting to identify with the failure.

I almost gave them the standard answer. Discipline. Consistency. Show up anyway. The standard answer is fine, and sometimes the standard answer is the right answer, but this time I caught myself and asked a different question. The question was, “what specifically gets in the way at the moment you would have to do the thing.” Not in general. Not as a theme. At the actual moment.

The answer, when we slowed down enough to look at it, was incredibly specific. It was not motivation. It was not willpower. It was a tiny, almost invisible friction in the environment at the exact moment they would have needed to take the first action. A misplaced object. An app that was buried two screens deep. A specific lighting condition that they associated with a different mood. The kind of thing that is so small it gets dismissed when you talk about it in the abstract.

When we addressed the specific friction, the habit started installing within four days.

The lesson I am taking from this is one I should have learned years ago but apparently needed to learn again. The gap between what we intend to do and what we actually do is rarely a character problem. It is almost always a logistics problem. And the logistics problem is usually smaller and more specific than we are willing to give it credit for, because admitting that the obstacle is small means admitting that we could have fixed it a long time ago.

The character framing is more flattering, in a way. If the issue is your character, you are someone with a deep struggle. If the issue is the location of an app on your phone, you are someone who could not be bothered to drag an icon. Most of us would rather have a deep struggle than a shallow oversight.

I have been auditing my own gaps this week with this lens. The audit is not flattering, but it has been productive. Two of my own stuck behaviors turned out to be downstream of friction I had not bothered to remove. Once removed, the behaviors are starting to install. Not because I got more disciplined. Because I got more honest about what was actually in the way.

If you have a stuck behavior, do not start with discipline. Start with logistics. Find the smallest possible obstacle at the moment of action, and remove it. Then watch what happens.

I had a long conversation with someone this week who is several layers ahead of me in their own build. The kind of person whose business is at a scale I have not yet reached, who has been at this longer than I have, and whose calm, when you sit across from them, is the kind of calm that you cannot fake.

I asked them, near the end of the conversation, what they have learned to protect most carefully as the operation has grown. The answer was not what I expected. I expected something about time, or focus, or strategic thinking. The answer they gave was sleep.

They said, with no theatrics, that the single most consequential variable in their operation is whether they had eight hours the night before. Everything else, including their judgment, their patience, their creativity, their willingness to handle conflict, their ability to make good calls under pressure, downstream of that one input. And as the business has grown, the only thing they have gotten progressively more strict about is what time they go to bed.

I sat with that for the rest of the day.

The lesson is not that I need to sleep more, although that might be true. The lesson is about the relationship between the size of what you are building and the smallness of the inputs you protect. The bigger the build, the more critical the small inputs become, and the more disciplined you have to be about the inputs that, in isolation, look unimportant.

Most of us treat the small inputs like they are negotiable. The sleep. The walk. The water. The five quiet minutes. The conversation with the spouse. The thing the kid wanted to show you. The boring thirty minute review you keep skipping. Each one of these, in isolation, can be deprioritized without consequence. The work of the day looks more important. The small input gets pushed to the side, again, and again, and again.

What I have been watching happen, in my own life and in the lives of operators I am close to, is that the small inputs do not bill in real time. They bill on a delay. You can skip the sleep for a week and feel mostly fine. By week three, you are making decisions you would not have made when you were rested, and you cannot tell, in the moment, that the decisions are off. By month two, your judgment is so degraded that you start to wonder if the business itself has gotten harder. The business has not gotten harder. The operator running it has gotten worse, in slow motion, and there is no alarm bell that fires when this happens.

The people who build the biggest things have figured out, often the hard way, that the small inputs are not actually small. They are the substrate. Everything sits on top of them. Treat them like they are unimportant, and the whole stack gets shaky.

I am going back through my own list this week, looking for the small inputs I have been quietly negotiating away. There are more of them than I want to admit. The work I do this coming week is going to be downstream of how I handle that list.

The third thing landed on me on Thursday, when I was sitting in front of my whiteboard, doing the thing I do when I am trying to figure out the next move for the business. I had been listing the things I needed to add. New tools. New automations. New offers. New people. New channels. The list had grown long, and the longer it got, the more anxious I felt, because every item on the list was a project, and I do not have the capacity to run twelve new projects in parallel.

I stood there for a while, looking at the list, and then I did something I do not do often enough. I asked the opposite question. Not what do I need to add. What do I need to remove. What is on the current stack that is not earning its keep. What process, tool, commitment, recurring meeting, or piece of work am I carrying out of inertia rather than utility.

The answer was much longer than I expected.

There were three recurring meetings I am hosting that nobody is getting real value from, including me. There were two software subscriptions I am paying for that I have not opened in six weeks. There was an offer I have been keeping alive because I cannot bear to let it die, even though it has not converted in months and the math no longer supports it. There were two relationships I am maintaining that have stopped being mutual, where I am the one doing all the lifting, and the lifting is not building anything.

By the end of the audit, I had a remove list that was twice the size of the original add list. The remove list, if I act on it, will give me back enough time, money, and attention to fund most of the items on the add list, without adding anything new to the schedule.

That is the lesson. The constraint is rarely capacity. The constraint is almost always the stuff I am still carrying that I no longer need to carry.

I think most operators are running a similar problem. The load looks heavy because the load is heavy. But a meaningful chunk of the load is not earning its place. It is just there because it was once there, and removing it requires a small act of administrative courage that we keep postponing.

I have been postponing my own remove list for months. I am not postponing it anymore. Some of the removals are going to be uncomfortable. The recurring meetings are with people who are going to have feelings about it. The offer I am sunsetting has a small group of customers who like it, even though they do not love it enough to refer it. The relationships I am stepping back from are with good people, just not the right people for this season.

The removals are the work this coming week. Not because I am chasing some minimalist aesthetic. Because the operation is running heavier than it needs to, and the heavy is the obstacle.

Go further with less. Not as a philosophy. As a practical move. Audit what you are carrying. Drop what is not earning. Watch what happens to your pace.

Three lessons. Logistics over character. Small inputs over big effort. Subtraction over addition.

If I had to summarize the week in one line, it would be that I have been making most things harder than they need to be, and the path forward is mostly about removing the friction, protecting the inputs, and dropping the carry. None of that is glamorous. None of that is going to make for a great post on LinkedIn. All of it is going to compound in ways I will not see for months.

I am going to take this list into the new week and let it run. We will see how it goes.

Thank you, as always, for being on the other end of these. The fact that any of this is useful to anyone besides me is something I have not gotten over. I hope at least one of these three landed somewhere it will do some good.

See you Tuesday.

One step, one day. Grace over guilt.

Dan

You're spending 40 hours a week writing code that AI could do in 10.

While you're grinding through pull requests, 200k+ engineers at OpenAI, Google & Meta are using AI to ship faster.

How?

The Code newsletter teaches them exactly which AI tools to use and how to use them.

Here's what you get:

Sign up and get access to the Ultimate Claude code guide to ship 5X faster.

Join 200K+ engineers