The Culture Debt Map · Practice 02
AI transformation runs on two axes: how mature your tech is, and how much your people trust it.
Inside a company the same matrix applies. One axis is Tech Maturity — systems, automation, data that flows. The other is Trust Maturity — whether people surface errors, adopt the tools, and treat change as safe. High tech with low trust doesn’t scale; it gets rejected. Where you sit decides what to fix first.
The Leaky Funnel
- High Tech · Low trust
The AlgoEgo State
- High Tech · High trust
The Cold Start
- Low Tech · Low trust
The Best-Kept Secret
- Low Tech · High trust
- Trust Maturity (EGO) →
- The Cold Start
Low tech, low trust — survival mode. Triage before any AI.
- The Leaky Funnel
High tech, low trust — the org rejects its own tools. Build the trust bridge.
- The Best-Kept Secret
High trust, low tech — great culture, manual labor. Deploy the Algo.
- The AlgoEgo State
High tech, high trust — operational velocity. The system self-heals.
The four states, in detail.
Each has a different trap and a different first move. Find yours, then read the one above it.
Bottom left · Low tech / low trust
The Chaos Zone
The reality
High burnout, manual data errors, siloed departments, constant firefighting.
The trap
Too busy fixing mistakes and navigating politics to ever implement a strategy.
First move
Triage. No AI yet. Simplify one workflow manually and stop the bleeding first.
Next stop: usually Trust first — make honesty cheap before adding tools, or you’ll build straight into the Rejection Zone.
Top left · High tech / low trust
The Rejection Zone
The reality
Modern stack, flat adoption. Shadow IT multiplies; every deployment triggers a stronger immune response.
The trap
Adding more tools to a body that’s rejecting them. The tech isn’t the problem — the fear is.
First move
Pause new tech. Build the trust bridge: make surfacing errors safe, visibly, from the top.
Move right along the Trust axis → the Algo & Ego State. The tech investment starts paying off the moment people stop fearing it.
Bottom right · Low tech / high trust
The Comfort Zone
The reality
A great culture running on goodwill and overtime. It works — until you try to grow.
The trap
Mistaking a happy team for a scalable one. The goodwill becomes the bottleneck.
First move
Deploy the Algo. You’ve earned the right to automate — start with the drudgery the team most resents.
Move up along the Tech axis → the Algo & Ego State. High trust makes change safe; you’re sitting on an unused advantage.
Top right · High tech / high trust
The Algo & Ego State
The reality
Operational velocity. Tech amplifies people; because trust is high, errors surface instantly and the system self-heals.
The trap
Your risk is now speed. Governance has to keep up with velocity.
Hold it
Reinvest the time into strategy, add guardrails, and codify the operating system.
There’s no higher square — the work here is governing the speed and documenting the playbook so it survives key departures.
The methodology
How I read the score — and how I'd move you to the Algo & Ego State.
The calculator is the map, not the work. Here’s how the number is built, and the sequence I use to move an organization from wherever it lands to high-tech, high-trust — in the order that actually holds.
How the score is built
Two axes
Tech Maturity (ALGO) and Trust Maturity (EGO), each scored out of 25.
Five signals each
Tech: data flow, tool governance, systems-not-heroes, live AI use, cycle-time measurement. Trust: error safety, real adoption vs. shadow IT, reaction to change, upward challenge, how automation is received.
The threshold
16 of 25 is the line between Low and High on each axis. The two verdicts combine into one of four states.
What it is not
Not a technology audit. It measures whether your organization can absorb the tools you’re buying — the thing that actually decides adoption.
1
Diagnose · both axes
Locate you honestly — ask the team, not just the founder
Founders answer the tech questions; the team answers the trust ones. I read both, because the gap between “we’re data-driven” and the secret Excel sheet the team actually uses is where Culture Debt hides.
2
Sequence · the weaker axis first
Fix the layer that's actually blocking adoption
The map dictates order. Rejection Zone? Trust first — pause new tools and dismantle blame culture, or the next deployment fails like the last. Comfort Zone? Tech first — you’ve earned the right to automate. Chaos? Triage before either. Sequencing is the strategy.
3
Build · toward the top-right
Raise tech and trust together
Reintroduce tools with the team as co-designers; automate the work they most resent; baseline cycle times so gains are visible. Adoption follows authorship — trust and tech maturity rise together, which is what moves the marker into the Algo & Ego State rather than along one edge.
4
Defend · hold the position
Add guardrails and codify the operating system
Once you have velocity, the job shifts to governance: data and AI guardrails, reinvesting the reclaimed hours into strategy, and documenting the operating system so it survives when key people leave.
Know where you land. Then let's move you.
Run the diagnostic to place your marker on this map — or book a call and we’ll read it together and map the sequence.