First-Time Manager Field Guide

Start here Build steady habits, one conversation at a time A practical field guide for new people managers finding their rhythm in the first months. Fictional example: Jordan has inherited a six-person service team split across day and evening shifts. Use the guide to choose a next step, make work clearer, and follow through consistently across shifts. Choose your next management task Start with the conversation or decision in front of you. Prepare a first one-to-one Use a complete agenda that makes room for the employee's view and a clear next step. Set expectations and delegate Turn a vague request into an observable result with agreed decision boundaries. Find the right support Choose a role-based handoff when a concern needs more than a manager conversation. A useful rhythm for the first month Jordan is learning how the day and evening shifts connect. The aim is not to change everything at once; it is to make commitments visible and build a dependable way to check in. Listen before changing the routine Meet people on both shifts and ask what helps work move smoothly between them. Hold an individual first one-to-one with each team member. Ask where handoffs lose context or leave ownership unclear. Close the loop When you agree an action, name who owns it and when you will revisit it. Record the agreed work action in the team's normal work notes. Return to open questions at the next check-in. Useful conversations Make the first one-to-one a listening conversation A practical agenda for a 30-minute first meeting Jordan schedules a separate conversation with each of the six team members, including colleagues on the evening shift. The purpose is to understand the work and agree a useful follow-up—not to arrive with a finished diagnosis of the team. Before the meeting: choose a time that works for the employee's shift, bring a short agenda, and leave space for their priorities. If you cannot meet during their shift, agree a workable alternative rather than assuming day-shift timing suits everyone. A complete first one-to-one agenda About 30 minutes; adjust the pace so the employee has room to speak. Open and agree the purpose Say: “I’d like to learn what helps you do good work, what gets in the way, and what would be useful for us to follow up. What would you like to make sure we cover?” Hear their view of the work Ask what a smooth shift looks like, which tasks require the most coordination, and what information from the other shift is most useful. Ask what is working and what is difficult Invite one example of each. Ask what happened, when it happens, and what effect it has on the work. Listen without jumping to a solution. Clarify support and expectations Ask what they need from you, what decisions they currently make independently, and where they would want a check-in before acting. Agree one or two next steps Name the action, the owner, and a date or next conversation to revisit it. If you do not know an answer, say when you will return with one. Close with their understanding Summarize what you heard and ask, “What have I missed or misunderstood?” Confirm the next check-in and how you will share any agreed work information across shifts. When a conversation raises a concern Listen carefully, stay within your role, and make a clear handoff when needed. What if someone tells me something that worries them? Thank them for telling you. Ask what happened and what support they are asking for; do not press for speculation or try to diagnose the cause. Reflect back what you heard, agree what you will do next, and avoid promising a particular outcome or complete confidentiality before you understand the appropriate process. What if I do not know whether this needs People support? Do not make the employee wait while you guess. Tell them you will seek guidance through the confidential People support route, and use that route to ask what to do next. Share only the personal detail needed for the handoff. What should I tell the rest of the team? Share only work information colleagues need to do their jobs. Do not repeat a colleague's private concern or imply that a particular People decision has been made. Expectations and delegation Make the work clear enough to check A practical guide to setting observable expectations and delegating with clear decision boundaries. In Jordan's six-person service team, a handoff between day and evening shifts is a useful place to replace vague requests with a shared, checkable result. From ambiguous to observable A worked example for the team's day-to-evening shift handoff. Request “Keep the handoff tidy.” “Before your shift ends, add each open customer case to the handoff log.” What complete means “Make sure the next shift has what it needs.” “Include the case reference, current status, next action, and any agreed customer follow-up time.” Review “Let me know if there are problems.” “We’ll review the first three handoffs together at Friday’s check-in and adjust the format if something is missing.” Delegate a result, not just a task Keep ownership and authority explicit in the handoff-checklist example. Outcome Ask a team member to draft a handoff checklist that captures the case reference, status, next action, and follow-up time for open cases. Decision boundary They may propose the checklist layout and test it with colleagues on both shifts. They should not change the team's official case-recording requirements or promise a new customer response standard. Check-in and ownership Agree a short review after the first three uses. The team member brings examples of what worked; Jordan decides whether to adopt the draft or seek the appropriate process owner's input. Agree the boundaries before work starts A simple delegation agreement keeps the result and handoff clear. If a boundary is unclear, pause that part of the work and clarify ownership before proceeding. Name the outcome and the evidence that will show it is complete. Agree which decisions the colleague can make independently. State what must come back to you or the relevant process owner. Set the check-in point and decide together what happens next. Find support Know when to bring someone else in Use a clear role-based handoff when a concern or decision goes beyond your current authority. A manager can listen, clarify the next step, and seek guidance without diagnosing a concern or promising an outcome. Match the next step to the situation Keep the employee informed about what you will do next. Routine work or coaching Ask the employee for a specific example of where the work is getting stuck. Agree one manageable next action and a time to review it. Bring a recurring team-level obstacle to your manager with its impact and examples. A concern beyond your role Listen without diagnosing or promising a result. Use the confidential People support route for guidance on the appropriate next step. Tell the employee what you will do and when you will update them, without promising an outcome. An unclear process or decision boundary Pause a decision that exceeds the authority you understand yourself to have. Ask your manager or the relevant process owner who can make the decision. Return to the employee with the clarified owner and next step. Keep the handoff clear and respectful A useful handoff gives the next role enough context to advise, without turning a private conversation into team news. Explain to the employee what you plan to share and with whom; if you are unsure how to handle the information, seek guidance through the appropriate confidential People support route. Jordan records agreed work actions in the team's normal work notes, keeps private details out of shared shift handoffs, and returns to the employee at the agreed time. For official people policies, confidential support, and local manager responsibilities, use the organization's authoritative internal resources and the appropriate People role. Terms: An observable expectation names the work and evidence someone can check. A decision boundary states what a delegated colleague may decide independently and what must be referred to an authorized role.