Leading Your First Team

1. Doer: Complete the task. At this level, you focus on your own output. You measure success by whether you finished the repair, served the customer, closed the sale, or completed the shift. This level still matters when the team faces an emergency or needs a demonstration. It cannot remain your main job because your personal capacity limits the whole team.

2. Coach: Help someone else complete the task. Instead of taking over, explain the standard, ask the employee to describe their plan, and watch enough work to give useful feedback. For example, if a new employee mislabels stock, show one correct label, explain why the details matter, and have the employee relabel the remaining items. Coaching builds skill without making you the permanent backup worker.

3. Builder: Create repeatable ways to work. A repeatable way to work tells people what to do, when to do it, and how to check the result. This might include a closing checklist, a three-step customer handoff, or a clear rule for reporting equipment problems. Write the process in plain language and test it with someone who did not create it. If that person cannot follow it, simplify it.

4. Owner: Protect the team’s priorities and standards. At the top level, you decide what deserves attention, explain trade-offs, and address problems early. You may need to choose between covering a shift yourself and spending an hour training two employees. If the absence creates an immediate safety risk, cover it. If the team can operate safely, use the time to strengthen the team instead of hiding the staffing problem.

The ladder helps you choose the right response. When a customer complaint arrives, do not automatically jump to the Doer level. Ask whether the employee needs a quick answer, coaching, a better process, or a decision about the team’s priorities. The right level depends on the situation.

Your new role also needs boundaries. A boundary states what you will do, what you expect from others, and when you will step in. For example: “Bring urgent safety issues to me immediately. Bring routine scheduling questions to the shared schedule before asking me. I will review unresolved items at 3:00 p.m.” This boundary protects your attention while giving the team a clear route for help.

Confidence grows from visible decisions, not from pretending to know everything. When you do not know, say, “I need to check the information before I decide. I will give you an answer by 2:00 p.m.” Keep that promise. Ask yourself at the end of each day: “Did I solve a problem, or did I help the team solve it next time?” Your answer shows which rung you used.

A First-Week Role Reframe

Consider a first-time manager taking responsibility for a six-person service team. The team has missed two morning start times, customers have waited too long for updates, and employees interrupt the manager throughout the day for small decisions. The manager wants to prove competence by handling more work personally. That choice would keep the pattern alive.

Use the following sequence during the first week.

1. List your new responsibilities on Monday morning. Write five items that only the manager can reliably own: setting daily priorities, assigning coverage, checking safety, giving feedback, and reporting results. Then write five tasks that trained team members can handle. Expected outcome: you separate management work from work that others can perform.

2. Set two decision boundaries before the first shift. Tell the team, “Handle routine customer updates using the agreed script. Bring safety concerns, refunds above $100, and staffing gaps to me immediately.” Expected outcome: employees know which decisions they can make without waiting.

3. Observe one complete work cycle on Tuesday. Watch an employee receive a request, complete the work, update the customer, and close the task. Do not interrupt unless safety or service quality requires it. Record where the process breaks. Expected outcome: you identify the real cause instead of guessing from isolated mistakes.

4. Coach one person on Wednesday. Use this short sequence: ask what happened, ask what the person planned, explain the standard, and have the person repeat the task. If customer updates take too long, practice a message such as, “Your service is scheduled for Thursday. We will contact you by 4:00 p.m. if anything changes.” Expected outcome: the employee leaves with a usable behavior, not just a warning.

5. Build one simple tool on Thursday. Create a shared closing checklist with no more than seven items. Include the person responsible and a check box for each item. Test it at the end of the shift and remove anything unclear. Expected outcome: the team can complete the close without asking you about every step.

6. Review results on Friday. Check three measures: the number of late starts, the number of routine interruptions, and the number of customer updates completed on time. Compare them with Monday’s notes. Expected outcome: you learn whether the new boundary and process changed behavior. If not, adjust the process or repeat the coaching; do not simply take the work back.

Quick checklist

• Write the five responsibilities that belong to you as manager. - Identify tasks trained team members can own. - State which decisions require your approval. - Set a response time for questions that can wait. - Observe a full work cycle before changing the process. - Coach one behavior with a clear standard. - Build one short checklist and test it. - Review results at the end of the week.

The numbers in this example do not need to become a complicated report. They give you a basic check: Did the team start on time more often? Did routine interruptions decrease? Did customers receive updates when promised? If the answer remains no, return to the ladder and find the missing level. You may need coaching rather than a new checklist, or a clearer priority rather than more instructions.

Mistakes That Pull You Back Into the Old Role

Taking back work too quickly

A team member makes an error, and you finish the task yourself because it seems faster. The short-term result improves, but the employee learns that you will rescue the work. The next problem comes back to you.

Do this: Stop when the risk allows it. Ask, “What part is unclear?” Explain the standard, agree on the next attempt, and set a time to review it. Take over only when safety, legal requirements, or a serious customer impact demands immediate action.

Not this: “Move over. I’ll do it.”

State the reason behind your intervention when you must take over: “I am handling this because the customer’s equipment could be damaged. Afterward, we will review the correct procedure.” That explanation protects trust and turns an emergency into a learning opportunity.

Being available for every question

An open door can become a constant interruption. If employees ask you to approve every small decision, they may not understand their authority or may fear criticism.

Do this: Create a question rule. For example, ask employees to group routine questions for the 3:00 p.m. check-in and contact you immediately only for safety risks, serious customer complaints, or staffing problems. Keep a shared note for items that can wait. This works because the team gets help without losing the whole day to interruptions.

Not this: Ignoring questions and hoping people become independent.

A boundary without a response time feels like abandonment. Review the shared note at the promised time, answer each item, and update the rule if the same question appears repeatedly.

Trying to prove authority through control

Some new managers believe confidence means having the final answer on every issue. They correct small details in front of others, change instructions without explanation, or demand approval for work they could delegate. Employees then hide mistakes or wait for permission.

Do this: Explain the result you need, the limits that matter, and the decision the employee owns. Say, “The customer must receive an update by 4:00 p.m. You choose whether to call or text, as long as you record the contact.” Check the outcome rather than controlling every movement.

Not this: “Do it exactly my way because I am responsible now.”

Your title gives you responsibility; it does not make every personal preference a rule. Separate safety requirements, customer promises, and business standards from your preferred method. That distinction helps the team respect necessary limits while still using judgment.

The move from individual contributor to manager becomes clearer when you stop asking, “How can I do more?” and start asking, “What does the team need from me at this level?” Use the Role Reframe Ladder to choose your response, set boundaries that people can follow, and measure whether your actions improve the team’s work. Your confidence will grow from repeated evidence: clearer decisions, fewer preventable interruptions, and employees who can handle more without waiting for rescue.

End of chapter one. 9 more chapters and about 17,870 words in the full book.