Leading Your First Team

The Peer-to-Manager Reset has three parts: mindset, boundaries, and credibility. Mindset means accepting that your job now includes decisions about people, not only tasks. Boundaries separate friendly working relationships from special treatment. Credibility means showing, through repeated actions, that you make fair decisions and follow through.

Start with these four steps:

1. Name the role change. Write three responsibilities you now own, such as assigning work, checking quality, and addressing attendance problems. Naming them prevents you from treating management as “the same job with a new title.” Your former peers need to see that you understand the responsibility you accepted.

2. Set equal working rules. Choose the standards that apply to everyone: start times, safety checks, customer updates, job documentation, or closing duties. Explain the reason for each rule and apply it consistently. Equal rules reduce suspicion because people can compare your decisions against a known standard.

3. Replace friendship-based decisions with work-based decisions. When you assign overtime, approve time off, or divide desirable jobs, use clear factors such as skill, availability, rotation, and recent workload. Keep a simple written record. You do not need a complicated system; a dated note in a shared folder can show how you reached a decision.

4. Build credibility through small promises. Promise only what you can deliver, then complete it when you said you would. If you tell the team you will confirm next week’s schedule by Thursday at noon, send it by Thursday at noon. People judge a new manager less by confident speeches than by whether everyday commitments happen.

Your relationship with former peers should become more professional, not less human. You can still eat lunch together or talk about weekend plans. The boundary appears when a personal relationship affects a work decision. For example, you might listen to a friend explain why they need Saturday off, but you should approve or decline the request using the same scheduling rules you use for everyone else.

Use direct language when you announce the change. Say, “I am still part of this team, but I now make the work assignments and handle performance concerns. I will explain decisions, apply the same standards, and listen when you have a concern.” Avoid saying, “Nothing will change.” Something has changed, and pretending otherwise makes later corrections feel like betrayal.

Credibility also requires visible fairness, not identical treatment in every situation. A new employee may need more instruction than an experienced worker. Someone handling a complex repair may receive extra time because the job requires it. Explain the work reason. Ask yourself, “Could I explain this decision to the whole team without mentioning a private friendship?” If the answer is no, review the decision before announcing it.

The practical takeaway is simple: keep your warmth, change your decision process, and make your new responsibilities visible.

Apply the Reset to a First-Week Schedule

Consider a team of five technicians. You worked beside them before becoming manager. The team starts at 8:00 a.m., completes a safety check before each job, and sends customers an arrival update. You must create next week’s schedule, address one missed safety check, and avoid giving the easiest route to your closest friend.

Use the reset in this order:

1. List the decisions you own before Monday morning. Write “route assignments,” “time-off approvals,” “safety checks,” and “customer updates” on one page. Mark each decision as either a team standard or a case that needs judgment. Expected outcome: you know where your manager role begins instead of waiting for former peers to treat you differently.

2. Publish the three non-negotiable standards. Send a short message on Friday: “Everyone starts at 8:00, completes the safety check before leaving, and sends the customer update by 8:15.” Add the reason: these steps protect workers and keep customers informed. Expected outcome: the team hears the same expectations before you correct anyone.

3. Assign routes using written factors. Give the emergency route to the technician with the required certification, rotate the preferred downtown route, and assign the remaining jobs based on workload and travel time. Record the reason beside each name. Expected outcome: your closest friend may not receive the easiest route, but you can explain the decision without favoritism.

4. Address the missed safety check privately. Say, “The checklist was missing on Tuesday’s job. Complete it before every departure. What prevented you from doing it?” Listen for a real obstacle, such as missing forms or a rushed dispatch. Then agree on the fix and set a follow-up date for Friday. Expected outcome: you correct the behavior without embarrassing the person or ignoring the standard.

5. Hold a 15-minute Friday review. Ask each technician what worked, what caused delays, and which rule needs clarification. Do not promise every requested change. Record two actions you can complete the following week. Expected outcome: the team sees that you listen, while your written actions show that listening does not mean automatic agreement.

6. Check your own behavior at the end of the week. Review the schedule, time-off decisions, corrections, and promises. Look for exceptions that benefited a friend or punished someone you found difficult. Expected outcome: you catch uneven treatment before it becomes a pattern.

Quick checklist

• [ ] Explain what responsibilities changed. - [ ] Set three or four rules that apply to everyone. - [ ] Use written work reasons for assignments and time off. - [ ] Correct problems privately and promptly. - [ ] Keep personal conversations separate from work decisions. - [ ] Record promises and complete them by the stated time. - [ ] Review your decisions for favoritism and inconsistency.

A useful test comes at the next team meeting. Ask whether each person can describe the main rules, how assignments get made, and where to raise a concern. If people give different answers, repeat the explanation and make the process clearer. The goal does not involve making every person happy with every decision. The goal involves making decisions understandable, consistent, and connected to the work.

Avoid the Traps That Weaken Your Authority

Trying to prove you are still one of the group

Some new managers keep joining every complaint session, share confidential information, or laugh off poor work to show that promotion has not changed them. Former peers may enjoy the access, but they also learn that you will protect the old relationship before protecting the standard.

Do this: Keep ordinary conversation, but leave conversations that attack another team member or pressure you for special treatment. Say, “I want to hear a work concern, but I will not discuss someone’s private situation in a group.”

Not this: “I know the rule says no, but I will make an exception because we have always helped each other.”

The fix involves accepting that some old habits must end. You can remain respectful without acting like a peer in every situation.

Announcing strict rules, then making exceptions

A manager may declare that everyone must arrive at 8:00, then ignore a late arrival from a close friend. One exception can make the rule look optional. The team may stop raising concerns because they expect decisions to depend on relationships.

Do this: Before making an exception, identify the work reason, decide whether the same reason could apply to others, and explain the general rule without sharing private details. If the schedule needs flexibility, change the rule for everyone instead of quietly excusing one person.

Not this: “You are usually reliable, so I will overlook it this time.”

If a genuine emergency caused the problem, address the emergency with care and still record the attendance issue according to your workplace process. Fairness means considering relevant facts, not pretending every situation matches.

Avoiding a difficult conversation until the problem grows

Former peers often feel harder to correct because the manager remembers working beside them. Waiting two weeks to mention missed paperwork or poor customer communication gives the problem time to become normal. It also makes the eventual correction feel sudden.

Do this: Speak privately within one or two workdays. Describe the specific action, explain its effect, ask what caused it, and agree on the next check. For example: “The customer update went out at 10:05 instead of 8:15. That left the customer waiting without information. What got in the way? Starting tomorrow, send it before leaving the first job, and I will check the log Friday.”

Not this: “You need to take your job more seriously.”

Specific feedback gives the person a fair chance to change. It also protects your credibility because the team can see that you address work problems based on facts rather than mood.

The Peer-to-Manager Reset works when your actions tell the same story every week: the relationship can stay respectful, but the standard stays clear. As you build that foundation, your team can spend less energy guessing where they stand and more energy doing dependable work.

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