2026 will redefine IT as a strategic driver of global growth. Automation, AI-driven support, unified platforms, and zero-trust security are becoming standard, especially for distributed teams. This toolkit helps IT and HR leaders assess readiness, define goals, and build a scalable, audit-ready IT strategy for the year ahead. Learn what’s changing and how to prepare.

Download the Toolkit

Sundays are for the ledger. Not the revenue ledger. The other one. The ledger where I write down what the week actually taught me, so I do not have to learn it again next month.

Most weeks, I learn a handful of things. Some of them are tactical. Some of them are uncomfortable. Some of them are things I have technically already learned before, but I had to be reminded, because the lesson had not yet gotten deep enough into my bones to change my behavior. That is most lessons, honestly. The first time you hear something, it is information. The twentieth time, it becomes instruction.

Here are three lessons from the past seven days that I want to lock in before they fade.

I had a situation this week where someone asked me to join a project. It was flattering. It was interesting. It had a lot of the surface features of an opportunity. And my gut, from the first read of the email, said no.

The old version of me would have stalled. I would have written a polite holding reply. I would have told myself I needed to think about it. I would have promised a response in a few days, which would have stretched to a week, which would have stretched to a quiet silence that the other person would have eventually read as a no, but not before they spent ten days in limbo waiting for me to make up my mind.

I did not do that this week. I wrote back within an hour. I thanked them for thinking of me. I told them it was not the right fit at this moment, and I was specific about why. I did not offer any wiggle room. I did not leave the door cracked. I closed the door, gently but firmly, and I wished them well.

Here is what happened next. Within two hours, the person wrote back and thanked me. They said they appreciated the clean answer. They said most people would have taken a week to get back to them, and the clarity was refreshing. They asked if there was someone I would recommend instead, and I was able to introduce them to someone who was actually a better fit.

Total time from their ask to resolution: under three hours. Total emotional energy spent on either side: minimal. Relationship preserved. New relationship created. Respect level: higher than it would have been if I had dragged it out.

The lesson, which I have technically already learned a dozen times but keep re-learning, is that delaying a no does not protect the relationship. It damages it. People would rather hear no today than maybe for two weeks. The polite holding reply is not polite. It is cowardice dressed up as consideration. And the longer you let it sit, the more expensive the eventual no becomes.

From now on, same-day no is the policy. I am writing it down so I cannot forget.

The second-order benefit of this, which I did not anticipate, is what it does to my own nervous system. When I let a decision sit in my inbox for a week, that decision is taking up mental rent the entire time. I am thinking about it in the shower. I am thinking about it on the drive. I am composing the reply in my head while I am supposed to be paying attention to something else. A same-day no closes the loop. The mental tab shuts. My head is lighter within an hour. That lightness compounds across a week. By Friday, the person who says no quickly has space in their brain to think. The person who drags it out is carrying seven open loops into the weekend.

This one stung a little. I went back through the last three months of content I have produced, newsletters, posts, podcast scripts, and I was honest with myself about which pieces landed and which ones did not. The pattern was clear. The pieces I produced in the morning, before my energy had been spent on meetings and reactive work, were consistently better than the pieces I produced in the afternoon or the evening.

Not a little better. Categorically better. Sharper arguments. Cleaner writing. More honest voice. The difference was not small.

This was not a revelation in the abstract. I have read the same advice from a dozen other writers and operators. Do your creative work when your mind is fresh. Do the reactive work later. Protect your mornings. I knew the advice. I just had not actually looked at my own output to see whether I was taking it.

I was not. My calendar for the last three months shows me doing email and client work from 9 to noon, three or four days a week, and then trying to do my creative output from 2 to 5. Which is, predictably, the least productive creative window in a working day. I was trying to write the sharpest version of my ideas at the exact moment my brain was least equipped to do it.

The fix was obvious. I moved creative work to the first two hours of the day, before email, before the inbox, before any meetings. I moved client work and reactive tasks to the afternoon, where my brain can coast on process rather than having to generate something new. It has been one week. The difference is already visible in the quality of what I am producing.

The lesson is not that mornings are magic. The lesson is that I was ignoring my own data. I had a pattern in front of me and I was choosing not to act on it because the current calendar was convenient. Convenience is a silent killer. It does not announce itself. It just slowly erodes the quality of your work until one day you look up and realize you have been underperforming for a quarter.

Look at your own data this week. Look at the work you have produced recently, and be honest about which pieces were sharp and which were muddy. Then look at what time of day you produced each one. The pattern will be obvious. And the fix will be too.

The deeper lesson here is that we have a habit of treating advice as if it applies to other people. You hear it, you nod, you say yes that makes sense, and then you never check to see if it applies to you. The reason the advice exists is because it is almost universally true. The reason we do not act on it is because we assume we are the exception. We are not the exception. We almost never are. The humility of auditing your own data, and discovering that the generic advice happens to be specifically accurate for you, is the beginning of real improvement. Everything before that is just collecting content.

The third lesson came from a conversation with a client this week. We were working through a tough call they were facing, a decision about whether to cut a service line that was generating revenue but eating more of their team’s attention than it was worth. The numbers were clear. The service line was unprofitable once you factored in the real cost of delivering it. They knew they needed to cut it.

They had known for six months. They had not cut it. And the reason they had not cut it was not the cut itself. It was everything the cut would trigger. The conversation with the team member who had built the service line. The awkward notification to the clients who were currently on it. The reshuffle of how leads would be routed moving forward. The question of what would replace the revenue. The question of what the cut said about them as a leader.

The decision itself, intellectually, was a five-minute conversation. The fallout of the decision was a six-month drag. And because they had not been separating the two in their head, they had let the fallout prevent the decision.

I did the same thing this week, on a smaller scale, with an offer I have been meaning to sunset for a while. The offer is not a strategic fit anymore. It has drifted from the core of what I want to be known for. And yet I had been keeping it alive for months, not because the offer itself was hard to kill, but because killing it meant I would have to tell a few people, update the website, reconfigure the onboarding, and admit to myself that I had spent time on something that was not going to compound.

Once I separated the decision from the fallout, the decision took ten seconds. The fallout is taking a week. But the decision is done. And the weight of holding the open question is gone.

The lesson is to always separate the decision from the fallout in your own head. Most of the time, the decision is simple. The fallout is what you are afraid of. But if you do not name the fallout as a separate thing, you end up stalling on the decision because the whole package feels too heavy to touch. Name the decision. Decide. Then treat the fallout as a project, with its own timeline and its own set of steps. That is how you stop getting stuck.

None of these lessons are new. All of them are things I have heard before, in different forms, from different teachers. What made them land this week is that they each cost me something concrete. A stalled opportunity. A quarter of mediocre output. A six-month-old decision I had been carrying around for no reason. The lessons were free in the abstract. They were expensive in the actual.

That is how most real learning happens, in my experience. You already know the lesson. What you do not know yet is the specific cost of not learning it. And the lesson does not actually stick until the cost has been paid. The cost is the teacher. The cost is what converts the information into instruction.

So if you are reading any of this and thinking, yeah, I already know that, welcome to the club. We all know. The question is not whether we know. The question is whether the price has gotten high enough yet for us to actually act.

I think mine has, on all three of these this week. We will see if the behavior sticks. I will report back.

One step, one day. Grace over guilt. 

— Dan Kaufman

Is your AI chatbot too wordy? It’s a Tuesday night and you need dinner inspiration, not an essay. 

heywa flips that. No long paragraphs to crawl through, just visual inspiration that matches how we actually explore. 

Try heywa. From finding new recipes through to identifying new habits which stick.

Try heywa for free