How to Talk to a Skip-Level Boss? Stop Just Saying "It's Going Fine"

How to Talk to a Skip-Level Boss? Stop Just Saying “It’s Going Fine”

At last quarter’s All Hands, the CTO suddenly asked me in the elevator, “I heard you guys wrapped up that cross-team project? How did it go?”

I froze for a second, then replied, “Um… it went smoothly.”

He nodded and walked away.

The moment the elevator doors closed, I started kicking myself: I could have been more specific. I could have talked about how we solved the problem of constantly changing requirements, how the impact had already exceeded expectations, how the team still had untapped potential…

But I didn’t. The only thought in my head was: “This is my boss’s boss. I’d better not say too much.”

This is how many people really feel when facing “skip-level communication”—saying more means risking more mistakes, so better to say less; or rambling on with details without hitting the point; or worse, leaving the impression that “are you trying to bypass your manager?”

It’s not that we can’t talk. It’s that we don’t know how to gracefully complete an “upward but not overstepping” communication in an organization with clear power boundaries.

In this article, let’s talk about the moment that’s easiest to stumble in, but also the most rewarding:

When a skip-level boss comes to chat, how do you respond without being awkward, without making mistakes, and still get remembered?

1. Not every conversation is “skip-level communication”

Many people hear “skip-level” and immediately think of taking shortcuts, snitching, or brown-nosing.

In reality, most skip-level communication happens naturally in high-exposure scenarios, such as:

A skip manager asks you a question during a project review meeting
After cross-department collaboration, another department head privately messages you to say thanks
During an organizational strategy adjustment, senior leadership does a “temperature check” and asks how you feel about the new goals

If you treat all of these as “better to say less,” you’re simply giving up your sphere of influence time and time again.

So the first thing is to redefine “skip-level communication”:

It’s not you proactively going to talk, but rather senior leadership showing curiosity, expectation, or observation toward you.
You just need to judge the intent, respond appropriately, without grabbing the mic or bypassing the process,
and you can complete an “upward value signal delivery.”

Simply put, it’s not about “stealing your boss’s job,” but about making good use of “the microphone the organization has already handed you.”

2. Skip-level communication = intent judgment + value anchoring + option supply

We can use this formula to structure a high-quality skip-level conversation:

1) Intent judgment: Why is he suddenly asking you?

A senior leader’s question is often more than casual. It could be:

🔍 A spot check on project effectiveness (e.g., Did it land as planned? Does the team buy into the goals?)
👀 A temperature reading on organizational climate (e.g., OKRs have changed a lot recently—is everyone keeping up?)
🧭 A covert assessment of talent (e.g., Can this person handle responsibility? Do they have upward potential?)

If you hear, “I heard you’ve been pretty busy lately?”
and you reply, “Yeah, there’s definitely a lot of work,”

then you’ve probably missed a signal check.

A sharper response could be:

“Yes, we just wrapped up Project X. The numbers came in a bit better than we expected, and the team has started discussing how to break down the new goals for the next phase.”

You’re not “reporting results.” You’re simply framing the information around “team status” and “project progress,” making it easy for the other person to pick up the signal.

✅ Tip: When faced with a vague question, don’t rush to share feelings. Instead, provide a structured snapshot of the current state.

2) Value anchoring: Talk only about impact, not emotions

A skip-level boss doesn’t really care “how hard you worked.” They want to know:

Is the problem you solved worth it?
Does your approach show methodology?
Does your understanding of the matter have depth?

For example, you’re involved in a cross-department collaboration project, and your boss’s boss asks, “Did you get that thing done recently?”

Beginner version:

“It’s done, but the marketing team kept changing requirements. We were actually pretty passive.”

👎 This can easily be read as “blaming others,” and it also reveals that you haven’t built a mechanism.

Advanced version:

“We did struggle with changing requirements at first. Then we added a ‘change tiering mechanism,’ and now requirements are basically stable—changes happen at most once every two weeks. The pace is much better.”

👍 This not only shows a solution, but also incidentally delivers a team methodology.

You’re not taking credit. You’re anchoring your awareness and sense of responsibility to a specific value through “problem-solving.”

3) Option supply: Don’t complain about problems; offer choices

If the skip-level boss asks about a problem you haven’t solved yet, don’t rush to vent about difficulties.

Instead, first describe the problem, then offer an option you’re already pursuing, or a direction you’d like them to decide on.

For example:

“While collaborating with the Infra team, we found there’s duplicated development in the data flow design. We’ve tried abstracting a unified data model at the access layer and have talked with them twice.
If there could be a coordination mechanism for a platform-level review, it might go faster. We can draft something on our side first.”

This structure carries an implicit message:
“We’re not bypassing anyone. We just want the problem solved faster.”

Reminder: Skip-level communication is not about making specific requests. It’s about offering options, letting the other person know that you have drive and respect organizational boundaries.

3. Avoid these two minefields

After covering what to say, we must also flag two high-frequency risks:

Minefield 1: Reporting specific problems up the chain

“I’ve told my manager about this problem many times, but he never takes it seriously, so I came to you…”

The moment you say this, no matter how tactfully, it sounds like you’re shifting blame onto your manager.

You may just want help, but the organizational structure will assume you’re undermining process trust.

A smarter way to say it:

“Our team is working on it, but we’re also evaluating whether we can simplify the entire collaboration path from a higher perspective. We can put together a first draft. If the direction is right, things will speed up after that.”

You’re not snitching. You’re handling a thorny problem with a “bigger picture” approach.

Minefield 2: Belittling your direct manager to “prove your own ability”

“My manager said this project wasn’t important, but I thought it was worth doing, so I pushed it forward myself…”

You may want to show independent judgment, but it sounds like you’re scripting a “my boss doesn’t see the value, so I’ll carry it myself” narrative.

A safer and more effective way:

“We had different opinions on the priority within the team. I tried building a small validation model first, and the data looked good, so I moved it forward. My manager also supports us learning as we go.”

✅ You don’t need to “win” the narrative. You just need to show the completeness of your thinking.

4. The best skip-level communication is like “planting seeds of trust”

Looking back on that elevator conversation, the boss’s boss wasn’t asking me to report anything. He was simply interested in the project outcome and wanted to casually check on the team’s state.

It was a probe of the organizational trust structure—
“Are you just an executor, or do you have independent judgment?”
“Are you waiting for your boss to speak, or are you already moving forward on your own?”
“Are you someone who sees problems, or someone who solves them?”

We think skip-level communication is about “saying the right thing,”
but its underlying logic is actually—
whether the other person is willing to give you a little more resources, information, or opportunities.

So next time you encounter a “skip-level” moment, don’t just say “It’s going fine.”

What you need to do is judge the other person’s intent, respond with a concise structure, and deliver the value you’re creating.

You don’t need to “push yourself forward.”
You just need to let the other person see that you’re already standing at the front of the line.