Why You Should Ask: "What's Staying the Same?

You just received an announcement about a major change at work. New system. Process update. Organizational restructure.

The email explains what's changing. It's clear. It's thorough. It's professional.

And you still don't know if your job just got turned upside down or if this barely affects you.

Here's the question that clarifies everything: "What's staying the same?"

Why this question matters

When your brain receives news about change, it doesn't calmly evaluate the new information. It runs a threat assessment.

What else might be changing that they didn't mention? What am I going to lose? What's the real scope here?

This isn't catastrophizing. It's biology. Your nervous system is designed to scan for danger during uncertainty. And organizational change triggers that scan.

Without explicit boundaries, your brain assumes the worst-case scope. That vague announcement about "streamlining operations" could mean anything. Your role could be eliminated. Your team could be disbanded. Your entire workflow could be rebuilt.

Or it could mean almost nothing changes for you.

You have no way to tell unless someone explicitly says what's not changing.

What this question reveals

When you ask "what's staying the same," you're forcing clarification on scope.

Good leadership will answer with specifics: "Your reporting structure isn't changing. Your current projects stay on track. The weekly meeting format remains the same."

Poor communication will give you vague reassurance: "Don't worry, this won't affect you much." That's not an answer. That's deflection.

If they can't tell you what's stable, either they haven't thought it through, or the scope is bigger than the announcement implied. Either way, you just learned something important.

This protects you from false alarms

Most organizational change announcements are written too broadly. They use enterprise-wide language that makes it sound like everything is shifting.

"We're implementing a new approach to customer service" sounds like it affects everyone. But if your role has no customer contact, this might not touch you at all.

Without asking what's staying the same, you'll spend energy worrying about a change that doesn't apply to you. You'll prepare for disruption that never arrives. You'll waste bandwidth on false alarms.

Asking for stability anchors prevents that.

This also catches gaps when change is real

Sometimes the change does affect you, but the announcement glossed over critical details.

When you ask "what's staying the same," you might discover that something you assumed was stable is actually changing. Your workflow. Your team structure. Your decision authority.

If leadership says "everything else stays the same" but you know that's impossible given what they described, you've identified a gap. They either haven't thought through implications, or they're withholding information.

Now you know to probe further before the change hits.

How to ask this without sounding "difficult"

You're not challenging the change. You're asking for clarity.

Frame it operationally:

"To make sure I'm focusing on the right things—what's staying the same in terms of [reporting structure / current projects / daily workflow / team responsibilities]?"

This signals that you're trying to execute well, not resist. You're asking for boundaries so you can adapt efficiently.

Most managers will appreciate the question. It shows you're thinking systematically. And if they can't answer it, that's data.

You deserve to know the scope

Change is hard enough when you understand what's actually shifting. It's exponentially harder when you're defending against unknowns.

Your brain needs stability anchors to process change effectively. Without them, you're operating in constant threat assessment mode. That's exhausting. It's also unnecessary.

You have the right to know what's changing and what's not. If leadership hasn't provided both sides, ask for it.