The First-Time Manager

By the end of this chapter, you will have a written availability plan, a recovery schedule, and clear instructions for urgent and non-urgent requests. You will also know how to explain those boundaries without sounding uncaring. I learned this lesson after treating every message as equally important. My open-door approach became an always-open door, and my team stopped checking what they could handle on their own. Once I set response windows and named real emergencies, the team made faster decisions and I finished work with enough energy to lead well the next day.

Use the Sustainable Boundaries Map in three stages: Define, Protect, and Teach. Define your working limits. Protect recovery time with calendar blocks and practical rules. Teach the team how to work within those limits. The roadmap is simple: first set the map, then apply it to a real week, then correct the mistakes that commonly weaken it.

Build Your Sustainable Boundaries Map

The map starts with one distinction: availability is not the same as commitment. You can care about the team and still respond tomorrow morning. A boundary tells people what they can expect, not what they must never ask for.

Write your normal working hours first. If you work from 8:00 a.m. to 5:00 p.m., include your lunch and any regular time away from messages. Then define response times for each channel. For example, you might answer chat during the workday, review email by 3:00 p.m., and return non-urgent text messages the next morning. Your team needs a predictable answer more than instant access.

Use these three parts of the Sustainable Boundaries Map:

1. Define the window. Choose the hours when you normally respond. A clear window, such as 8:30 a.m. to 5:00 p.m. Monday through Friday, prevents people from guessing whether you are available. State exceptions only when they truly matter.

2. Protect recovery blocks. Put lunch, the end of the workday, and at least one evening or full day away from work on your calendar. Treat these blocks as work-protecting appointments because rest improves the decisions you make when you return.

3. Teach the escalation rule. Explain what counts as urgent, who should act first, and which channel to use. A same-day safety issue may require a phone call. A supply request for next week can wait for the normal workday. Without this rule, every sender labels a request urgent.

4. Review the map weekly. Spend ten minutes on Friday checking where the boundary failed. If five messages arrived after 8:00 p.m., do not simply blame the team. Ask which rule was unclear, then adjust the rule or repeat it.

A useful tool here is the two-door rule. Every request goes through one of two doors: “Can wait” or “Needs action now.” “Needs action now” should meet a specific test: it threatens safety, stops essential work, risks a serious customer commitment, or requires a decision before the next normal work period. Everything else enters the next work window.

Recovery needs more than a promise. Schedule a shutdown routine that takes ten minutes: check tomorrow’s first task, record unfinished work, set your status to unavailable, and close work applications. This routine gives your mind a clear stopping point. If you continue carrying open tasks in your head, you may leave the workplace physically while remaining at work mentally.

Tell the team exactly how the system works. Say, “I check chat during working hours. For urgent issues after 5:00 p.m., call me. If I do not answer, contact the duty person listed on the schedule. Please do not send routine updates by text.” That statement removes guesswork and gives the team another path when you are unavailable.

Apply the Map to One Working Week

Consider a five-person repair shop team. The manager starts at 7:30 a.m., finishes at 4:30 p.m., and receives customer updates through email, team chat, and personal text messages. During one week, he answers 11 messages after 8:00 p.m. Three messages concern the next day’s schedule; eight can wait. He feels exhausted, while the team keeps sending messages because he answers quickly.

Apply the Sustainable Boundaries Map in this order:

1. List the channels on Monday morning. Write “team chat: 7:30 a.m. - 4:30 p.m.; email: checked at 10:00 a.m. and 3:00 p.m.; phone: urgent issues only after 4:30 p.m.” Post the list where the team sees it. Expected outcome: everyone knows where to send each type of request.

2. Define the urgent test. Write three examples: a worker cannot safely continue, a customer’s same-day service will fail without a decision, or a building problem threatens equipment. State that tomorrow’s route changes do not qualify after hours unless they affect safety. Expected outcome: fewer false emergencies.

3. Assign backup coverage. Put one team member on the weekly duty schedule. The duty person handles routine after-hours questions and calls the manager only when the urgent test applies. Expected outcome: the manager receives fewer interruptions and the team practices solving ordinary problems.

4. Block recovery time. Add 4:30-5:00 p.m. for shutdown and 5:00-8:00 p.m. as unavailable time. Turn off work notifications at 5:00 p.m. on four weekdays. Keep the phone available for calls from the duty person. Expected outcome: a dependable end to the workday without making the manager unreachable during a real emergency.

5. Review the results Friday. Count after-hours contacts, urgent calls, and routine issues handled without the manager. A useful first target is to reduce 11 after-hours messages to four or fewer while keeping urgent response time under 20 minutes. Expected outcome: a measurable boundary rather than a vague intention.

Send the team a short written note before the new schedule begins. Explain that the change protects reliable leadership, not personal convenience. Invite questions during the next team meeting, then repeat the rule for two weeks. People often test a new boundary because they are checking whether it will last.

Quick checklist

• Write your normal response hours. - Name the correct channel for each type of request. - Define three or four true emergencies. - Create a backup contact or duty schedule. - Block lunch and end-of-day recovery time. - Turn off routine notifications after work. - Record after-hours contacts for one week. - Review the map every Friday and fix unclear rules.

Correct the Boundaries That Fail

The “always available” promise

A new manager may say, “Call me anytime,” because the team needs support. The team hears permission to interrupt for every question, including matters that can wait until morning. The manager then feels resentful when people use the access offered.

Do this: Say, “I am available during these hours. After that, call only for safety, stopped work, or a same-day customer risk.”

Not this: “You can reach me whenever you need me.”

The first statement offers support with limits. The second makes your recovery depend on everyone else’s judgment.

The fake emergency

A team member may label a missing supply, a minor customer complaint, or tomorrow’s staffing question urgent. If you respond immediately every time, you train the team to skip normal planning.

Do this: Ask, “What happens if we wait until 8:00 a.m.?” If the answer involves no safety risk, stopped essential work, or serious same-day damage, place it in the next work window. Keep an after-hours log so you can identify repeated planning failures.

Not this: Solve every problem at night because the sender used the word “urgent.”

The fix may require a better morning checklist, an earlier supply order, or a clearer handoff. Boundaries work best when they expose the process that created the interruption.

The boundary that ignores your own habits

You may announce a 5:00 p.m. finish and then send messages at 9:00 p.m. because you finally have time to think. Your team will follow your behavior more closely than your written rule.

Do this: Draft messages, schedule them for the next workday, and keep a private note for ideas that can wait. Ask a trusted colleague to point out when you break your own availability rule.

Not this: Tell the team to disconnect while continuing to contact them at night.

A boundary becomes credible through repetition. Start with one clear week: define the window, protect the recovery blocks, and teach the two-door rule. Then measure what changed. When your team knows when to reach you, how to handle routine work, and what truly needs immediate action, you create something better than constant access: dependable leadership that can last.

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