Symptoms tell you something is wrong. Dynamics tell you why.
Most organizations have a long list of symptoms. Initiatives that stall. Strategic decisions that don’t get executed. AI projects that consume budget without producing value. Teams that don’t trust each other. Leadership that doesn’t know what’s actually happening on the ground.
Fixing symptoms — running another initiative, hiring another consultant, deploying another tool — produces short-term motion. The symptoms come back, because the dynamics underneath are still operating.
The leaders who get organizational change right look underneath. They examine incentives, structure, communication patterns, and how decisions actually get made versus how they’re supposed to get made. They look at the gap between stated values and lived behavior. They look at where the organization is fighting itself.
TRUST is the structured way to do that work.
Four principles shape every engagement.
These principles are how TRUST is run, not what it covers. They show up in how stakeholders are interviewed, how findings are reviewed, how the deliverable is structured, and how the engagement holds itself accountable.
Transparency over insulation.
Too many technology leaders hold information too tight, creating a black box that breeds distrust with business partners. TRUST runs on the opposite premise. When stakeholders understand what is being assessed and why, alignment follows.
Perception is data.
How the organization is perceived by Finance, HR, Product, and executive leadership is as important as any technical metric. Perception gaps are trust gaps. TRUST treats these perceptions as evidence, not opinion.
Measure what matters.
The research in Accelerate and the DORA metrics — deployment frequency, lead time, mean time to recovery, change failure rate — provide an evidence-based foundation for understanding organizational performance. These aren’t just engineering metrics. They’re indicators of organizational health.
No surprises.
Any findings attributed to a group are reviewed with that group before broader presentation. The technology leadership team participates in and owns the entire assessment process. The executive readout contains nothing the relevant stakeholders haven’t already seen.
One methodology. Three applications.
The TRUST methodology shape — six phases, four principles, structured deliverables — is consistent across every application. What changes is the entry posture, the duration, and the relationship between the practitioner and the organization.
New Leader Transition.
A new technology leader entering an organization uses TRUST as their structured first-90-days approach. Anchored to the executive onboarding window: thirty days of learning, thirty days deepening assessment and beginning synthesis, thirty days producing findings and a path forward. The practitioner is of the organization — they have a mandate, a team to lead, and a long-term role.
Consulting Engagement.
An external consultant or advisor uses TRUST as a structured diagnostic for a client organization. Duration is scope-driven and complexity-driven. Typical ranges: 6–8 weeks for smaller organizations or focused-scope engagements; 9–12 weeks for typical mid-market engagements; 16+ weeks for larger or more complex enterprise engagements. Each engagement is scoped specifically. The practitioner is engaged by the organization with a defined sponsor, deliverable, and finite engagement window.
Leadership Development.
TRUST also serves as a model for entering new situations — whether as a new leader, a project lead inheriting a team, or a senior contributor stepping into broader responsibility. The framework is used as a thinking structure rather than a calendar-bound engagement. The practitioner is learning the methodology and applying it to their own situation.
A focused inquiry — or two.
A TRUST engagement examines an organization through one or more focus lenses. The lens determines which questions are asked in stakeholder interviews and which dimensions get the operational deep dive. The methodology’s phases, principles, and deliverable structure are consistent regardless of lens.
Lens 1 — Technology & Organizational Transformation.
The original lens. Focused on technology delivery effectiveness — engineering performance, organizational design, technical practices, operational maturity, and the leadership and cultural conditions that determine whether the organization can execute. Used when the engagement is centered on making an IT, software, or technology organization more effective.
Explore the dimensions →Lens 2 — AI Readiness & Strategy.
Focused on whether and how the organization can leverage AI to advance its business strategy. Examines AI strategy alignment, current AI use, AI fluency, AI risk and governance, market and competitive context, AI investment and ROI posture, capability acquisition posture, agentic capability and workforce, and organizational capacity for AI.
Explore the dimensions →When both lenses are applied in a single engagement, the deep dive covers dimensions from each. The two inform each other — AI strategy decisions surface organizational implications, and organizational realities constrain AI strategy options.
A structured path from question to evidence to action.
TRUST runs in six sequenced phases. Each produces specific outputs that feed the next. By the end, leadership has a comprehensive picture, a written report, and a prioritized action plan they own.
Phase 1 — Introduction & Transparency
Establishing what TRUST is, what it isn’t, and how it will run. Aligning with the engagement sponsor on scope, lens (or lenses), and stakeholder list. Setting expectations about transparency, the No Surprises Principle, and how findings will be shared. This phase is short but critical — it’s where the principles get demonstrated, not just stated.
Phase 2 — Perception & Partnership Assessment
Structured conversations with business partners — Finance, HR, Product, business units, executive leadership, board members where applicable. Designed to surface how the organization is perceived from the outside in: where trust exists, where it doesn’t, what business partners need from technology that they’re not getting, where the gaps between expectation and delivery live. Perception, in TRUST, is data. Perception gaps are trust gaps.
Phase 3 — Leadership Team Assessment
Focused work with the technology leadership team itself. Where is alignment real and where is it performative? How do strategic decisions actually get made? What conversations don’t happen that should? Uses the Five Dysfunctions lens — trust, conflict, commitment, accountability, results — alongside structured interviews with managers and individual contributors to understand the team from multiple angles.
Phase 4 — Operational Deep Dive
Examination of the organization’s operational dimensions. The depth and breadth depend on the lens (or lenses) being applied. Each lens has its own dimension set, detailed below. Phase 4 is typically the longest phase. The published questions are starting points; the engagement follows where the answers lead.
Phase 5 — Synthesis & Alignment
Pulling everything together. What does the evidence say? What patterns connect across the layers? What are the highest-leverage interventions? Where is leadership ready to act, and where will resistance show up? Phase 5 is governed by the No Surprises Principle. Findings are reviewed first with the technology leadership team, then with the business partners whose teams contributed perceptions, before being presented to executive leadership. The point isn’t to soften messages — it’s to build accuracy, ownership, and trust in the conclusions. This phase produces the written TRUST Framework Report and the structured Findings Framework.
Phase 6 — Strategy & Roadmap
The assessment culminates in a transformation roadmap that translates findings into action. The roadmap balances quick wins that build momentum with longer-term strategic investments that transform capability. The point of the readout is not the report. It’s the alignment that comes from leadership confronting the evidence together — and committing to a path forward they own.
Findings organized into action.
The output of TRUST isn’t a report. It’s a framework for action, structured so leadership can move on what matters first.
Strengths to Protect
What’s working well that we must not break in the course of change.
Quick Wins
High-impact improvements that can be made with relatively low effort. Build early momentum and demonstrate that change is real.
Strategic Priorities
Significant initiatives that require investment but transform capability.
Technical Debt
Infrastructure and systems that require attention to enable future progress.
Trust Gaps
Perception misalignments that need to be addressed through transparency and delivery.
Where Lens 1 looks.
The Operational Deep Dive for Lens 1 covers twenty-one dimensions across leadership, operations, technology, people, and the cultural conditions that shape execution. The dimensions adapt to organizational context. Each dimension shows what we’re examining, what that examination tells us, and the starting questions we use. The questions are starting points; the engagement follows where the answers lead.
Where Lens 2 looks.
The Operational Deep Dive for Lens 2 covers nine dimensions specific to whether and how the organization can leverage AI to advance its business strategy. Each dimension shows what we’re examining, what that examination tells us, and the starting questions we use. The questions are starting points; the engagement follows where the answers lead.
Across the nine dimensions, the AI Readiness lens surfaces:
- Whether AI strategy is real and connected to business strategy, or aspirational and disconnected
- What AI is actually happening in the organization (visible and shadow)
- Where capability and fluency live, and where they don’t
- What risks are being carried, knowingly or otherwise
- How the organization is positioned competitively in an AI-reshaping market
- Whether AI investments are evaluated and producing returns
- How the organization decides what to build, buy, or partner for
- How agentic AI fits alongside the human workforce
- Whether the organization can absorb AI-driven change at the pace AI is moving
The lens output feeds into the standard TRUST deliverables: the Framework Report, the Findings Framework, the Risk/Readiness Scorecard, the Strategy & Roadmap, and the Executive Readout.
The depth comes from iteration.
The questions on this page — across both lenses — are starting points. They show the shape of what TRUST examines: the dimensions we look at, the kinds of questions we ask, the structure of inquiry.
The diagnostic depth doesn’t come from a longer list of questions. It comes from following where the answers lead. Each answer opens up follow-on questions we wouldn’t have known to ask without the first. Patterns surface across dimensions. Connections emerge that no single question would have revealed. Nuances appear that change the interpretation of earlier answers.
This is what makes TRUST a methodology rather than a survey. The published questions are how we enter; the engagement is how we go deeper.
Evidence, alignment, and a path forward.
The deliverables are consistent across all engagements. The depth scales with the engagement scope.
TRUST Framework Report
The written document. Findings across the dimensions covered, supported by aggregated evidence from the assessment. Designed to be read by leadership, board members, and PE sponsors — not consultants.
Findings Framework
Findings organized into the five categories (Strengths to Protect, Quick Wins, Strategic Priorities, Technical Debt, Trust Gaps). Structured so leadership can move on what matters first.
Risk/Readiness Scorecard
A structured rating across the dimensions covered. Where the organization is ready to execute, where it’s exposed, where intervention is most needed. Useful for ongoing tracking after the engagement closes.
Strategy & Roadmap
Specific, sequenced recommendations. Not a wish list. The interventions most likely to unlock execution, balanced between quick wins and strategic investments.
Executive Readout Session
Live facilitation of leadership through the findings. The session where alignment actually happens.
Sample readout available — View an anonymized TRUST sample readout to see the format and depth of the deliverables.
When the work calls for evidence, not opinions.
TRUST is the right call when leadership is making a decision that’s too big for opinions. A new strategic direction. A significant AI investment. A post-acquisition integration. A board-level question about whether the organization can execute on what it’s promising. The leaders who get these decisions right don’t guess at the answer — they get evidence.
It’s the right call when the leadership team is divided, but no one can articulate exactly why. The disagreement is real, but it’s tracking something that hasn’t been named. TRUST surfaces what’s underneath.
It’s the right call when symptoms keep recurring. Initiatives that stall. Decisions that don’t get executed. The same patterns showing up under different banners. The leaders who get organizational change right look at the dynamics — not just the symptoms.
It’s the right call before a significant AI or technology investment. The organizations that succeed aren’t the ones with the best tools. They’re the ones who understood their own dynamics before they started.
The leaders who get this right don’t run TRUST because something is broken. They run it because they’re about to make decisions that are too important to make blind.
If TRUST is the work, let’s talk about it.
A 30-minute conversation about your situation, where the evidence might land, which lens (or lenses) fit, and what the right scope looks like. No pitch — a real conversation about whether this is the right work right now.
jason@drag6.com