How Alanna Ball Thinks About Safety Networks When Expertise Is Not Enough

Episode 13 of the Headline Podcast was published on January 14, 2026, with Alanna Ball, founder at Women in Safety and WHS Partner. Ball defended a practical thesis that safety leadership becomes stronger when community, representation, care, and sponsorship are treated as operating conditions rather than personal extras.

That thesis matters because expertise can become a lonely form of authority. A technically capable safety professional may still lack the relationships needed to test a judgment, hear an experience that is missing, or help another person enter the profession with more confidence than they had at the start.

Why expertise alone leaves a leadership gap

Safety work rewards knowledge, and it should. Standards, exposure assessment, control verification, and incident investigation all require disciplined technical judgment. The gap appears when the organization assumes that technical competence automatically produces influence, trust, or access to the people who can change the conditions around the work.

A network closes part of that gap because it gives a leader somewhere to take an unresolved question before it hardens into a private assumption. The network may include a peer in another business, a worker who sees the task differently, a mentor who recognizes a political obstacle, or a sponsor who can move a decision into the right forum.

In the conversation, Ball said, “You can't be what you can't see.” That sentence is not limited to representation in a job title. It also describes the range of decisions a person can imagine making when they have never seen someone with a similar background lead a difficult conversation, challenge a senior manager, or recover from a mistake without losing their place.

What a real safety network provides

A useful network has three functions. It helps a person learn, it helps a person test a judgment, and it helps a person become visible to opportunities that would otherwise circulate through informal relationships.

Learning is the easiest function to recognize. A new EHS manager can ask how another site handles a difficult contractor decision or how a supervisor made a stop-work expectation credible. The value is not copying the answer. The value is seeing the assumptions behind it and deciding which parts fit the local exposure.

Judgment testing is more demanding. The person who challenges a proposed control must be able to describe the concern without being reduced to a blocker. A trusted network can help separate a technical disagreement from a status conflict, which gives the leader a better chance of escalating the right issue.

Visibility is the function leaders often miss. If development depends on being remembered by the right person, capable professionals can remain outside the conversation even while delivering strong work. A network makes contribution easier to see, but sponsorship is still required to convert visibility into a fair opportunity.

Why sponsorship is different from encouragement

Encouragement is valuable, although it does not always change access. A manager can tell someone to apply for a role, speak with confidence, or share their opinion. Sponsorship goes further because the sponsor uses their position to create a legitimate opening, recommends the person when decisions are being made, and stays present when the candidate is not in the room.

Ball described that responsibility through a memorable image: “Be a Rapunzel, not a drawbridge woman: when you get to the top of the castle, throw your hair down for the next person.” The image is useful for safety leaders because professional progress is often treated as an individual achievement, even though access to influential work is shaped by who invites, recommends, and protects the next voice.

Sponsorship should not become favoritism. The safeguard is transparency about the opportunity, the capability required, and the evidence used to decide. A leader can open a door while still asking the person to meet a clear standard. The ethical issue is not whether leaders advocate for people. It is whether advocacy is reserved for those who already resemble the decision makers.

Representation changes the questions in the room

Representation is often discussed as a headcount issue, but safety decisions are shaped by attention. A room with similar experience may move quickly because everyone recognizes the same cues. That speed can feel efficient while leaving an important exposure unspoken.

Different perspectives do not guarantee a better decision. They do make it more likely that someone will ask what the plan assumes about the body, schedule, language, sensory environment, family responsibility, or social pressure of the people expected to carry it out.

The leadership test is therefore not whether a diverse person was present. It is whether their knowledge could alter the decision. If the meeting invites a different voice only after the control is chosen, the organization is collecting representation without sharing influence.

How vulnerability can improve technical leadership

Vulnerability has a poor reputation in operational settings because leaders worry that admitting uncertainty will weaken authority. The opposite can happen when the admission is precise. “I do not yet know whether this control will hold during the night shift” gives the team something to investigate. “I have all the answers” closes that route before the evidence arrives.

The boundary is accountability. A leader who names uncertainty still has to assign the next check, protect the people while the question is open, and communicate what was learned. Vulnerability is useful when it improves the decision process. It becomes harmful when it turns into emotional disclosure that asks workers to reassure the person with authority.

For an EHS manager, one practical test is to listen for the response that follows an admission. Does the team bring evidence, or does everyone rush to restore the leader's confidence? The first response indicates a working network. The second indicates that the hierarchy remains stronger than the invitation to speak.

Neurodiversity is a work-design question

Ball connected neurodiversity with a broader humanizing purpose. She said, “All we're doing by talking about neurodiversity is humanizing our workforce. We are not robots.” That point is relevant to safety leadership because work systems often treat variation as noise instead of asking whether the design makes safe performance harder for some people.

The practical questions are familiar to any serious safety leader. Are instructions clear when the environment is noisy? Can a person ask for clarification without being mocked? Does the control depend on rapid social interpretation? Are shift changes designed for the way information is actually retained and transferred?

These questions do not lower expectations. They improve the chance that the expectation can be understood, performed, and verified. A network helps because the people who notice these mismatches are not always the people who own the procedure, the training package, or the budget.

Recommendation

After listening to Episode 13, an EHS manager can run a 30-day network review around one real safety decision. Start by selecting a decision that affects workers who are rarely invited into the design conversation, such as a shift change, a new digital tool, or a revised emergency response.

During the first week, map five people who can add evidence, challenge an assumption, or open a route to action. Include at least one worker, one peer outside the immediate function, and one person whose experience is usually absent from the room. Do not call the map a stakeholder list if nobody has permission to influence the decision.

During the second week, ask each person what the current plan assumes and what it makes difficult. Record the answers without converting them into a vote. The aim is to expose the work conditions that a technical review may not see.

During the third week, assign one sponsor to carry the strongest unresolved issue into the decision forum. Publish the question, the owner, and the evidence still required. During the fourth week, return to the people who contributed and show what changed, what did not change, and why.

This routine gives the network a job. It also prevents inclusion from becoming a celebration without consequence. The measure is not how many people attended. The measure is whether someone with less access could change the quality of a safety decision.

Conclusion

Alanna Ball's conversation offers a direct correction to the idea that safety leadership is built by accumulating expertise alone. Knowledge remains the foundation, but community tests it, representation widens it, vulnerability makes uncertainty discussable, and sponsorship helps it travel to people who have not yet been given a fair opening.

The Headline Podcast has described this work as the space where leadership and safety come together to shape better workplaces and better lives. The phrase becomes credible when leaders turn networks into operating routines, then use those routines to make better evidence and better opportunity visible.

Listen to the full conversation with Alanna Ball, then compare one important safety decision with the people who were invited to shape it. For more context, read our analysis of vulnerability as a safety leadership skill and explore the Headline Podcast.