Organizational Health Assessment
A sample TRUST assessment executive readout demonstrating what the framework delivers.
Assessment overview
47
Interviews conducted
6
Stakeholder groups
20
Dimensions assessed
Core finding
The technology organization has strong technical talent and genuine incident response culture, but significant perception gaps and leadership alignment issues are eroding stakeholder trust. The gap between how technology rates its own performance and how stakeholders experience it is the primary driver of organizational friction.
Operational health scorecard
20 dimensions assessed across delivery, culture, architecture, governance, and talent.
Deployment frequency
DORA
Lead time for changes
DORA
Mean time to recovery
DORA
Change failure rate
DORA
CI/CD maturity
Delivery
Measurement & KPIs
Delivery
Westrum culture
Culture
Change readiness
Culture
Team structure
Architecture
Cloud maturity
Architecture
Security posture
Governance
AI practices
Governance
Leadership health
Culture
Key person risk
Talent
Distributed teams
Talent
Budget transparency
Financial
Vendor ecosystem
Financial
Digital product
Product
Data analytics
Data
Innovation culture
Innovation
Perception gap analysis
How technology rates itself vs. how stakeholders perceive performance across key dimensions.
Largest perception gap
Budget transparency shows a 38-point gap between how technology rates itself (60%) and how stakeholders perceive it (22%).
Key findings
10 findings organized by category — from strengths to protect to trust gaps to address.
Evidence
The organization has a genuine blameless postmortem culture. Teams surface problems quickly, collaborate on fixes, and document learnings. This is rare and valuable.
Recommended action
Document and preserve this culture explicitly. Ensure it extends to newer teams and survives leadership transitions.
Evidence
Security posture scores 4.0/5.0 with strong DevSecOps practices, regular penetration testing, and effective incident response.
Recommended action
Maintain investment. Use security team as a model for operational excellence elsewhere.
Evidence
Finance describes technology spending as opaque. A structured monthly review would close the largest perception gap quickly.
Recommended action
Establish monthly review within 30 days. Include cloud cost dashboards, project-level spending, and investment ROI tracking.
Evidence
Leadership meetings are status reports, not working sessions. Restructuring creates space for real debate and decision-making.
Recommended action
Convert one weekly meeting to a working session format with pre-read materials and decision items.
Evidence
Stakeholders lack visibility into technology priorities and progress. A quarterly transparency report closes multiple perception gaps.
Recommended action
Create and publish first report within 60 days. Include metrics, priorities, wins, and challenges.
Evidence
Manual deployment steps create bottlenecks, key person dependencies, and limit deployment frequency. Current lead time is 2 weeks.
Recommended action
Invest in automated pipeline. Target: reduce lead time from 2 weeks to 2 days within 90 days.
Evidence
Five Dysfunctions assessment reveals fear of conflict and lack of commitment. This drives silo behavior throughout the organization.
Recommended action
Engage leadership team facilitator. Establish conflict norms and decision-making frameworks.
Evidence
The billing system is 12 years old, undocumented, and maintained by one person. It processes $50M annually and represents the highest single point of failure.
Recommended action
Begin migration planning. Secure budget. This is the highest-risk technical debt item.
Evidence
Technology rates delivery predictability at 60%. Stakeholders rate it at 32%. This 28-point gap is the largest perception mismatch.
Recommended action
Implement transparent delivery tracking. Share progress weekly. Set and meet smaller commitments to rebuild confidence.
Evidence
AI practices score 1.5/5.0 — the lowest operational dimension. Shadow AI usage exists without governance. Business units are using AI tools that technology doesn't know about.
Recommended action
Inventory current AI tool usage. Establish data governance guardrails. Create sanctioned tool list. Build AI strategy.
90-day transformation roadmap
Sequenced priorities organized into three phases, each building on the last.
Foundation and quick wins
Launch monthly Finance business review
Establish weekly leadership working sessions
Document and protect incident response culture
Begin stakeholder perception baseline
Inventory AI tool usage across organization
Strategic foundations
Launch CI/CD automation for top 3 bottlenecks
Begin leadership team effectiveness program
Establish AI governance guardrails
Begin legacy billing system migration planning
Publish first quarterly technology report
Momentum and measurement
Conduct 60-day stakeholder perception check
Measure DORA improvements from CI/CD changes
Assess leadership team progress on Five Dysfunctions
Plan Q2 priorities based on 90-day results
Beyond 90 days
The 90-day roadmap establishes foundation and momentum. The ongoing transformation continues with quarterly reassessments, expanded stakeholder feedback loops, and progressive capability building.
Want this for your organization?
Every TRUST assessment produces a tailored executive readout like this one — based on real interviews, real data, and real findings.
Start a Conversation