Domain ATransformation Theatre vs Real Behaviour Change
The gap between what you’re rolling out and what staff actually do in front of customers is widening. New systems are going in, but day-to-day behaviour hasn’t moved in proportion — which is the definition of transformation theatre. The tell is the workaround: if your people are maintaining side spreadsheets, unofficial processes, or informal shadow systems to get work done, your platforms aren’t being adopted, they’re being endured. This is Whited Sepulchre Logic in early form — impressive façade, unchanged substance.
Next 30 daysRun a workaround audit. Ask frontline staff directly — without their managers in the room — what they do outside the official system to get their job done. Document it. You’ll find 3–6 workarounds and one of them will explain half your current complaints. Post 1 (Whited Sepulchre) covers the pattern.
Domain BService Friction and Trust Erosion
Complaint themes have started to drift. Customers are using words like “impersonal,” “robotic,” or “I had to repeat myself” more often than they were a year ago. Your satisfaction scores may not have moved yet, but the qualitative signal is running ahead of the quantitative one — which is exactly what the Service Value Gap looks like in formation. Customers are still here, but the emotional contract is fraying. Left alone, this becomes churn in 12–18 months and the churn will be blamed on price.
Next 30 daysPull the last 200 complaints and tag them by theme rather than by resolution code. Count the frequency of “had to repeat,” “no one,” “again,” “runaround,” “couldn’t reach.” That frequency, tracked month-on-month, is your early warning system. Post 2 (Service Value Gap) and Post 11 (Early Warning Signals) cover the method.
Domain CInternal Service Chain Health
Internal teams are starting to behave transactionally with each other. Ticketing is replacing conversation. Handoffs are being completed according to the process but failing for the customer — the classic “I did my bit, not my problem” pattern. This is Internal Service Logic in early decay, and it’s the most reliable upstream predictor of external service failure you have. External customer trust is capped by internal service relationship quality. If internal relationships are hardening, external ones will follow within two quarters.
Next 30 daysMap one customer journey that feels like it’s degrading and walk it end-to-end across every internal handoff. Identify each point where the next team relies on the previous team’s goodwill rather than the system. Those are your leak points. Post 3 (Internal Customers) and Post 9 (Service Blueprints) are the architecture.
Domain DAI Readiness and Governance
Your AI governance is real but underdeveloped. You may have a never-automate list that hasn’t been revisited, a human-in-the-loop that’s become a rubber stamp, or a roadmap that started business-led and has quietly been colonised by vendor pitches. The early signal here is the phrase “we need to be doing something with AI” entering leadership conversations without a specific business problem attached. Human-led AI Logic says AI should be a context engine or empathy amplifier — not a destination in itself. If your roadmap has become vendor-led, you’re at risk of building to someone else’s commercial interest.
Next 30 daysAudit your AI roadmap against specific business outcomes. For every item, name the outcome it serves and whether that outcome was identified before the vendor pitch or after. If more than half were after, you’re in vendor drift. Post 7 (Human-AI Collaboration) is the corrective frame.
Domain ELeadership Authenticity
Senior leaders are signalling AI engagement without doing much of it personally. Governance processes are starting to slow decisions under cover of “careful consideration.” Announcements are outpacing behavioural change — the classic rhetorical transformation pattern. This is Leadership Engagement Logic in early drift. The dangerous part isn’t the individuals; it’s that a leadership team performing AI engagement trains the whole organisation to do the same, and that’s how theatre scales.
Next 30 daysEach member of the senior leadership team writes down, in 200 words or less, how they personally used AI this week for real work. Share as a leadership team exercise, not a publication. The ones who can’t answer honestly reveal where the drift is. Post 6 (Lost Service Muscle) and Post 14 (Human Reset) cover the leadership presence issue.
Domain FFinancial Exposure and Hidden Cost
The true cost of service-culture drift hasn’t been quantified, and your board is making technology decisions from an incomplete picture. You can see the tech spend clearly; you can’t see churn, rework, escalation handling, and turnover in service-exposed roles clearly. That asymmetry always biases decisions toward more technology spend, because it’s the only side of the equation that has numbers. This is exactly the ROI Paradox from Post 10 — the hidden costs are real but invisible, so they lose every budget argument.
Next 30 daysCommission a hidden-cost estimate for the last 12 months: service-related churn (revenue lost), rework (hours × rate), escalation handling (volume × average cost), turnover in service roles (replacement cost × frequency). Even a rough number reframes the next technology investment conversation. Post 10 (Financial Pressures) is the frame.