TL;DR

• Lead with curiosity, not authority, your job is to understand before you direct

• Use "Tell me about..." and "What would you do if..." questions in early 1-on-1s

• Build credibility through clarity on decision-making, not technical expertise

• Avoid pretending to know more than you do, seniors can spot it instantly

• Establish your leadership style early: ask good questions, remove blockers, protect their time

How do You Earn Respect as a New Manage in an Unfamiliar Department?

Short answer: Lead with curiosity, not authority. Admit what you don't know, ask smart questions in your first 1-on-1s, and focus on removing blockers rather than proving technical expertise. Your team will respect you for being transparent about your learning process and following through on what you say you'll do.

You just got your first management role. Congratulations.

Now the hard part: you're walking into a department you don't fully understand, leading a team that knows more than you do about the day-to-day work.

Maybe you're moving from marketing to operations. Or from individual contributor to leading a technical team. Or you've been promoted to manage a department that's been running without you for years.

Whatever the scenario, the challenge is the same: How do you lead people when you don't yet understand the details of what they do?

This is one of the most common, and most uncomfortable, leadership transitions. But it's also one of the most clarifying.

Because: you're not supposed to be the technical expert. You're supposed to be the leader.

Let me show you how to do that without pretending, without overstepping, and without losing the respect of your team before you've even built it.

Your Job Isn't to Know Everything - It's to Make Better Decisions Possible

The biggest mistake new managers make in this situation?

They think they need to prove they belong by demonstrating technical knowledge they don't have yet.

So they:

• Nod along in meetings when they don't understand

• Avoid asking "basic" questions because they don't want to look ignorant

• Make decisions too quickly to appear confident

• Jump in with ideas before they understand the context

And the team sees right through it.

Senior employees can smell fake confidence from a mile away. They've seen managers come and go. They know when someone is pretending.

What they respect is a manager who:

• Admits what they don't know

• Asks smart questions

• Makes decisions based on input, not ego

• Protects their time and removes blockers

Your authority doesn't come from knowing the technical workflows. It comes from making good decisions, being clear about priorities, and creating the conditions for your team to do their best work. (This is exactly what we work on inside the Resilient Manager Hub—how to lead with clarity even when you don't have all the answers.)

That starts with listening.

How to Approach Your First Few Weeks with Senior Team Members

Your seniors are watching you closely. Not because they want you to fail, but because they're trying to figure out what kind of manager you're going to be.

Will you:

• Micromanage or trust them?

• Listen or lecture?

• Protect their work or add unnecessary complexity?

• Make decisions that make sense or create chaos?

Here's how to show up in those first few weeks:

1. Lead with curiosity, not authority

Your first job is to understand before you direct.

In your first 1-on-1s, don't come in with a plan to fix things. Come in to learn.

Say this out loud:

"I'm here to understand how things work before I make any changes. I want to learn from you."

That one sentence does two things:

1. It signals respect for their expertise

2. It gives you permission to ask questions without looking weak

2. Ask "Tell me about..." and "What would you do if..." questions

In your first 1-on-1s, your goal is to understand:

• What they do day-to-day

• What slows them down

• What decisions they wish they had more control over

• What their biggest frustrations are

• What they need from you as their manager

Here are the questions that get you there:

To understand their work:

• "Tell me about a typical week for you. What takes up most of your time?"

• "What's one thing you wish people outside this team understood about your role?"

• "Where do things tend to get stuck or delayed?"

To understand decision-making:

• "What decisions do you currently have to escalate that you wish you could just make yourself?"

• "If you could change one process or policy tomorrow, what would it be?"

To understand what they need from you:

• "What did your last manager do that was helpful? What didn't work?"

• "What's the most useful thing I can do for you as your manager?"

To understand team dynamics:

• "Who do you go to when you're stuck on something?"

• "What's something this team does really well that I should protect?"

These aren't performance review questions. They're listening questions. And your job in these early 1-on-1s is to listen more than you talk.

3. Be transparent about your learning process

Don't hide that you're new to the department. Your team already knows.

Instead, frame it as a strength:

"I'm going to ask a lot of questions over the next few weeks. Some of them might seem basic. That's intentional, I want to understand how you think about the work, not just what the work is."

This does two things:

1. It removes the awkwardness of not knowing

2. It reframes your questions as leadership strategy, not ignorance

4. Establish your leadership style early

Your team is trying to figure out: What does this manager care about?

Be explicit about it.

In your first team meeting or in early 1-on-1s, say something like:

"Here's how I think about my role: my job is to make sure you have clarity on priorities, remove blockers, and protect your time so you can do your best work. I'm not here to micromanage. I'm here to make your job easier. If I'm not doing that, tell me."

Now they know what kind of manager you are. And they know what to expect from you.

How to Gain Respect While You're Still Learning

Respect doesn't come from knowing everything. It comes from:

1. Admitting what you don't know

When you don't understand something in a meeting, say:

"Can you walk me through that? I want to make sure I understand it correctly before we move forward."

Not:

"Got it." (when you don't)

Your team will respect you more for asking than for pretending.

2. Making decisions based on input, not impulse

Don't make changes in your first 30 days just to prove you're "doing something."

Instead, gather input, identify patterns, and then act.

When you do make a decision, explain your reasoning:

"Based on what I've heard from the team, here's what I'm prioritizing and why..."

That's not weakness. That's leadership.

3. Following through on what you say you'll do

If you say you'll follow up on something, follow up.

If you say you'll escalate a blocker, escalate it.

If you say you'll protect their time, don't add unnecessary meetings.

Credibility is built in the follow-through, not the promise.

4. Defending your team's time and priorities

One of the fastest ways to earn respect?

Push back on unreasonable requests from leadership or other departments.

When someone tries to add work to your team's plate, ask:

"What should we deprioritize to make room for this?"

Your seniors will notice. And they'll remember.

(Need help learning how to say no without guilt? Check out my free resilience resources for managers.)

Rookie Mistakes to Avoid

1. Trying to prove you belong by overexplaining your credentials

Your team doesn't care about your resume. They care about whether you make their job harder or easier.

Show them through your actions, not your backstory.

2. Making decisions without understanding the full context

Just because something worked at your last company doesn't mean it will work here.

Before you propose a change, ask: "Have we tried this before? What happened?"

3. Skipping 1-on-1s because "we're too busy"

Your team is watching to see if you prioritize relationship-building or just task execution.

If you cancel 1-on-1s, you signal that they're not a priority.

4. Treating senior employees like they need to be managed closely

Seniors don't need micromanagement. They need:

• Clarity on priorities

• Autonomy to execute

• A manager who removes obstacles

Give them space. Check in, but don't hover.

5. Pretending you have all the answers

The fastest way to lose credibility? Fake it.

If you don't know, say: "I don't know yet, but I'll find out."

Then find out.

Final Thought: You Don't Need to Be the Expert, You Need to Be the Leader Who Asks the Right Questions

You're not walking into this role to become the most technically skilled person on the team. You're walking in to make better decisions possible.

That means:

• Listening before you direct

• Asking questions that reveal priorities, not just processes

• Being transparent about what you're learning

• Following through on what you say you'll do

• Building trust through consistency, not perfection

Your seniors don't need you to know everything. They need you to be clear, steady, and willing to learn.

Do that, and you'll earn their respect faster than you think.

What about you? If you're a first-time manager stepping into an unfamiliar department, what's your biggest concern right now? Or if you've been through this before—what advice would you give?

Ready to Build Your Leadership Confidence?

If you're navigating the challenges of new management, whether it's leading an unfamiliar team, handling difficult conversations, or just trying to stay calm under pressure, you don't have to figure it out alone.

Take the free Manager Resilience Scorecard to see where you stand across the 5 pillars of resilient leadership. You'll get your personalized score and specific next steps to strengthen your leadership foundation.

It takes 3 minutes, and you'll know exactly where to focus your energy to lead with more confidence and less overwhelm.