Your First 90 Days as a Manager: What to Learn, Change, and Hand Over

Becoming a manager can leave you with two jobs: the individual work you were good at and the new responsibility for helping a team succeed. If you keep both at full volume, the team can end up waiting for your decisions while you work late on your old tasks. Use your first 90 days to agree on the role, understand the team’s work, establish a few reliable management habits, and hand over responsibilities deliberately. The timeline below is a planning aid. Adapt it to your team’s needs, especially if you are taking over during a crisis or a major change.

Before day 30: agree on the job you now have

Meet with your manager to define what success in the role looks like. Ask which outcomes matter most, what authority you have, which decisions need approval, and how much individual delivery remains part of your job. Some roles intentionally combine management and hands-on work. The problem is an unspoken combination nobody has sized realistically.

List the work you are carrying from your previous role. For each item, agree whether you will finish it, hand it over, reduce its scope, or stop it. Attach an owner and date to the handover. “I will delegate more” will not free your calendar if every old commitment still depends on you.

The Center for Creative Leadership’s guidance for first-time managers describes the shift away from relying mainly on personal skills and technical expertise toward leading others. The practical implication is to evaluate your new week differently: alongside your own deliverables, consider whether teammates have the context, decisions, support, and room to do their work.

Listen for how the team actually works

Spend time with each teammate and the partners who depend on the team. Ask what they own, what gets in their way, what they want to keep, and where they need a decision. Listen for repeated problems, but do not treat the first account you hear as the entire explanation.

Useful questions include: “Which part of your work takes more effort than it should?” “Where are responsibilities unclear?” “What do you want me to understand before changing anything?” and “What kind of support helps you do your best work?” Keep commitments you make in these conversations visible to yourself and follow through.

If you were promoted from within the team, discuss the change directly. Former peers should know how decisions, feedback, and confidential information will be handled. Familiarity does not remove the need for clarity. Avoid making private promises that you cannot apply fairly across the team.

Observe existing routines before adding new ones. A weekly meeting may already solve a problem that is not obvious from its calendar title. Ask what would be lost if you removed it. Conversely, keep a meeting only when its purpose remains useful; inheriting it is not a sufficient reason to preserve it forever.

Establish a few dependable management habits

Begin with regular one-on-ones, clear priorities, and a place to record decisions and commitments. The exact cadence should fit the team’s work. Reliability matters more than creating an elaborate system that you cannot maintain.

In one-on-ones, make room for the teammate’s agenda, current obstacles, feedback, and development. If the conversation becomes only a status report, ask what they need from you that is not visible in the project tracker. Follow up on earlier commitments before adding new advice.

Make priorities explicit enough to resolve a conflict. “Everything is important” leaves the team to choose without shared context. Explain what should happen when two requests collide and which circumstances require you to reconsider the order. If you do not have authority to resolve the conflict, bring it to your manager with options.

Keep sensitive employee information in the appropriate employer-approved systems. A personal reflection about your own management practice can describe what you learned without copying a colleague’s health details, compensation information, or confidential performance discussion. Your learning record and the organization’s employee records serve different purposes.

Days 31–60: delegate an outcome with enough context

Choose a real responsibility you can hand over, then explain the result needed and the boundaries. A vague task assignment can leave a teammate responsible for delivery while you continue making every decision. They need to know what they can decide, where you want a check-in, and when to ask for help.

Use this delegation note as a starting point. Review it with the person taking ownership and revise it if the scope or support is unrealistic.

• Outcome: What must be true when this work is complete?
• Purpose: Why does it matter, and who will use the result?
• Authority: Which decisions can the owner make independently?
• Boundaries: What limits on scope, access, budget, or quality apply?
• Support: What context, introductions, or training will you provide?
• Checkpoints: When will you review progress, and what will you look at?
• Escalation: What should trigger an earlier conversation?

In a fictional example, a new support manager hands a recurring onboarding session to an experienced specialist. The specialist owns the agenda and delivery, while policy changes still require approval. They review the first session together and agree to check in after the next two. The manager remains available but stops rewriting each slide.

Expect a learning period. If the first attempt is uneven, distinguish a missing skill from missing instructions or authority. Ask what support would help before taking the work back. When intervention is necessary, explain why and agree how ownership will return; otherwise a temporary rescue can quietly become the permanent arrangement.

Fix one repeated obstacle with the team

By the second month, you should have examples of what repeatedly slows the work. Choose a problem small enough to improve and meaningful enough to matter. It may be unclear intake, late decisions, uneven handoffs, or a recurring meeting that leaves everyone with different assumptions.

Describe the problem and ask the team to help design the change. “We have had three requests arrive without an owner. What should be agreed before the next request enters the queue?” is more useful than announcing a full process overhaul based on your first impressions.

Define how you will know whether the change helped. That might be fewer requests returned for missing information or less confusion about who decides an exception. Use the evidence available; do not invent a percentage improvement to make a small change sound substantial. If the experiment adds work without solving the problem, adjust it.

Days 61–90: review how your behavior affects the team

Ask teammates and partners for feedback on specific changes. Are priorities clearer? Do they know when they can decide without you? Are your check-ins useful? Has a handover actually increased ownership, or are they still seeking permission because you routinely reverse their choices?

Review your own calendar and commitments. Look for work that has migrated back to you, meetings where you have no clear contribution, and decisions delayed because you are the only available approver. Your calendar will not capture everything, but it can reveal whether the role you agreed on matches the way you spend the week.

Prepare a short review with your manager: what you learned, what changed, what remains unresolved, and what support the team needs next. Include team outcomes and your contribution without taking credit for every result. Your job is to help the team succeed and to explain your part accurately.

Use the next quarter to deepen a small number of practices. You may need better coaching questions, clearer prioritization, or a more reliable handover process. Keep a record of your own decisions and lessons. Bloomly can help organize those reflections with your management Role, while confidential employee records remain in the systems your organization requires.

Your first 90 days should give you a clearer understanding of the team, the expectations of your role, and the work you need to stop carrying alone. Agree on priorities, create dependable conversations, and delegate with context and authority. Then ask whether those changes are helping. You do not need a finished management style by day 90. You need a workable foundation, an honest view of the remaining problems, and a few habits the team can rely on.