You give an instruction and get an eye roll. You set a standard and watch it get ignored the moment you leave the room. You call a team meeting and half the room is on their phone.
If that sounds familiar, you've probably already tried the obvious fixes. Being firmer. Being friendlier. Writing things down. Maybe you've read that respect has to be earned, which is true but useless on its own, because nobody ever explains what earning it actually looks like on a Tuesday afternoon when a nineteen-year-old is ignoring you.
I managed teams in franchise businesses for eleven years, around 300 staff over that time, most of them young, casual, and completely unimpressed by job titles. Here's what I learned: staff almost never disrespect the person. They disrespect the inconsistency.
Respect isn't about authority. It's about predictability.
Think about the managers you respected in your own working life. It probably wasn't the loudest one, or the most qualified one. It was the one whose reactions you could predict. You knew what they'd praise, what they'd pull you up on, and that it would be the same today as it was last week, and the same for you as it was for everyone else.
Now flip it. A manager who lets a late arrival slide on Monday and explodes about it on Friday isn't seen as flexible. They're seen as random. And people don't follow random. They manage around it, they test it, and eventually they ignore it.
Most new managers lose respect in exactly this way, and it happens for an understandable reason: they don't actually know their team yet. They can't be consistent because they don't have a clear picture of who is performing, who is struggling, and who is coasting. So every decision is made on vibes, in the moment, under pressure. Staff feel that instantly.
The two questions your team is silently asking
Every team member is running two assessments on you at all times:
- 1. Does this manager actually see what I do? Do they notice that I cover shifts, fix problems, carry the new starters? Or am I invisible until something goes wrong?
- 2. Is this manager fair? Are the standards the same for everyone, or does the favourite get away with things I'd be pulled up for?
If the answer to either question is no, respect leaks out of the relationship no matter how competent or likeable you are. And you can't answer those questions well from memory, gut feel, or whoever happened to be on shift when you walked past.
Start with an honest map of your team
Here's the exercise I'd give any manager whose team has stopped listening. Take every person on your team and place them on two scales:
- Capability. Can they do the job to standard? Skills, speed, quality, judgement.
- Commitment. Do they want to? Effort, reliability, attitude, care.
Two scores per person. That's it. When you plot them, everyone lands in one of four zones:
- Champion (high capability, high commitment): your best people. Respect problems here usually mean they feel unseen or under-stretched.
- Rogue (high capability, low commitment): skilled but checked out. Often your biggest respect problem, because the rest of the team watches how you handle them. Reluctance to follow process from your most capable person is a message, and it needs a conversation, not a crackdown.
- Apprentice (low capability, high commitment): willing but undertrained. These people rarely disrespect you. They just need investment.
- Misplaced (low capability, low commitment): wrong role, wrong fit, or a hard conversation overdue. Avoiding that conversation costs you respect with everyone else.
The moment you have this map, something changes. You stop treating the team as one blob that "doesn't respect you" and start seeing four different situations that need four different responses. Cracking down on an Apprentice for a capability gap is unfair, and the team knows it. Going soft on a Rogue's commitment gap is weak, and the team knows that too. Matching your response to the actual problem is what fairness looks like from the outside.
Then make check-ins boringly regular
The map only rebuilds respect if it's alive. A one-off assessment is a judgement. A repeated one is a relationship.
Sit down with each person for ten to fifteen minutes on a regular cycle. Not a performance review, just a check-in. Ask what's making work harder, where they feel confident, what would make them stay. And don't score people purely on your own observation, because what you see is the performance staff put on while the manager is watching. The people who actually know who carries the team, who cuts corners, and who quietly fixes things are the teammates working alongside them every shift. Use each check-in to gather structured feedback about how the rest of the team is doing, fold those answers into your capability and commitment scores, and your map starts reflecting how people work when you're not in the room. Over a few sessions you'll see movement: an Apprentice climbing in capability, a Champion drifting in commitment before they quit, a Rogue responding to being taken seriously.
That movement is the whole game. When staff realise you notice their trajectory, not just their latest mistake, the two silent questions get answered. Yes, this manager sees what I do. Yes, this manager is fair. Respect follows from there, and it doesn't need volume or a title to hold.
---
Tracking capability and commitment across a whole team by hand gets tedious fast. Teamark runs the matrix for you: structured check-in questions, scores plotted per session, and a moving picture of where every team member sits and where they're heading. Individual answers are never shown to teammates. Try it at teamark.app.