Your First 30 Days as a Manager, What to Do (and What to Resist)

Three weeks into my first management role, I reorganized the team's project tracking system.

I had good reasons. The existing setup was confusing, tasks were duplicated across three places, nothing had clear owners. I spent a weekend building something cleaner and rolled it out on a Monday. Two people thanked me. One person was visibly annoyed and said almost nothing for two weeks after that. A fourth told me, months later, that she'd had that system exactly the way she wanted it and had just been starting to train a new contractor on it when I changed everything.

I hadn't asked anyone. I'd seen a problem and fixed it. That's how I'd operated as an individual contributor: move fast, improve things, show value. It was exactly the wrong instinct for the first month of managing.

Claire Hughes Johnson writes in Scaling People about new leaders who invest in understanding before acting, and how they build trust faster than those who move quickly to prove themselves. Fast movers often spend their second month repairing the relationships they damaged in their first. That was me. The project tracking system worked fine by March. The relationships took longer.

Your first 30 days have one job: understand what you inherited.

The biggest mistake new managers make in month one

It's not being too soft. It's not being too strict. It's changing things too fast.

When you're new, change signals one of two things to your team: either "this person knows something we don't," or "this person doesn't know what they're doing and is guessing." In month one, you don't yet have the credibility or context to make the first interpretation likely. So changes land as the second.

This doesn't mean do nothing. It means do the work of understanding before doing the work of improving. The changes that stick are the ones built on real knowledge of how things actually work, not how they look from the outside.

There's also a subtler risk: if you change something and it breaks, you don't yet have the trust to recover from it cleanly. You're still building the relationship that makes mistakes forgivable.

Wait. Watch. Learn. Then lead.

Week 1: Show up and listen

The goal of week one is to make it clear to every person on your team that your primary interest is in understanding them and their work, not impressing them or asserting yourself.

Have a 1:1 with each direct report in the first week. Keep it simple. Ask:

• What's your biggest priority right now?
• What's working well that you want to make sure stays intact?
• What's frustrating or in your way that you'd change if you could?
• What do you wish your previous manager had done differently?
• What would make you feel like this transition went well for you?

Take notes. Don't jump to solutions. Don't promise to fix things yet. Your job this week is to collect information, not act on it.

One thing I've found useful: ask each person the same questions in roughly the same order. When you do this across five or six people, the contrast in answers is revealing. One person says "what's working is how close-knit the team is." Another says "honestly, I'm not sure we work that well together." Both answers are useful. Neither would surface in a group setting.

Also: meet with your own manager. Understand what success looks like at 30, 60, and 90 days from their perspective. What are they worried about? What do they need from you? What's already working well that you shouldn't disrupt?

Week 2: Understand the dynamics

By week two you have enough information to start connecting dots.

You've heard what each person on your team is working on. Now ask yourself the harder questions: Who trusts each other? Who doesn't? Where's the tension? Who's carrying more than their share? Who's quietly disengaged? Is there something nobody's said out loud yet that everyone seems to know?

Teams have history. Relationships that predate you. Grievances that haven't been addressed. Systems that were built for reasons nobody remembers anymore. You won't see all of this in week one, but by week two, patterns start to emerge if you're paying attention.

This is also the week to observe your team working: in meetings, in how they communicate asynchronously, in how they interact with each other and with stakeholders. What's the actual culture, versus the stated culture?

Don't share your observations yet. Just log them.

Week 3: Map the friction points

Friction points are the places where work slows down, breaks, or creates stress for people. They're not always problems, sometimes they're just mismatches between how things are set up and how work actually needs to flow.

By week three, you should be able to identify three to five real friction points. Not complaints, friction points. Specific, observable places where something isn't working well and you now have enough context to understand why.

Examples: a team that has no shared visibility into each other's priorities, so people duplicate work. A handoff between two roles that's never been clearly defined. A recurring meeting that produces no decisions. A piece of process that made sense six months ago and doesn't anymore.

Write them down. Sit with them. You're not fixing them yet, you're building the list you'll prioritize in week four.

Week 4: Draft your first 30-day assessment

By the end of month one, you should be able to write a clear-eyed summary of:

1. What's working and should stay: things you've observed that are genuinely strong and should be protected, not disrupted
2. What needs attention soon: problems that aren't crises yet but will become them if left alone
3. What you still don't know: the honest list of gaps in your understanding that need more time
4. Your first two or three priorities: the specific things you'll focus on in month two, with clear rationale

This isn't a document you necessarily share with your whole team, though parts of it might be worth sharing in a team meeting to show you've been paying attention. The real value is internal, it forces you to synthesize everything you've learned and make a deliberate choice about where to start.

Sharing your priorities with your manager is important. It gets you aligned and gives them confidence that you're operating thoughtfully.

What success actually looks like at day 30

At the end of month one, success doesn't look like a team that's visibly better. It looks like a manager who understands what they inherited, has a real relationship with each person on the team, knows which two or three things actually need to change, and has resisted the urge to change everything else.

None of that is visible from the outside. No one will congratulate you for it. But it's the foundation that makes everything in months two and three actually work.

The managers who lead the best in their second and third month are almost always the ones who did the quiet work of listening in month one. I'm not sure there's a shortcut. The contractor I disrupted with my project tracking overhaul? She and I eventually built a good working relationship. But I earned that slowly, over months, not in the first week when I could have just asked her how things worked before changing them.

The New Manager Starter Pack at cadencehq.co/starter-pack includes a 30/60/90 Day Plan template, a 1:1 question bank, and a team onboarding checklist: everything you need to get through month one with structure and confidence.

And if you're ready to build a consistent 1:1 habit, try Cadence free at app.cadencehq.co: it's built specifically for managers who want to manage people better, not just track tasks.

Hit the ground running in your new role.

Cadence gives you 1:1 templates, team meeting agendas, and task tracking to build your management rhythm from day one. 14-day free trial.