First-time manager field guide
The New Manager’s Guide: What to Do in Your First 90 Days
You got promoted. The title changed immediately. Your habits did not. This guide gives first-time workplace managers a practical path through day one, the first week, and the first 90 days.
Immediate answer
What should a new manager do first?
A new manager should first clarify expectations with their own manager, meet each direct report, understand the team’s current priorities, observe how work actually moves, and avoid major changes until there is enough context.
- Clarify what your manager expects in the first 30, 60, and 90 days.
- Meet every direct report and learn what helps or blocks their work.
- Understand current commitments, deadlines, risks, and unresolved problems.
- Set a simple rhythm for one-to-ones, team meetings, and urgent issues.
- Choose one small, visible improvement instead of launching a transformation.
The central rule: reduce uncertainty before you increase activity.
01
Before day one: prepare without scripting a performance
Gather enough context to avoid arriving blind, but do not build an elaborate reform plan before meeting the people who already understand the work.
Questions to ask your manager
- What are the three most important outcomes expected from this team?
- What problems require immediate attention, and what can wait?
- How will my performance be evaluated after 30, 60, and 90 days?
- Which stakeholders should I meet early?
- What decisions can I make independently?
- Where has the team struggled previously?
- Are there commitments already made that I need to protect?
Prepare a short introduction
Explain your role, your immediate approach, and what the team should expect from you. Keep it brief enough that it does not become a speech about your leadership philosophy.
“I’m going to spend the first few weeks understanding the work, the team, and where friction is showing up. I will not change processes just to prove I am active. I will be clear about decisions, follow through on commitments, and raise problems early.”
Do not promise that nothing will change. Do not promise that everything will improve quickly. Promise a fair process, clear communication, and steady follow-through.
02
Your first day as a new manager
Your first day is not an audition for authority. It is the beginning of an evidence-gathering process.
Meet your manager
Confirm immediate priorities, sensitive issues, decision boundaries, and what should not be disrupted. Ask which meetings matter and which reports are actually used.
Introduce yourself to the team
Keep the introduction brief. The team is mainly trying to understand whether you will create clarity or additional noise.
- Explain what you are responsible for.
- State what you will focus on during the first weeks.
- Explain how urgent issues should be raised.
- Confirm when individual meetings will happen.
- State that you will listen before making significant changes.
Start mapping the work
Collect the current priorities, owners, deadlines, dependencies, recurring meetings, and unresolved risks. You are not trying to solve them all. You are building a reliable picture.
Watch what people avoid
Pay attention to topics that create silence, unclear ownership, repeated delay, or emotional reactions. Those patterns often reveal more than formal reports.
03
Your first week: observe before you optimize
The first week creates a strong temptation to prove that the promotion was deserved. That pressure often produces unnecessary meetings, premature announcements, and solutions to problems that have not been understood.
Your first-week objectives
- Complete one-to-one meetings with every direct report.
- Understand the team’s active commitments and risks.
- Identify where decisions slow down.
- Learn how information currently moves.
- Clarify how urgent issues should be raised.
- Notice where ownership is unclear.
- Avoid changing roles, tools, or processes without evidence.
Questions for your first one-to-ones
- What are you responsible for right now?
- What is going well that I should avoid disrupting?
- Where does work usually get stuck?
- What decision are you waiting for?
- What do previous managers often misunderstand about this work?
- How do you prefer to receive feedback?
- What support helps you, and what support becomes interference?
- What should I know that will not appear in a report?
Run your first team meeting without trying to impress everyone
The first team meeting should create orientation, not theatre.
- State what you understand so far.
- Explain what you are still learning.
- Confirm immediate priorities.
- Clarify how decisions and urgent issues will be handled.
- Explain the one-to-one schedule.
- Invite corrections and missing context.
- End with specific next steps and owners.
Avoid vague language such as “my door is always open.” Explain when to message, when to wait for a one-to-one, and what counts as urgent.
04
Days 8–30: build a stable management rhythm
After the first week, your role shifts from observation toward controlled action. You still do not need a dramatic transformation. You need a repeatable operating rhythm.
Create a basic management system
- A predictable one-to-one cadence.
- A useful team-meeting rhythm.
- A visible list of priorities and owners.
- A clear path for decisions and escalations.
- A simple method for tracking commitments.
- A regular check-in with your own manager.
Consistency creates authority faster than intensity.
Build authority without becoming harsh
New managers often confuse authority with certainty, speed, or firmness of tone. Real authority comes from patterns people can predict.
- You make decisions when a decision is needed.
- You explain enough without defending every choice endlessly.
- You keep commitments.
- You address problems before resentment builds.
- You apply standards consistently.
- You admit what you do not know without surrendering responsibility.
“Based on the information we have, this is the direction we are taking. I will review it after we see the first results. Until then, let’s work from the same decision.”
Read more aboutbuilding authorityandstopping overexplanation.
Set boundaries with former peers
Managing former peers creates specific pressure. You may worry that setting expectations will appear disloyal or arrogant. The opposite risk is more common: avoiding necessary management to preserve the old relationship.
“I value the relationship we already have, and my responsibilities have changed. I need to be fair and consistent across the team. That means some conversations and decisions will feel different from before.”
Do not share confidential management information to prove that you are still one of the group. Do not give former friends special access, and do not compensate by treating them more harshly.
Read the full guide to managing former peers.
Delegate without micromanaging
Delegation is not moving a task off your list. It is transferring ownership with a clear finish line.
- The outcome required.
- Why the task matters.
- What good looks like.
- The deadline or review point.
- The authority the person has.
- What must be escalated.
- When progress will be checked.
“Please prepare the client-risk summary by Thursday at 2 p.m. It should identify the five largest risks, the owner of each risk, and the recommended action. Escalate anything that could affect the launch date. Let’s review the outline Tuesday afternoon, then you own the final version.”
Do not check every hour. Do not disappear until the deadline. Agree on the check-in before the work begins.
Read the complete delegation guide.
Give feedback before the issue becomes emotionally expensive
Delayed feedback rarely becomes easier. The manager spends days building frustration while the employee receives no clear signal that something needs to change.
- Describe the observable situation.
- Explain the specific behavior.
- State the impact.
- Clarify the expected change.
- Agree on the next checkpoint.
“In yesterday’s client meeting, the project update was missing the revised delivery date. That left the client unsure about the plan. In future updates, include the current date, the reason for any change, and the next decision point.”
Read the complete feedback guide.
Have difficult conversations while the problem is still manageable
Prepare the exact issue, the evidence you can describe without exaggeration, and the change or decision required after the conversation.
“I want to address a pattern that is affecting the team.”
Describe the pattern, listen to relevant context, and return to the expectation. A conversation can be respectful without becoming indefinite.
Read the difficult-conversations guide.
Manage up without sounding insecure
Your manager does not need a stream of anxiety. They need useful visibility.
- What changed.
- Why it matters.
- What you have already done.
- What decision or support you need.
- What happens next.
“The supplier delay puts Friday’s delivery at risk. We have moved two internal tasks forward and asked for a partial shipment. I need approval by 3 p.m. to use the backup supplier if confirmation does not arrive.”
Read the complete managing-up guide.
Protect your capacity
New managers often say yes to every request because refusal feels risky. The result is a manager who becomes the team’s emergency backup, approval queue, and emotional support line.
- Does this require my role or only my effort?
- What current priority will move if I accept it?
- Can ownership remain with the person closest to the work?
- Is the deadline real?
- What decision is actually needed from me?
“I can take this on, but it will move the reporting review to Thursday. Which outcome has the higher priority?”
05
Days 31–60: move from personal effort to team ownership
By the second month, you should know enough to distinguish isolated incidents from repeated patterns.
- Clarify ownership for recurring work.
- Remove one or two persistent bottlenecks.
- Improve the quality of delegation.
- Give timely feedback.
- Reduce meetings that do not produce decisions.
- Make team priorities visible.
- Build stronger stakeholder relationships.
- Review performance risks before they become crises.
This is also the stage where many managers return to individual-contributor work because it feels more comfortable. Resist proving value by becoming the team’s best technician again.
Your job is increasingly to improve the conditions in which other people perform.
06
Days 61–90: stabilize the system and choose the next improvements
By the third month, you should be able to explain:
- What the team is responsible for.
- What is going well.
- Where work repeatedly slows down.
- Which standards are clear and which remain vague.
- Who owns each major outcome.
- What decisions belong to you.
- What risks require attention next quarter.
Review the first 90 days with your manager
- Results delivered.
- Problems identified.
- Changes made.
- Changes deliberately postponed.
- Team capability gaps.
- Stakeholder risks.
- Your own management habits that need correction.
- Priorities for the next quarter.
Review the first 90 days with the team
You do not need a ceremonial presentation. Share what you learned, what changed, what remains unresolved, and what the next period will focus on.
- What we should protect.
- What we should improve.
- What we should stop.
- What requires a longer decision.
- What the next 30 days will look like.
07
What not to change too quickly
- Do not change a process solely because it looks inefficient from the outside.
- Do not reorganize roles before understanding informal responsibilities.
- Do not replace recurring meetings before learning what information they carry.
- Do not introduce a new tool when the real problem is unclear ownership.
- Do not announce standards you are not prepared to enforce.
- Do not promise resources before checking authority and budget.
- Do not copy your previous manager’s style without considering the new team.
- Do not confuse visible activity with useful progress.
08
The most common first-time manager mistakes
Immediate change
Trying to prove competence by changing systems before understanding them.
Overexplaining
Defending every decision because silence feels unsafe.
Taking work back
Rescuing delegated work at the first sign of difficulty.
Delayed feedback
Waiting until frustration becomes visible in tone or behavior.
Preserving friendship
Avoiding fair management to protect former peer relationships.
Constant availability
Teaching the team that every issue must pass through the manager.
Hidden trade-offs
Accepting work without showing what will move or be delayed.
Meeting instead of deciding
Creating discussion when the team needs a clear decision.
09
A condensed new-manager checklist
Before day one
- Clarify expectations and authority.
- Identify key stakeholders.
- Review active commitments and risks.
- Prepare a brief introduction.
First day
- Meet your manager.
- Introduce your approach.
- Confirm urgent priorities.
- Schedule one-to-ones.
- Avoid major announcements.
First week
- Meet every direct report.
- Map priorities, owners, and blockers.
- Learn how decisions are made.
- Set communication expectations.
- Choose one small improvement.
Days 8–30
- Establish meeting rhythms.
- Clarify ownership and escalation.
- Delegate with a clear finish line.
- Give early feedback.
- Set boundaries with former peers.
- Protect your capacity.
Days 31–60
- Remove persistent bottlenecks.
- Improve accountability.
- Reduce unnecessary dependence.
- Strengthen managing-up updates.
- Address recurring performance issues.
Days 61–90
- Review results and patterns.
- Confirm next-quarter priorities.
- Identify what to protect, improve, stop, or postpone.
- Review your management habits.
- Build the next 90-day plan.
10
Explore the Plain Act management library
Use the main guide for orientation, then open the focused article that matches the problem you are handling now.
Why New Managers Overexplain
How pressure turns useful explanation into a request for permission.
Read the article →How to Delegate Without Micromanaging
Transfer ownership with a clear outcome, authority, and review point.
Read the article →How to Give Feedback Without Killing Morale
Address observable behavior early without turning feedback into an attack.
Read the article →How to Build Authority as a New Manager
Build authority through consistency rather than performance or harshness.
Read the article →Why New Managers Say Yes to Everything
Make capacity trade-offs visible before constant availability becomes the system.
Read the article →How to Manage Up Without Sounding Insecure
Give your manager useful visibility instead of a stream of anxiety.
Read the article →Difficult Conversations for New Managers
Address problems while they are still specific, manageable, and correctable.
Read the article →Your First Team Meeting as a New Manager
Create orientation and operating clarity without delivering a leadership speech.
Read the article →Do Not Try to Fix Everything in Week One
Why early restraint protects trust, context, and decision quality.
Read the article →How to Set Boundaries With Former Peers
Acknowledge the role change without becoming cold or unfair.
Read the article →A deeper system for your first month
The First 30 Days as a New Manager
This guide is designed to help immediately. The book is the deeper Plain Act manual for authority, delegation, feedback, difficult conversations, managing up, capacity, and decision pressure.
11
Frequently asked questions
What is the first thing a new manager should do?
Clarify expectations with your own manager, learn the team’s active priorities, and meet each direct report before making major changes. Your first responsibility is to reduce uncertainty and understand the operating context.
What should a new manager do in the first week?
Complete individual meetings, map current work and risks, set a simple communication rhythm, and avoid unnecessary structural changes. Look for one small improvement that reduces friction without destabilizing the team.
What should a new manager avoid?
Avoid overpromising, changing systems without context, taking delegated work back, delaying feedback, trying to remain everyone’s friend, and making yourself permanently available.
How can a new manager build authority?
Build authority through consistency: make clear decisions, follow through, apply standards fairly, address problems early, and explain enough without defending every decision indefinitely.
How should a new manager manage former peers?
Acknowledge that the role has changed, set the same standards for everyone, protect confidential information, and avoid giving former friends either special treatment or unnecessary harshness.
How often should a new manager hold one-to-ones?
A weekly or biweekly rhythm works for many teams, but the right frequency depends on experience, workload, and risk. The important point is to create a predictable space for priorities, feedback, development, and blockers.
What is a realistic 30-60-90 day plan for a new manager?
Use the first 30 days to learn and establish an operating rhythm, days 31–60 to improve ownership and remove persistent friction, and days 61–90 to stabilize standards, review results, and set the next-quarter plan.
Should a new manager make quick changes?
Only where the risk is clear and delay would cause harm. Most changes should wait until the manager understands why the current process exists, who depends on it, and what may break if it changes.
Final principle
Your first 90 days are not a test of how much activity you can produce.
They are a test of whether you can create clarity without panic, authority without performance, and progress without destabilizing the people doing the work.
Start by understanding. Decide when the evidence is sufficient. Follow through consistently.