Is Belonging a Leadership Skill Leaders Can Practice?
Belonging is a leadership skill, built the same way delegation or decision-making is built: through repetition, feedback, and the willingness to get it wrong before getting it right. It lives in the small moments where a leader notices who has gone quiet in a meeting and repairs quickly when they misstep. That distinction matters more than it sounds like it should. Most organizations treat belonging as a program HR designs and rolls out, when the real work happens in the daily habits of the leader running the meeting.
This is the sixth and final theme in our 2026 series on what's shaping leadership this year. If you haven't seen the other five, from steadiness amid constant change to the feedback reckoning we've been tracking all year, you can find the full series here. Belonging closes the year because it is, in some ways, the container for everything else. A team can't take in hard feedback, adapt to change, or grow together in community if its members don't trust they're allowed to stay in the room as themselves. That's true whether we're working with a hospital care team, a utility crew, a tech org, or a nonprofit board, which covers most of the leaders we sit across from in our Seattle-based coaching practice.
What's the Difference Between Diversity, Inclusion, and Belonging?
Diversity describes who is in the room. Inclusion describes whether they're invited to speak. Neither one guarantees belonging, which is the harder-earned outcome underneath both: whether the people in that room believe, at a level deeper than policy, that they don't have to shrink to stay.
Ruchika Tulshyan, who writes on inclusive leadership in her book Inclusion on Purpose, makes the case that inclusion takes ongoing, deliberate practice rather than good intentions alone, and that belonging is the moment someone can bring their authentic self to work and still be trusted with real decisions and real leadership. That reframes the question every leader is actually being asked, from whether the company has a belonging problem to whether you, personally, are building this muscle in the way you run your next meeting.
Peter Block gets at something similar in Community: The Structure of Belonging, where he describes leadership as a set of structures and practices available to anyone willing to build them, regardless of natural temperament. That idea sits underneath everything that follows here. Building belonging on your team comes down to a few repeatable habits and the discipline to keep using them, whether or not you happen to be the warmest or most extroverted person in the room.
Does Belonging Actually Affect Business Outcomes?
Research on more than 1,700 full-time employees found that a strong sense of belonging is linked to a 56% increase in job performance, a 50% reduction in turnover risk, and a 75% decrease in sick days, and that if every worker at a 10,000-person company felt that degree of belonging, the productivity gains would top $52 million a year (Harvard Business Review). That same research found that 40% of people report feeling isolated at work, with lower organizational commitment and engagement as the result (Harvard Business Review). Separately, the American Immigration Council's Belonging Barometer found that 64% of Americans report a lack of belonging specifically in their workplace (American Immigration Council), which suggests the gap most leaders assume exists is actually wider than they think.
The retention picture is just as direct. An EDUCAUSE poll of higher education IT and technology professionals found that 90% of employees with a strong sense of belonging also reported job satisfaction, compared with just 8% of those without it (EDUCAUSE Review). A spread that wide doesn't show up often in organizational research, and it's a hard number to argue with when you're building a case for why belonging deserves a leader's time and not just a line item in the culture deck.
None of this works, though, if it stays abstract. A diverse team that doesn't feel safe enough to speak up tends to settle into groupthink dressed up with better optics.
What Is the Notice, Invite, Credit, Repair Framework?
We've been piloting a simple four-part practice with the leaders in our Friday coaching sessions, and it holds up because the entire practice runs on attention, something available to any leader regardless of budget, program, or title. Each part below comes with a practical move you can use in your very next meeting.
Notice
Before your next recurring meeting, ask yourself whose voice you haven't heard in the last three sessions. That's the whole first move: building the habit of scanning for absence with the same attention you already give to presence.
Practical move: Right after the meeting, while it's fresh, jot a quick note to yourself: who did I make space for today, and who did I not get to? This is a check on your own facilitation. If the same name keeps showing up in the "didn't get to" column, treat it as information about your meeting design and adjust how you run the room accordingly.
Invite
When you notice, invite specifically. A general "does anyone else want to weigh in?" tends to get answered by the people who already talk the most. Naming someone directly, and pointing to something specific they've worked on, opens the door differently.
Practical move: Before the meeting starts, pick one person to invite in directly, tied to something specific they've worked on, and have the question ready in your notes. If they pass, treat that as a complete answer. Your job here is making sure the door was open. What someone does with an open door is theirs to decide.
Notice and Invite work as checks on a leader's own facilitation habits. A quiet meeting presence can mean plenty of things that have nothing to do with performance: someone who thinks before they speak, someone who was never given a real opening, someone whose expertise doesn't map to the topic at hand today. These two moves exist to make sure the door was genuinely open, which is a question about the leader's habits, separate from any conclusion about how the other person chose to use that opening.
Credit
Say the name behind the idea, out loud, in the moment it happens. This is one of the simplest and most underused belonging behaviors available to a leader. When women on President Obama's White House staff noticed their ideas were being talked over or absorbed into other people's contributions, they began repeating and crediting each other by name in meetings until the room caught up, a practice later reported by the Washington Post and often called "amplification" or shine theory. Lifting someone else up in the room strengthens the whole room.
Practical move: The next time someone's idea shapes a decision, name them in the same sentence you use to announce that decision. Follow up afterward with a short written note crediting them by name, copying anyone else who should see it, so the credit lives somewhere beyond the room it happened in.
Repair
You will get this wrong sometimes. You'll talk over someone, misgender a name, forget a contribution. Loretta Ross, the longtime civil rights organizer and MacArthur Fellow known for distinguishing between "calling in" and "calling out," has written extensively about this kind of repair work. Trust builds through how quickly and plainly you repair a mistake, without over-apologizing or making the moment about your own guilt.
Practical move: Write your repair line ahead of time so it's ready when you need it, something like "thank you for telling me, I'll do better." Let the discomfort of getting it wrong actually land, rather than rushing to smooth it over. What separates a repair that builds trust from one that doesn't is where your attention goes afterward: toward the person you affected and what they need, not toward managing your own guilt or seeking reassurance that you're still a good leader.
What's the One Practice to Start With Today?
Pick one recurring meeting on your calendar this week. Before it starts, ask yourself the notice question: whose voice haven't I heard from in the last three sessions? Just notice, and write down the name. That single habit, repeated weekly, is where every other part of this framework becomes possible. Inviting someone specifically, crediting them publicly, or repairing a misstep with them all depend on having noticed they're there in the first place.
What builds trust with your team, more than getting everything right, is whether they believe you're paying attention.
Frequently Asked Questions
-
Diversity is about who is represented in an organization. Inclusion is about whether those people are invited to participate and speak. Belonging is the deeper outcome: whether people trust they can show up as themselves without having to shrink to stay in the room.
-
Both, but the skill lives with individual leaders. HR can set policy and provide training, and the moment-to-moment shaping of whether someone feels they belong happens through how their direct leader notices, invites, credits, and repairs.
-
It's a four-part practice for building belonging in day-to-day leadership. Notice means scanning for who's been quiet. Invite means asking for input specifically rather than generally. Credit means naming contributions publicly and in the moment. Repair means addressing mistakes quickly and plainly, without over-apologizing.
-
Diversity tends to improve team performance when it's paired with psychological safety and a genuine sense of belonging among team members. Research suggests the innovation and performance gains often credited to diverse teams depend on that combination being present.
-
The two overlap closely, and belonging describes a further layer beyond psychological safety. Psychological safety, a concept developed by Harvard Business School's Amy Edmondson, describes whether a team feels safe to take interpersonal risks like admitting a mistake or raising a concern. Belonging goes further: it's whether someone feels they can show up as their authentic self and still be trusted with real responsibility.
-
Leaders in our coaching sessions typically notice a shift within a few weeks of consistently practicing the Notice and Invite steps, since those are the most visible to the team. Credit and Repair tend to build trust more slowly, over a full quarter or two, because trust compounds with repetition rather than arriving all at once.
Want Support Building This on Your Team?
Turning a framework like this into a habit takes more than reading about it, which is exactly where our coaches step in to work alongside leaders directly. Our executive coaches work with leadership teams across healthcare, utilities and energy, tech, and nonprofit organizations throughout Seattle and the Pacific Northwest, and belonging is one of the areas we hear about most often once a leader starts paying closer attention to their own meetings.
If you're curious what this could look like for your team, reach out to learn more about our executive coaching services. We'd love to talk about what you're noticing.