Where Does Your Organization Stand?
Structural Diagnostic Across the Five Circles
Digital transformation rarely fails because of a lack of ambition. In most cases, progress stalls because one structural layer of the enterprise remains unresolved — while investment, technology, and activity continue to accumulate on top of it.
The objective is not to optimize individual layers, but to understand whether the system is coherent across them.
This diagnostic is designed to produce a full structural profile across all five circles. Rather than routing to a single constraint, it shows the health of every layer simultaneously — because the relationship between circles matters as much as the score of any individual one.
Answer each statement based on what is actually true in your organization today. Not what is planned. Not what is occasionally true. Not what was true before the last reorganization. What is consistently, observably true right now.
Score each circle by counting ‘Yes’ responses:
• 6–8 Yes: Intact — this structural layer is functioning and supporting the circles above it.
• 3–5 Yes: Partial — this layer exists but has significant gaps that will constrain progress.
• 0–2 Yes: Critical — this layer is broken. Investment above it will fragment rather than compound.
Circle I — Strategic Clarity
Whether the organization has a shared, specific understanding of how technology reshapes the operating model.
Answer Yes or No to each statement based on what is actually true in your organization today — not what is planned, intended, or occasionally true.
• Leadership across the organization can articulate a consistent transformation hypothesis — not a vision statement, but a specific explanation of how platforms, data, and automation reshape how the business operates.
• Technology investment decisions are made with reference to a shared operating model, not driven primarily by vendor capabilities or departmental requests.
• When two business units propose competing digital initiatives, there is a clear, agreed basis for resolving the trade-off.
• The CTO and CEO would give substantially the same answer if asked separately how technology enables the enterprise growth model.
• New digital initiatives are evaluated against a defined architectural direction before funding is approved.
• The organization has not launched three or more significant digital programs in the last two years that were later deprioritized or abandoned due to strategic misalignment.
• There is explicit agreement at executive level about which capabilities should be platforms and which should be point solutions.
• Technology-driven structural improvements are tracked and reported at the same level as product delivery milestones.
Circle I Score: _____ / 8
Circle II — Architectural Foundation
Whether systems, data, and integration are designed to support reusable capability at scale.
Answer Yes or No to each statement based on what is actually true in your organization today — not what is planned, intended, or occasionally true.
• Core entities — customer, product, transaction, identity — have a single, consistent definition used across all systems.
• In the last 12 months, a new capability was built by extending an existing platform rather than building a new standalone system.
• When two systems need to share data, they do so through a governed interface — not a point-to-point integration or manual export.
• The number of integrations required to support a new initiative has stayed the same or decreased over the last two years.
• A new engineering team joining the organization can access and reuse existing platform capabilities without significant custom integration work.
• Analytics and reporting across different business units produce consistent results for shared metrics — revenue, customer count, product performance.
• Adding a new channel — mobile app, partner portal, new market — does not require rebuilding core business logic from scratch.
• The architecture team has authority to reject implementations that introduce duplication or violate data model standards.
Circle II Score: _____ / 8
Circle III — Organizational Foundation
Whether decision rights, incentives, and enforcement mechanisms are aligned so teams consistently reinforce the architecture.
Answer Yes or No to each statement based on what is actually true in your organization today — not what is planned, intended, or occasionally true.
• Business units use shared platforms as their default — not because they are required to, but because it is faster than building locally.
• Team performance metrics include platform reuse and contribution to shared capabilities, not only local delivery speed.
• When a team builds outside the shared platform under delivery pressure, this is treated as an explicit exception requiring leadership sign-off — not a default workaround.
• The organization has a clear owner for each shared platform who has authority and accountability for its evolution.
• In the last 12 months, at least one initiative that would have introduced architectural duplication was challenged and redirected.
• Deployment pipelines include automated checks that prevent non-compliant data models or integrations from reaching production.
• Incentive structures do not create situations where the fastest path for a team is to bypass shared infrastructure.
• Governance decisions about shared platforms are made before implementation begins, not after divergence has already occurred.
Circle III Score: _____ / 8
Circle IV — Capital & Execution Engine
Whether investment and delivery models continuously strengthen foundational capability rather than erode it.
Answer Yes or No to each statement based on what is actually true in your organization today — not what is planned, intended, or occasionally true.
• Foundational platform capabilities receive dedicated, continuous funding that persists across planning cycles — not episodic investment that resets each quarter.
• There is an explicit budget allocation for technical debt reduction and platform evolution, separate from product delivery funding.
• Platform investment decisions are not routinely overridden by product feature requests during mid-cycle reprioritization.
• The effort and time required to deliver new capabilities has decreased — or stayed the same — over the last 18 months.
• Technical debt is tracked, owned, and addressed on a defined schedule — not deferred indefinitely.
• Performance metrics for the technology organization include system-level efficiency measures, not only delivery velocity and output.
• The CTO can defend foundational investment in budget discussions with a clear economic model showing long-term return.
• When the organization has faced budget pressure, platform and foundational investments were protected rather than being the first items cut.
Circle IV Score: _____ / 8
Circle V — The Scalable System
Whether the system improves as it grows — where each new capability reduces the effort required for the next.
Answer Yes or No to each statement based on what is actually true in your organization today — not what is planned, intended, or occasionally true.
• New products or markets can be launched by extending existing platform capabilities — not by standing up new infrastructure.
• The coordination effort required to deliver new capabilities has decreased as the organization has grown.
• AI initiatives operate on consistent data and within defined workflows without requiring continuous manual oversight to correct outputs.
• Headcount in the technology organization has grown more slowly than transaction volume or capability output over the last two years.
• When a new engineering team is formed, they become productive using existing platforms within weeks — not months.
• Operational incidents caused by integration failures or data inconsistency have decreased year-over-year.
• The cost of operating the platform — infrastructure, maintenance, support — has grown more slowly than the value it delivers.
• The organization can absorb a significant increase in demand — 2x transaction volume, a new market, a major product launch — without a proportional increase in engineering effort.
Circle V Score: _____ / 8
Interpreting Your Profile
Transfer your scores to the profile below. The pattern across all five circles matters as much as any individual score.
| Circle | Your Score | Status | 6–8 Intact | 3–5 Partial | 0–2 Critical |
| I — Strategic Clarity | _____ / 8 | Intact / Partial / Critical | |
| II — Architectural Foundation | _____ / 8 | Intact / Partial / Critical | |
| III — Organizational Foundation | _____ / 8 | Intact / Partial / Critical | |
| IV — Capital & Execution | _____ / 8 | Intact / Partial / Critical | |
| V — The Scalable System | _____ / 8 | Intact / Partial / Critical |
Profile Shapes
Each profile represents a dominant structural constraint. In every case, the priority is not to advance further — but to resolve the constraint first.
Most organizations will recognize themselves in one of six common structural profiles. In each case, the primary constraint is identified and the immediate priority is named.
A Note on Mixed Profiles
Most organizations will not fit cleanly into a single profile. Architectural coherence may exist alongside organizational misalignment. Capital discipline may coexist with strategic ambiguity. This is normal.
In a mixed profile, it is tempting to continue advancing the stronger circles while deferring the weaker ones. This approach will not hold. The weakest circle will eventually constrain everything built above it.
Address the lowest-scoring circle first, regardless of where momentum currently exists. The circles are sequential by design. A foundation that is not solid will fragment everything built on top of it — and it will do so at exactly the moment the enterprise is trying to scale.