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?