Respecting Team Members

Introduction

You have learned to build rapport, communicate with empathy, give autonomy, and recognize contributions. Each of these practices contributes to creating a team where engagement can flourish. But beneath all of them lies an even more fundamental practice, one that determines whether all the others actually work or fall flat: respect. How you respect your team members shapes everything else. Without respect, rapport feels hollow. Without respect, empathy feels performative. Without respect, autonomy feels conditional. Without respect, recognition feels manipulative. Respect is the foundation upon which every other engagement practice rests.

Yet respect is one of the most misunderstood concepts in leadership. Many leaders believe they respect their team members because they are professional, polite, and reasonable. They are surprised when team members report feeling disrespected. The gap between intending to respect and actually communicating respect is enormous, and it is often invisible to the leader. What feels like respect from one side of the relationship can feel like the opposite from the other.

Respect is also frequently confused with other concepts: politeness, formality, deference, friendliness, or simply not being mean. None of these is respect. A leader can be unfailingly polite while systematically disrespecting team members. A leader can be formal and professional while undermining people's dignity. A leader can be friendly while treating team members as resources rather than as humans deserving of full respect. Genuine respect is something deeper and more specific than any of these surface behaviors.

The stakes of respect are enormous. When team members feel respected, they bring their full selves to work, take risks, contribute ideas, persist through challenges, and develop genuine loyalty. When team members feel disrespected, they hold back, protect themselves, perform only what is required, and eventually leave for environments where they will be treated as the humans they are. The financial cost of lost engagement and turnover due to disrespect is enormous. The human cost, in damaged confidence, eroded wellbeing, and lost potential, is incalculable.

Many leaders engage in disrespectful behaviors without realizing it. They interrupt team members. They check phones during conversations. They take credit for others' work. They make decisions about people without consulting them. They speak about team members behind their backs in ways they wouldn't to their faces. They show different levels of respect to people based on hierarchy or visibility. They dismiss ideas without genuine consideration. They treat their team members' time as less valuable than their own. None of these behaviors is announced as disrespect; they are simply patterns of behavior that accumulate into a felt experience of being valued less than one deserves.

This article explores what respect truly means, the difference between respect and politeness, the three dimensions of respect (respect for person, respect for work, respect for autonomy), the specific behaviors that communicate respect, the patterns that communicate disrespect even when unintended, how respect interacts with hierarchy and power dynamics, how to handle situations where you genuinely disagree or must give difficult feedback while maintaining respect, the challenge of treating everyone with equal respect regardless of their level or role, how cultural backgrounds affect what respect looks like, how to recover when you have communicated disrespect, and the daily practices that build a culture of genuine respect on your team.

The leader who masters respect creates a team where every member feels valued as a human, where dignity is maintained even in difficult conversations, where contributions are honored, where autonomy is real, and where people willingly bring their full capabilities to work because they are treated as worthy of that contribution. This is one of the most powerful leadership practices available, and it costs nothing but discipline and attention. Building this discipline is the work of this section.

Simple Meaning: Respecting Team Members

Respecting team members is the deliberate leadership practice of treating each person on your team as a full human being deserving of dignity, recognition of their value, honoring of their autonomy, and acknowledgment of their unique contributions, in every interaction and every decision that affects them. It is the underlying disposition that shapes how every other leadership behavior actually lands.

Respect is the foundation upon which every other engagement practice either works or fails. When team members feel respected, your rapport-building registers as genuine, your empathy lands as authentic, your autonomy feels real, and your recognition feels meaningful. When team members feel disrespected, even subtly, all of these other practices fall flat because the underlying message is contradicted by the felt experience of not being valued as fully human. Respect is not politeness or formality. It is the recognition that this person, this professional, this human being, deserves to be treated as someone who matters, whose time matters, whose contributions matter, whose perspective matters, and whose dignity is not yours to diminish. For leaders, respecting team members is not an attitude you have but a discipline you practice through dozens of small choices every day: how you listen, how you make decisions, how you handle disagreement, how you allocate your attention, how you talk about people in their absence. The leader who masters respect creates a team where engagement is possible. The leader who fails at respect, no matter how skilled at other practices, cannot create lasting engagement because the foundation is missing.

Respect operates through three essential dimensions that work together:

All three dimensions must be present for genuine respect to be communicated. Respecting the person without respecting their work is patronizing. Respecting the work without respecting the person is transactional. Respecting both without respecting their autonomy is paternalistic. Real respect requires all three working together: treating them as full humans, taking their work seriously, and honoring their capability to think and decide for themselves.

What Respect Is Not

Many leaders believe they respect their team members because they engage in behaviors that look like respect on the surface. Understanding what respect is NOT clarifies what genuine respect requires.

The Test of Real Respect

Here is a simple test for whether your respect is real: would your team members describe you as someone who genuinely respects them, or just as someone who is polite, professional, and reasonable? The first describes real respect. The second describes the surface behaviors that often substitute for respect without delivering it. Real respect is felt as substantively different from politeness, and team members know the difference. If you don't know whether your team members would describe you as genuinely respectful, ask them. Their answer is the truth about whether your respect is real.

The Three Dimensions of Respect

Each dimension of respect can be developed through specific practices. Understanding them in depth allows you to identify where your respect is strong and where it needs work.

Respect for the Person

Respect for the person is the foundational recognition that this human being has inherent dignity that is not contingent on their performance, role, or utility to you. It is treating them as someone who matters because they exist, not because of what they produce.

Respect for the Work

Respect for the work is the recognition that what team members do has substance, value, and craft that deserves serious engagement. It is treating their work as worthy of your real attention rather than as mere output to be consumed.

Respect for Autonomy and Judgment

Respect for autonomy and judgment is treating team members as capable adults who can think for themselves, make decisions, and exercise their own judgment. It is honoring their agency rather than treating them as incapable of choosing for themselves.

The Behaviors That Communicate Respect

Respect is communicated through specific behaviors practiced consistently. These behaviors can be learned and developed.

The Patterns That Communicate Disrespect

Many leaders engage in patterns that communicate disrespect without realizing it. These patterns are often unintentional but profoundly damaging.

Respect and Power Dynamics

Respect interacts with power dynamics in important ways. As a leader, you have positional power that affects how respect lands. Understanding these dynamics is essential for genuine respect.

The Power Asymmetry Reality

The power asymmetry between leader and team member means that respect requires more from the leader. You can damage someone with a small comment that they couldn't damage you with. You can disrespect them in ways they cannot disrespect you back. Your behavior has more weight than equivalent behavior from a peer. This means your standards for respectful behavior must be higher, not lower, than you would apply to peer relationships. The discipline of respect is partly about being conscious of your power and how it amplifies your behavior.

Respect in Difficult Conversations

Some leaders avoid difficult conversations thinking it's respectful. Others have difficult conversations in ways that violate respect. The skill is having difficult conversations that maintain or even deepen respect.

The Core Principle

The core principle of respectful difficult conversations is that the hardness of the content doesn't justify violating respect. You can deliver any message, including the hardest possible ones, while maintaining full respect for the recipient. The discipline is in separating the content from the delivery: the content can be hard while the delivery preserves dignity. Leaders who confuse "I had to be tough" with "I had to be disrespectful" haven't yet developed the skill of difficult conversation with maintained respect.

Treating Everyone with Equal Respect

One of the hardest tests of respect is treating everyone with equal respect regardless of their level, role, or visibility. Many leaders show more respect to senior people, more visible people, or people they personally like. Genuine respect is given equally to all team members.

The Equal Respect Discipline

Equal respect requires deliberate attention because the natural tendency is to give more to people who give more visibility back. Track your attention. Notice who gets more time, more substantive engagement, more advocacy, more warmth. If the same people are consistently getting more, that's a pattern that needs addressing. Equal respect means equal treatment in essence, even when specific forms vary based on individual preferences and contexts.

Cultural Dimensions of Respect

What respect looks like varies across cultures. What feels respectful in one cultural context may feel disrespectful in another. Leaders managing diverse teams need to be aware of these differences.

The Universal Foundation

While specific expressions of respect vary culturally, the foundation is universal: every person deserves to be treated with dignity, to have their work taken seriously, and to have their autonomy honored. The cultural variations are in how these are expressed, not in whether they should be. Leaders who navigate cultural differences well honor the universal foundation while adapting expressions to what works for each team member.

Recovering from Disrespect

All leaders sometimes fail at respect. You interrupt someone you didn't mean to interrupt. You make a decision without consulting someone you should have. You speak about someone in their absence in ways you regret. You react in stress in ways that disrespect. How you recover matters.

The Hidden Opportunity

Counter-intuitively, well-handled recovery from disrespect can actually deepen respect rather than damage it. When you acknowledge a failure honestly, take ownership, apologize genuinely, and change behavior, you demonstrate exactly the kind of accountability that earns deep respect. The recovery becomes evidence of who you really are: someone who treats people with respect, including when that means acknowledging you failed to do so. This is one of the most powerful forms of respect-building available.

Daily Practices of Respectful Leadership

Respect becomes a leadership capability through daily practices. Specific practices build the disposition over time.

Daily Practices

• Be punctual and present: Show up on time. Be fully present when with team members. Devices away.
• Listen without interrupting: Let people finish their thoughts. Practice the discipline of silence and attention.
• Engage substantively: When team members bring you something, engage with the substance, not just the surface.
• Credit them appropriately: When their work is discussed, credit them. Don't say "we" when it was them.
• Watch your body language: Be aware of dismissive non-verbal communication. Adjust deliberately.
• Honor commitments to them: Don't reschedule lightly. Show up when you said you would.

Weekly Practices

• Audit your respect distribution: Are you treating all team members with equal respect? Or are some getting more attention, time, or substantive engagement than others?
• Review difficult conversations: Did you have any difficult conversations this week? Did you maintain respect through them?
• Check for repair needs: Was there any moment when you may have communicated disrespect? Does anything need acknowledgment or repair?
• Reflect on your listening: Did you listen well this week? Did you let people finish? Were you present?
• Substantive engagement with each team member: Did you spend real time with each team member's work and thinking this week?

Monthly Practices

• Self-assessment: Honestly evaluate your respect patterns. Where are you strong? Where do you fall short?
• Solicit feedback: Ask team members about your respect. Create safety for honesty.
• Watch for patterns: Are there team members consistently getting less respect? What patterns might explain that?
• Calibration check: Are you treating team members consistently across days, regardless of your state, pressures, or moods?
• Cultural awareness: Are you adapting respect expression to different cultural backgrounds appropriately?

Ongoing Mindsets

• Respect is a foundation, not a feature: It underlies everything else you do as a leader.
• Respect is shown through behavior, not declared: What you do counts more than what you say.
• Power asymmetry requires higher standards: Your authority means you must be more careful, not less.
• Equal respect for all: Every team member deserves the same fundamental respect regardless of level, role, or visibility.
• Hard conversations don't require disrespect: You can deliver any message while maintaining dignity.
• Recovery deepens trust: Acknowledging and repairing failures of respect builds more trust than never failing would.

Respect in IT and Agile Teams

Respect has specific applications in IT and Agile environments.

• In Code Reviews: Review code without diminishing the author. Critique the work, not the person. Engage substantively with their thinking.
• In Architecture Discussions: Take seriously the thinking of engineers at all levels. Junior engineers' ideas deserve real engagement, not dismissal.
• In Sprint Planning: Honor engineer estimates. Don't pressure them to commit to what they say isn't realistic. Trust their judgment on feasibility.
• In Daily Standups: Be present. Engage with what team members report. Don't multitask or check phones during their updates.
• In Sprint Retrospectives: Hear all feedback, including criticism of yourself and your leadership. Don't get defensive. Treat team feedback as legitimate.
• In Production Incidents: Maintain respect even under pressure. Don't blame in the moment. Focus on resolution. Conduct blameless post-mortems.
• In Technical Disagreements: Engage with the substance. Don't pull rank to win arguments. Let the best thinking win, not the most senior position.
• In Stakeholder Communication: Defend team work. Don't throw engineers under the bus to stakeholders. Represent their work accurately.
• In Career Conversations: Take their aspirations seriously. Don't impose your idea of their career on them. Support what they choose.
• In Performance Discussions: Critique behavior, not character. Frame as growth. Maintain dignity even in difficult feedback.

Practical Workplace Scenario

Scenario

A team lead named Anil managed a team of eight engineers building a customer service platform. By his own assessment, he was a respectful leader. He was polite to his team. He was professional. He was reasonable. He didn't think of himself as someone who disrespected people.

Then a quiet engineer, Sneha, asked for a private conversation. What she said surprised him: "Anil, I've been on this team for eighteen months. I want to give you feedback that's hard. I don't feel particularly respected here. I'm not saying you're rude or mean. But there are patterns that add up to me feeling that you don't really see or value me. I want to share specifics, if you're open to hearing them."

The Specifics

What Sneha shared was hard to hear:

• "You interrupt me in meetings frequently. I notice you do this less with the louder engineers. I've stopped trying to make significant points because I usually get cut off."
• "You check your phone during our one-on-ones. Sometimes you respond to messages while I'm talking. It tells me that whatever you're looking at is more important than what I'm saying."
• "You've made decisions about my work without consulting me three times in the past six months. Once it was about my project assignment, once about my role, once about my technical area. Each time, you informed me of the decision after it was made. I would have liked to be consulted."
• "In team meetings, you give substantive engagement to the more visible engineers' ideas. When I suggest things, your response is usually a quick 'we could try that' without real engagement. I've stopped suggesting ideas because the dismissal is automatic."
• "You don't credit me for work I've done. Recently the migration I led was discussed in a stakeholder meeting, and you said 'we built this' without naming me. The credit went to the team generally rather than to the person who actually did the work."
• "I notice you give more attention to the engineers you click with personally. The ones you go to lunch with get more substantive engagement. I haven't been included in those informal moments, and I think that affects how you engage with me professionally too."
• "Two months ago, you said something dismissive about my work in front of a stakeholder. You didn't mean it badly, I think, but I felt diminished. I haven't fully recovered from that moment."

Anil's Initial Reaction

Anil's first reaction was defensiveness. He wanted to explain that he didn't mean any of these things, that he treated everyone the same, that the specific incidents she mentioned had context she might not know. But he caught himself. The defensiveness itself was disrespect. She had given him a gift of honest feedback, and his job was to listen, not to defend.

He said: "Sneha, thank you for sharing this. It's hard to hear, and I appreciate that it was probably harder to say. Let me ask: can you tell me more about each of these? I want to make sure I really understand what you experienced."

The Deeper Conversation

Over the next hour, Sneha shared specifics. What Anil heard challenged his self-image. He had thought of himself as respectful, but he had been engaging in patterns of disrespect without realizing it. His warmth toward some team members meant relative coldness toward others. His engagement with louder engineers meant relative disengagement from quieter ones. His tendency to check his phone meant divided attention that team members felt. His habit of making decisions efficiently meant excluding people from decisions that affected them.

The Honest Investigation

Anil decided to ask other team members for similar feedback. He framed it carefully: "Sneha gave me feedback that I haven't been showing the respect I want to be showing. I'd like to hear from you about how my behavior actually lands. Not for me to defend; just for me to understand."

What he heard was consistent and difficult:

• Multiple team members had noticed the differential treatment
• The phone-checking was a widespread complaint
• Several engineers had felt their ideas dismissed without engagement
• The pattern of making decisions without consultation was familiar to others
• Several engineers had felt the credit issue: their work being absorbed into "team accomplishment" without their names

Anil realized that his self-perception had been wrong. He had thought of himself as respectful because he was polite. But politeness wasn't respect. And his actual behaviors had been communicating disrespect to multiple team members for months or years.

The Plan

Anil committed to changes:

• Listening discipline: No more interrupting. Let people finish, even when he had something to say.
• Phone discipline: Phone away during one-on-ones and team meetings. Full presence.
• Consultation discipline: Talk with team members before making decisions that affected them. No more unilateral decisions about their work or roles.
• Engagement equity: Substantive engagement with everyone's ideas, not just the visible engineers'. Track this consciously.
• Credit discipline: Name specifically who did what. No more absorbing individual work into "team accomplishment."
• Attention equity: Distribute his time and engagement equally across the team, not concentrated on people he personally clicked with.
• Apologies where warranted: Specifically acknowledge the moment when he had diminished Sneha in front of a stakeholder. Acknowledge similar moments with others.

The Process

The first weeks were uncomfortable. Anil had to fight strong habits. Putting his phone away during one-on-ones meant resisting constant urges to check. Letting people finish meant forcing himself to hold back even when he had ready responses. Consulting before deciding meant slower processes than his natural efficiency wanted.

But team members noticed. Sneha said: "I notice you're listening differently in our one-on-ones. You're really there. It means a lot." Another engineer commented: "I appreciate that you've been engaging more substantively with my ideas in meetings. I'm sharing more now because the engagement feels real." A third said: "I noticed you named me specifically in the stakeholder presentation last week. I haven't been credited like that before."

The Result

Six months later, the team dynamic had visibly shifted. Sneha reported: "I feel respected on this team in a way I didn't before. I'm bringing my full self to work, contributing ideas, taking more risks. The difference is significant." Other team members reported similar shifts. Engagement scores improved. People who had been quiet became more vocal. People who had been disengaged became more invested.

Anil reflected: "I thought I was a respectful leader. I was polite, professional, reasonable. What I learned was that politeness isn't respect, and my actual behaviors had been communicating disrespect for years without my realizing it. The interrupting, the phone-checking, the unilateral decisions, the differential treatment, the failure to credit specifically. None of these were what I intended, but all of them were what people experienced. And what people experience is what counts, not my intentions. The change required me to do uncomfortable things consistently for an extended period. Many habits that felt efficient to me were actually disrespect to my team. Fighting those habits is ongoing. But the reward has been substantial: a team where people feel valued, contribute fully, and are engaged in ways they weren't before. And I'm grateful Sneha was brave enough to give me feedback that almost no one would give their leader. That feedback changed how I lead. I am a fundamentally different leader because of it, and the team is fundamentally different because I am."

Learning

Anil's experience teaches important lessons:

• Leaders systematically underestimate how disrespectful their behavior is, often because they're polite
• Politeness is not respect; respect requires substantive behaviors, not just courteous demeanor
• Small patterns of disrespect accumulate into significant impact over time
• Team members often won't volunteer feedback about disrespect; they protect themselves and you
• When team members do give feedback about respect, it's usually after long suffering and only a fraction of what they've experienced
• Defensiveness in response to feedback about respect is itself disrespect; listening is the first respectful act
• Real change requires changing patterns, not just intentions
• The investment in respect pays back enormously in engagement and team functioning

Respect Reflection Checklist

Self-Reflection Questions

Use these questions to assess your respect practice and identify growth opportunities.

1. If my team members were asked confidentially whether I genuinely respect them, what would they say?
2. Do I confuse politeness with respect? What evidence do I have about whether my respect is substantive?
3. What patterns of mine might be communicating disrespect without my intending it?
4. Am I treating all team members with equal respect, or are some getting more substantive engagement than others?
5. How do I handle disagreement? Do I maintain respect when team members disagree with me?
6. Do I interrupt people? Do I let them finish their thoughts? Whose words do I cut off most often?
7. How present am I in conversations? Devices? Multitasking? Mental wandering?
8. How do I treat people's time? Am I punctual? Do I reschedule lightly?
9. Do I credit team members specifically for their work, or do I absorb their contributions into "we" and "the team"?
10. Am I consulting team members on decisions that affect them, or am I deciding unilaterally?
11. How do I deliver difficult feedback? Do I maintain dignity through hard conversations?
12. Am I the same person whether team members are present or absent?
13. Have I acknowledged and apologized for moments when I communicated disrespect?
14. What is one specific change I will make this week to communicate more respect to my team?

Key Takeaways

• Respect is the foundation upon which every other engagement practice either works or fails. Without genuine respect, rapport feels hollow, empathy feels performative, autonomy feels conditional, and recognition feels manipulative.
• Genuine respect operates through three dimensions: respect for the person (treating them as full humans), respect for the work (engaging substantively with what they do), and respect for autonomy and judgment (trusting their capability to think and decide).
• Respect is NOT politeness, friendliness, the absence of meanness, formality, treating everyone identically, deference to hierarchy, withholding disagreement, tolerating poor behavior, or symbolic recognition.
• Specific behaviors communicate respect: listening without interrupting, being present in conversations, honoring time, speaking consistently about people, including them in decisions, taking ideas seriously, crediting contributions, defending them appropriately, acknowledging mistakes without diminishment, asking opinions substantively, apologizing when wrong, and honoring confidentiality.
• Patterns that communicate disrespect, often unintentionally, include interrupting, checking devices during conversations, making people wait, taking credit, public criticism, dismissing ideas, deciding unilaterally, speaking about people in their absence, comparing unfavorably, inconsistent treatment, dismissive body language, withholding information, and demanding personal information.
• Power asymmetry between leader and team member means that respect requires higher standards from the leader. Small disrespects from leaders land harder than equivalent behavior between peers.
• Difficult conversations can maintain or even deepen respect when handled well. The hardness of content doesn't justify violating respect; you can deliver any message while preserving dignity.
• Equal respect across all team members regardless of level, visibility, or personal connection is one of the hardest tests of leadership respect. Differential treatment based on hierarchy, visibility, or personal chemistry communicates that respect is conditional.
• Cultural backgrounds affect what specific expressions of respect look like. The universal foundation is honoring dignity, work, and autonomy; the expressions vary culturally.
• Recovery from disrespect through acknowledgment, ownership, apology, and changed behavior can actually deepen respect rather than damage it permanently.
• Respect becomes a leadership capability through daily, weekly, and monthly practices: listening discipline, full presence, equitable engagement, audit of patterns, and solicitation of feedback.
• The leader who masters respect creates a team where every member feels valued as a human, where dignity is preserved in all interactions, and where engagement is possible because the foundation is solid.
• Many leaders systematically underestimate how disrespectful their behavior is because they confuse politeness with respect. Real respect requires substantive behaviors, not just courteous demeanor.

Reflection Activity: My Respect Audit

Complete the tables below to honestly assess your respect practice and plan improvements.

Part 1: Respect by Team Member

Part 2: My Respect Patterns Audit

Part 3: My Action Plan

Mini Case Study

A team lead named Suresh managed a team of six engineers building a financial reporting platform. He thought of himself as a fair leader. He didn't have favorites. He didn't play games. He was direct and reasonable. By his self-assessment, he treated everyone respectfully.

But a senior engineer, Maya, who had been on the team for three years, gradually became less engaged. Her work was still good, but her energy was different. She participated less in optional discussions. She didn't volunteer for new initiatives. She seemed to be doing her work but not investing in the team.

Suresh asked her: "Maya, I've noticed you seem less engaged lately. Is there something I should know about?"

Maya was direct: "Yes. I don't feel respected here. And I've been processing whether to tell you or just leave."

The Conversation

Suresh asked her to share what she was experiencing. Her examples were painful:

• "You consistently engage substantively with the technical opinions of the male engineers on the team. When I offer technical perspectives, you often respond with 'thanks, we'll consider that' or move on. It's a subtle difference, but it's consistent."
• "In stakeholder meetings, you've described work I led as 'the team built' while you describe similar work by male engineers with their names. I've noticed this pattern multiple times."
• "When I disagree with you, your response is usually shorter and more dismissive than when male engineers disagree. With them, you engage; with me, you wrap up the conversation."
• "You consult the male engineers on architectural decisions in informal conversations. I find out about decisions in meetings after they've been substantially shaped. I'm a senior engineer, but I'm not being consulted as one."
• "In our one-on-ones, you spend much less time on my work than I see you spending with male engineers in theirs. The substantive engagement isn't there."
• "Six months ago, when a junior engineer interrupted me in a team meeting and dismissed an idea I'd been explaining, you didn't say anything. He continued, and you engaged with him as if I hadn't been speaking. That moment stays with me."

Suresh's Reaction

Suresh's first instinct was to deny. "I treat everyone the same. I don't have favorites. I'm not biased." But Maya pushed: "I'm not asking whether you intend to. I'm telling you what I experience. The patterns are consistent over years. I'm not the only one who has noticed; I've talked with other women in the company who experience similar things with their leaders. What I'm asking is whether you're willing to look at the patterns honestly."

Suresh paused. He realized that his defensiveness was itself the problem. Whether or not he intended any of this, Maya was telling him what she experienced. Her experience was the truth of what his behaviors communicated, regardless of his intent. "Maya, thank you for telling me. I want to look at this honestly. Help me see what you see."

The Investigation

Suresh did something difficult: he asked someone he trusted to observe his interactions for a week and tell him honestly what they saw. What this observer reported was painful:

• His engagement with women's technical input was visibly less substantive than with men's, even when the content was equivalent
• He used different language in describing similar work depending on the gender of who did it
• He spent less time in one-on-ones with women on the team than with men
• He didn't interrupt the dynamics in meetings where women were spoken over or had their ideas later attributed to men
• His informal consultations were almost exclusively with male engineers

Suresh had not been consciously biased. He genuinely believed he treated everyone the same. But the patterns of his actual behavior told a different story. He had been engaging in subtle forms of disrespect to women on his team for years, while believing he was being fair.

The Hard Truth

Suresh realized that "I don't intend to be disrespectful" wasn't sufficient. His behaviors had been communicating disrespect to women on his team regardless of his intent. The patterns were real even though he hadn't been aware of them. And changing them required more than good intentions; it required new behaviors and constant vigilance.

The Plan

Suresh committed to:

• Substantive engagement equity: Engaging with every team member's technical input with the same substantive seriousness, regardless of gender
• Specific credit: Naming specifically who did work in stakeholder discussions, especially for women whose work had been absorbed into "team accomplishment"
• Equal one-on-one time: Spending equal substantive time with each team member's work
• Interrupting interruptions: Speaking up when team members were interrupted or talked over, especially when patterns were gendered
• Informal consultation equity: Including women engineers in informal consultations the way he included men
• Apologizing for past failures: Specifically apologizing for the meeting where Maya was talked over without his intervention
• Ongoing awareness: Working with someone to provide ongoing observation of his patterns, since his self-perception had been so unreliable

The Process

Change was uncomfortable. Suresh had to actively notice his patterns and adjust deliberately. He had to engage substantively with input he might have absorbed quickly. He had to credit specifically when he had gotten used to general attribution. He had to interrupt meeting dynamics he had previously ignored. He had to share informal access he had previously concentrated among male engineers.

Maya noticed. "I see you trying. The changes are visible. And I appreciate the apology for the meeting incident. That mattered." Slowly, she re-engaged with the team. Her ideas came back. Her energy returned.

The Outcome

Twelve months later:

• Maya was fully engaged again and had taken on a significant technical leadership role
• Two other women on the team had reported feeling more respected and engaged
• The team's overall culture had shifted toward more equitable engagement
• Some male engineers had also noticed and appreciated the more substantive culture
• The team's diversity in technical contribution had improved

Suresh reflected: "I thought I was fair. I believed I treated everyone the same. What I learned was that my actual behaviors had been communicating systematic disrespect to women on my team for years, despite my belief that I was being fair. The patterns were real even though I hadn't been aware of them. Maya nearly left because of patterns I didn't see in myself. The hardest lesson was that good intentions don't substitute for examining your actual behaviors. What people experience is what counts, not what you intend. And the people most affected by patterns of disrespect are often the people least able to give you feedback about it, because the same patterns that disrespect them also make their feedback harder to receive and accept. I'm a fundamentally different leader because of Maya's courage in telling me what she was experiencing, and because of my willingness to look at it rather than defending myself. The team is fundamentally better. And I'm grateful, though I wish it hadn't taken Maya nearly leaving for me to see."

The Lessons

• Leaders systematically underestimate the disrespect their actual behaviors communicate, especially when they believe they're being fair
• Subtle differential treatment based on gender (or race, or other identities) is real and damaging even when unintentional
• The people most affected by patterns of disrespect are often least able to give feedback about it; the same patterns make their feedback harder to give and harder for leaders to receive
• Defensiveness in response to feedback about respect is itself a form of disrespect
• Self-perception about respect is unreliable; external observation often reveals patterns we don't see
• Good intentions don't substitute for examining actual behaviors and their impact
• Real change requires constant vigilance because the patterns are habitual and easy to revert to
• The investment in equitable respect pays back enormously in team functioning and in retaining diverse talent

Conclusion

Respect is the foundation upon which every other engagement practice rests. Without genuine respect, rapport feels hollow, empathy feels performative, autonomy feels conditional, and recognition feels manipulative. With genuine respect, all of these other practices land as authentic and contribute to engagement. Without respect as the foundation, no amount of skill in other practices produces lasting engagement.

Respect is not politeness, friendliness, the absence of meanness, or formality. It is the substantive recognition that team members are full humans deserving of dignity, that their work has value worthy of serious engagement, and that they have judgment capable of being trusted. Real respect requires all three dimensions working together: respect for the person, respect for the work, and respect for autonomy and judgment.

Many leaders engage in patterns that communicate disrespect without intending to: interrupting, checking devices during conversations, making decisions unilaterally, dismissing ideas quickly, comparing unfavorably, treating people inconsistently, withholding information, and showing dismissive body language. These patterns are often invisible to the leader but felt sharply by team members. The gap between intending to respect and actually communicating respect is one of the largest gaps in leadership self-perception.

Power asymmetry between leader and team member means that respect requires higher standards from the leader, not lower. Your authority amplifies your behavior. Small disrespects from you land harder than equivalent behavior between peers because team members cannot easily push back. This means the discipline of respect requires constant vigilance and awareness of your position.

Difficult conversations test respect most. The skill is delivering hard messages while maintaining dignity. Performance feedback, disagreement, declining requests, bad news, addressing behavior, and discussing limitations can all be done while preserving respect. The hardness of content doesn't justify violating respect; you can deliver any message while honoring the recipient.

Equal respect across all team members regardless of level, visibility, or personal connection is one of the hardest tests of leadership. Differential treatment, even subtle, communicates that respect is conditional on hierarchy, visibility, or chemistry. Real respect is given equally to all.

When you fail at respect (and you will), recovery through honest acknowledgment, ownership, apology, and changed behavior can actually deepen respect rather than damage it. Some of the most powerful respect-building happens through recovery from failure, demonstrating that you are someone who acknowledges mistakes and changes behavior.

The most important lesson is this: What your team members experience is what counts