The Case
A client went through layoffs that reduced headcount by twenty two percent, but the workload didn’t follow and the people who knew how things worked were gone.
Leadership’s mandate was simple. Continue business as usual. Do more with less.
The business outcome they wanted was performance, stability, and value realization.
Many leaders would call the resulting slowdown a performance problem. I was not convinced.
So I traced the signal backward.
The Trace
Trust had declined and safety had declined, leaving people to protect themselves instead of speaking up.
The human outcomes required for performance to happen were absent: trust, safety, confidence, and capability. The system outcomes required were also absent: clear decision making, effective workflows, reliable escalation paths, knowledge transfer, and accountability.
Then I assessed the condition of the dimensions.
Governance
Decision rights that were held by departed people were now unassigned, so no one knew who decided what. The escalation log was empty not because nothing was wrong but because no one knew where to go or trusted what would happen if they did.
Enablement
Tacit knowledge left with the people who walked out, which meant the remaining workforce could not validate what they did not have the expertise to recognize as wrong. Training existed and documentation existed, but judgment is not built through training events. It is built through practice, feedback, and proximity to people who know.
Empowerment
The behavioral environment had shifted to self protection, so people did exactly what was asked and nothing more. Discretionary effort was gone, not because people were lazy but because discretionary effort requires safety and safety was not there.
Operations
The ways of working were designed for a different capacity, so the same processes with half the people produced friction instead of flow. Escalations that should never reach the leader were landing on their desk because no one else had the authority to resolve them.
This was not a people problem. It was a structural one.
The Intervention
We started with safety and trust.
We ran a pulse survey, not an engagement survey that sits on a shelf. It was a targeted read on whether people believed it was safe to speak up, whether they trusted leadership to act on what they heard, and what was blocking them from doing their best work.
Leadership went first.
The survey revealed that sixty seven percent of employees did not believe it was safe to raise concerns about process failures, so the leader named that out loud in the next all hands and committed to three specific changes within thirty days. This was not a communication. It was an action. Visible. Specific. Credible.
We nurtured safety through repetition.
Every time someone spoke up, something happened. A thank you. An acknowledgment. A fix. A feedback loop that closed with the person who raised the concern. That is how safety is built. Not by memo. By repetition.
We rebuilt trust through follow through.
Trust is not rebuilt by promises. It is rebuilt by closing loops. What we said we would do, we did. When we said we would do it, we did it on time. When we could not, we said so before the date passed.
Only then did we deploy the structural interventions.
We built knowledge management through standard operating procedures and process engineering, creating living processes that captured how work actually got done and would survive when people left. We built escalation channels with named owners and response times, not email chains that went nowhere but designed pathways with a clock and a feedback loop. We put decision rights and accountability structures behind them. A person. A role. A clock. A feedback loop.
What Shifted
Before the intervention, the leader was spending sixty five percent of their time on issues that should have been resolved two levels down and zero escalations reached the correct owner within five days. Discretionary effort had disappeared and the roadmap was slipping by an average of three weeks per quarter.
Ninety days after the intervention, escalations reached the right owner within forty eight hours in seventy eight percent of cases. The leader’s time on lower level issues dropped from sixty five percent to twenty five percent. Managers reported that their teams were surfacing problems instead of hiding them and roadmap slippage was reduced to less than one week per quarter.
The board question shifted from why are we behind to how do we protect this capability.
My Role
In this engagement, my role was to diagnose gaps, friction and misalignment within and across the dimension by tracing signals upward and outward, to design the tangible intrventions-process changes and the intangible climate work simultaneously, to facilitate the decision rights assignment session with leadership, to coach the leader through the go first move, and to build the escalation protocol with a named owner and a clock.
The client’s team executed. I designed the conditions for execution to hold.
The Pattern
This same pattern shows up everywhere. The signal changes. The trace does not.
AI mandates fail when the rubric rewards compliance instead of judgment and no one has built an escalation pathway for when the tool is wrong. Return to office mandates fail when trust is gone and no one has defined decision rights for who can request an exception. Post layoff pressure to deliver fails when capacity is depleted and the workforce is protecting themselves instead of performing.
The business outcome tells us what the organization wants. The mandate tells us how leadership plans to get there. The condition of the system determines whether it will.
If you are seeing signals you cannot explain, that is the conversation I work inside.
Hi, I’m Dasheika. Translator. Catalyst. Builder. Institutionalizer.
I help leaders read the signals across their ecosystems, find where execution is breaking, and design what it takes to restore it.
Founder of CultureClusive.
connect@cultureclusive.com