So I asked for help. The advice was confident. I provided make, model, specs, everything it needed.

It told me SATA. I bought SATA.

I cloned the old drive. Installed the new one. The case slid back in place smoothly. It booted up without a problem. Everything that could go wrong went right.

But then shortcuts were missing and programs didn’t load. The drive I replaced was my data drive, not the OS drive.

My C: drive was an M.2 stick drive, not SATA. The execution was clean, but the diagnosis was wrong.

I sat with that for a minute. The frustration of it. Not just the mistake. The specific quality of a mistake that only happens when you do everything right.

Eventually I pulled the service manual. Found an extra SATA port I didn’t know existed. Ordered a data cable and a power splitter. And figured out that the clone I’d written off as wasted work would boot fine from the new location.

The false start wasn’t wasted. It just wasn’t useful yet.

But the thing I keep coming back to isn’t the pivot. It’s the moment before it. When everything worked and nothing was fixed.

Confident advice isn’t the same as correct advice. And the gap between them is usually invisible until it isn’t.

There’s a version of that I’ve always called discipline. Show up when you said you would and finish what you started. Don’t improvise when you committed to something. Eliminate decision fatigue.

But at one point this weekend, I had a window and a choice. The plan said wait. Something quieter said go.

So I went.

It felt strange. Not wrong. Just unfamiliar. Like a muscle I don’t use enough.

After a bit of discomfort the muscle felt better for having been used. The drive would still get me home, but under the lights it was also something new.

Often the plan stops being a tool and starts being a rule. How often risk avoidance looks like discipline from the inside. How often we stay in our processes, procedures, and the way we’ve always done it, not because it’s the right call, but because leaving wasn’t in the plan.

Rigidity dressed up as discipline is still rigidity.

Worth noticing.

So far, I’ve been using my two modern Lodge skillets, but last weekend I stumbled across a late-period era Wagner at an antique shop. Probably from the 60s or early 70s. Not quite vintage, but older than I.

It wasn't in bad shape. No warping, no cracks. Just decades of carbon and old seasoning built up in uneven layers. Just rough and dark and a little neglected looking.

Someone had loved that pan.

There’s a whole process for restoring a pan like that: lye bath or Easy Off with the yellow cap and a day in a garbage bag to release the old carbon and seasoning, a good scrub, maybe a vinegar bath for rust. Followed by a good wash with soap and water, a towel dry, and a spell on the burner to completely dry things out and open the pores in the iron.

That’s all procedure. Written and repeatable.

What was unexpected, and what struck me, was the look of the bare iron.

Specifically the circular tooling marks from the craftsperson who pulled that skillet out of its sandy mold, hooked it to a lathe, and expertly machined it to a smooth finish. That’s something you don’t see in modern skillets. That’s a direct connection from that person’s labor, though the stovetops, ovens, and campfires of the last 60 years, and into my care where I can pass it along someday.

It’s been through three rounds of seasoning now and even cooked its first cornbread. Eventually I may not be able so see it, but I’ll know that fingerprint left by the lathe is there, proof of the care that goes into crafting something designed to endure.

It came from a consulting firm. Real money, real pages, a roadmap for what a system could do. No plan behind it. No resources. No one accountable for what happened next.

It was how I was supposed to learn what was possible.

I’ve seen versions of it everywhere since. The recommendations that never became decisions. The framework that lived in a presentation and nowhere else. The follow-up engagement to implement the recommendations from the last engagement.

It’s not always bad intent. Sometimes it’s just what happens when help is designed around a deliverable instead of an outcome.

A deliverable ends when the pages are done. An outcome ends when something actually improves.

The people I work with are busy enough already. The last thing they need is more pages.

Spent real time on it. Picked the metrics, designed the layout, got it into production. It was genuinely well made.

People kept sending emails with questions the dashboard was supposed to answer.

The easy explanation was that nobody read the announcement. And we all know people resist new tools. And maybe the training wasn’t enough.

The harder explanation was that nobody asked the people sending emails what they actually needed to see.

The dashboard answered my questions. Not theirs.

I keep coming back to this when leaders tell me they have a communication problem. Communication is almost always part of it. But it’s also a safe place to stop. You can admit poor communication without confronting the work that came before it.

The harder question is whether the case was built for the people who had to say yes. Not just the people already in the room.

The people still sending emails weren't the problem. They were the answer to a question I didn’t ask.

We didn’t workshop each other’s drafts. We didn’t share what we were working on. We got on a call, said hello, and wrote. Silently. For up to two hours.

It sounds strange but it worked remarkably well.

Nobody pushed anyone. Nobody checked in. People came and went as they needed. But, when the time was over, we’d done the thing that was easy to put off.

The accountability wasn’t pressure. It was just the quiet knowledge that someone else had blocked the same time and would be there when I logged on.

I’ve been thinking about that lately.

Protected thinking time is one of those things most leaders know they need and almost nobody actually keeps. Not because they don’t value it. Because it’s the easiest thing to give away. A meeting request lands. A question needs an answer. The calendar fills from the outside in.

Early Ink didn’t solve that just by adding discipline. It solved it by adding company. Writing, like leadership, can be lonely. And nobody wanted to be the one who didn’t show up. Once you were there, the work came easier than it did alone.

I’m holding lunchtime on Wednesdays for that same reason. Office Hours. Come with a question or just come to work. Either way, you won’t be keeping the time by yourself.

Join me for Office Hours here.

I said yes. Rolled up my sleeves. Started working.

I didn’t ask when they needed it. Who was waiting on it downstream. What done actually meant to them.

I asked about the how. Not the what or the when.

By the time I figured out I had the priorities wrong, someone was already waiting. The work wasn’t late because I was slow. It was late because I jumped in before I understood what I was jumping into.

I talk about clarity before execution. I believe it. I’ve seen what happens when organizations skip it.

Apparently I needed the reminder too.

The question I skipped was thirty seconds. The recovery took longer than that.

When do you need this? Who else is counting on it? What does done look like to you?

Thirty seconds of clarity. A lot less cleanup.

What’s the last thing you jumped into before you fully understood what you were jumping into?

It doesn’t look like abdication. It looks like effort. They’re in early, head down, doing. Answering emails that aren’t theirs to answer. Solving problems that belong to someone else. Moving things forward. Or so it feels.

But direction quietly goes dark.

The team keeps moving, because that’s what good teams do. They fill the vacuum with their best guesses, their competing priorities, their own noise. And the leader, buried in doing, doesn’t notice because doing feels like helping.

I see this pattern often. Usually in the hard stretches, when pressure is high and everything feels urgent. The instinct to roll up your sleeves is understandable. Even admirable, on the surface.

But the work that only a leader can do: naming what matters, setting the direction, helping people see where they’re going, doesn’t get done when the leader is doing everyone else’s.

The quiet question I keep sitting with:

What have you stopped leading because you started doing?