Naming what we carry: A tool for the first step toward transformation

Many leaders and organizations struggle to achieve impact because of unaddressed conditioned patterns that quietly sabotage even the best-laid plans.

Organizational-conditioned patterns are learned, compulsive, reactive, and often invisible behaviors and norms that shape how decisions get made, how people relate, and how the work gets done. As coauthor of Destroying Sanctuary: The Crisis in Human Service Delivery Systems, Sandra Bloom refers to this collection of conditioned patterns “trauma organized systems” and adds that such a system “virtually prohibits the proper delivery of services to the individual clients who are the source of the organization’s original mission, while damaging many members of the organization’s workforce.”

Bloom’s more recent work, Creating Sanctuary: Toward the Evolution of Sane Societies shows also that organizations, like individuals, develop self-protective behaviors in response to instability or threat, and that those behaviors persist long after the original danger has passed, hardening into the very rigidity that later drives decline.

Just as individuals develop conditioned patterns in response to early experiences, organizations develop collective, conditioned patterns in response to their history, leadership, funding environment, and sector norms.

An organization that grew under a founder who couldn’t tolerate dissent, learns to function by keeping disagreements private, the same way a child learns to read a parent’s mood before crossing a room. An organization that survived a funding crisis by slashing staff salaries, learns that cutting corners is always available to them. It also learns that staff who believe in the mission will stay and absorb almost any loss to keep the organization alive, and that tolerance for compensating them poorly quietly becomes normal. That lesson doesn’t unlearn itself just because the crisis passed, and it carries a ripple effect. The organization’s ability to deliver on its mission erodes, and the strain lands on staff and the communities it serves.

Trauma-organized systems persist because, at some point, they’ve worked by keeping something safe. But now, these same conditioned patterns underlie unhealthy organizational cultures and the inability to successfully implement strategy.

In this article, we look at what it takes to loosen a pattern’s grip. We walk through the first step of our approach and a tool to support that first step: identifying and naming organizational patterns, as a path to developing new authentic ways of being and truly advance organizational mission.

Naming as a first step

Naming conditioned patterns is the first important step in addressing the behaviors that limit organizational success. Naming allows staff and leaders to say plainly: “This is what we often do, and here is what it costs us.” That naming is the first step, but it is not a small thing; it has real cognitive weight.

Psychiatrist Dan Siegel calls this “name it to tame it,” as coauthor of The Whole-Brain Child: 12 Revolutionary Strategies to Nurture Your Child’s Developing Mind. The act of putting an experience into words engages the brain’s reasoning centers and quiets its alarm system, shifting a person from reacting on impulse to responding with intention. Organizations aren’t brains, but they are made of people whose nervous systems work exactly this way, and an unnamed pattern operates the same way an unnamed feeling does—as an ambient force that drives behavior from underneath, rather than a fact the group can reason about together.

Naming allows an organization to get to the root of the issue instead of just addressing the visible symptom, whether that be a missed target or a tense meeting. Siegel’s insight is that naming doesn’t just describe the alarm, it interrupts it. Once something has language, it stops running the show from the background and becomes available to the thinking, choosing part of the system.

Naming moves the pattern from ambient discomfort into a specific, addressable thing. Once it is named, it becomes a decision the organization can choose to stop making. An organization that can name its difficulty in acknowledging conflict is on a stronger path to transformation than one which schedules a new meeting format to solve the “tension” in the weekly leadership meeting.

The pitfalls of naming as a practice

This organizational development work is complex. Investing in new ways of working together toward a mission can generate great opportunity but also risks and pitfalls. I’d rather name both than pretend the first one is the whole story. A few considerations are outlined below:

1. Naming as performance: Organizational theorist Chris Argyris spent decades studying why smart, well-intentioned people and organizations struggle to name their own dysfunction. Argyris observed that organizations develop what he called “undiscussables”—problems too threatening or embarrassing to name directly. This is where naming can quietly fail even when it appears to succeed. The existence of these undiscussables becomes undiscussable in turn, since acknowledging them would violate the organization’s own stated commitment to openness.

Argyris called this pattern of behavior “skilled incompetence.” People can become highly skilled at identifying and even discussing a pattern in ways that feel like accountability, while remaining ineffective at the deeper, more threatening work of actually changing it.

An organization can name a pattern in a retreat, nod at it in a memo, reference it in a values statement, and never once disturb the underlying defensive routine that produced it. Naming, in other words, is not self-executing. It can become its own kind of cover, a way of appearing to have done the work of change without having done it.

2. The asymmetry of recognition: Who names a conditioned pattern, and how it gets named, shapes everything about how the work unfolds from that point forward, because leaders and staff rarely recognize a pattern the same way, at the same time, or at the same cost to themselves.

Leaders tend to recognize patterns abstractly and strategically. In a planning retreat or in a board memo, a leader can often say with real fluency that “we struggle with follow through” or “we’re too conflict avoidant.” That same leader is frequently the last to see their own role in keeping the pattern alive day after day: in the meeting they end 10 minutes early rather than sit through the tension; they soften a report before it reaches the board; the direct report they’ve quietly stopped giving hard feedback to avoid the discomfort of trying again because the last time didn’t go well.

Staff, on the other hand, tend to feel the pattern first. They feel it in their bodies before they have language for it. They feel it in their workload, in who gets interrupted in meetings, in whose emails get answered the same day, in who has been quietly managed out of the organization for saying the wrong true thing in the wrong tone. What staff are frequently missing is not the insight; it’s the standing to challenge these actions—and sometimes the language—to say it out loud, without paying for it professionally. The distance between what leadership can see and is willing to say, and what staff feel and cannot safely say, is where organizational dysfunction most often hides in plain sight.

3. Readiness, time and capacity: Pattern work takes real time: time to build trust, time to process what surfaces, time to practice new responses before old ones reassert themselves under stress. Nonprofits are frequently underresourced and overextended, so when leaders introduce pattern awareness as one more initiative layered onto an already full plate, without adjusting timelines or expectations elsewhere, they risk repeating the very pattern of over-functioning and burnout.

Readiness is not a fixed threshold to clear once. It shifts with organizational stress, funding cycles, staffing changes, and world events. A team that had capacity for this work in the spring may not have it during a budget crisis in the fall. Therefore, leaders need to keep checking in with staff on their capacity to do this work, not just at the start of the work, but throughout it.

Conditioned patterns don’t limit themselves to one domain. Strategy and culture aren’t two separate systems running in parallel; they’re downstream of the same conditioning.

4. The risk of weaponization: Weaponizing pattern awareness against staff, turning it into a passive-aggressive form of shaming or blame, is a risk. This can look like a manager labeling an employee’s valid frustration as “triggered,” or citing someone’s trauma response to wave off a legitimate concern instead of addressing it. The inverse risk deserves equal attention. Pattern language can also be weaponized against leaders, since a leader’s patterns often have an outsized influence on organizational patterns.

Pattern language, once introduced into an organization’s vocabulary, does not stay contained to its intended use. It becomes available to anyone, for any purpose, including purposes that have little to do with healing. “That’s just your trauma response” can become a way to dismiss an individual’s legitimate concern without engaging on its substance.

To address this risk, leaders considering this work should anticipate that the language they introduce may be turned back on them. They should build norms early as a container, before conflict arises, for how pattern language will and will not be used.

There are pitfalls, but they can be mitigated if this work is approached thoughtfully and intentionally. Each of these risks shares a root cause: asking people to name something before the organization has built the capacity to hold what surfaces. That capacity isn’t built through one training or a values statement, but through structure, modeling, and practice; and the lowest-risk place to start practicing is strategy.

Start with strategy

Conditioned patterns don’t limit themselves to one domain. Strategy and culture aren’t two separate systems running in parallel; they’re downstream of the same conditioning. But naming a pattern’s impact on strategy and naming its impact on culture are not equally costly, and that difference in cost is worth using rather than working around it.

“That’s just your trauma response” can become a way to dismiss an individual’s legitimate concern without engaging on its substance.

When we think about naming a pattern’s impact on our organization’s strategic efforts, it is easier and less vulnerable to say that “we chase every new opportunity instead of staying focused,” than it is to say that “we avoid conflict because the last person who pushed back got quietly frozen out.” Both patterns potentially touch strategy and culture alike, but the first implicates a process, not a person. It has the shape of something you can put on a slide and solve with a framework. The second implicates people, usually people with more power than whoever is doing the naming, the power dynamics and potential consequences are exactly what makes it harder for staff to say and slower to build team trust.

This is precisely why strategy is the place to start. It gives an organization a lower-stakes way to practice the actual skill underneath all this work, sitting with an uncomfortable truth about itself instead of managing it away. When we practice naming a conditioned pattern that impacts strategy, it asks less of a team than naming a cultural one. In our own work, we build pattern identification into strategic planning. It isn’t the only way in, but it’s the entry point that asks the least of a team while they build the skill.

For example, a team that has never once said a hard true thing out loud is not ready to tell a founder that people are afraid to speak up. But a team that has practiced saying “our strategy keeps failing for the same reason every time,” and seeing that the hard truth gets received without punishment, has started building something real. The practice provides evidence that it is possible to engage in naming without negative consequences; it doesn’t have to cost you your job or your standing within the organization.

Every conditioned pattern named and survived is a small proof of concept. This is a room where hard truths can be said out loud. That evidence is the muscle, and continual practice is the strength training.

Organizations that skip straight to naming the personal, the relational patterns, the favoritism, the fear, the person nobody can give feedback to; often find that the team hasn’t yet developed the capacity to hold what it surfaces from that naming. Starting with strategy isn’t a way of avoiding the harder culture work, it’s how you build the collective capacity required to  shift that culture.

Leaders go first

Leaders should do the work first as a way to model the process and deepen capacity. It can be useful for an individual leader to sit with an honest assessment of their own patterns and how they contribute to organizational impact, before asking the same of anyone else. A leader who has already sat with an uncomfortable truth about themselves is less likely to become defensive when a staff member names a related pattern from their own vantage point. The leader has already practiced the discomfort in private, which makes it more survivable in public.

A leader who starts with individual reflection can see the difference between abstract naming and personal recognition. “We’re conflict avoidant” and “I am the reason conflict gets avoided in this room” are not the same insight, even though they sound related, but only the second one is actionable by the person holding it. A leader who has made that connection for themselves is far better equipped to lead the organization through the same move, because they are not asking staff to do something they haven’t done first.

And this is where Amy Edmondson’s research at the Harvard Business School on psychological safety becomes useful, because it explains why a leader’s own naming matters so much more than a leader’s permission granting. When a leader demonstrates fallibility and names their own mistakes and limitations out loud, they are signaling to the team that admitting error and raising concerns is safe rather than punished. The leader’s own naming becomes the demonstration.

A structured way to do this work

Naming a pattern well takes more scaffolding than a single honest conversation can provide. A pattern that has been protected by an organization’s defensive routines for years does not become discussable just because someone in the room decides to be brave. It becomes discussable when there is a process to hold what surfaces, one that paces the work, protects the people naming things, and keeps the group’s attention on patterns rather than on people.

One way organizations can build this practice is through structured, repeatable pattern assessment. This can be achieved by engaging in three core activities: individual reflection, facilitated group processes, and a continual assessment of readiness and capacity. This is the thinking behind the Kin Consultant Group’s organizational conditioned patterns toolkit —a free resource built to accompany this article. Together, these elements can help an organization build something more reliable than expressing good intentions in the moment. It provides a container and process built with the pitfalls in mind.

Individual reflection: This is a lower-stakes entry point, useful for building your own awareness first, especially if you’re not yet sure your organization is ready for a shared process. Individual reflections help us recognize organizational conditioned patterns, those that we observe in others as well as the ones we uphold ourselves. When engaging in this reflection, it is essential to keep in mind that reflecting on your experiences as an individual, while important, does not offer a complete picture of the organizational patterns that need to shift and why. Everyone in your organization experiences the dynamics of the organization differently, so when you are ready to begin the work of shifting your organizational conditioned patterns, you will need collaborators with whom you build a shared understanding of the conditioned patterns and work together to implement practices and accountability measures toward a different way of being.

Facilitated group process: A team or leadership group can work together with a skilled internal or external facilitator to name conditioned patterns and develop individual and group practices to address them. Doing so requires both facilitated structure and psychological safety. A solid facilitation plan and skilled facilitator help create the conditions for people to share their perspectives, name challenges, and surface tensions. When those tensions come to the surface, the facilitator’s role becomes especially important. They can notice when a conversation is escalating or when people begin to withdraw—situations that can slow the process down—so that difficult moments become opportunities for learning rather than sources of harm. A facilitator can name dynamics that group members may be reluctant to raise, help reframe charged statements so they can be heard, and make sure that quieter or less powerful voices are not drowned out. They can also help the group decide what to do with what emerges, whether that means addressing an issue in the moment, returning to it later with more care, or connecting it to the practices the group is building. Opening up the assessment to a group without a person, a process, and a plan to hold what emerges, can surface chaos rather than change.

Assessing readiness and capacity

Before beginning this work, it’s worth asking honestly whether your organization is ready for it. Readiness starts with leadership buy-in, and it requires a genuine commitment to safety. People need to be able to share their experiences of the workplace without fear of punishment. Capacity comes down to time and practice. Conditioned-pattern work needs real bandwidth, and organizations need to weigh its timing against their other priorities. If now isn’t the right moment, choose a time in the future and begin protecting it now. And if your organization has little experience with difficult conversations, go more slowly. Begin with individual reflection, then look for the colleagues who are already able to engage in hard conversations and build support from there. Starting small isn’t a delay. It builds the capacity the larger work depends on.

Where this leaves us

Naming a pattern is only the beginning. Changing it means showing up differently, with ourselves, with each other, and with the work. These are interesting times, and the challenges we are trying to meet are too big for the ways of being that created them. Meeting them asks us to become people and teams capable of something new, and that change starts with how we choose to show up.

Change is hard. But no one ever built a culture people trust, a strategy that survives contact with reality, or a team that can say hard things and stay together instead of turning back at the first signs of difficulty. The pitfalls are real, but they cannot be the reason we don’t engage in the work of naming and healing our collective patterns. If anything, they are the reason to walk in with eyes wide open, with support, and with practices that steady the ground under everyone’s feet.

The patterns are already at work. The only choice is whether they keep unnamed, or whether we begin the practice of doing something different.