The Soul Audit

Posted by K. Brown November 18th, 2026

The Soul Audit

The Soul Audit

Every organization has a stated culture — the values on the wall, the language in the all-hands meeting, the description in the employee handbook and the onboarding materials and the careers page. And every organization has the culture that actually operates day to day, which is the aggregate of how decisions really get made, how people actually treat each other when things are difficult, and what behavior is genuinely rewarded and what is genuinely penalized regardless of what the stated values say about either. 

The gap between these two cultures is always present in some form. In genuinely healthy, well-managed organizations it tends to be small. In organizations with a serious culture problem it can be enormous. The difficulty is that the gap is not always visible from inside, particularly to leadership — the people most likely to believe the stated culture is the operating culture are often the people whose daily experience most closely approximates it, which is to say the people closest to the top. 

A soul audit is not a standard culture survey. Culture surveys ask people what they think about the culture, and people answer in the context of what they believe is safe to say and how they want to be perceived. The aggregate of those responses tells you something, but it does not reliably tell you whether the stated culture and the operating culture are the same thing. 

A soul audit asks three questions that are more direct and more diagnostic than any survey instrument, and the answers to those questions — sought honestly, without the framing that makes answers safe — reveal the actual state of the operating culture more accurately than what the organization says about itself in any formal channel. 

The First Question: Who Gets Rewarded and for What 

The first question a soul audit asks is: look at the people who have been most visibly rewarded in the last twelve months — promoted, recognized, given expanded responsibility, held up as examples — and examine specifically what they did to earn that recognition. 

This question cuts through stated values immediately, because the pattern of who gets rewarded is the most reliable signal of what the organization actually values. Organizations that say they value integrity but consistently reward the person who hit their numbers through methods that bent the rules are organizations where the integrity value is aspirational, not operational. Organizations that say they value collaboration but reward individual contribution regardless of how it was achieved are organizations where the collaboration value is a cultural decoration, not a decision-making input. 

The soul audit version of this question does not stop at who got promoted. It asks what specifically they did — what choices they made, what they prioritized, what they were willing to do that others were not. The pattern across those answers tells you what the organization’s actual operating values are, stripped of the language and the intent that frames them in the stated version. And it tells you what the people watching those rewards are learning about what is actually expected of them. 

In most organizations that conduct this analysis honestly, there is at least one category of behavior that the stated values explicitly discourage but that the reward pattern implicitly encourages. Finding that category is the first productive output of the audit. 

The Second Question: What Do People Not Say in Meetings 

The second question is harder to ask and harder to answer honestly, but it is often more revealing than the first: what are the things that people clearly know but do not say in the meeting where those things are relevant? 

Every organization has them. The concern that is widely held but never surfaced in the forum where it would be most useful. The reservation about the plan that everyone in the room shares but no one voices. The feedback that the senior leader’s decision was wrong that circulates in the hallway after the meeting but never reaches the person who made the decision. The information that the system has a problem that the team knows about but that has not made it to the people with the authority to address it. 

The presence of these unspoken things is not evidence that people are cowardly or disloyal. It is evidence that the psychological safety required to surface them does not exist — that the organizational signals about what happens when you raise uncomfortable truths have taught people that the cost of raising them is higher than the cost of sitting on them. 

The soul audit asks leaders to specifically identify the things that they believe people in the organization know but are not saying to them — and to ask that question not in a blame-assigning or defensively investigative way, but in a genuinely curious way: what are the things that are probably true about this organization that are not making it into the conversations I am part of? The answers, if sought honestly, tend to be surprisingly available — not because people have been hiding them but because they are often not far below the surface, needing only a genuine invitation to emerge. 

The Third Question: What Would Have to Happen for Someone to Leave 

The third question is perhaps the most direct: think about three of the people in the organization whose departure would genuinely hurt the organization, and ask what would have to happen for each of them to decide to leave. 

This question is diagnostic because it surfaces, in concrete terms, the gap between what the organization is currently providing and what the people who matter most to it actually need. The answers are usually not primarily about compensation, though compensation is real. They tend to be about the conditions under which the work is done — whether they have autonomy, whether they feel genuinely respected, whether the culture they signed up for is the culture they are actually experiencing, whether the direction the organization is heading is one they want to be part of. 

These conditions are things the organization can influence. But they can only be influenced if they are known. The soul audit version of this question is not hypothetical future-proofing. It is a diagnostic present-state question about whether the conditions that the organization’s most important people need are currently being provided — and if they are not, what specifically would need to change. 

The Pattern Across All Three 

The most useful output of a soul audit is not the answer to any single question. It is the pattern that emerges across all three: the behaviors that are being rewarded, the information that is not surfacing, and the conditions that are not being met together form a picture of the operating culture that is more accurate than any survey or engagement score. 

What that picture reveals is different in every organization. Some organizations discover that their stated values are largely reflected in their operating reality, with specific gaps that are addressable. Some discover that the gap between stated and operating culture is significant and requires genuinely difficult changes in how decisions are made and how behavior is rewarded. Some discover that the culture is healthy in the areas leadership can see but deeply compromised in areas that are not visible to the people at the top. 

The value of the audit is not in producing a score. It is in producing the honest picture that allows the organization to make deliberate choices about what it wants to reinforce and what it wants to change. The organizations that conduct this kind of honest examination — not as a response to a crisis, but as a regular discipline of healthy organizational management — tend to catch the culture problems when they are still correctable rather than after they have produced the talent departure or the client failure or the team breakdown that makes the culture problem unmistakable. 

The Technology and Security Culture Version 

The soul audit questions have a specific application in technology and security organizations that is worth developing directly, because the culture problems in these environments tend to produce specific and sometimes serious operational consequences. 

The first question — who gets rewarded and for what — surfaces a pattern in technology organizations that is common and consistently damaging: the reward for visible heroics versus the absence of reward for invisible prevention. The engineer who stays up all night to restore a system that went down is recognized and celebrated. The engineer who designed and maintained the systems that prevented comparable failures from occurring is not, because the failures they prevented are invisible. The firefighter is the hero. The person who builds the fire prevention infrastructure operates in organizational obscurity. 

This reward pattern trains the team. It creates incentives to allow fires to develop because firefighting produces recognition, and it creates disincentives to invest in prevention because prevention is not visible. In security specifically, this reward pattern is directly dangerous: it creates cultural incentives for incident response over proactive security investment, which means the organization is continuously developing its recovery capability while its prevention capability receives less investment, less attention, and less organizational recognition — producing an organization that is better at recovering from incidents than at preventing them, when it should be optimizing for the reverse. 

The second question — what do people not say in meetings — has a specific security implication. Security professionals who operate in organizational cultures where surfacing bad news is penalized are security professionals who delay disclosure of vulnerabilities, incidents in development, and coverage gaps. The security team that is afraid to tell leadership that the security program has a significant gap will manage the discovery process to minimize organizational disruption rather than to maximize the speed of remediation. By the time the gap is acknowledged, it has been present longer and the exposure has been greater than it needed to be. 

The third question — what would make the most valuable people leave — surfaces something specific in technology and security contexts: the people in these roles often have clear, accurate pictures of the security posture, the technical debt, the coverage gaps, and the organizational decisions that are creating risk. When they leave because the culture does not allow that picture to be surfaced and acted on, they take not just their skills but their risk awareness. The organization becomes less safe, not just less capable, when this category of person departs. 

The Practical Cadence 

A soul audit is not a one-time event. It is most useful as a regular organizational discipline — a periodic deliberate examination of the gap between stated and operating culture that catches drift before it becomes entrenched. 

The organizations that do this well tend to conduct it informally and continuously: the leader who pays attention to what is not being said in meetings as a regular practice, who asks directly about what the most valuable people would need to stay as part of routine talent conversations, who examines the pattern of recognition decisions explicitly rather than waiting for a culture survey to surface the pattern they have already been creating. 

The formal version — a structured examination of all three questions with the explicit intent of surfacing the gap between stated and operating culture — is most useful on a annual basis, and most useful when it is conducted with genuine curiosity rather than the intention of confirming that the culture is what it is supposed to be. The leaders who conduct it honestly tend to find things they did not expect and would have preferred not to know. They also tend to find things that are addressable if known early — and that would have been expensive if discovered through the departure, the incident, or the team breakdown that was the eventual consequence of the unclosed gap. 

The Courage the Audit Requires 

A soul audit of the kind described in this piece is not comfortable to conduct, and it was not designed to be comfortable. The questions it asks are specifically designed to surface things that leadership would often prefer not to know — or things they already know at some level but have not been forced to confront directly, because the process that would confirm them and make them impossible to attribute to other causes has not yet been run. 

The organization that honestly examines who has been rewarded and for what may discover that its actual reward pattern is systematically reinforcing behavior that its stated values explicitly discourage. The organization that honestly examines what people are not saying in meetings may discover that the culture of psychological safety it has been cultivating is more nominal than real. The organization that honestly examines what would cause its most valuable people to leave may discover that some of those conditions are already present. 

These discoveries are not comfortable. They are also the discoveries that, when acted on, prevent the turnover, the incident, and the culture breakdown that the unexamined gap was producing. The organizations that conduct the audit honestly and act on what it reveals tend to describe it, in retrospect, as one of the most valuable things they did. The organizations that conduct it and find reasons to dismiss what they found tend to encounter the same issues, at greater cost, at the point where they could no longer be dismissed. 

The soul audit is ultimately a practice of organizational courage — the willingness to look at the organization as it actually operates in practice, not as it is described in values statements and culture decks, and to be genuinely honest about the gap between the two. That courage is available to any leader who chooses to exercise it. The cost of not exercising it is consistently higher than the cost of the uncomfortable truths it reveals. 

Tom Glover is Chief Revenue Officer at Responsive Technology Partners, specializing in cybersecurity and risk management. With over 35 years of experience helping organizations navigate the complex intersection of technology and risk, Tom provides practical insights for business leaders facing today’s security challenges.

Eliminate All IT Worries Today!

Do you feel unsafe with your current security system? Are you spending way too much money on business technology? Set up a free 10-minute call today to discuss solutions for your business.

Archives