Your First 30 Days as a Manager: What Should You Actually Do?
A four-week plan for your first month in charge, with the actual records to keep at each stage and a checklist you can print.
Quick answer
Your first 30 days as a manager should build foundations, not prove your authority. Split the month into four stages. In week 1, understand the people, the work, existing commitments and what your own manager expects. In week 2, establish responsibilities, standards, communication routines and priorities. In week 3, act: delegate a real responsibility, address early problems and fix one genuine issue. In week 4, review progress, ask for feedback and agree next month's priorities. Treat this as a framework, not a fixed timetable. Safety risks, serious misconduct or urgent operational problems need action on day one.
Key takeaways
- Listen before you change things, but do not use listening as a reason to avoid decisions you already own.
- Reduce uncertainty before you ask for better performance. People cannot meet a standard nobody has stated.
- Delegate one meaningful outcome in week 3, with agreed checkpoints, rather than taking over unfinished work.
- Keep four simple records during the month. They turn good intentions into evidence you and your manager can review.
- After 30 days you should have a foundation and a plan, not a transformed team.
Why are the first 30 days important for a new manager?
Your first month sets how your team reads you. Before the promotion, you earned credibility by doing good work. Now your results come through other people, and your title alone will not make them follow you. They will watch whether you understand their work, treat them fairly and make sensible decisions.
Take Alex, promoted to supervise a six-person customer service team after three years as one of its strongest members. On Monday Alex was a colleague. By Wednesday the team wants to know what will change, and Alex's manager wants to know when complaints will come down. Both groups expect something different, and Alex cannot satisfy either by guessing.
The first 30 days give you time to understand problems before you try to solve them, make responsibilities clear and show through your behaviour what kind of manager you will be. The six capabilities behind this plan are covered in our guide to leadership skills for first time managers. This article turns them into a month of concrete actions.
Week 1: Understand the people, the work and the expectations
Listen before you change things. That does not mean you can put off responsibilities you already hold. Deadlines still fall due in your first week, and a safety or customer risk you spot on day two is yours to act on.
Meet with your own manager
Book this meeting first. You need to know what success looks like, what the team's current priorities are, which performance concerns already exist, what you can decide on your own, what resources you have and how your manager wants to hear from you. Useful questions:
- What would make you say my first three months went well?
- Which two or three outcomes matter most for the team right now?
- Are there performance issues or commitments I should know about before I start?
- What can I decide myself, and what needs your approval?
- How often do you want updates, and in what form?
Meet individually with team members
Hold a 20 to 30 minute conversation with each person. The purpose is to learn, so ask more than you tell:
- What is working well?
- What makes your job harder than it needs to be?
- Which responsibilities take most of your time?
- What should I understand before making changes?
- What support would help you do your job better?
Take notes and resist promising fixes on the spot. If someone raises a problem, say you will look into it and come back to them. A promise you later cannot keep costs you more trust than saying "let me understand this first".
Understand the existing work
Review current deadlines, customer commitments, workloads, processes and immediate risks. Look at the actual reports, logs and systems, not only what people tell you. Capture what you find in a short record like the one below.
| Area | What I found | Source | Priority | Next step |
|---|---|---|---|---|
| Complaints | Most recent complaints mention callbacks not made within the promised 48 hours | Complaint log, one-on-ones | High | Agree a callback standard with the team in week 2 |
| Refund report | Weekly report late three of the last four weeks; one person owns it with no backup | Shared drive, manager meeting | High | Confirm owner, due time and a backup |
| Escalations | No written process; the previous supervisor handled escalations from memory | One-on-ones | Medium | Delegate drafting a simple process in week 3 |
| Workload | One team member answers most phone calls while others work mainly on email | Phone system report | Medium | Review allocation after expectations are set |
Authority confirmed with manager: Alex can change rosters and team processes. Refunds above the approval limit stay with the manager.
Week 2: Establish clear expectations and working relationships
Reduce uncertainty before you ask for better performance. By the end of week 2, every person should know what they own, what good looks like and how you will work together.
Clarify responsibilities and standards
For each important outcome, confirm who is responsible, what acceptable performance looks like, the deadline, when to escalate and how you will review progress. Turn vague instructions into ones a person can measure:
Measurable: "Whoever takes an enquiry returns the customer's call within 48 hours and records the contact in the system. If the issue is outside your authority or cannot be resolved in the agreed time, escalate it to me straight away."
Establish a communication routine
Set up a small number of routines, each with a clear job: a short team catch-up to share priorities, fortnightly one-on-ones, a simple way to report progress, one place to raise problems and one channel where you announce decisions. Meetings only help when they have a purpose. If a catch-up has nothing to decide or share, cancel it.
Establish professional boundaries
If you were promoted from within the team, people will watch how you treat your friends. Apply the same rules to everyone, keep confidential information confidential and stop joining in on complaints about the business. You can stay friendly. You cannot stay one of the group in every conversation.
Put the result on one page and share it with the team. For the full approach, see our guide to setting expectations and holding staff accountable.
| Responsibility | Owner | Standard | When | Escalate to Alex when |
|---|---|---|---|---|
| Customer callbacks | Person who takes the enquiry | Return the call and record the contact in the system | Within 48 hours | Immediately, if the issue is outside your authority or cannot be resolved in the agreed time |
| Weekly refund report | Mia (backup: Tom) | All refunds listed, totals checked against the payment system | Mondays by 12pm | Figures do not reconcile |
| Written complaint replies | Rostered team member | Reply using the approved template | Within 2 business days | A customer mentions legal action or safety |
| Team catch-up | Alex | 10 minutes: priorities, blockers, decisions | Tuesday and Thursday, 9am | Not applicable |
How we work: one-on-ones every second week for 20 minutes. Decisions are posted in the team channel. Raise problems early; nobody gets blamed for flagging one.
Week 3: Start delegating and addressing problems
Start leading through other people rather than taking over their work. This is the week most new managers find uncomfortable, because doing the work yourself still feels faster.
Delegate one meaningful responsibility
Choose an outcome that matters, that someone on the team can achieve with support and that you would otherwise do yourself. Agree the result, the standard, the deadline, the resources available, how much they can decide on their own and when you will check progress. Write it down. The record below shows Alex's delegation as it stood at the end of the month, so you can see the full cycle from kick-off in week 3 to sign-off in week 4. Our guide on how to delegate without micromanaging covers how to pick the right task and the right person.
- Outcome
- A written escalation process for customer complaints
- Delegated to
- Priya
- Standard
- One page, covers the four most common complaint types, tested by a colleague on live complaints
- Deadline
- Friday of week 4
- Resources
- Two hours off the phones on Wednesday and Thursday; the previous supervisor's old escalation emails
- Authority
- Priya decides the steps and format. Changes to refund limits stay with Alex.
| Checkpoint | Progress | Agreed next step | Status |
|---|---|---|---|
| Monday, week 3: kick-off | Outcome, standard and scope agreed | Priya lists the common complaint types | Done |
| Wednesday, week 3: draft review | Four types listed, steps drafted for two | Add billing disputes; Tom to test the draft | On track |
| Monday, week 4: test | Tom used it on six live complaints; one step unclear | Priya rewords step 3 | On track |
| Friday, week 4: sign-off | Final version shared at the team catch-up | Review how it is working in one month | Complete |
Address an early performance problem
When someone misses an agreed commitment, talk to them privately and find the cause before you decide what to do. The cause usually falls into one of four groups: the expectation was unclear, they lacked time or resources, they lack the skill, or they are unwilling to meet a reasonable requirement. Each needs a different response, and only the last one is a conduct conversation.
Alex: "The refund report came in on Tuesday afternoon instead of Monday at 12. What got in the way?"
Mia: "Monday mornings I'm on the phones until 11, so I only start it after that, and the payment system export takes ages."
Alex: "So the time is the problem, not the report itself. If I take you off the phones from 9 on Mondays, can you have it in by 12?"
Mia: "Yes, that would do it."
Alex found a resource problem, not a capability or attitude problem, and fixed it in one conversation. If the report had still been late after the change, the next conversation would look different. Where a concern becomes formal, follow your workplace's policies and get advice from your manager or HR first. The Fair Work Ombudsman's guide to managing underperformance sets out a fair process.
Make one practical improvement
Pick one improvement that addresses a genuine problem from your week 1 and week 2 notes, such as the callback standard in Alex's case. Do not make changes to show you are in charge. Your team will judge your first change by whether it made their work easier or better.
Week 4: Review progress and plan the next 30 days
Management includes checking whether your decisions are producing the results you intended. In week 4, step back and look at the evidence.
Review team progress
Check whether key deadlines are being met, whether people understand their responsibilities, whether workloads are manageable, whether your improvement is working and which problems need further action.
Ask for feedback
Ask your team and your own manager. Specific questions get more useful answers than "how am I going?":
- What is one thing I have done this month that made your work easier?
- What is one thing I should stop, start or do differently?
- Is there anything you expected me to deal with that I have not dealt with yet?
Agree the next priorities
Choose two or three priorities for the next month, confirm them with your manager and share them with the team.
| Area | Day 1 | Day 30 | Next 30 days |
|---|---|---|---|
| Callbacks | No standard; complaints about missed callbacks | 48 hour callback standard agreed; unresolved issues escalated straight away | Track weekly and discuss at catch-ups |
| Refund report | Late three of four weeks, no backup | On time since Mia's Monday roster changed; Tom trained as backup | Maintain; no further action |
| Escalations | Nothing written down | Priya's one-page process in use | Review with Priya after a month of use |
| Phone workload | One person carrying most calls | New roster drafted, not yet started | Start the roster and check in after two weeks |
Feedback received: two team members want clearer rules on which refunds need approval. Next month's priorities, agreed with manager: start the phone roster, settle refund approval steps, keep callbacks on standard.
First 30 days as a manager: practical checklist
Save or print this table. Each week ends with a record you can show your manager.
| Period | Essential actions | Evidence of completion |
|---|---|---|
| Week 1 | Meet your manager and each team member; review deadlines, workloads, processes and risks | Observation and priorities record |
| Week 2 | Clarify responsibilities and standards; set communication routines and boundaries | Team expectations summary |
| Week 3 | Delegate one outcome; address early issues privately; make one practical improvement | Delegation and follow-up record |
| Week 4 | Review results; ask for feedback; agree next month's priorities | 30 day review and next steps |
A realistic first 30 days management scenario
Alex has just been promoted to supervise the six-person customer service team. Complaints have risen, two people regularly miss deadlines and the previous supervisor left with almost nothing written down. Alex was one of the team's best performers and feels pressure to show results quickly.
This scenario is fictional. The example records earlier in this guide follow the same team.
A. Introduce new rules and performance targets immediately
It looks decisive. Without knowing why complaints rose, Alex risks targeting the wrong problem, and the team reads the new rules as a verdict on them from someone who sat beside them last week. Compliance may rise briefly while goodwill drops.
B. Spend the month observing and avoid significant decisions
Alex learns a lot, but late reports keep arriving, complaints keep rising and the team starts to wonder whether anyone is in charge. Alex's manager sees a month pass with no change.
C. Deal with urgent risks, meet everyone, clarify expectations and make targeted improvements
Alex acts on anything urgent, spends week 1 finding out what is driving complaints, sets clear standards in week 2 and fixes the callback and refund report problems with the people who do the work. Changes rest on evidence, so the team can see why they make sense.
Option C is usually the strongest start. If Alex had found a safety risk, a regulatory breach or serious misconduct, though, waiting until week 3 would be wrong; those need action straight away. The four-week framework gives Alex a sequence for everything else: understand the cause, set the standard, act on it and check the result.
Five mistakes to avoid during your first month as a manager
- Changing processes before you understand the problem. You fix symptoms and annoy the people who knew the real cause. Use week 1 to find it first.
- Trying to stay everyone's friend. Small favours to friends look like favouritism to everyone else. Keep the friendliness and apply the same rules to all.
- Doing employees' work instead of building their capability. The deadline is met and the team learns that you will cover them. Delegate the outcome and coach.
- Avoiding uncomfortable conversations. A missed commitment becomes a pattern. Raise it privately within days, starting with a question.
- Promising improvements outside your authority. A pay review or new system you cannot deliver damages trust quickly. Check what you can decide before you commit.
What should you have achieved after 30 days?
Aim for a foundation, not a transformed team. By day 30 you should ideally have:
- A working understanding of the people and their responsibilities
- Priorities agreed with your own manager
- Clear expectations for the work that matters most
- Basic communication and review routines
- An initial picture of any performance problems
- At least one meaningful responsibility delegated
- A practical plan for the next month
If your organisation has its own onboarding process, probation requirements or management framework, follow it. It takes precedence over this general guide.
How can you continue developing your management skills?
The first month gives you a start. The skills develop through what you practise afterwards: regular feedback, a mentor or experienced manager to talk decisions through with, coaching and the experience of handling real situations.
Structured learning is one option among these. The Certificate IV in Leadership and Management (BSB40520) suits new and developing supervisors who want a framework to work from. Vanguard Business Education (RTO 91219) delivers it through Applied Capability Education: you work through realistic workplace scenarios, make leadership decisions and complete assessment projects built around the kind of records shown in this guide. Formal training is not compulsory to become a good manager, and it does not guarantee a promotion or better job.
Frequently asked questions
What should a new manager do on their first day?
On your first day as a manager, meet your own manager to confirm priorities and your decision making authority, then introduce yourself to the team and book individual conversations for the week. Check for any deadline, customer commitment or safety risk that needs action immediately. Save major changes until you understand the work.
Should a new manager make changes immediately?
No, a new manager should usually wait until they understand the cause of a problem before changing how the team works. The exceptions are safety risks, serious misconduct and urgent operational or customer problems, which need action straight away. Most other changes work better when they are based on what you learn in the first two weeks.
How do you gain respect as a first time manager?
You gain respect as a first time manager through consistent behaviour: listening before deciding, applying the same rules to everyone, doing what you said you would and dealing with problems fairly and privately. Your team will judge you on what you do over weeks, not on your title or what you say in your first meeting.
What should you discuss with employees during the first week?
In the first week, ask each employee what is working, what makes their job harder, which responsibilities take most of their time, what you should understand before making changes and what support would help. Listen and take notes rather than promising fixes. You will act on what you learn once you understand the wider situation.
What if your first month as a manager is not going well?
If your first month as a manager is not going well, ask your own manager and one trusted team member for specific feedback, then pick the one or two problems that matter most. A difficult first month is common and does not mean you are in the wrong role. Repeat the review step, adjust your plan and keep going.
Final verdict
A productive first month is not measured by how many changes you make. It is measured by whether you now understand your team, have made expectations clear, have made decisions based on evidence, have dealt with the problems that mattered and have a workable way of leading the people in front of you.
Follow the sequence: Understand, Establish, Act, Review. Keep the four records. At the end of the month you will have a plan for the next one, and the evidence to back it.
See what practical leadership learning looks like
Developing management skills takes more than reading advice. Step into a realistic workplace leadership decision and see how Vanguard Business Education approaches practical leadership learning. It takes about eight minutes.
Try the Free Leadership ExperienceLooking at formal study? The BSB40520 Certificate IV in Leadership and Management is delivered 100% online, with no formal entry requirements, a qualified trainer and SmartCoach™ support. View the course and enrol when you are ready.