THE RESIGNATION I DIDN'T SEE COMING
September 14th, 2023. 11:47 AM.
Jessica, my Front Desk Team Lead, knocked on my office door.
"Do you have a minute?"
September 14th, 2023. 11:47 AM.
Jessica, my Front Desk Team Lead, knocked on my office door.
"Do you have a minute?"
"Of course, come in."
She closed the door. Sat down. Took a deep breath.
"I'm putting in my two weeks' notice."
My stomach dropped.
Jessica was my best team lead. Organized. Reliable. Loved by her team. Guest satisfaction scores on her shifts were consistently 4.7/5 (property average: 4.2/5).
Losing her would be devastating.
Her: "I got an offer at another property. Front Desk Supervisor role. It's a good opportunity."
Me: "We can match the salary. I can promote you here. What would it take to stay?"
Long pause.
Her: "Honestly, Syed... it's not about the money."
Me: "Then what is it?"
I was stunned.
Me: "What are you talking about? I trust you completely. You're my go-to person."
Her: "You trust me to execute. But you don't trust me to think. You check everything I do. You redo my work. You micromanage every decision. I feel like I'm just your assistant, not a leader."
I tried to defend myself.
Me: "I'm not micromanaging—I'm just making sure things are done right. I'm trying to develop you."
Her: "Syed, you reviewed the shift schedule I made and changed 8 things. You rewrote the email I sent to a guest. You sat in on my team meeting last week and corrected me in front of my team three times. That's not development—that's control."
She was right.
And I knew it.
This conversation changed how I lead.
Here's what I was doing wrong, why I couldn't let go, and the framework I built to delegate effectively without micromanaging.
After Jessica left (she didn't take my counteroffer—the damage was done), I spent 2 weeks reflecting.
I interviewed 4 other team members: "Do I micromanage? Be honest."
All 4 said yes.
Micromanagement Behavior #1: Redoing Their Work
Jessica would create the weekly shift schedule. I'd review it and change 6-10 shifts.
She'd draft an email to a guest. I'd rewrite it before it went out.
She'd handle a guest complaint. I'd follow up behind her to "make sure it was resolved correctly."
Ensuring quality
Catching errors
Signaling: "Your work isn't good enough"
Undermining her confidence
Jessica stopped trying to do excellent work. She thought: "Why bother? He's just going to change it anyway."
Micromanagement Behavior #2: Making Decisions They Should Make
Team member: "We have a guest requesting an early check-in. The room's not ready yet. What should I do?"
Me: "Tell them we'll have it ready by 1 PM and offer them complimentary coffee in the lobby."
Being helpful
Solving problems quickly
Creating dependency (they'd ask me every time instead of thinking for themselves)
My team became order-takers, not problem-solvers.
Micromanagement Behavior #3: Requiring Approval for Everything
Comp'ing a breakfast ($12 value)
Approving a late checkout
Ordering supplies
Adjusting the schedule
Maintaining control
Creating bottlenecks (everything waited for me)
My team couldn't move fast. Guests waited while team leads "checked with their manager."
Micromanagement Behavior #4: Hovering and Over-Communicating
| Jessica | "I'll handle the VIP arrival this afternoon." |
| Me (2 hours later) | "Hey, just checking—did you set up the VIP room?" |
| Jessica | "Not yet, the guest arrives at 3 PM. I'll do it at 2:30." |
| Me (1 hour later) | "Following up on the VIP room..." |
Staying on top of things
Communicating: "I don't trust you to remember"
Creating anxiety (Jessica felt like I was constantly checking up on her)
Jessica felt micromanaged and infantilized.
Micromanagement Behavior #5: Correcting Them Publicly
Jessica: "This week, let's focus on upselling room upgrades to leisure travelers."
Me (interrupting): "Actually, we should focus on corporate travelers—they have higher willingness to pay."
Adding valuable insight
Undermining her authority in front of her team
Her team didn't respect her as a leader (because I kept overriding her).
After identifying the behaviors, I had to understand why I was doing this.
Root Cause #1: I Confused "High Standards" with "My Way is the Only Way"
"If they don't do it exactly how I would do it, it's wrong."
There are multiple ways to solve most problems. My way isn't always best—it's just familiar.
Jessica's shift schedule was different from how I would have built it. But it wasn't wrong. It worked. It just wasn't my way.
By changing it, I was enforcing conformity, not quality.
Root Cause #2: I Derived Self-Worth from Being "The Solver"
"My value as a manager is solving problems. If my team doesn't need me, what's my purpose?"
A manager's job isn't to solve every problem—it's to build a team that can solve problems without you.
My ego was tied to being indispensable.
When Jessica handled something independently, I felt threatened (even though I shouldn't have).
Root Cause #3: Fear of Failure (and Blame)
"If my team screws up, I get blamed. So I need to control everything to prevent failure."
By controlling everything, I prevented my team from learning through failure.
They never developed the skills to handle things independently, so I had to keep controlling things.
Root Cause #4: I Didn't Know How to Delegate Without Abandoning
"If I delegate and don't check in constantly, I'm abandoning them."
Micromanage (check everything constantly)
I didn't realize there's a middle path: Structured delegation with accountability.
After losing Jessica, I rebuilt my leadership approach from the ground up.
"Jessica, can you handle the VIP arrival this afternoon?"
Just set up the room?
Greet the guest personally?
Follow up after check-in?
All of the above?
| WHAT | What needs to be done (specific outcome) |
| WHY | Why it matters (context) |
| BY WHEN | Deadline |
| DECISION AUTHORITY | What can you decide on your own vs. what needs my approval |
| SUCCESS CRITERIA | How I'll know it was done well |
| SUPPORT | What resources/support you have access to |
| WHAT | Coordinate the VIP arrival for Mr. Johnson (Suite 1205, arriving 3 PM) |
| WHY | He's a top-tier loyalty member and a repeat guest. We want to ensure exceptional experience. |
| BY WHEN | Room ready by 2:30 PM, personal greeting at 3 PM |
You can: Choose amenities (wine, fruit, welcome note), decide room setup, greet guest personally
Room set up per VIP standards (checklist in SOP)
I receive brief update by 4 PM (2-sentence email: "VIP arrival complete, any issues")
SUPPORT: Housekeeping supervisor (Maria) is aware and prioritizing the room. Budget for amenities: $75.
✅ Crystal clear expectations (no ambiguity)
✅ Defined decision authority (she knows what she can own vs. escalate)
✅ Context provided (she understands why it matters)
Result: Jessica doesn't need to ask me 5 follow-up questions. She can execute independently.
I gave everyone the same level of autonomy (very little).
Autonomy should be earned and graduated.
I make decisions, you execute
I check work frequently
You propose solutions, I approve before execution
I review work before it's final
You execute, inform me after (no prior approval needed)
I spot-check periodically (not every time)
Full autonomy in your domain
You make all decisions
I'm informed only if there's an issue or exception
Jessica was at Level 3 (proficient), but I was treating her like Level 1.
"You're at Level 3. Here's what that means: For routine operations (scheduling, guest service, team management), you have full authority. Execute, then inform me. I'll spot-check periodically, but I trust your judgment. If something unusual comes up or you need input, you can always ask—but you don't have to ask for approval."
This clarity changed everything.
She knew exactly how much autonomy she had. No more guessing.
Give task
The Result: I either hovered constantly OR went radio silent.
Structured check-ins based on task complexity and team member's level.
High-Stakes Task + Level 2 Team Member = Daily Check-Ins
Routine Task + Level 3 Team Member = Weekly Check-Ins
Check-In Cadence: Weekly (every Friday)
| Jessica | "It's done. We're fully staffed except Thursday PM—still need one agent. I'm working on it." |
| Me | "Great. Let me know if you need help covering Thursday." |
| Total time | 90 seconds. |
Reviewing the schedule line-by-line
Questioning her decisions
Checking that it's on track
Offering support if needed
When I saw Jessica do something I wouldn't have done, I immediately corrected it.
Jessica sent an email to a guest. I read it and thought: "I would have phrased that differently."
Old me: Rewrote the email before it sent.
Let her send the email (don't intercept)
If YES → Let it go. Different doesn't mean wrong.
Wait for a private moment
"Hey Jessica, I noticed [specific behavior]. It didn't quite land the way we wanted [outcome]. Here's what I've found works well in these situations: [suggestion]. What do you think?"
Hi Mr. Thompson,
Unfortunately, we can't accommodate your early check-in request for 11 AM because the room won't be ready. Check-in starts at 3 PM. Let me know if you have questions.
Thanks,
Old me: "That's too blunt. Rewrite it with softer language."
New me: Observe the outcome.
Reflection: Her email worked. It wasn't how I would have phrased it, but it was effective.
Action: Let it go. No feedback needed.
Guest replied (angry): "This is terrible service. I'm canceling my reservation."
"Hey Jessica, I saw the early check-in email. The guest was upset and canceled. I think the tone came across as blunt. In these situations, I've found it helps to acknowledge their request first, explain the constraint, then offer an alternative. Something like: 'I understand you'd prefer an early check-in. Unfortunately, the room won't be ready until 3 PM due to our cleaning schedule. I'd be happy to store your luggage and offer complimentary access to our pool/lounge while you wait—does that work?' What do you think?"
This is coaching, not micromanaging.
I owned everything. Jessica felt like she was executing my vision, not leading her own domain.
I gave her full ownership of specific areas.
"Jessica, you now own guest service recovery. That's your domain. You set the standards, you train the team, you handle escalations. I'm here if you need me, but this is yours. What's your vision for it?"
✅ She has agency (it's not just executing my plans)
✅ She's accountable (success or failure is hers)
✅ She's invested (it's her program, not mine)
How she structured the training
What specific language she used in scripts
Overall outcomes (guest satisfaction scores, complaint resolution time)
Budget (she proposed, I approved)
Jessica built a service recovery program that was better than what I would have built.
Because she had the autonomy to innovate.
Jessica had already left. But I applied this framework with my remaining team.
Metric #1: Team Autonomy
Time Saved: 60-90 minutes daily (I could focus on strategic work vs. tactical decisions)
Metric #2: Decision Quality
| Decisions that I disagreed with initially | 34 |
| Decisions that worked anyway | 28 (82%) |
| Decisions that failed and needed correction | 6 (18%) |
I would have corrected all 34 if I were still micromanaging. That would have been 28 unnecessary interventions.
Metric #3: Team Satisfaction
Before: 2.8/5
"My manager provides the right level of support (not too much, not too little)"
Before: 2.4/5
Metric #4: Performance
Before framework: 4.2/5 (property average)
Why?
Team leads who felt trusted and empowered delivered better service.
They weren't just following my orders—they were leading.
Metric #5: Retention
Before: 3 team leads quit in 12 months (including Jessica)
Framework #1: The Delegation Brief Template
| WHAT | [Specific outcome] |
| WHY | [Why it matters] |
| BY WHEN | [Deadline] |
| DECISION AUTHORITY | [What they own vs. what needs approval] |
| SUCCESS CRITERIA | [What "good" looks like] |
Framework #2: The Autonomy Ladder
| Level 1 (Tell Me) | New, learning → High oversight, frequent check-ins |
| Level 2 (Approve First) | Developing → Review before execution |
| Level 3 (Inform After) | Proficient → Execute, then inform |
| Level 4 (Own It) | Expert → Full autonomy |
Match your management style to their level.
Framework #3: The Micromanagement Self-Check
Is this actually wrong, or just different from how I'd do it?
Will this intervention help them grow, or create dependency?
Am I acting out of fear/ego, or genuine need?
Can I let them learn through natural consequences?
If you answered "different," "create dependency," "fear/ego," or "yes" → Don't intervene.
Framework #4: The Coaching Script
"I noticed [specific behavior]. The outcome was [result]. Here's what I've found works well: [suggestion]. What do you think?"
States observation (not judgment)
Links to outcome (not personal criticism)
Offers suggestion (not command)
Day 1: Self-Assessment
Do I redo my team's work?
Do I make decisions they should make?
Do I require approval for everything?
Do I check in too frequently?
Do I correct them publicly?
If you answered "yes" to 2+ → You're micromanaging.
Day 2: Ask Your Team
"Do I micromanage? Be specific—what behaviors make you feel that way?"
Be prepared for hard truths.
Day 3: Apply the Autonomy Ladder
Assess each team member (Level 1-4).
Adjust your management style accordingly.
Day 4: Create One "Your Domain"
Pick one team member who's at Level 3 or 4.
Give them full ownership of one area.
Day 5: Implement Delegation Briefs
For the next week, use the Delegation Brief template for every task you assign.
Track: Do you get fewer follow-up questions?
The Hospitality Insider
Enjoyed this post? Get weekly hospitality insights delivered to your inbox.
No spam, ever. Unsubscribe anytime.
Was this helpful?
Written by
Front Desk Manager at Galt House Hotel, managing 1,300+ rooms daily. Published author of 3 books on hospitality operations, leadership, and personal growth.
I spent 6 weeks building a hotel scheduling tool I was sure would sell. Launch day: zero customers. Here's the complete post-mortem—what I built wrong, why it failed, and the pivotal lesson that changed how I build products forever.
200+ pages of hotel procedures sitting in binders nobody reads. I uploaded them to ChatGPT and built an AI assistant that answers staff questions instantly. Here's the setup process, prompt engineering strategy, and 90-day results.
