The New Manager's First 30 Days: What to Do, What to Avoid

Key Facts for New Managers

• 60% of new managers fail or underperform in their first 24 months, per a long-running CEB (now Gartner) study cited across leadership research.
• Gallup finds managers account for 70% of the variance in team engagement — more than any other single factor, including pay or perks.
• The average age of a first-time manager is 30, but they don't receive formal leadership training until around age 42 — a 12-year gap (Zenger/Folkman, HBR).
• DDI's Frontline Leader Project surveyed 1,100 first-time managers and found 87% wish they had received more preparation before stepping into the role.
• Benchmark 1:1 cadence for week one: 30–45 minutes with every direct report, completed within the first 3–5 business days.

The First-30-Days Listening Loop

A simple three-phase framework we use at Rework: Listen → Diagnose → Commit. In weeks 1–2 you listen (1:1s, meeting observation, no announcements). In week 3 you diagnose (synthesize patterns from your observation log into 2–3 themes). In week 4 you commit — make one small, visible change tied directly to what the team told you. Each phase gates the next; skipping straight to "commit" is how new managers erode trust before they've earned the right to change anything.

It's Sunday night. You got promoted last week. Your team already knows. On Monday you'll sit at the same desk, maybe in the same open-plan office, but with a different title and a different mandate you haven't fully unpacked yet.

You're not sure what you're actually supposed to do when you get in. Send an email? Rearrange the team meeting? Call a team all-hands? Post something inspiring in Slack?

Most new managers spend their first week doing too much too fast. They announce changes before they understand what's broken. They try to signal leadership when the team just wants to see if you're safe to talk to.

Here's the thing nobody tells you clearly enough: the first 30 days aren't about proving yourself. They're about understanding the situation so you don't make decisions you'll spend the next six months walking back.

Why the First 30 Days Matter More Than You Think

First impressions as a manager are different from first impressions as an individual contributor. When you were an IC, a bad first week could be corrected in week two. As a manager, your early moves create the mental model your team uses to interpret everything you do afterward. Research from Gallup consistently finds that manager quality is the single biggest driver of team engagement — and that dynamic takes root in the early weeks.

If you come in making changes, your team concludes: "She doesn't listen, she just does." If you come in invisible, they conclude: "He's hands-off, we're on our own." Neither story is what you want. The story you want is: "She took the time to understand us before she acted." That story gets written in the first four weeks.

And it's not just your direct reports watching. Your own manager has a set of expectations about what a good new manager does in the early days. Peers from other teams are forming opinions. Skip-level leaders may be watching whether you stabilize or disrupt your team.

The good news: you don't need to be perfect. You need to be present, curious, and intentional.

Week 1: Listen First, Announce Nothing

Your entire job in week one is to understand the people and the context. That's it.

Before you change anything, before you share your vision, before you reorganize the team meeting, you need to know: What does each person care about? What's been frustrating them? What do they hope you'll do differently? What do they hope you'll leave alone?

Schedule 1:1s with every direct report in the first three days. Not a team meeting where people perform for each other. Individual conversations. 30 to 45 minutes each.

Here are the questions to use in your first-week 1:1s:

• "What's going well on the team right now that I should make sure I don't accidentally break?"
• "What's one thing you wish the previous manager had done differently?"
• "What are you working on that you're proud of?"
• "What's getting in your way that I might be able to help with?"
• "What do you need from a manager to do your best work?"

You're not there to answer questions or make promises. You're there to listen and take notes. Do not start giving opinions about what you're hearing. Don't say "that's interesting, I've actually been thinking about changing that." Just say "thanks, that's helpful, tell me more."

Keep an observation log. A simple document where you write down patterns across conversations without attributing them to specific people. After five 1:1s, you'll start seeing themes. Write those down.

One thing you should announce in week one: your communication style. How you prefer to give and receive updates, how you'll use the 1:1 time, what your initial meeting cadence looks like. People don't need your full management philosophy yet but they do need to know how to reach you and what to expect from you week to week.

Week 2: Map the Landscape

By week two, you've talked to every direct report at least once. Now you need to zoom out.

Understand the team's actual goals. Not the ones on the slide deck. The real ones. What are you being measured on as a team? What does success look like for your manager in the next quarter? Where does your team fit in the broader company or department strategy? A team operating agreement built early in your tenure can make these norms explicit.

You should have your own 1:1 with your manager in week two (ideally week one). The questions to ask:

• "What does success look like for me in this role over the first 90 days?"
• "What are the team's top priorities right now?"
• "Are there any landmines I should know about: relationships, projects, things that are more complicated than they look from the outside?"
• "How do you like to communicate? How often do you want updates from me?"

Map the unwritten rules. Every team has them. Who's the informal leader people actually go to with problems? What decisions get made in the meeting vs. in the Slack thread before the meeting? What's the team's real relationship with the deadline: aspirational or actual? The Center for Creative Leadership identifies this context-gathering as one of the most underdeveloped skills in first-time managers — and one of the most consequential.

You learn these things by watching. Sit in meetings and observe as much as you participate. Read back through old project documents and decision threads. Ask people over lunch, not in a formal interview way but just by being curious.

Understand each person's current situation. By end of week two, you should be able to answer for each direct report: What are they working on? What's their main goal right now? What's blocking them? What's their relationship to the team like?

If you can't answer those questions for even one person, schedule a second 1:1 before week three.

Week 3: Establish Your Operating Rhythm

Week three is when you stop only observing and start setting expectations. You're not making big changes yet, but you are beginning to establish how you'll work together.

Set your 1:1 cadence. Weekly 1:1s with each direct report. Same time, same day if possible. 30 to 45 minutes. Let them own the agenda. Tell them: "This is your time. Come with whatever's most useful for you: current work, blockers, development, anything. I'll add things I need to discuss, but it's your meeting first." Read more about how to run these well in Running 1:1s Your Reports Look Forward To.

Establish your team meeting norms. If the team has an existing weekly meeting, keep it for now, but start to add structure: a shared agenda sent the day before, a clear purpose (updates vs. decisions vs. collaboration), and a summary of actions and owners sent afterward. You're not overhauling it yet. You're just making it slightly more useful. For a deeper look at when and why team meetings fail, team norms conversations are worth reading before you restructure anything.

Be explicit about your communication style. Some people need a lot of context to feel informed. Some people want just the decision and the why. You don't know yet which people on your team are which, so for now just tell everyone: "I prefer to communicate over-proactively in the early days. I'll share a lot of context because I'd rather give too much than too little."

Tell each person your working principles. Not a manifesto, just a few sentences. Something like: "I'll give you direct feedback. I'd rather say something awkward than leave you guessing. I expect you to tell me when something isn't working. I'd rather know early than be surprised." This sets the tone for the feedback culture you're building.

Week 4: Make One Visible Improvement

By week four you've listened, mapped, and established rhythm. Now you should act, but on something small, specific, and clearly connected to what your team told you in week one.

This is important. The improvement shouldn't be something you thought of. It should be something they asked for. The whole point is to demonstrate that you listened, you acted, and the team's input shaped the outcome.

Examples:

• They mentioned a recurring meeting that everyone dreads. You cancel it and replace it with an async update.
• They said the project kickoff process is confusing. You write a one-page brief template and use it on the next project.
• They mentioned a tool they've been asking for. You get approval and roll it out.

The improvement doesn't have to be big. In fact, small is better. A small, fast win in week four is more powerful than a big ambitious initiative you're still designing in week eight.

When you implement the change, be explicit about the connection: "I heard from several of you in our first conversations that X was getting in the way. Here's what I'm doing about it." This closes the loop and builds trust in the feedback process you're creating.

Common Mistakes to Avoid

Changing processes before you understand them. That meeting everyone says is pointless might be the only time two teams synchronize. That workflow that looks inefficient might be compensating for a technical constraint you haven't learned yet. Before you fix something, understand why it exists. A Harvard Business Review analysis of new leaders found that premature process changes are a leading cause of trust erosion in the first 90 days.

Over-communicating your plans. New managers sometimes broadcast their ideas to signal that they're thinking big. But your team doesn't need your roadmap in week one. They need to know you're listening and you won't make things worse. Save the big ideas for after you've earned the room.

Neglecting your own manager. You have direct reports now, but you're still someone's direct report. The managers who struggle most in early months are the ones who go heads-down on their team and forget that their own boss needs to know what's happening. Check in with your manager proactively. Ask for feedback on how you're doing. Don't wait for them to come to you.

Making promises you haven't researched. When someone tells you about a problem in week one, the instinct is to fix it immediately. But "yes, I'll fix that" in week one can become a broken promise by week four if you didn't understand the full picture. Instead: "Thanks for telling me. I want to understand this better before I say what I'll do about it."

Bonding at the expense of authority. If you managed former peers, this one is especially acute. Being liked and being trusted as a manager require different behaviors. Read Managing Former Peers before stepping into any peer dynamics you're not sure how to handle.

Your 30-Day Checklist

By the end of your first 30 days, you should be able to check these off:

People:

• Had a 1:1 with every direct report at least twice
• Know each person's main goal and biggest current blocker
• Know who the informal leaders on the team are
• Had an expectations-alignment conversation with your own manager

Operating rhythm:

• Weekly 1:1 cadence set with each direct report
• Team meeting has an agenda and a purpose
• Communication norms established (how you'll give updates, how you want to hear about problems)

Progress:

• Made at least one visible improvement based on team feedback
• Have an observation log with key themes from your listening tour
• Can articulate the team's top three priorities without looking them up

What you have NOT done:

• Announced a major process change before finishing your listening tour
• Made promises you haven't validated
• Disappeared into your own work and left the team without check-ins

Your Manager README: Optional but Powerful

One thing that helps new managers establish expectations quickly is a short "manager README," a one-page document about how you work. This kind of structured self-disclosure is backed by SHRM research on new manager effectiveness, which shows that managers who proactively communicate their working style in the first two weeks build psychological safety faster. Shared openly with your team in week one or two.

A simple template:

My working style:

• I prefer direct communication. If something isn't working, tell me early.
• I'm a morning person. My best thinking happens before noon.
• I tend to process new ideas out loud. Don't interpret my questions as disagreement.

What I need from you:

• Bring me problems early, not when they've already exploded.
• Tell me if you're unclear on a priority rather than working on the wrong thing.
• If you're going to miss a deadline, tell me before the deadline, not after.

How I give feedback:

• I give feedback close to the event, not saved for review cycles.
• I try to be specific and behavior-based. If I'm not, ask me to be.
• I'll sometimes ask "how do you think that went?" And that's not rhetorical.

You don't have to use all of these. Pick what's true for you. And update it as you learn more about yourself in the role. The README signals to your team that you're self-aware and willing to be accountable, both things they need to see early.

How Rework Supports the First 30 Days

New managers juggle three surfaces in week one: a listening log, a commitments tracker, and their own remaining IC work. Most end up with notes in Notes.app, promises in Slack DMs, and IC tasks in whatever tool the team was already using — three places, none of which talk to each other. Rework Work Ops gives you one surface for all three. Capture 1:1 observations as private notes attached to each direct report's profile. Log early commitments ("look into the kickoff template by week 4") as trackable tasks with owners and dates, so nothing promised in a listening tour quietly falls off. And if you're a new sales or revenue manager, Rework CRM lets you hand off your own pipeline to your team cleanly while keeping visibility during the transition — the single biggest failure point for IC-to-manager promotions in customer-facing roles. Work Ops starts at $6/user/month, CRM at $12/user/month.

What Comes After Day 30

Your first 30 days were about listening and establishing. The next 60 days are about making the decisions that day 30 prepared you for. You'll set team goals. Here's how to do that with a team that's skeptical of goal-setting: Setting Goals for a Reluctant Team. You'll build a leadership identity as the person who does the work shifts to the person who gets the work done. Read The Shift from Doing to Leading for how that actually happens. And if you're bringing on a new hire during this period, the manager onboarding checklist keeps your first hire from derailing your first 60 days.

But it all starts with 30 days of being genuinely present and genuinely curious.

The teams that trust their managers aren't the ones whose managers had the best plans. They're the ones whose managers actually listened first.

Learn More

• Running 1:1s Your Reports Look Forward To
• Managing Former Peers
• The Shift from Doing to Leading
• Setting Goals for a Reluctant Team
• Building a Team Operating Agreement
• Manager Onboarding Checklist