A new manager often inherits expectations before fully understanding the system that produced them. CIPD’s line-management resources provide background on the responsibilities involved. The plan below is an operational framework for learning deliberately and establishing useful agreements. It does not assume that every team needs the same schedule or that a new manager should immediately redesign the organization.
1. Understand the purpose of the team
Begin by asking which outcomes the team is responsible for and how those outcomes support the organization. Compare the formal description with the work people actually do. A hypothetical support team may own customer resolution while spending substantial time compensating for upstream product problems.
That distinction affects priorities. The manager needs to understand the continuing obligations, the current pressures and the decisions that sit outside the team’s authority. A clear account of the purpose makes later changes easier to explain.
2. Learn the workflow from several perspectives
Speak with team members and the colleagues who depend on their work. Ask about recent examples, recurring delays and the information needed to make a decision. Separate a single difficult incident from a pattern that deserves broader investigation.
Avoid treating the first explanation as definitive. People may see different parts of the process and have legitimate but incomplete accounts. The manager’s task is to assemble a more coherent picture, including uncertainty and disagreements that need further examination.
3. Establish immediate working agreements
Clarify how priorities are set, how urgent issues are escalated and what people can decide independently. These agreements can reduce avoidable confusion without requiring a major reorganization. They should be specific enough that someone can use them during an ordinary working day.
A useful check-in asks what changed, what is blocked and what decision is needed. It should not become an additional reporting burden whose main purpose is to reassure the new manager. The format can be adjusted as the manager learns which information genuinely helps the work.
4. Choose a small, evidence-based improvement
Look for a bounded problem whose cause is sufficiently understood. A clearer handoff, a missing access permission or an outdated instruction may be a better first change than a broad new process. Involve the people affected and state the intended outcome before implementing the fix.
Review the result. Did the change reduce the problem, move it elsewhere or reveal another constraint? A small improvement can establish a useful pattern of inquiry and follow-through without pretending that every difficulty has an immediate solution.
5. Make the longer-term questions visible
At the end of the initial period, summarize what is known, what remains uncertain and which decisions need wider support. Discuss the account with the team rather than presenting it as a private diagnosis. The manager should also identify the capabilities they need to develop.
The goal of the first month is a stronger basis for leadership: clearer expectations, a more accurate understanding of the work and a credible way to improve it. Trust grows when the manager’s actions reflect what they have learned and the commitments they can actually keep.
