Your first three months do not have to be a dramatic transformation. A better goal is to understand the work, establish fair expectations and make a small number of visible improvements. Moving too fast often creates promises you cannot yet keep.
You’ll find a practical method, a realistic workplace example and a short checklist to try.
Days 1–30: listen before you redesign
Meet people individually. Ask what good work looks like, what slows it down and what they wish a new manager would understand. Notice which processes are written down and which live only in somebody’s head. Look for areas where the team has already tried to improve things. If you inherit a team, be especially careful not to mistake unfamiliar habits for bad habits.
Set a clear working agreement
Explain how you intend to communicate: response-time expectations, meeting cadence, availability and when to escalate a problem. Ask the team what would make those arrangements usable. A working agreement is more helpful than promises that your door is always open; it lets people predict when they can reach you and what they can decide independently.
Days 31–60: prioritise a few changes
Choose one operational friction point and one people-development opportunity. Define a baseline before changing anything: for example, how long decisions wait for approval or whether recurring one-to-ones happen. Share why you chose those issues and what would count as improvement. Saying no to other attractive projects is part of credible leadership.
Days 61–90: evaluate, do not declare victory
Ask colleagues which changes made work easier and which created new effort. Review quality alongside speed; a faster process that generates more errors is not progress. Update the next-quarter plan using evidence from the team. Acknowledge uncertainty about things that still need investigation rather than claiming the first 90 days solved everything.
Protect trust when you must make hard decisions
New managers sometimes postpone difficult conversations to remain liked. Fairness is better than avoidance. Explain expectations consistently, listen to context and follow your organisation’s process for sensitive issues. If the matter concerns legal rights, health, pay or disciplinary action, bring in qualified HR support rather than improvising.
An example from everyday work
In week two, you discover that every customer discount requires a senior manager. Instead of removing the approval rule immediately, map why it exists, review the risks and run a small trial with agreed limits. You gain useful evidence without asking the team to gamble on a new manager’s instinct.
Put it into practice
Choose the actions that fit your role, responsibilities and the people involved. You do not need to implement everything at once.
- Book listening conversations with each direct report.
- Write a short list of observed strengths and avoidable friction.
- Agree the decision and escalation rules with the team.
- Choose just two changes to test in the second month.
- Schedule a feedback check at day 60 and day 90.
What should I understand before changing how this team works?
What to do next
Pick one change you can observe in the next week. Explain it to anyone affected, check whether it helped and adapt based on what you learn. For issues involving employment rights, workplace safety, discrimination, formal performance procedures or health, seek appropriate professional support and follow your organisation’s policies.
Further reading and sources
These external resources provide wider professional or official context. Our frameworks and examples are original interpretations rather than quotations from these publications.