REALITYWIPE

OLD SCRIPT DETECTED

My team doesn’t respect me yet

Try this response:

Respect isn't granted before authority. It follows the leader who acts with consistency and care.

Take the 60-second self-check

SEE THE PRACTICE

Build a response for this thought—and one move to prove it.

THE THOUGHT

My team doesn’t respect me yet

YOUR RECORDED RESPONSE

Respect isn't granted before authority. It follows the leader who acts with consistency and care.

ONE PRIVATE MOVE

Identify one small decision you own this week (scheduling, a tool choice, a priority shift). Write down what you would decide. Notice where you're softening it into a question. Rewrite it as a statement.

The Promotion That Arrived Before the Permission

SCENE_01

The Moment Deference Feels Safe

You're five weeks into the role. The team is discussing the sprint timeline, and it's clear the current plan will miss the client handoff by three days. You know the fix: compress testing, move the demo, shift one engineer's capacity. But Sarah has been here four years. Marcus built half the system. You catch yourself about to say, 'What do you all think we should do?' instead of 'Here's what we're doing.' You soften it into a suggestion. The room stays neutral. Nobody pushes back, nobody owns it. You leave the meeting unsure if they heard you or just didn't care.

SCENE_02

The Private Reading That Follows

The silence reads as doubt. They don't respect the new title yet because you haven't proved you can do the work. If you push too hard, you'll confirm that you're just another manager who didn't come up through the trenches. So you ask more questions. You frame more decisions as collective choices. You wait for a sign that you've earned the right to sound sure. Weeks pass. The decisions don't get clearer. The team's passivity doesn't shift. Neither does your authority. You're still waiting for the moment when it will feel earned enough to claim.

SCENE_03

When the Window Starts Closing

Watkins' research on new-manager transitions identifies a specific vulnerability: the first 90 days are when you have the most credibility to set direction and the least patience to wait for permission. Your window isn't closing because the team is demanding proof. It's closing because consistent deference trains them to doubt your judgment. Respect doesn't wait until you've asked enough questions. It follows the person who reads the situation and acts on it. The sprint timeline is yours to set. Act there. Let the decision itself be the proof.

TRACE · 01/04

How this script runs you

  • You soften directives into suggestions so the team feels included in choices you're already authorized to make.
  • You interpret absence of disagreement as absence of respect and wait longer before deciding anything yourself.
  • You hold back on time-sensitive calls until you sense team consensus, missing the actual window to lead.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Respect Wait

My team doesn't respect me yet — I need to earn it before I can act with authority. Respect is something others grant after they've observed enough patience and deference from me. Until that day comes, acting decisively would reveal I'm an imposter.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Respect isn't granted before authority. It follows the leader who acts with consistency and care.
  • Asking for a vote on my own decisions isn't collaboration—it's using the team to avoid owning the call.
  • The 90-day credibility window is open now. Waiting longer doesn't preserve it. It closes it.

Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.

INSTALL · 04/04

The protocol, on one card

When I think

My team doesn’t respect me yet

I say

Respect isn't granted before authority. It follows the leader who acts with consistency and care.

Then I do one thing

Identify one small decision you own this week (scheduling, a tool choice, a priority shift). Write down what you would decide. Notice where you're softening it into a question. Rewrite it as a statement.

STATUS: READY_TO_INSTALL

Wipe this thought

4 minutes. Your voice. Free.

Start this exact wipe in the app →

The wipe protocol
  1. Write the thought exactly as it plays: "My team doesn’t respect me yet". Word for word — the wipe targets the sentence, not the vibe.
  2. Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
  3. Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
  4. Run the loop: play it every morning and night, log one proof action a day for 7 days.

Straight answers

How do I know if I'm deferring too much versus being genuinely collaborative?

Collaboration shapes how you decide; deference shapes whether you decide at all. If you're asking the team's opinion on something your role is explicitly responsible for, that's deference wearing collaboration's name. True collaboration uses team input to improve your decision, not to escape making one.

Won't acting too quickly without consensus make them lose respect?

Research on new-manager credibility shows the opposite pattern: leaders who wait for consensus rarely gain it. Teams respect decisive action paired with willingness to listen and adjust. Passivity reads as uncertainty, not humility.

What if I make a mistake on a decision I should have involved the team on?

Mistakes made with clear ownership are far easier to recover from than a pattern of unclear authority. Own the call, explain your thinking, and adjust. The team learns you make decisions and correct them—not that you hide until consensus gives you cover.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script