True Leadership Skills gives managers a direct, principle-based system for handling the performance problems that drain teams — lateness, lack of initiative, conflict, complaining, blaming, missed commitments, and more.
1. Principles — Master the core ideas that drive every effective leadership conversation.
2. Challenges — Practice real performance situations with decision points, exact language, and action steps.
3. Blind spots — Spot the leadership patterns that quietly undermine standards — and what to do instead.
4. Ask Randy — Describe a live situation and get direct guidance grounded in these principles.
Free preview: 4 principles, 3 challenges, 4 blind spots, and 3 Ask Randy questions.
How to confront the behavior without drama and shift ownership.
PerformanceStop the “tell me what to do” cycle and build ownership.
PerformanceOwn clarity, the interview, and whether capable people want this team.
HiringShut down the victim loop and redirect energy to solutions.
CultureWaiting for a better moment is how standards die.
PersonalEnd the deflection and put responsibility back where it belongs.
AccountabilityActivity isn’t direction—name the aim and the standard.
DirectionHumble leaders ask before they decide.
PersonalThese are the foundation. Every conversation, decision, and performance discussion should map back to one or more of them.
Your presence, standards, and consistency shape the team. Your actions are either making things better or making them worse. There is no neutral. Everyone has influence. Make the conscious choice to use your influence to drive change in employee behavior.
People change when the current path becomes more uncomfortable than the new one. Create productive discomfort. The challenge of effective leaders is that making others uncomfortable also makes them uncomfortable. You must be willing to accept discomfort to achieve your goals.
Rescuing, over-explaining, or softening consequences steals growth. Leave the responsibility where it belongs. You were likely promoted because you took responsibility. That same habit now works against you when leading others. Avoid the temptation to do it yourself. Give others the opportunity to succeed.
When you face a problem, you think until you believe you’ve found the answer — then you stop thinking. It becomes a belief. Wrong beliefs produce wrong actions. Understand this in yourself and you will begin to see it in others. Challenge beliefs that block performance.
If it bothers you, say something. Put the issue in the other person’s head, not just yours. Name the behavior without attacking character. Short, calm, and specific works better than long, emotional, or delayed.
You cannot control others or how they make you feel. You can control how you respond. Don’t get defensive and don’t overreact. Feeling stress doesn’t require you to show stress. Maintain self-control and people gain confidence in you as a leader.
Vague standards produce vague results. Make expected behavior observable and measurable. “Be more proactive” means nothing. “Bring me three options by Thursday at 2:00” is clear.
Telling takes responsibility away. Asking transfers thinking and ownership. When people answer in their own words, something clicks. Use questions to develop judgment and put responsibility back where it belongs.
If you ask for an excuse, you’ll get one. Asking “why” focuses on the past. You want them to focus on the future. Redirect: “What will you do differently so this doesn’t happen again?”
Most disappointment comes from expectations that were never stated. If you haven’t made the standard visible, you don’t get to be surprised when it isn’t met. Say what you want. Confirm what they heard.
What gets attention, agreement, relief, or protection tends to continue — including the behaviors you dislike. Stop rewarding patterns you don’t want. That includes your own.
Attention is energy. Drama, complaining, and excuses grow when they get airtime. So give attention to ownership, follow-through, and initiative. Choose deliberately what you feed.
Under pressure, your first job is to not make things worse. Keep your cool. Think before you act. You can still confront — just not from the urge to wound or win.
If the expectation lives only in your head, it is not a standard yet. Define it in visible terms and ask for it. Clarity is kindness.
Defensiveness, people-pleasing, overcontrol, and withdrawal often come from insecurity — theirs or yours. Seeing the driver restores choice. Understanding the behavior doesn’t excuse it. The standard remains.
Difficult people and hard moments are a mirror. Your response is the leadership lesson the team actually learns. Choose the response that matches the leader you want to be.
Old wounds show up as overreaction, avoidance, or distrust. Seeing that reduces personalization. It does not excuse poor performance. Accountability and compassion can coexist.
Employees (and managers) sometimes protect themselves from a threat that is no longer real. Name the fear when useful, then return to the present standard and the next action.
Judgment closes options. Observation keeps you free to choose. Describe what you see before you decide what it means. Then respond with intention.
Consistency builds trust faster than intensity. If you commit, follow through. If you set a standard, apply it. Your people believe what you repeatedly do, not what you announce once.
Starting without finishing trains the team that incomplete is acceptable. Close loops. Complete the conversation, the follow-up, and the project. Finished work creates trust and momentum.
Your example is always teaching. When leaders stay visibly engaged in productive work, standards rise. When leaders disappear into meetings and email, so does urgency. Model the work ethic you expect.
Their reaction tells you something about them, the situation, or the standard — not automatically something about your worth. Learn to read behavior as data. When you treat it as information instead of a personal attack, you stay free to choose your response instead of being controlled by how it makes you feel.
You are already paying people for the job they are doing. A raise is not a reward for time served or for asking — it is tied to taking on more real responsibility. When someone wants more money, the question is: what additional responsibilities are you ready to own? More responsibility creates growth, and growth is what keeps people engaged. The new ownership must be real and visible — not busywork invented to justify a paycheck.
Thinking about a problem is not the same as being able to say what it is. People often only understand what they mean after they hear themselves say it. As a leader, don’t lecture the insight. Ask questions until they can say the standard, the problem, and the next step out loud. What they can speak, they can own.
Try this: In your next hard conversation, ask: “In your words, what’s the real issue?” Wait. Then: “What are you going to do about it?”
Empathic listening is not soft management. Reflect content and feeling before you correct, direct, or problem-solve. Reflection is not agreement — it lowers heat so the direct approach can land. Levels: mimic → rephrase content → reflect feeling → content + feeling, then “Did I get that right?”
Try this: In the next emotional pushback, say only a level-4 reflection first. Wait for their yes/no before you continue.
If you can’t say what “good” looks like in observable terms, you hire hope. Vague roles attract vague candidates. Clear behaviors in the job and in the interview give you something real to select for — and something fair to manage later.
Try this: Before the next hire, write five observable behaviors for the role. Use them in follow-up questions.
People learn what really matters from what gets rewarded, ignored, and punished — not from the values poster. If high performers carry the load and low performers are protected, the system is training the wrong behavior.
Try this: Name one behavior you reward by accident (e.g. the squeaky wheel gets your time). Change one consequence this week.
Keeping good people is a leadership problem. Turnover is often feedback: unclear standards, unfair load, no path to grow, or pay without real responsibility. Fix the environment you control before you blame the labor market.
Try this: Ask a strong performer privately: “What would make you more likely to stay and grow here?” Listen fully before you explain.
If people can’t say where the team is going in plain words, you don’t have a vision—you have a slide. Vision belongs in a few honest sentences a front-line person can repeat and connect to today’s work.
Try this: Ask three people: “In your words, where is this team going?” If the answers scatter, clarify before you add another goal.
“Improve culture” is not a goal. A goal names what will be true, by when, and how you’ll know. If you can’t see it or schedule it, it isn’t a goal yet—it’s a wish.
Try this: Rewrite one fuzzy aim as: what / by when / how we’ll know.
Goals tell people what to hit. Standards tell them how we work so the goal is possible. Missed goals often mean unclear or unenforced standards—not simply “lazy people.”
Try this: For your top goal, write three daily/weekly “looks like” behaviors that support it.
Vision and goals stick when people can repeat them in their own words and name their part. Tell less. Ask: “What’s our aim, and what do you do that supports it?”
Try this: In your next huddle, have two people state the main goal in their words before you add anything.
What you reward, ignore, and put on the schedule is your vision in practice. If the vision says quality and the system only rewards speed, the system wins. Fix the contradiction or stop pretending.
Try this: Name one way your calendar, praise, or consequences contradict the goal you say matters most.
You aren’t expected to have all the answers. Before an important decision, talk with the people who will live with it—especially those closer to the work. Input isn’t weakness. Skipping the people who will execute or be affected is arrogance dressed up as speed. You’re still the decision-maker—you’re not taking a vote on everything—but the more honest input you get, the better the decision and the buy-in after.
Try this: Before your next non-urgent decision that hits the team, ask at least two people who do the work: “What am I missing?” Listen fully before you explain your preference.
Desperate decisions feel like relief—hiring a weak fit so you don’t have to cover the work, or taking any body because you waited too long to act. That’s often how you buy a worse problem later. Act while you still have options, not only when you’re cornered.
Try this: Before your next “we have to hire someone now” moment, write the standard for the role. If the candidate doesn’t meet it, keep covering while you hire right—not lower the bar.
Bad decisions may not blow up for months, so leaders miss the link. Fixing a problem late can make things messier before they improve. Positive changes also take time to show. Move early, then stay the course long enough for the result to appear—and for momentum to build. The sooner you solve it cleanly, the sooner improvement can start.
Try this: Name one change you made that hasn’t “paid off” yet. Decide the review date before you abandon it.
Interrupting prioritizes your thought over their dignity. In leadership it also kills truth: people stop bringing the full story. Self-control other people experience as respect—hear the whole thought before you respond.
Employee performance problems, your leadership patterns, hiring/retention, and direction (vision, goals, standards).
Select a common problem. You’ll get the situation, the principles in play, exact language, and the actions that produce change.
When the performance problem is on the team—confront the pattern, not the excuses.
Repeated tardiness that others notice.
AccountabilityWaits for direction instead of moving work forward.
OwnershipFocuses on problems and spreads negativity.
CultureYou own clarity, the interview, and whether capable people want this team.
HiringFriction that reduces team effectiveness.
RelationshipsDeflects responsibility onto people or circumstances.
AccountabilityShuts down, argues, or ignores coaching.
DevelopmentLots of activity; unclear direction. Vision and one goal, not more motion.
DirectionMeets the bare minimum and shows little drive.
PerformanceImmediately justifies, deflects, or escalates.
AccountabilityThe system may be rewarding the wrong behavior.
RetentionSpreads talk that damages trust and focus.
CultureAgrees to actions then fails to deliver.
AccountabilityDraws hard lines to avoid ownership.
OwnershipSame core questions for fairness; skill is the follow-up.
HiringAgrees in the room, then works against the decision.
CultureClaims results that belong to the team.
TrustBrings every small decision upward.
Ownership“Hit the number” without defining how we work.
DirectionAttention is elsewhere during work time.
PerformancePushes back on change without a better plan.
ChangePolish passed the interview; ownership didn’t show up on the job.
HiringPersonal issues dominate the workday.
CultureRequests more money without matching results.
PerformanceYour best people became the patch for weak standards.
RetentionCrowds out quieter voices in meetings.
RelationshipsSteers around hard work and hard conversations.
OwnershipThe speech and the system don’t match.
DirectionUneven treatment that damages trust.
CultureSilent resistance that still influences the room.
CultureOnboarding was hope; standards weren’t enforced early.
RetentionHoards knowledge or refuses to support others.
TeamAnger or emotion that damages the environment.
Self-controlEverything is priority—so nothing is.
DirectionCommitments slip without early escalation.
AccountabilityWords and actions don’t match.
TrustYou told them. They never had to say it.
DirectionIncomplete work becomes the pattern.
ExecutionActivity without results; weak example for others.
ExampleSkip standards and system; hunt for a villain.
DirectionPatterns in your behavior as a leader—not the employee’s. “You…” means the manager.
You wait, hint, or hope it self-corrects.
PersonalPushback feels like an attack; you argue or shut down.
PersonalFaster to do it yourself—so they never grow.
PersonalDisapproval without “what good looks like.”
PersonalYou protect comfort; standards slip.
PersonalLoud problems get your time; steady performers get load.
PersonalThey’re not your peer support group.
PersonalRules depend on mood, favorites, or who pushes back.
PersonalUnspoken expectations, then frustration.
PersonalYou steal the lesson; the pattern continues.
PersonalMajor change announced; the people closest to the work are blindsided.
PersonalInput theater—not learning.
PersonalWorse than not asking—destroys trust.
PersonalEndless polling; no decision.
PersonalBad fit because you won’t cover the work—or you waited too long.
PersonalDelay shrinks options; then every decision feels forced.
PersonalNo patience for lag; never build momentum.
PersonalActed late; surprised it gets worse before better.
PersonalHave a performance problem you want added or want feedback on? Tell us what you’re facing.
Submit a ChallengeThe behavior is visible. Others are watching how you handle it.
Jordan has been 10–20 minutes late three times in the last two weeks. You’ve mentioned it casually once. It continues. The rest of the team notices. You’re starting to feel the irritation and the pressure to “do something.”
Managers influence by what they do and by what they don’t do.
· ·
Lateness continues when you wait for “one more time,” send group emails, or debate why they were late.
Better move: Name the pattern the same day. State the visible standard. Ask for the plan — not the excuse.
What is your first move?
Open cleanly:
“Jordan, I need to talk with you about start times. You’ve been late three times in the last two weeks. What are you going to do to make sure this doesn’t happen in the future?”
State the standard (Principle 7):
“Starting on time means you are at your workstation, ready to work, at 8:00. Not walking in at 8:10.”
Don’t ask for excuses (Principle 9):
Do not ask “Why were you late?” If an excuse appears, acknowledge briefly and redirect: “I understand. What will you do so this doesn’t happen again?”
Leave responsibility with them (Principle 3):
“What will you do differently so this doesn’t continue?”
Close with consequence clarity:
“I expect this fixed immediately. If it isn’t, we’ll move to the next step in the process.”
Identify one performance pattern you’ve been tolerating. Schedule the direct conversation within 48 hours. Use the language above.
Principle 1: Your silence or delay is an active influence. The team is reading it as acceptance of the standard.
Principle 2: The discomfort of the conversation is temporary. The discomfort of ongoing lateness compounds every day you wait.
Principle 3 & 5: A short, clear statement (“You’re late. That stops.”) moves the problem out of your head and into theirs. You do not need a long discussion to confront.
Principle 7: “Be on time” is vague. “At your workstation ready to work at 8:00” is observable.
Principle 9: Asking “why” invites an excuse and keeps the focus on the past. Skip the why. Ask only for the future solution.
The employee is capable but stays in “tell me what to do” mode.
Alex completes assigned tasks adequately but rarely moves to the next logical step without being told. When work slows, Alex waits. You’ve found yourself giving more and more detailed instructions. You’re doing the thinking for both of you.
Managers influence by what they do and by what they don’t do.
· ·
If you keep directing every next step, you train waiting. Vague calls for “more initiative” don’t create it.
Better move: Describe what ownership looks like. Ask for their plan. Stop absorbing the thinking.
Which response creates the most growth?
Name the pattern:
“Alex, I’ve noticed you wait for me to tell you the next step even when the work is clear. That needs to change.”
Reset the expectation (Principle 7):
“I expect you to identify the next action, make a recommendation, and move forward on items within your scope without waiting for me.”
Create productive discomfort (Principle 2 & 3):
“From now on, when you bring me a problem, come with at least one recommended solution. I’ll stop giving the answer first.”
Ask rather than tell (Principle 8):
Replace answers with questions: “What do you see as the options?” “What do you recommend?”
Surface the belief (Principle 4):
“What do you believe happens if you make the wrong call?” (Then address the real fear.)
In the next three interactions where someone asks you what to do, respond with a question instead of an answer. Track what happens.
Principle 3 & 8: Every time you tell instead of ask, you take the responsibility (and the growth) away. The short-term speed costs long-term capability.
Principle 2: Sitting in the silence after you ask a question is uncomfortable — for both of you. That discomfort is the mechanism of change.
Principle 4: If you believe the person “just isn’t a self-starter,” you will keep telling. Challenge that belief first.
Principle 7: Define what initiative looks like in observable terms: “I expect you to bring a recommended next step, not a blank request for direction.”
Negativity that spreads and lowers the standard for everyone.
Taylor regularly points out what’s wrong — processes, other people, leadership decisions — but rarely offers solutions or takes ownership. Other team members are starting to echo the same tone. Energy is dropping.
Managers influence by what they do and by what they don’t do.
Giving attention to the squeaky wheel · ·
Complaint grows when it gets airtime and when nothing is redirected to a request or plan.
Better move: Listen once, then require a request or next step. Stop feeding the loop.
Best first response?
Name it:
“Taylor, I’ve noticed a pattern of focusing on problems without moving to solutions. What are you going to do to make sure this doesn’t happen in the future?”
Set the new standard:
“When you raise an issue, I expect you to also bring what you think should be done about it — or what you’re willing to do.”
Remove the audience:
“Venting to the team is not acceptable. Bring concerns to me directly.”
Ask rather than tell (Principle 8):
“What’s your recommendation?” “What are you going to do about it?”
Leave ownership:
“I won’t solve this for you. What are you going to do differently starting today?”
The next time someone complains without a solution, stop the conversation and ask for one concrete recommendation before continuing.
Principle 1: Tolerating chronic complaining teaches the whole team that negativity is an acceptable contribution.
Principle 2 & 5: A short private statement that the pattern must change is often enough to create the necessary discomfort. You do not need a long debate.
Principle 3 & 8: Asking “What’s your recommendation?” instantly transfers responsibility. Telling them what to do keeps it with you.
Principle 5: Bringing the behavior to their awareness (“I’ve noticed a pattern of complaining without solutions”) is the confrontation. It does not have to become an argument.
Interpersonal friction that reduces team speed and trust.
Sam and another team member clash regularly. Tone is sharp, collaboration is minimal, and others avoid putting them on the same work. You’ve heard both sides. Productivity is suffering.
Managers influence by what they do and by what they don’t do.
· ·
Conflict hardens when you stay out too long or jump in hot.
Better move: Address early, privately where possible, and keep your self-control.
Strongest move?
Individual conversations first:
“Sam, the way you and [Name] interact is affecting the team. That stops now.”
Define the standard (Principle 7):
“Professional behavior means respectful tone, timely responses, and focusing on the work — not on winning or scoring points.”
Own only your side (Principle 3):
“I am not asking you to like each other. I am requiring you to work effectively together. What will you change in your approach?”
Self-control (Principle 6):
Stay calm even if they become defensive. Do not get pulled into the history.
If you currently have interpersonal friction on the team, schedule the individual conversations within 72 hours. Use the language above.
Principle 1: Allowing ongoing friction teaches the team that professional standards are optional when personalities clash.
Principle 3: You cannot make two people like each other. You can require each person to own their side of the professional behavior.
Principle 5: A clear, calm statement of the required standard is the confrontation. You do not need to relitigate every past incident.
Principle 6: If you become emotional or defensive, the conversation shifts from standards to personalities. Your composure keeps the focus on behavior.
Deflects responsibility onto people, processes, or circumstances.
Casey consistently explains missed deadlines, errors, or incomplete work by pointing to other people, unclear instructions, system problems, or external factors. Rarely owns the outcome. Other team members are starting to notice that accountability is uneven.
Managers influence by what they do and by what they don’t do.
· ·
Blame continues when you accept stories about why it’s someone else’s fault.
Better move: Redirect to ownership: what will you do next? Don’t prosecute the past.
Best response to the pattern?
Name the pattern:
“Casey, I’ve noticed a pattern. When something misses the mark, the explanation is usually about someone else or something outside your control. What are you going to do to make sure this doesn’t happen in the future?”
State the standard (Principle 7):
“I expect you to own the outcome of your work. That means when something is off, you start with what you controlled and what you will do differently.”
Ask rather than tell (Principle 8):
“What part of this result do you own?” “What will you do differently next time?”
Leave responsibility (Principle 3):
“I’m not interested in a list of reasons it wasn’t possible. I’m interested in what you are going to control going forward.”
The next time someone explains a miss by pointing outward, stop and ask: “What part of this do you own?” Then wait for the answer.
Principle 3 & 8: Every accepted excuse is a small transfer of responsibility away from the employee. Asking “What do you own?” puts it back.
Principle 9: Asking “why” invites an excuse and commits the person to a past narrative. Skip the why. Ask only for what they will do differently going forward.
Principle 2: Requiring ownership creates discomfort. That discomfort is what makes the old pattern less attractive than the new one.
Principle 4: If you believe the person is “just unlucky” or “always caught in other people’s failures,” you will keep accepting the deflection. Challenge that belief.
Principle 5: You do not need a long investigation of every claim. Naming the pattern of blaming is itself the confrontation.
Shuts down, argues, or ignores coaching when given direction for improvement.
Riley receives clear, specific feedback on a performance gap. Instead of engaging, Riley becomes quiet, argues the point, or later continues the same behavior as if the conversation never happened. Progress stalls.
Managers influence by what they do and by what they don’t do.
· ·
Resistance wins when you soften the standard to keep peace or match their heat.
Better move: Stay calm. Restate the standard. Ask for their plan to meet it.
Best response when resistance appears?
Name the pattern:
“Riley, when I give feedback, the response is often resistance or the behavior stays the same. What are you going to do to make sure this doesn’t happen in the future?”
State the standard:
“I expect you to hear the feedback, own the gap, and tell me what you will do differently.”
Ask rather than tell (Principle 8):
“What will you change starting this week?”
Don’t ask for excuses (Principle 9):
If justification starts, redirect: “I’m not looking for reasons. I’m looking for what you will do differently.”
Self-control (Principle 6):
Stay steady. Do not match their emotional intensity.
The next time you give feedback and meet resistance, do not debate. Restate the expected change and ask only for the next concrete action.
Principle 2: Resistance is often a bid to avoid discomfort. Holding the standard creates the productive discomfort that drives change.
Principle 6: Your calm is contagious. Escalation from you hands control of the conversation to the employee.
Principle 8 & 9: Asking “What will you do differently?” keeps ownership with them and stays future-focused. Asking “why” invites a past-focused defense.
Principle 4: If you believe “they just can’t take feedback,” you will stop giving it. Challenge that belief and keep the standard clear.
Meets the bare minimum, shows little drive, and rarely contributes extra effort or ideas.
Morgan completes assigned tasks at an acceptable level but never stretches, volunteers, or looks for better ways. Output is steady but flat. Others notice the low energy and begin to lower their own effort.
Managers influence by what they do and by what they don’t do.
· Unaware of how people are performing ·
Coasting becomes the job when average effort has no consequence and no clear scoreboard.
Better move: Make outcomes visible. Address the gap early. Stop protecting low effort.
Best move?
Name the pattern:
“Morgan, I’ve noticed your work stays at the minimum required. That is no longer enough in this role.”
Describe the expected behavior (Principle 7):
“I expect you to complete the core work and also identify improvements, anticipate problems, and contribute ideas without being asked.”
Ask rather than tell (Principle 8):
“What will you take ownership of this month beyond the assigned tasks?”
Leave responsibility (Principle 3):
“This is your performance to raise. I’m here to support, not to carry the extra effort for you.”
Identify one person who is coasting. Define in writing what stronger contribution looks like, then have the conversation.
Principle 1: Tolerating coasting teaches the whole team that minimum effort is acceptable.
Principle 2: Raising the standard creates discomfort. That is the point.
Principle 7: “Be more proactive” is vague. Describe the visible behaviors you want to see.
Principle 3 & 8: Asking them to define their own next contribution keeps ownership with them.
Immediately justifies, deflects, or escalates when a mistake or gap is pointed out.
When you point out an error or a missed standard, Jordan quickly explains why it wasn’t their fault, points to someone else, or becomes sharp in tone. The correction never lands cleanly and the same issues repeat.
Managers influence by what they do and by what they don’t do.
· ·
Defensiveness escalates when feedback is vague, public, or delivered when either of you is flooded.
Better move: Private, specific, calm. Describe behavior. Don’t argue their character.
Best response to defensiveness?
Stay steady (Principle 6):
Do not match the intensity. Keep your voice and body language calm.
Name the pattern if it repeats:
“When I raise a problem, the first response is usually a defense. That has to stop.”
Redirect (Principle 9):
“I’m not looking for why it happened. I’m looking for what you will do so it doesn’t happen again.”
Ask for ownership (Principle 8):
“What will you change?”
Practice one short redirect phrase: “I’m not looking for reasons. What will you do differently?” Use it the next time defensiveness appears.
Principle 6: Defensiveness often tries to pull you into emotion. Your self-control keeps the conversation on the standard.
Principle 9: Any question that starts with “why” hands the floor back to the defense. Stay future-focused.
Principle 3: Every successful defense that ends the conversation steals growth. Keep responsibility with them.
Principle 5: A short, calm redirect is often enough. You do not need a long confrontation.
Spreads talk about others that damages trust, focus, and team energy.
Alex regularly shares negative information or speculation about coworkers. Conversations turn into side discussions about people rather than work. Trust erodes and some team members start avoiding Alex or the whole group.
Managers influence by what they do and by what they don’t do.
· ·
Drama grows when leaders participate, ignore it, or never name the standard for talk about people who aren’t present.
Better move: Shut it down cleanly. Redirect to the person involved or drop it.
Best first move?
Name it directly:
“Alex, I’ve noticed a pattern of talking about other people in ways that create drama. That stops now.”
Describe the expected behavior (Principle 7):
“Professional behavior means discussing work and solutions, not other people’s character or private issues. If you have a concern about someone, bring it to me or to them directly.”
Leave responsibility:
“This is your behavior to change. What will you do differently starting today?”
The next time gossip starts, interrupt it immediately and redirect. Then decide whether a private conversation is required.
Principle 1: Your silence is permission. The team watches what you allow.
Principle 5: A short private statement is usually enough to start the change. You do not need a long confrontation.
Principle 2: Removing the social reward of gossip creates discomfort that reduces the behavior.
Principle 7: Define the positive standard clearly so the person knows what “professional” looks like in practice.
Agrees to actions or deadlines, then fails to deliver without clear communication.
Sam consistently says “yes” or “I’ll take care of it,” then the commitment slips. Deadlines pass, updates are missing, and you find yourself chasing or doing the work yourself. Reliability is eroding.
Managers influence by what they do and by what they don’t do.
· ·
Missed commitments continue when “yes” has no inspection and no cost.
Better move: Make commitments explicit. Inspect follow-through. Require early escalation.
Strongest response?
Name the pattern:
“Sam, I’ve noticed a pattern. You agree to take things on, and then they don’t get completed as committed. What are you going to do to make sure this doesn’t happen in the future?”
Describe the standard (Principle 7):
“Following through means the work is done by the agreed time, or you raise the risk early with a revised plan. Silence is not acceptable.”
Don’t ask for excuses (Principle 9):
If reasons start, redirect: “I’m not looking for why it slipped. I’m looking for how you will make commitments reliable from here.”
Ask for ownership (Principle 8):
“What will you do differently so your commitments can be trusted?”
Identify one person with repeated missed commitments. Have the direct conversation and set one clear, measurable follow-through expectation for the next two weeks.
Principle 3: Every time you cover a missed commitment, you take responsibility away from the person who owns it.
Principle 9: “Why didn’t it get done?” produces a story. “What will make the next commitment reliable?” produces a plan.
Principle 2: Feeling the impact of a missed commitment is often the discomfort that creates change.
Principle 7: Reliability is observable. Define what “done on time with early escalation” looks like in practice.
Hard lines used to avoid ownership.
When asked to help with a task outside their narrow role, an employee responds, “That’s not my job.” Work sits. Others pick up the slack. The phrase is becoming a shield.
· ·
“Not my job” works when team support was never defined and you absorb the work yourself.
Better move: Define team support as part of the role. Ask for their plan. Stop rescuing.
What is your first move?
Open:
“I heard you say that’s not your job. On this team, supporting the work is part of everyone’s job.”
Describe:
“Supporting the work means when a teammate is overloaded on a shared deadline, you help close the gap.”
Ask:
“What’s your plan for helping get this finished today?”
The next time you hear “not my job,” respond the same day with a clear standard and a request for a plan.
Principle 11: Every time you absorb the work, you reward the refusal.
Principle 8: Asking for their plan puts ownership back on them.
Principle 14: If team support was never defined, define it now.
Agreement in the room, resistance outside it.
In the meeting, the employee nods and agrees. Afterward, they tell coworkers the decision is wrong and quietly work against it. Alignment is breaking down.
· ·
After-meeting resistance continues when public agreement is never held to private support.
Better move: Name the pattern. Require concerns in the room. Support decisions once made.
What is your first move?
Open:
“I need to talk about what happens after meetings. You agreed in the room, then worked against the decision outside it.”
Standard:
“Once we decide, we support the decision publicly. If you disagree, raise it in the meeting — not in the hallway.”
Ask:
“How will you handle disagreement differently going forward?”
Address one clear example this week. State the standard for how decisions are supported after the meeting.
Principle 20: Teams trust leaders who close the gap between words and actions.
Principle 5: Undermining continues when it is never named.
Results claimed; trust eroded.
A team member presents work in a way that makes it sound like theirs alone. Contributors notice. Motivation drops. You saw the real effort distribution.
· ·
Credit-stealing becomes culture when leaders stay silent to keep peace.
Better move: Name what you observed. Set the standard for how shared work is presented.
What is your first move?
Open:
“I want to talk about how credit was described in that update. The way it landed made the work sound like it was yours alone.”
Observe:
“Alex and Priya did the analysis. Your role was coordination. That distinction matters.”
Standard:
“Going forward, name contributors when you present shared work.”
Have the private conversation before the next shared presentation.
Principle 19: Start with what you observed, not a character judgment.
Principle 5: Unnamed credit-stealing becomes the culture.
Every small decision comes upward.
An employee brings frequent small questions they could answer themselves. Your day is interrupted. Their judgment is not developing. You’ve answered so often that asking you is now the default.
· ·
Dependency grows every time you answer questions they should own.
Better move: Require a recommendation before you decide. Define their decision lane.
What is your first move?
Open:
“I want you making more of these calls without me.”
Ask:
“Before you bring me a question like this, I want your recommendation and your reasoning.”
Boundary:
“If it’s inside your lane and reversible, decide and tell me later.”
The next three times they ask something they should own, respond with: “What do you recommend?”
Principle 3: Every answer you give can steal a rep of judgment.
Principle 8: Asking for their recommendation builds the muscle.
Attention is elsewhere during work time.
An employee is frequently on their phone during work. Output is slipping. Others notice. You’ve looked the other way because you didn’t want a small issue to become a big conflict.
· ·
Phone use and distraction become the norm when leaders look the other way.
Better move: Describe the pattern. State the visible standard. Follow up on behavior.
What is your first move?
Open:
“I need to talk about phone use during work. I’ve seen it repeatedly during the last week.”
Standard:
“During work time, phones stay put away except for approved breaks or emergencies.”
Ask:
“What’s your plan to meet that standard starting tomorrow?”
Have the conversation this week. State the standard once, clearly, and follow up on behavior — not intentions.
Principle 7: “Be more focused” is not a standard. Visible phone rules are.
Principle 12: What you tolerate is what grows.
Pushes back on change without a better plan.
You introduce a process improvement. One employee complains, delays adoption, and recruits others to resistance. The old way was comfortable. The new way is better for the team.
· ·
Change fails when resistance is negotiated indefinitely to keep peace.
Better move: Acknowledge discomfort. Set a non-negotiable adoption date. Support skill, not refusal.
What is your first move?
Open:
“I know the new process is uncomfortable. We’re still adopting it.”
Standard:
“Starting Monday, this is how the work gets done. I need you on board.”
Ask:
“What support do you need to be fully using it by Monday?”
Pick one resisted process. Set a clear adoption date and have the direct conversation.
Principle 2: Change requires discomfort. Expect it.
Principle 4: Resistance often protects an old belief that the old way was safer.
Personal issues dominate the workday.
An employee regularly brings personal conflict into the workplace — long emotional conversations, venting to coworkers, difficulty focusing. Work and morale are affected.
· ·
Personal drama takes over the workplace when there is compassion without a boundary.
Better move: Care, then set the line: work time is for work. Point to proper support channels.
What is your first move?
Open:
“I care that you’re going through a hard time. I also need work time to stay focused on work.”
Boundary:
“During shifts, personal issues can’t dominate the floor or other people’s attention.”
Support:
“If you need resources or time off to handle this, let’s talk about that separately.”
Have a private conversation that separates support from workplace impact.
Principle 12: Drama grows when it gets an audience.
Principle 17: Compassion does not require unlimited workplace processing.
Money request without matching results.
An employee asks for a raise. Their performance is average or below. They emphasize tenure, personal expenses, or what others earn. You need to respond without damaging the relationship or the standard.
· ·
Pay conversations go sideways when performance standards were never visible — or when you stall to avoid discomfort.
Better move: Tie compensation to clear results. Show the gap. Make the path visible.
What is your first move?
Open:
“I want to talk about pay and responsibility together.”
Standard:
“Pay follows responsibility. I’m already paying for the role as it is. If we expand what you own, we can align pay to that.”
Gap:
“Right now the gap is in consistency and ownership. What additional responsibilities are you ready to own? Let’s define those clearly — then we can talk about pay.”
Respond with a clear performance-based framework, not a vague maybe.
Principle 14: People can’t hit a pay standard they can’t see.
Principle 20: If you say raises follow performance, your decisions must match.
Crowds out quieter voices.
In meetings, one employee interrupts, talks over others, and fills the airtime. Quieter people stop contributing. Decisions get worse because you only hear one voice.
· ·
Dominant voices keep the floor when leaders never reset norms or address the pattern.
Better move: Reset the norm in the room. Coach the dominant person privately.
What is your first move?
In the meeting:
“I want to hear from people who haven’t spoken yet.”
Privately:
“You’ve been taking a lot of the airtime and cutting others off. That needs to change.”
Ask:
“How will you make space for others in the next meeting?”
Address the pattern before the next team meeting.
Principle 12: The voice you always reward is the voice you get more of.
Principle 5: Name the behavior privately and clearly.
Hard work gets steered around.
An employee consistently finds ways around difficult customers, hard conversations, or unpleasant tasks. Easier work gets done. Hard work piles up on others.
· ·
Avoidance becomes their role when hard work is quietly given to more reliable people.
Better move: Name the pattern. Assign one difficult task with a clear finish line.
What is your first move?
Open:
“I’ve noticed the hard customer calls and tough tasks are getting steered away from you.”
Assign:
“This account is yours to handle through resolution. Here’s what done looks like.”
Ask:
“What’s your plan for the first conversation?”
Assign one avoided task this week with a visible definition of done.
Principle 2: Avoidance continues until the cost of avoiding exceeds the cost of doing.
Principle 18: Sometimes avoidance is fear — still require the action.
Uneven treatment damages trust.
Whether it’s you or a team lead, some people get better information, easier assignments, or more leeway. Others notice. Trust is dropping.
· ·
Trust dies when access, leeway, and accountability are uneven.
Better move: Audit assignments and exceptions. Equalize standards. Correct one double standard now.
What is your first move?
Open:
“I’ve heard concern about uneven treatment. I’m looking at how assignments and flexibility are distributed.”
Standard:
“Same standards, same access to information, same accountability — regardless of who is involved.”
Action:
“If I’ve created a double standard, I’m correcting it.”
Review the last two weeks of assignments and exceptions. Correct one visible double standard.
Principle 20: Trust dies when stated values and actual treatment diverge.
Principle 1: Your distribution of opportunity is influence.
Silent resistance still influences the room.
During meetings or coaching, an employee eye-rolls, sighs, or shows contempt nonverbally. The message is clear to everyone. No words have been addressed yet.
· ·
Silent disrespect becomes culture when eye-rolling and contempt go unnamed.
Better move: Name the behavior calmly and privately. Require professional presence.
What is your first move?
Open:
“I want to address something from the meeting. The eye-rolling and sighing when we discussed the change.”
Impact:
“That communicates disrespect to the room, whether you intended it or not.”
Standard:
“If you disagree, say it with words, professionally. Nonverbal contempt is not acceptable.”
Address the next instance within 24 hours, privately and specifically.
Principle 5: Unnamed disrespect becomes culture.
Principle 6: Your calm is part of the confrontation.
Knowledge is hoarded; the team stays fragile.
A capable employee refuses to train others or help bring teammates up to speed. They say they’re too busy, or “I figured it out myself.” The team remains dependent on one person.
· ·
Knowledge hoarding continues when being indispensable is rewarded and training is optional.
Better move: Make developing others a measured expectation with a date and definition of done.
What is your first move?
Open:
“I need you training others on this process, not carrying it alone.”
Describe:
“Done looks like: two teammates can complete the process without you by the 30th.”
Ask:
“What’s your plan to get them there?”
Set one concrete cross-training deliverable this month with a date and a definition of done.
Principle 3: Hoarding work can be a way of keeping status — still require the transfer.
Principle 11: If being indispensable is rewarded, people stay indispensable.
Anger or emotion that damages the environment.
An employee loses their temper — raised voice, harsh words, or visible rage. The team is shaken. You need to address it without either minimizing it or matching the emotion.
· ·
Outbursts continue when leaders minimize (“that’s just how they are”) or respond in kind.
Better move: Same-day private conversation. Name behavior and impact. Outbursts are not negotiable.
What is your first move?
Open:
“We need to talk about what happened in the meeting. Raising your voice and slamming the folder was not acceptable.”
Impact:
“It damaged trust and made it harder for people to work with you.”
Standard:
“Disagreement is allowed. Outbursts are not. If you’re flooded, take a break and return when you can stay in control.”
If an outburst occurs, address it before the end of the day.
Principle 13: Your calm response is the first repair.
Principle 6: Self-control is required of everyone, including high performers.
Commitments slip without early escalation.
Deadlines are missed. You’re informed late or after the fact. Rework and scramble follow. The employee always has a reason. Reliability is now the issue.
· ·
Deadline slips become normal when late notice is accepted and “why” replaces planning.
Better move: Define on-time with early escalation. Ask for the future plan, not the story.
What is your first move?
Open:
“The last three deadlines slipped without early warning. What are you going to do to make sure this doesn’t happen in the future?”
Standard:
“On time means delivered by the agreed time, or you raise the risk as soon as you see it — not the day it’s due.”
Ask:
“What’s your plan to make the next commitment reliable?”
Pick one recurring deadline pattern and reset the standard this week.
Principle 9: Why it was late is less useful than how the next one will be on time.
Principle 21: Reliability is finishing, not intending.
Words and actions don’t match.
An employee makes commitments and doesn’t follow through. Apologies are frequent. Trust is thin. People plan around the unreliability instead of confronting it.
·
Trust thins when words and actions diverge and nobody inspects the gap.
Better move: Name the pattern. Shrink to verifiable commitments. Inspect follow-through.
What is your first move?
Open:
“There’s a gap between what you say you’ll do and what gets done. That gap is now a trust issue.”
Standard:
“If you commit, I expect completion or early escalation — not silence.”
Shrink:
“Let’s start with one commitment this week that you will complete fully.”
Identify one person with a say/do gap. Reset with one small, inspected commitment this week.
Principle 20: Trust is built by matched words and actions.
Principle 11: If broken commitments have no cost, they continue.
Incomplete work becomes the pattern.
Projects, tasks, and conversations are started with energy and then abandoned. The team is littered with half-finished work. Frustration is high. New starts still look exciting.
·
Unfinished work multiplies when starts are praised and completions are invisible.
Better move: Freeze new starts. Define done. Finish before launching more.
What is your first move?
Open:
“We have too many things started and not enough finished.”
Rule:
“No new projects until these three are complete.”
Define:
“Complete means X is delivered and handed off — not ‘mostly done.’”
List open work with one person. Choose two items to finish before anything new starts.
Principle 21: Finishing is the standard; starting is easy.
Principle 11: If starts get praise and finishes get silence, you get more starts.
Activity without results; weak example.
Someone fills the day with motion — meetings, messages, visible busyness — but key results don’t move. Others copy the theater. Productive work is harder to see than activity.
·
Activity theater continues when busyness is praised and outcomes are undefined.
Better move: Shift the scoreboard to visible results. Model productive work yourself.
What is your first move?
Open:
“I want to focus on outcomes, not activity.”
Scoreboard:
“By Friday, success looks like these three results.”
Ask:
“What’s the plan that produces those results — not just a full calendar?”
Redefine one role or one week around three visible outcomes instead of activity.
Principle 22: Leaders teach what productive work looks like by what they do and what they praise.
Principle 7: If the outcome isn’t described, busyness will fill the gap.
Thinking and habits that quietly undercut the results you want—and what to do instead.
Interviewing, listening, direction tools, and defining the root of the problem—so people can say what’s real and what they’ll do next.
Many HR teams require the same core questions for every candidate to reduce bias and discrimination risk. That is good practice — not a limitation on your judgment.
The real power is in the follow-up questions. The scripted list gets a comparable baseline. Follow-ups (asked fairly, about what the candidate just said) reveal ownership, honesty, learning, and whether they can describe behavior — not slogans.
Choose a core question. You’ll see what you really want to learn, a sample weak answer, and space to craft a fair follow-up.
Follow-ups should explore their story — not introduce new protected-class topics or a different test for one candidate than another.
Reflection is not agreement. Hear them before you fix, defend, or advise. Understanding shows up when you can say their point accurately.
Then: “Did I get that right?” — only after that, problem-solve.
As a leader, you can walk someone through these questions out loud. The goal is their definition and their next step.
Vision is direction. Goals are outcomes by when. Standards are what good looks like every day. Fill this in plain words—then get your people to say it back.
Check: Ask two people to say the goal in their words and name one thing they do that supports it.
This is a guided sequence of questions so they (or you) talk until the real problem is stated in plain words—not the surface problem you began with. Don’t stop at the first answer. Keep asking what’s underneath until you reach a root you can fix—and have them say it out loud.
HR may require the same core questions for every candidate. Your job is still to understand the person — through disciplined follow-ups on what they said.
You finished the standard questions. Two candidates sound polished. One blames every past employer. One gives vague “team player” answers with no examples. You need signal, not theater.
Describe what it looks like · Ask rather than tell · Say it to understand it · Hear them before you decide
“You mentioned X — what did you do next?” · “What part of that outcome was yours?” · “If you faced it again, what would you change?”
“Nobody good is out there” can hide a leadership problem you still own: unclear standards, weak interviews, or a workplace that doesn’t attract capable people.
You’re short-staffed or stuck with mediocre candidates. It’s easy to blame HR, the market, or pay bands. Often the role isn’t defined in behaviors, interviews reward polish over ownership, or your team’s reputation (standards, fairness, growth) doesn’t draw the people you say you want.
You hire the standard you can describe · Describe what it looks like · Pay follows responsibility · People stay or leave because of what you reward, ignore, and tolerate
“I’m not hiring hope. Here is what good looks like in this role — and here is how I’ll test for it in the interview.”
The interview selected for polish. The job required ownership. Follow-ups are where that gap shows — if you ask them.
Résumé and first answers looked strong. Within weeks: missed handoffs, excuses, low initiative. You may have been charmed by confidence and never tested for responsibility.
You hire the standard you can describe · Ask rather than tell · Say it to understand it · Your system teaches more than your speeches
“You said the project succeeded — what part of that outcome was yours?” · “When it went off track, what did you do next?”
That’s rarely only a pay problem. It’s often a system that rewards comfort and punishes high standards.
Your best people take the load, clean up messes, and get more work. Low performers are protected by avoidance, excuses, or “they’ve been here forever.” Capable people notice — and leave.
Your system teaches more than your speeches · People stay or leave because of what you reward, ignore, and tolerate · Pay follows responsibility · Confronting behavior creates awareness
To a strong performer: “You’ve been carrying more than your share. Here’s the standard I’m restoring on the team, and here’s how I want to use your strength going forward.”
To a weak performer: name the pattern, the impact, and the plan — not the excuse.
You didn’t just have a staffing gap — you trained your best people that their reward for excellence is more weight.
Whenever something breaks, you hand it to the reliable ones. The squeaky wheel gets attention; the steady ones get load. Over time they disengage or leave — and you’re back to “we can’t find good people.”
Your system teaches more than your speeches · People stay or leave because of what you reward, ignore, and tolerate · Don’t take responsibility from others · Pay follows responsibility
“I’ve been leaning on you because you’re reliable. That’s not fair long-term. Here’s how I’m changing the standard on the team — and here’s the responsibility I want you to own by choice, not by default.”
Early weeks taught them what the real standard is. If you didn’t enforce it, they learned correctly.
They started with energy. After the honeymoon: minimum effort, excuses, waiting to be told. You may have delayed feedback to “let them settle in” — and the system taught that average is fine.
You hire the standard you can describe · Your system teaches more than your speeches · Describe what it looks like · Confronting behavior creates awareness
“In the first month you did X. Lately I’m seeing Y — dates and examples. That has to match the standard we hired you for. What’s your plan starting tomorrow?”
Activity is not the same as direction. Hard work without a clear aim still drifts.
Everyone is occupied. Projects multiply. When you ask what success looks like this quarter, answers scatter—or people describe tasks, not outcomes.
Vision is direction, not decoration · Goals must be observable and dated · Standards make goals reachable · They align to what they can say
“We’re working hard. I’m not seeing us move toward __. Starting today, that goal is the filter: if it doesn’t serve __, we question it.”
People believe what you reward and allow—not what you laminated.
The vision talks about quality, care, or excellence. Daily life rewards speed, silence, or firefighting. Capable people stop taking the vision seriously.
Your system reveals the real priorities · Your system teaches more than your speeches · Standards make goals reachable
“We say __. What we actually reward is __. I’m changing that starting with __.”
A target without “how we work” is pressure without a path.
You’ve set a number or deadline. People scramble. Quality slips, blame rises, and nobody agreed what good daily work looks like.
Standards make goals reachable · Describe what it looks like · People cannot meet standards they cannot see
“The goal is __. To hit it, we will always __. We will never __. Here’s what that looks like on a normal day.”
When everything is priority, you’ve chosen none.
The list is long. People cherry-pick easy wins or freeze. You’re frustrated they “don’t focus,” but the system asked them to focus on everything.
Goals must be observable and dated · Your system reveals the real priorities · Vision is direction, not decoration
“These three matter this quarter. The others wait. If it isn’t on this list, it isn’t the main aim.”
You informed them. You didn’t get them to own it in their own words.
You announced the goal in a meeting or email. A week later, people describe different targets—or only their task list.
They align to what they can say · Say it to understand it · Ask rather than tell
“In your words, what’s our main aim for the next 90 days—and what’s one thing you do that supports it?”
Villains feel satisfying. Standards and system fixes produce change.
The date passed; the target wasn’t met. The room wants a name to blame. Without looking at standards, load, and clarity, you’ll miss again.
Standards make goals reachable · Your system reveals the real priorities · Confronting behavior creates awareness · Responsibility is how people grow
“We missed __. I’m not looking for a villain. I want: what standard slipped, what we’ll do differently this week, and how we’ll know.”
Waiting for a better moment is often how standards die.
You notice the problem. You feel the irritation. You hint, send a group message, or wait. The behavior continues—and the team watches what you allow.
Confronting behavior is easier than you think · Discomfort drives behavior change · Your silence is permission · Don’t ask for excuses
“I want to talk about something specific. This week you were late Monday, Wednesday, and Friday. I’m not asking why. What’s your plan to be on time starting tomorrow?”
If you can’t hear pushback, you teach people to stop telling you the truth.
An employee, peer, or boss questions a decision. Your body goes to defend. You argue points, explain intent, or shut down—before you’ve understood them.
Hear them before you fix or confront · People’s reactions are information · Self-control is your superpower · Say it to understand it
“You’re frustrated because this change hit your workload without warning. Did I get that right?” Then: “Here’s what I can do—and here’s what stays.”
Doing it yourself is faster today and more expensive every month after.
Work isn’t right or fast enough. You pull it back. They learn to wait. You get busier. Ownership never transfers.
Responsibility is how people grow · Don’t take it from them · Ask rather than tell · Describe what it looks like
“Show me what you’ve done so far. What do you think the next step is? I’ll check quality when it’s done—I’m not taking it back.”
Disapproval without a picture of “good” creates fear, not improvement.
You know it’s not right. You say so. They still don’t know what right looks like—so they guess, freeze, or get defensive.
Describe what it looks like · People cannot meet standards they cannot see · Ask rather than tell
“Done looks like __. What I saw was __. What’s your plan to match the standard next time?”
Avoiding conflict with one person creates conflict with the whole standard.
You know they’re below the line. You soft-pedal, make excuses for them, or hope a peer will carry them. High performers notice.
Behavior that is rewarded continues · Your system teaches more than your speeches · People stay or leave because of what you reward, ignore, and tolerate
“This is the third miss on __. The standard is __. I need a plan today. If it continues, we move to __.”
Loud problems get attention; steady excellence gets more work.
Whoever complains loudest owns your calendar. Reliable people clean up and burn out. You’re training volume, not performance.
What you give attention to grows · Your system reveals the real priorities · People stay or leave because of what you reward, ignore, and tolerate
“I can give this 15 minutes now. What’s the problem, what you’ve tried, and what you need from me—one clear ask.”
They’re not your peer support group. Venting downward damages trust and authority.
You’re frustrated with upper management, a peer, or another employee. You unload on someone who reports to you. It feels like relief. It costs safety.
How you respond reveals who you are as a leader · Self-control is your superpower · Do not make it worse
To yourself: “This goes to a peer or my coach—not my team.” If repair: “I spoke out of line about __. That’s on me. Here’s what we need to focus on.”
Uneven rules teach people to manage you—not the work.
Favorites get slack. Pushback gets a pass. Quiet people get the letter of the law. Trust erodes.
Your system teaches more than your speeches · Behavior that is rewarded continues · Describe what it looks like
“The standard is the same for everyone in this role. Here’s what it looks like—and here’s how we’ll handle misses.”
Unspoken expectations create conflict—and false confidence that “they should have known.”
You’re disappointed. They feel blindsided. Nobody wrote down what “good” looked like.
Unspoken expectations create conflict · Describe what it looks like · People cannot meet standards they cannot see · You hire the standard you can describe
“I don’t think I made clear what done looks like. Here it is: __. Say it back so we’re aligned. Going forward, this is the standard.”
Rescue feels kind. It often steals the lesson and guarantees a repeat.
They miss, drop, or avoid. You cover, complete, or soften the landing every time. They don’t change. You get tired.
Responsibility is how people grow · Don’t take it from them · Behavior that is rewarded continues
“I can help you think it through. I’m not going to take it over. What’s your plan to finish by __?”
Important calls made alone often create rework, resistance, and the story that leadership doesn’t respect the people doing the job.
You lock in a change that affects schedules, process, or customers. The people closest to the work find out when it’s announced. You’re surprised they push back or that details you missed blow up later.
Humble leaders ask before they decide · Ask rather than tell · Hear them before you fix · Observe first
“I’m leaning toward __. You’re closer to this than I am—what am I missing? What would go wrong if we did it this way?”
After deciding: “I’ve heard you. Here’s what I’m deciding and why—including what I took from your input.”
That’s not humility. That’s confirmation shopping.
You “got input”—from people who already share your view, or who won’t risk disagreeing. Dissenters were never in the room. You feel validated; the decision is still half-blind.
Humble leaders ask before they decide · People’s reactions are information · Ask rather than tell
“I don’t need cheerleaders right now—I need what I’m missing. Where does this break?”
Asking and discarding is worse than not asking. People learn their voice is decoration.
You held meetings, took notes, then announced the plan you already had with no trace of their input. Trust drops. Next time they won’t speak up.
Humble leaders ask before they decide · Do what you say · Your system teaches more than your speeches
“You raised __. I considered it. I’m still going with __ because __. Here’s how we’ll watch for the risk you named.”
Humility seeks information. Leadership still decides. Endless polling is avoidance.
Every decision becomes a group negotiation. Nothing lands. People are tired of meetings. You’re trying not to look autocratic—and you’ve stopped leading.
Humble leaders ask before they decide · Discomfort drives behavior change · Finish what you start
“I want your input by __. I’ll decide after that. We’re not voting—we’re making sure I see what you see.”
Relief is not a hiring standard. A weak fit so you don’t have to do the work is a long-term problem on a short fuse.
You’re short-handed. You’re tired of covering. Someone available looks “good enough.” You know they aren’t the standard—but the bind feels worse than the risk. Often the bind exists because action on the last problem was late.
Don’t trade a short-term fix for a long-term problem · You hire the standard you can describe · Consequences lag. So does progress.
“I’m not hiring to escape the work. I’m hiring to the standard—even if that means covering longer.”
Delay shrinks options. Then every decision feels like you “have no choice.”
The performance problem, vacancy, or conflict was visible months ago. You waited. Now customers, your boss, or the team are in pain—and you’re forced into faster, riskier calls.
Don’t trade a short-term fix for a long-term problem · Discomfort drives behavior change · Confronting behavior is easier than you think
“We waited. That’s on us. We still don’t lower the bar to get out of the bind.”
Progress lags. If you abandon the right move before it can work, you never build momentum.
You raised a standard, fixed a process, or stopped rescuing. For a while it feels worse or quieter—not “fixed.” You blink and go back to the old pattern.
Consequences lag. So does progress. · Finish what you start · Your system teaches more than your speeches
“The change is right. We give it time to show—and we don’t quit at the first quiet week.”
When you wait too long, action can make things messier before they get better. That’s lag—not proof you should reverse.
You finally confront, replace, or restructure. Drama rises. Performance dips short-term. You panic and soften the standard.
Consequences lag. So does progress. · Don’t trade a short-term fix for a long-term problem · Do No Harm
“This may get messier before it gets better. We’re still holding the standard.”
If you can’t say what this is really about in one sentence, use Tools → Defining the root of the problem first. Describe a real management situation. Randy’s coaching approach responds using True Leadership Skills principles and gives you language you can use today. Follow-ups stay in context for this conversation.
Privacy: Questions you submit may be reviewed to improve this coaching service. Do not include unnecessary personal identifiers.
Saved on this device only — last 3 conversations.
Free preview: 4 principles, 3 challenges, 4 blind spots, and 3 Ask Randy questions.
Subscribe for the full library and ongoing Ask Randy coaching.
1. Sign in with email (magic link — no password)
2. Subscribe
Legacy unlock code (one-time purchases)