Nobody Handed You the Context. Build It Yourself.

Why everything feels equally important right now, and how to clear the fog for your team.

You're a couple of months into the new team.

You're in a leadership meeting and someone references a decision that was made last year. Everyone nods. You have no idea what they're talking about.

That afternoon, someone on your team asks what the real priority is this quarter. And you hear yourself hedging.

Nobody handed you a transition document. There was no briefing on the history, the politics, the old scars, the unwritten rules.

So you're making calls in the fog and hoping they land.

Here's what I want you to see.

Clarity is missing because you are short on context. And a context gap is something you can actually close.

Clarity is not certainty.

Certainty is knowing exactly how everything plays out before you commit to anything. You're never getting that. Not now, not three years from now.

Clarity is knowing where you're going, why you're going there, and what matters most right now, even while some of it is still unknown.

The pull toward certainty is strongest when you're new. No track record with your boss. No leadership capital with your team. A wrong call feels risky. So you wait. You gather a little more. You hold off on committing.

There's a researcher named Karl Weick, one of the leading voices on how organizations actually make sense of things. His work shows that effective organizations don't sit around waiting for perfect certainty before they act. They build a shared understanding that's plausible, coherent, and good enough to move forward together.

Good enough to move forward together. That's the bar.

And this is ten times harder for you than for the peer down the hall. She's been here five years. She's watched how this stuff plays out, so she knows what to take seriously and what to ignore.

You haven't. Not yet.

That's why everything feels equally important right now. It's why prioritizing feels so hard. You're missing the context to separate signal from noise, and that's an information gap. Information gaps close.

Become the Clarity Engine

That's what I call this job. Not a relay. An engine.

A relay passes messages down from senior leadership with no interpretation. That's the forwarded email with no note on it. Your team can read. What they need from you is the read.

A Clarity Engine runs three things on a constant loop. You gather context from every direction. You form a read on what it all means. You share that understanding with your team.

Gather. Make the call. Share. Then do it again.

Start with the gathering, and don't skip your own people.

Sit down one-on-one with your boss, your peers, your cross-functional stakeholders, and your direct reports. Here's what I ask.

"Tell me how you see the current situation in our business."

"Where is there resistance that I may not be aware of?"

"What constraints do I need to know about?"

Then keep the door open outside of those conversations. You're in a meeting and you can feel there's history behind the discussion that you're not seeing. Afterward you message a peer: "I could sense there was a lot of history behind that discussion. Would you mind helping me understand what I might not be seeing?"

Notice that I put your direct reports on that list. They're not just sitting there waiting to receive information from you. Some of them have been here for years. They have the exact pattern recognition you're missing.

Ask them and you get a double benefit. You get the context. And you show that person you value what they know, and that on this team it's okay to be a bit vulnerable. You're not pretending to have all the answers. 

Gathering isn't clarity. You still have to make the call.

This is where a lot of managers stall. You've got a pile of new information and you're waiting to feel sure about what it means.

Certainty isn't coming. Making the call is you looking at everything you've gathered, forming the most plausible read you can, knowing it's incomplete, and committing to it anyway.

You don't have to do that alone. Go back to someone who has the pattern recognition. Your boss, a peer, the senior engineer who has been here eight years.

"Here's what I'm piecing together. It sounds to me like our real priority is X, and I think behind the scenes Y is getting in the way. Does that match what you're seeing?"

If they say "yep, you've got it," a plausible guess just became real clarity and it cost you ten minutes.

If they say "close, but you're missing something," they just handed you the piece you needed.

Either way you come out ahead.

Hand over the understanding, not just the decision

Watch out for this pitfall. You walk out of that meeting and tell your team, "Our priority this quarter is outcome A."

Clean. Simple. And useless the moment they hit an obstacle.

In their heads they're asking: why not B? That's where we seemed to be heading. What changed? What got traded away?

They didn't get any of that, so they can't reason about it. All they have is the instruction, and now all they can do is wait for the next one.

Walk them through how you got there instead.

"We were weighing A against B. Leadership is seeing early churn signals in the enterprise segment, and that tipped it toward A. The trade-off we're accepting is that B slows down for a quarter. If the churn data changes, this could change too."

Same decision. Now they can move without you in the room.

Notice the last line of that explanation. I don't speak in absolutes with my team. When the plan eventually changes, and it will, nobody reads it as proof you were never clear to begin with. Clarity was only ever a plausible read, good enough to take action. A change of direction is new information doing its job.

Say that up front and a course correction doesn't rattle anybody. They were already expecting it.

Be careful with the first version of anything

Here's another pitfall to watch out for. Somebody comes to you in week two with a strong take. “This person is a low performer.” “That team is impossible to work with.” “This project is a lost cause.”

Taking action feels like leadership. But you don't have the pattern recognition yet to know whether you're hearing the truth, one person's version of it, or an old grudge coming back around.

Years ago I joined a product group that had recently been acquired by the company I worked for. At my first quarterly leadership offsite we spent hours debating one of the biggest strategic decisions facing the business. I walked out thinking we'd made real progress and were headed in a clear direction.

Three months later we came back together. Same topic. Same debate. Nothing had moved.

Three months after that, it happened again.

I had walked into a conversation that had been running for years, with competing priorities and deeply held beliefs I couldn't have understood on my first day. We eventually decided not to make the change at all.

If I had pointed my team where it looked like we were heading after that first offsite, I would have sent them the wrong way with total confidence.

Acting decisively on bad context is one of the fastest ways to burn your credibility in a new role.

So before you react, get another angle on the same story.

You're not going to feel sure.

You're going to feel sure enough to take action, and then you adjust as you learn.

Keep the engine running.

Best,

Jeff

P.S. If you've recently taken on a new team and it feels like you're guessing your way through every decision, let's connect on a short call. You will meet directly with me and we'll figure out where your biggest context gaps are and how to start closing them this week. Here's a link to my calendar.