Organizations Move On but People Never Forget

Why do old organizational promises continue showing up years after leaders believe they’ve been resolved? In this episode of Conflict Reveals Culture, David Ryan Barcega Castro-Harris explores the gap between leadership intentions and remembered experiences, revealing why trust is often shaped less by what leaders meant to do and more by what people experienced along the way.Through a restorative lens, this reflection examines organizational memory, accountability, and the hidden lessons people learn when commitments remain unfinished. If you’ve ever wondered why skepticism follows new initiatives or why some conversations refuse to stay in the past, this episode offers a deeper understanding of what conflict may be revealing about trust and culture.The new initiative had barely been announced before someone spoke up and questioned the leader about the last promise that hadn’t been kept.Three years earlier, the organization had announced a new initiative. Staff were told that resources were coming, workloads would be adjusted, and longstanding concerns about staffing would finally be addressed. There was a lot of excitement at launch meetings, presentations, timelines, and commitments. Staff invested their energy, participated in planning groups, offered feedback, and adjusted their expectations based on what they had been told.Then, as always, priorities shifted. Some pieces of the initiative moved forward while others quietly disappeared. Leadership changed, budgets tightened, new challenges emerged, and the organization moved on—or at least leadership thought they did.Now, every time a new commitment is announced, someone brings up that earlier initiative. Every time leaders describe a new vision, people respond with caution. When the leader asked for trust, staff responded with skepticism.This leader came to me saying, “We’ve discussed this so many times. Why can’t they let it go? This was years ago. Most of the people involved then aren’t even here anymore.”What stood out was the assumption that time should have resolved it. Because sometimes leaders experience a decision as completed long before people who are affected experience it as resolved.My name is David Ryan Barcega Castro-Harris, all five names for all the ancestors, and this is Conflict Reveals Culture, a podcast about the tensions, frustrations, and conflicts that show up inside organizations and what they reveal about what we’ve built.From a leadership perspective, the situation can be confusing. A promise was made years ago. Circumstances changed. The organization adapted. New priorities have emerged. New leaders have arrived. New challenges have demanded attention.At some point, leaders understandably begin to wonder: Why do people keep bringing up past decisions? Why are they still holding grudges? Maybe these folks are just resistant to change, or they’re just stuck in the past. Is it really that big of a problem, or is this just a few frustrated individuals preventing the organization from moving forward?The questions are understandable, and the interpretation makes sense. And it’s true that organizations can’t continue to litigate every past decision. Leaders are often making choices with imperfect information, and so not every initiative succeeds. Not every commitment goes through as planned.From a zoomed-out perspective, leadership can see the improved conditions. They can see the hard work that people have done toward well-intentioned efforts that just didn’t pan out. But when the old promises surface, it can feel unfair. It can feel as if the leader can never regain trust, no matter what they do.If that’s the experience leaders are having, it’s understandable that they would want to focus on helping people move forward. But when we try to move forward too quickly by helping people let go, we may miss what their insistent memory is trying to communicate.I don’t like to use definitive statements, but trust is almost never built based on intentions. Trust is built on experience, and those things aren’t the same.A leader may remember working tirelessly to solve a problem, while staff just remember not getting the results that they were promised. A leader might remember the obstacles, but staff remember the commitment.But what if people weren’t responding to the broken promise itself? What if they’re responding to what they learned about the experience surrounding that promise?Maybe they learned that organizational commitments are conditional. Maybe they learned that enthusiasm at the onset of an initiative doesn’t necessarily mean that it will be followed through. Maybe they learned that difficult conversations go behind closed doors, so attention shifts elsewhere. Maybe they learned that accountability for commitments is uneven. Maybe they learned that organizational memory is shorter for leaders than it is for employees.They might conclude that promises are important when they’re announced but less important when circumstances change, or that unresolved commitments eventually become invisible to leadership even when they remain highly visible and important to staff.None of these conclusions have to be objectively true to shape employees’ behavior. People usually respond to what they believe their experiences have taught them.That’s one reason old decisions continue to show up in present conversations. The issue might not be the decision itself. It’s that the decision became evidence—evidence about what commitment means, evidence about whose concerns matter, evidence about whether leadership cares about unfinished business, and evidence about whether accountability applies upward as well as downward.So when leaders think they’re facing a trust problem about today’s initiative, folks might actually be responding to lessons they learned three initiatives ago.Trust is cumulative, and people carry those experiences forward and use them to interpret future commitments. New promises don’t arrive in a vacuum. They arrive alongside every previous promise that people remember.It doesn’t mean that leaders are dishonest or staff are inherently unreasonable. It just means that culture has a longer memory than leaders might realize.And if conflict reveals culture, it’s possible that the pattern here is that pain from unresolved commitments lingers long after leadership considers them complete.Consider an organization led by someone named Mia.Five years ago, Mia’s predecessor announced that employee compensation would be reviewed and adjusted to address longstanding inequities. There were staff surveys, committees were formed, outside consultants came in, and folks were hopeful for change.Then funding challenges emerged, and the review process got derailed. A year later, the previous leader left the organization, and the initiative quietly disappeared.Now Mia is in charge. As she’s getting started with strategic planning, she’s spending time getting staff input and trying to help staff feel ownership of decision-making.At the next staff meeting, she announces three new initiatives, and immediately Kareem raises a question:“What happened to the compensation review?”Mia is frustrated because she wasn’t even employed by the organization at the time the promise was made. Kareem isn’t trying to undermine the process. He’s trying to understand whether these new commitments will follow the same pattern as the ones before.Both people are responding reasonably. Mia is hopeful for this new initiative, and Kareem is hesitant because he sees a similar situation unfolding.While important, this conflict isn’t all about the compensation review. It’s revealing the broken trust that a team has in their leadership based on their differing experiences with organizational memory and accountability.A restorative perspective shifts the question.Instead of asking, “How do we prevent people from getting stuck in the past?” we might ask, “What would people need in order to believe that unresolved commitments are being taken seriously?”Leadership may need flexibility when circumstances change and staff who are willing to adapt to new information so they can coordinate efforts and efficiently move forward. Those needs are legitimate.But in order to have a trusting work environment, staff need consistency. They need follow-through. They also might need acknowledgment of the harm that was caused when expectations were shared and left unfulfilled. Those needs are legitimate too.Conflict often emerges when legitimate needs collide. This isn’t about right or wrong or whose needs matter more. But we have to understand that, in this case, resistance to change might be an attempt to secure accountability for past commitments.What appears to be negativity might fundamentally be an expression of: “I’ve been hurt before. Can I trust you?”Someone who appears to be stuck on past decisions an organization has made might actually be insecure about their status with the institution moving forward.When faced with circumstances like this, it’s important for leaders to reflect:What lessons might people have learned from previous initiatives that shape how they interpret present ones?How does accountability function when commitments can’t be fulfilled as originally planned?What experiences have taught people whether leadership follow-through was reliable or not?What organizational memories seem highly visible to staff but less visible to leaders?When skepticism appears, what information might it be providing about previous experiences?And if trust is shaped by experiences, what experiences are people remembering now?Next time you’re tempted to say, “People should just move on,” consider another possibility.What if they haven’t moved on because the issue remains unresolved in their understanding of the organization’s story?What if their recurring references to old unfulfilled promises and commitments aren’t primarily about resolving the past?What if they’re opportunities to build trust, to demonstrate accountability?Take this information as a gift, because this conflict is revealing something important about the culture that people believe they’re living in.If this reflection brought a person, team, or organization to mind, send this to them.If you appreciated the reflection, subscribe wherever you listen to podcasts.Subscribe to get them directly to your inbox.If you’re leading a team where conflict, mistrust, accountability challenges, or unresolved tensions are affecting culture, you can learn more about my work at AmplifyRJ.com. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit conflictrevealsculture.substack.com