How Alanna Ball Thinks About Belonging in Safety Culture

Episode 13 of Headline Podcast, published on January 14, 2026, brought Alanna Ball into a conversation about representation, community, trust, and the human side of safety work. She defended a simple idea with demanding consequences: people need to see themselves in the profession before they can imagine belonging in it.

The episode changes how leaders should think about belonging in safety culture. It is not a mood, a campaign, or a softer substitute for process. It is a condition that influences who speaks, who stays, whose experience is trusted, and whether a team can use difference before a weak signal becomes a serious exposure.

Belonging in safety culture is the demonstrated ability of people to participate in risk decisions, professional development, and everyday challenge without having to conceal relevant aspects of who they are or copy one approved way of working.

What visibility changes in a safety profession

Visibility gives a person a credible future to picture. When a young practitioner sees women leading safety conversations, or sees a professional whose background does not match the old template, the profession becomes less abstract and less guarded. That shift matters before a person enters a meeting, applies for a role, or raises a concern.

On Headline Podcast, Alanna Ball said, “You can't be what you can't see.” The sentence is memorable because it exposes a practical failure in many organizations. They may publish a statement about inclusion while the visible examples of authority remain narrow, which tells employees that advancement still requires imitation.

Visibility should therefore be tested with three questions. Who is invited into the room? Who is trusted with consequential work? Who is named when the organization explains what good leadership looks like? If the answers stay concentrated in one group, the culture is teaching a lesson that the policy does not intend.

Why community is a control, not a social extra

Community becomes a safety control when it improves the quality and speed of information available to people making decisions. A practitioner who has a trusted peer can test an interpretation before escalating it, ask for help without performing certainty, and learn which response routes actually work under pressure.

This does not mean that every relationship is useful or that professional warmth replaces technical competence. It means that competence travels through relationships. A procedure may define what to report, but a community affects whether a person believes the report will be understood, protected, and acted upon.

Alanna Ball's work with Women in Safety gives the idea a concrete shape. A network is not valuable because it produces a full calendar of events. It is valuable when a person can find one credible connection at the moment a difficult career, identity, or leadership question appears.

Trust and care before process

Safety leaders often reach for process because process feels fair. A form, workflow, or escalation route gives everyone the same visible steps. Yet the same process can produce different outcomes when one person expects curiosity and another expects suspicion.

The Headline conversation surfaced trust and care as conditions that make process usable. Care does not ask leaders to ignore performance, risk, or accountability. It asks them to notice the human context in which those standards are applied, then respond in a way that preserves dignity and keeps relevant information available.

Consider a new safety professional who makes a public mistake in month 2 of a role. One manager may turn the error into a warning to others. Another may examine what support, access, or context was missing while still correcting the decision. The second response does not lower the standard. It protects the person's ability to learn and participate after the correction.

That distinction is central to culture. A team can have a process for reporting concerns and still lose information if its responses teach people that honesty is professionally dangerous.

The trap of polished belonging

Belonging can become cosmetic when an organization celebrates identity without changing access. A campaign may feature diverse faces, a panel may include a new voice, and a conference may publish a thoughtful statement, while hiring, sponsorship, meeting behavior, and promotion continue to reward the same narrow pattern.

The test is not whether the organization can tell a convincing story about inclusion. The test is whether a person can disagree, ask for help, and receive a meaningful opportunity without paying a hidden penalty for being different.

Four warning signs reveal the gap. The organization invites people to speak but does not return with decisions. It celebrates a visible role model but does not provide a route for others to gain access. It calls exclusion a communication style. It treats a network as an event rather than as a durable support structure.

Leaders who see these signs should resist the temptation to launch another message. The better response is to trace one decision from invitation to outcome and identify where participation narrowed.

What leaders miss about imposter syndrome

Imposter syndrome is often discussed as if it were an individual confidence defect. That framing can make the organization invisible. A person may doubt their competence, but the doubt can also be reinforced by repeated signals that their accent, gender, neurotype, career path, or way of asking questions is not the expected professional form.

On the episode, vulnerability and imposter syndrome were connected to community. A trusted group does not remove every doubt. It gives a person a place to reality-test the doubt, distinguish a learning need from exclusion, and continue building capability without carrying the question alone.

For a manager, the practical response is not to offer a motivational sentence and move on. Ask what evidence the person is using, what access they lack, who can sponsor the next opportunity, and which behavior from the team is making participation harder. Those four questions turn a private feeling into a management issue that can be examined.

Neurodiversity humanizes the workforce

Alanna Ball said, “All we're doing by talking about neurodiversity is humanizing our workforce. We are not robots.” The quote redirects the conversation away from a narrow inclusion label and toward work design. People vary in how they process information, communicate uncertainty, focus attention, and recover from overload.

That variation matters to safety because many work systems assume one preferred style. They expect a fast verbal response, treat eye contact as evidence of confidence, or deliver complex changes through one meeting with no written follow-up. Those choices can hide understanding gaps while appearing efficient.

A safer design gives people more than one reliable route to understand and contribute. A supervisor can state the decision verbally, record the critical change, allow a question after the meeting, and check comprehension without turning the check into a test of personality. The goal is not to create a special path for every individual. It is to stop confusing one familiar style with the only valid sign of competence.

From individual courage to team design

Organizations often praise people who speak up despite pressure. That praise can hide a design problem. If every concern depends on unusual courage, the system is asking individuals to compensate for weak access, unclear sponsorship, and poor response routines.

The episode suggests a different question. What would make the desired contribution ordinary? The answer may involve a peer network, a recurring check-in, a named sponsor, a clear route for challenge, or a meeting rule that prevents the most senior voice from closing the discussion too early.

The comparison matters because safety culture is built through repeated decisions. In organizations shaped by more than 25 years of international EHS leadership, the hosts have seen that culture becomes credible when the daily experience matches the declared value. Headline extends that conversation by asking who gets to participate in building the system.

Recommendation

Start with one team, one decision, and one 30-day review. Use 6 checks for access, sponsorship, response, communication, correction, and follow-through. Ask the team which conditions make participation easier and which conditions make it costly. Compare the answers with meeting invitations, access to development, sponsorship, correction practices, and the route used when someone challenges a control.

Then choose one barrier that can be removed without waiting for a new program. Give it one owner, one observable change, and one date for review. If the barrier is unclear communication, add a written decision record. If the barrier is exclusion from key work, change the access list. If the barrier is fear after challenge, review the last response and repair what the team learned from it.

Keep the technical standard firm. Change the conditions under which people can meet it. That is the practical contribution of belonging to safety culture.

To hear the full conversation, listen to Episode 13 with Alanna Ball on Headline Podcast, where she explains why “you can't be what you can't see” and why community must make room for people to grow. Read more Headline Podcast conversations and subscribe to the show through Headline Podcast if this question belongs in your leadership agenda.