Sunday. The week's over, the next one hasn't started yet, and this is the hour I actually like best in the whole seven days.

Yesterday's edition was the unresolved stuff. Today's is the opposite. These are three things that closed this week. Not theories I read somewhere. Things that happened, that cost me something, and that I now know differently than I knew them on Monday.

Here they are.

I wrote on Tuesday about building decision rules so the tired version of you doesn't have to be brilliant under pressure. I stand by every word of it. And then Thursday happened and taught me the part I left out.

I have a rule about scope changes. If the work changes, the money conversation happens before the work, not after. Written down. Been operating on it for a while. Proud of it.

Thursday, a project I'm on grew. Not dramatically, but genuinely. Extra deliverable, extra stakeholder, an additional round of review nobody scoped. And I noticed it. That's what makes this useful instead of just embarrassing. I saw it in real time. I thought the exact words "this is a scope conversation."

And then I did the work anyway, and told myself I'd raise it at the next check-in.

Here's what I learned. Writing the rule was maybe twenty percent of the job. The other eighty is having a specific, pre-decided, low-drama sentence ready for the moment the rule needs to be enforced. Because in the moment, the barrier isn't that I forgot the rule. The barrier is that I have to say something slightly uncomfortable to a person I like, in a live conversation, without sounding like I'm nickel-and-diming them.

I never wrote that sentence. So when the moment arrived I had the principle and no language, and the absence of language is what actually killed it.

So I wrote the sentence Friday morning. It's about eleven words long, it's boring, and it's designed to be said out loud without any emotional weather attached to it. Something like: "That's a bit outside what we scoped, let me get you a number for it." That's it. No apology, no justification, no long preamble about how projects evolve.

The lesson generalizes further than I expected. Every rule I have that I actually keep, I have a script for. Every rule I have that I break, I've only got the principle. The enforcement is a separate skill from the decision, and I'd been treating them as one thing.

There's a second piece I didn't see until I'd written the sentence down. Having the language ready doesn't just make the conversation possible. It makes it smaller. When I'd imagined raising scope with this client, I'd imagined a whole negotiation. A discussion about the relationship. Some kind of reckoning. With eleven words prepared, it stops being a confrontation and becomes an administrative note. That's the difference between a thing you dread and a thing you just do.

Most of what I've avoided in business, I've avoided because I'd inflated it in my head into something larger than it was, and the inflation happened in the gap where the words should have been.

If you took anything from Tuesday's piece, add this to it. Write the rule, then write what you're going to say when someone tests it. The rule is for you. The sentence is for them.

There's a decision I've been sitting on since June. I'm not going to get into the specifics because it involves other people and it's not resolved enough to write about publicly, but the shape of it is this: a structural change to how part of my business operates, one that's clearly correct on the numbers, and that I've delayed four separate times.

Every delay had a reason. I wanted another month of data. I wanted to talk to one more person. I wanted to see how a related thing shook out first. Each of those was a real reason and none of them were lies.

This week I made myself write down, on paper, what specific piece of information I was still missing and what I would do differently depending on what it said.

I couldn't answer the second half. There was no version of the incoming data that changed the decision. I'd already decided in June. I was just waiting for the situation to become obvious enough that the decision would feel like it was made for me.

That's the thing I actually learned, and it stung a little. What I've been calling due diligence is frequently a search for cover. I want the numbers to get bad enough, or the pattern to get clear enough, that when I finally move, I'm not really choosing. I'm just responding to something undeniable. And responding to the undeniable is emotionally free. Choosing is not.

The test I built out of this is one question, and it's a good one. If the information I'm waiting on came back either way, would I do anything differently? If the answer is no, I'm not gathering information. I'm gathering permission, and there's nobody who can give it to me.

I've run this on four other open loops since Wednesday. Three of them failed the test. Which means I've been carrying three decisions around as if they were open when they were actually closed, and paying the mental rent on all three.

Closing a decision you already made is one of the cheapest energy recoveries available. It costs nothing but the willingness to admit you knew.

I'll add one caveat, because I don't want to turn this into a case for reckless speed. There are decisions where more information genuinely changes the answer, and moving early on those is just impatience wearing a productivity costume. The question isn't how long you've been thinking. It's whether the thinking is still doing anything. Some deliberation is load-bearing. Most of mine, this year, was not.

I got some feedback this week that I did not enjoy.

Someone whose judgment I trust looked at something I'd been working on and told me, without much cushioning, that the thing I thought was the strong part was the weak part. Not that it was bad. That it was doing something different from what I thought it was doing, and that the difference mattered.

My first reaction was the reaction. Defensive, internally. Started building the case. Started assembling the list of reasons they'd misread it. I didn't say any of that out loud, which I'm giving myself minor credit for, but it was all right there.

Then I sat with it for about a day and realized they were right, and that I'd known they were right about ninety seconds into the conversation, and that everything after that was my nervous system trying to protect a thing I'd already put a lot of hours into.

Here's the lesson, and it's not "take feedback well," because that's a bumper sticker.

The lesson is about the cost curve.

The people who tell you the truth are expensive in the moment. Every conversation with them has some friction in it. You leave feeling slightly worse than you arrived. There's a real, felt cost, and it's why most of us drift, over years, toward people who are easier to be around.

But the cost of the other kind is deferred and much larger. The people who agree with you cost nothing on Tuesday and cost you eight months on a bad direction. That bill just arrives later, and it arrives without a name on it, so you never connect it back to the pleasant conversations that let it happen.

I looked at my actual circle this week, seriously, for the first time in a while. Who tells me the truth? Not who's smart, not who I like, not who I've known longest. Who has actually said something to me in the last twelve months that I didn't want to hear.

The list was shorter than I'd have guessed. Not empty. But shorter.

What I'm doing about it isn't dramatic. I'm not firing anybody from my life. I'm just going to be a lot more deliberate about who I take real work to. There's a difference between people you enjoy and people you show the draft to, and I've been sloppy about that distinction because it felt like a slight to make it.

It's not a slight. Most people aren't equipped to give you hard feedback and shouldn't be asked to. Asking someone for a truth they can't give you is a setup for both of you.

And there's a mirror on this one that I don't love. If I want people who'll tell me the truth, I have to be one. Which means the conversations I've been softening, the feedback I've been rounding off to keep things comfortable, that's the same disease from the other side. I've been the pleasant one in a few relationships where somebody needed me to be the honest one.

That's the version I'm going to work on first, because it's the only half of the equation I fully control.

One practical note on how I'm going to do it, since I hate leaving something like that as a sentiment. When I catch myself about to soften something, I'm going to ask whether I'm protecting them or protecting me. Nine times out of ten in my experience it's me. I'm not sparing their feelings, I'm avoiding an uncomfortable thirty seconds. Naming that in the moment doesn't make the thirty seconds easier, but it does make it harder to pretend I'm being kind.

Three things. A rule needs a script. Waiting for information is often waiting for permission. Honest people cost more today and less over the whole run.

None of these were pleasant to learn. That's usually how you know they were real. The lessons that arrive gently are mostly things you already believed.

Tomorrow starts a new week. You don't need to overhaul anything. Pick one of these, find the one place it clearly applies in your business or your life, and do that one thing this week. That's it. That's the whole assignment.

The compounding takes care of itself if you keep showing up. It just doesn't feel like it's working while it's working, which is the tax on anything worth building.

Thanks for reading this week. Genuinely. There's a lot of noise out there and you gave me some of your Sunday.

Go easy on yourself today. You're further along than the story in your head says you are.

One step, one day. Grace over guilt. — Dan Kaufman