Leading Your First Team

The Role Reset Map has three points: Own, Enable, and Inspect. These points describe where a manager should spend attention. They also give you a simple test when a task lands on your desk: should you own the decision, enable someone else to handle it, or inspect the result?

1. Own the direction. Set the team’s priorities, standards, schedule, and boundaries. Your team needs to know what matters most when two demands compete. For example, if a repair shop must choose between a same-day emergency and three scheduled jobs, you decide how the team should handle that choice instead of leaving each employee to guess.

2. Enable the work. Give people the information, tools, authority, and practice they need to complete their responsibilities. If an employee must ask you before ordering a common supply, either give a spending limit or create a clear ordering rule. Constant permission requests slow the team and train people to wait.

3. Inspect the result. Check whether the work meets the agreed standard, then respond quickly when it does not. Inspection does not mean watching every movement. It means reviewing the finished job, customer feedback, schedule, safety record, or other evidence that matters. A manager who never checks creates standards that exist only in conversation.

Use the map before you take work back from an employee. Ask three questions: What decision belongs to me? What support does this person need? What evidence will show that the work is complete? These questions stop you from grabbing the task simply because you can finish it faster. Speed matters, but teaching someone to handle the task correctly matters more when you manage a team.

Your leadership expectations should match the map. Tell the team how you will communicate, make decisions, give feedback, and handle mistakes. A useful starting statement sounds like this: “I will set clear priorities, make decisions when the team needs a decision, and give feedback directly. I expect you to raise problems early, follow the agreed process, and bring a proposed solution when possible.” This statement gives people something they can observe. It avoids vague promises such as “I have an open-door policy,” which can mean anything and often leaves employees unsure when to interrupt you.

The map also changes your calendar. Reserve time for team work instead of filling every hour with individual tasks. A practical first schedule might include a 15-minute priority check each morning, two 30-minute one-to-one conversations during the week, and a 45-minute Friday review of results and unresolved problems. These blocks create space for management before urgent work consumes the day.

Applying the Map During Your First Week

Consider a new manager taking responsibility for a five-person installation crew. The manager still completes two installations each week and answers customer calls, but the team also needs scheduling decisions, quality checks, and coaching. The following plan applies the Role Reset Map without abandoning essential work.

1. List every recurring task on Monday morning. Write down the work you perform in a normal week, including customer calls, ordering materials, approving time sheets, troubleshooting, and physical jobs. The list may contain 25 to 30 items. Mark each task as Own, Enable, or Inspect. Expected outcome: You identify at least three tasks that someone else can perform with clear instructions and at least two decisions that only you should make.

2. Set three team priorities by Monday afternoon. Choose priorities that the team can act on, such as “finish scheduled installations by Friday,” “confirm every customer appointment by 4 p.m. the previous day,” and “report missing materials before leaving the warehouse.” Explain why each priority matters. Expected outcome: Every employee can repeat the priorities and describe what action supports them.

3. Hold a 30-minute team meeting on Tuesday. Explain your role change directly. Say what you will decide, what employees can decide, and how they should raise problems. For example, allow employees to resolve supply purchases up to $150 without approval, but require approval above that amount. Expected outcome: Employees receive decision limits instead of relying on guesswork or constant permission.

4. Transfer one responsibility with a written standard on Wednesday. Give scheduling follow-ups to one employee. Provide a short checklist: confirm the address, arrival window, required materials, customer contact number, and special access instructions. Review the first two completed follow-ups together. Expected outcome: The employee completes the task independently by Friday, with fewer interruptions for you.

5. Inspect two results on Friday. Review the week’s completed jobs, customer confirmations, missed appointments, and material problems. Discuss what met the standard and what needs correction. Do not wait for a monthly review if a problem affects next week’s work. Expected outcome: You leave the week with one confirmed improvement, one unresolved issue, and a specific owner and deadline for the next action.

Your first week does not need to prove that your team has changed completely. It needs to show that your role has changed. You set direction, give people room to work, and check the results.

Quick checklist

• Write down your recurring tasks and label each one Own, Enable, or Inspect. - Choose three priorities the team can repeat in plain language. - Set clear decision limits, including a dollar limit where useful. - Explain how and when employees should raise problems. - Transfer one responsibility with a written checklist. - Schedule two quality checks instead of fixing every problem yourself. - Review results on Friday and assign the next action.

Avoiding the First Manager Traps

Doing the work because you can do it faster

Your experience makes this trap especially tempting. You see an error, take the tool, rewrite the schedule, or call the customer yourself. The immediate problem disappears, but the employee learns that you will rescue the work. The next problem reaches you sooner.

Do this: Explain the standard, ask the employee to correct the work, and set a time to review the result.

Not this: Take over silently and complain later that nobody can handle the task.

Being friendly instead of being clear

A new manager may avoid correcting missed deadlines or poor work because the team used to be made up of peers. Employees then receive mixed signals: the stated standard says one thing, while your actions accept another. Clear feedback protects the working relationship because people know where they stand.

Do this: Describe the specific gap, explain its effect, and state the required change. “The customer confirmation went out after the appointment window, so the crew arrived without access details. Send confirmations by 4 p.m. the day before.”

Not this: Say “Please communicate better” and expect the problem to disappear.

Changing every rule at once

You may notice ten things that need improvement. If you change all ten during your first week, employees cannot tell which change matters most, and you cannot tell which change produced a result. Start with the expectations that protect safety, customer commitments, quality, and daily coordination.

Do this: Choose three priorities for the first week, measure whether the team follows them, and adjust after Friday’s review.

Not this: Announce a complete overhaul before you understand how the current work actually moves.

The Role Reset Map gives you a firm starting point: own direction, enable capable work, and inspect the result. Put it into practice now by writing your task list, choosing three priorities, and scheduling your first Friday review. As you lead, the goal is not to become the person who solves every problem. The goal is to build a team that understands the work, takes responsibility, and knows when to ask for help.

End of chapter one. 9 more chapters in the full book.