The Integrated Tech Stack Diagnostic scores integration architecture as pattern fit, inventory, data quality, change control, and shadow IT.
It scores each of the five dimensions on a 0 to 5 scale, weighted 0.20 each.
A red score proposes the owning playbook for architecture, data quality, or governance.
What the Lowest Anchors Describe
The lowest data quality anchor describes dashboards that show numbers nobody trusts. At that score, the diagnostic finds no checks running on the data at all. The lowest change control anchor describes changes made live with no review. Downstream modules then discover the broken integrations.
The lowest inventory anchor describes no inventory and owners left unnamed. At that score, the company cannot state its tool count within a range. The lowest shadow IT anchor describes teams that adopt tools freely, with no scans. Unknown data flows then sit outside the hub.
The lowest anchor for integration architecture describes point-to-point spaghetti, where a change in one system breaks three others. That anchor applies at 10 or more tools with no blueprint. At a score of 3, a hub exists, but the blueprint stays partial.
Before anyone selects a hub platform, the Hub-and-Spoke Consolidation Sprint confirms the diagnostic constraint from the Intelligent Foundations module. An Architecture Pattern Fit red also asks that module to confirm its own Tool Stack Compatibility red.
How the Anchors Read Integration Architecture
Several inbound routes from other modules point at the same stack. A Cross-Functional Collaboration red in the Intelligent Foundations module prioritizes system integration over tool optimization. In that module, a Data Hygiene red requires data centralization before any AI project. A Tool Stack Compatibility red makes Hub-and-Spoke architecture non-negotiable.
Consider a hypothetical distributor with point-to-point connections across 10 or more tools and no blueprint. The written anchors place that architecture at the score of 1 anchor for Architecture Pattern Fit. That firm would then see an Architecture Pattern Fit red propose the Hub-and-Spoke Consolidation Sprint. Leadership would confirm that proposal before the 8-week duration starts.
The top anchor for integration architecture asks for a single blueprint of the stack. That blueprint shows every system, connection, and data flow, and it must pass the 60-second new-hire test. A partial blueprint, or none at all, shows up directly in the score.
The Integrated Tech Stack Diagnostic
Owners who want outside background can read about business systems work as a separate topic. A measured reading of the stack tells an owner where the weak dimensions actually sit. The Hub-and-Spoke Consolidation Sprint also maps all point-to-point connections as part of its work.
The Integrated Tech Stack Diagnostic scores 5 dimensions on a 0 to 5 scale against written anchors. Each dimension carries an equal weight of 0.20 per dimension in the composite. The composite score is a weighted sum of the five dimension readings. Three standing page metrics carry the published thresholds that the checks use.
The diagnostic is one module instrument inside the VWCG OS operating system, and its routes reach other modules. A red data quality reading also routes work to the KPI Precision Grid module, which restricts its baseline to sources that passed the parity check. A red inventory reading marks systems-map evidence stale in the Exit and Acquisition Layer module until the inventory reaches amber.
The Dimensions Behind the Score
Architecture Pattern Fit asks whether the current integration architecture pattern is identified and whether a blueprint exists. It also asks whether the pattern matches the configuration the Intelligent Foundations module requires when AERI tool stack compatibility is red. The middle anchor describes a hub with unmanaged workflow sprawl, known as the 80-workflow pattern. The top anchor requires a single blueprint that passes the 60-second new-hire test.
System Inventory Completeness asks whether the System Inventory Sheet covers every tool with all five fields. Those five fields are owner, API access availability, data objects captured, refresh cadence, and monthly cost. The sheet must stay current within the quarter, and a complete sheet is diligence-ready. Owners who want separate background can read about inventory management consulting as well.
Data Quality Monitor Performance asks whether all three published checks are live and owned. Row-count parity runs a daily CRM versus warehouse check, and divergence above the 1% threshold flags a sync failure. A nightly fuzzy-match bot counts duplicate records on email and company name. A 15-minute latency alert pings the Integration Steward, and the KPI Precision Grid weekly review needs data no older than 24 hours.
Change Control Governance asks whether changes are ticketed, impact-reviewed, and staging-tested under a coded SOP with 90-day review. Shadow IT Containment asks whether a quarterly SaaS discovery scan runs and whether net-new platforms require CFO and CISO signoff. Each dimension carries its own anchors, and each one routes on its own reading.
Bands, Margins, and Routing
A composite score falls into one of three published bands with no gaps or overlaps. Red runs from 0.0 up to but not including 2.0. Amber covers 2.0 to 3.5 inclusive, and green runs above 3.5 up to and including 5.0.
A color changes only when a score clears the band edge by a margin, or holds for two consecutive scorings. The margin is 0.25 points on the 0 to 5 scale and 5 points on the AERI 0 to 100 scale. A score that crosses an edge by less than the margin keeps its old color until a second scoring confirms it. Safety routes differ, because they tighten on the first reading.
Amber dimensions route to the Stack Hygiene and Amber Monitoring playbook with 30-day pulse checks. Green dimensions hold and are monitored quarterly through the Core Execution module, with event-driven handling for the new-integration signal. A red dimension proposes the owning remediation playbook rather than opening it at once. Leadership confirms that proposal at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first.
From Red Score to Remediation Playbook
A red reading is a proposed route with a named owner and a stated duration that starts at confirmation. A jobs to be done lens can help an owner ask what each system was hired to accomplish. That question stays outside the method.
Architecture Pattern Fit or System Inventory Completeness red proposes the Hub-and-Spoke Consolidation Sprint. An AERI red on tool stack compatibility can trigger the same sprint. The Integration Steward owns it at 10% FTE minimum with a COO sponsor, and it runs 8 weeks. Connections migrate into the hub in dependency order, starting with the KPI Precision Grid dashboard feeds.
Data Quality Monitor Performance red proposes the Data Quality Monitor Standup, and data-quality reds from other modules can also trigger it. It instruments the three published checks, then triages and fixes first-week findings at the source system. The Integration Steward owns the run, which lasts 3 weeks. Monitor output flows to the KPI Precision Grid module so dashboard trust is visible on the KPI grid.
Change Control Governance or Shadow IT Containment red proposes Change Control and Steward Activation. The playbook drafts the change-control SOP, registers it in the SOP Codex module, and moves all stack modifications onto the ticket path. It also runs the first quarterly shadow IT scan and records findings in a remediation log. The Integration Steward owns it, with the COO, CFO, and CISO for net-new signoff, over 4 weeks.
Governance, Shadow IT, and Trust
A RACI lens maps cleanly onto the assignments the method already states. The Integration Steward owns all four playbooks, and the COO sponsors the Hub-and-Spoke Consolidation Sprint. The CFO and CISO sign off on net-new platforms. Applying that lens as an outside check helps an owner confirm that nobody holds a role by assumption.
A balanced scorecard lens suggests that integration health deserves a place beside financial measures. The instrument treats data quality as an operational condition with published thresholds and a named steward. An owner can apply that lens by asking which reported numbers depend on the checks. A SWOT lens can also help an owner list which systems act as strengths and which create weaknesses.
Suppose the daily CRM and warehouse counts in a firm diverge by more than 1%. The row-count parity check flags a sync failure. The Integration Steward acknowledges the alert, and that acknowledgement is tracked. That dimension counts the tracked acknowledgement as part of its measure.
What the Diagnostic Protects
Downstream modules, including People and Culture Analytics, consume trusted data at the top data quality anchor. Owners can read about HR management consulting systems that scale people operations as separate background. The Hub-and-Spoke Consolidation Sprint migrates people data into the hub after the dashboard, health-score, and pipeline feeds. People data therefore sits inside the governed flow rather than outside it.
A theory of constraints lens suggests treating the least reliable link in the data chain as the constraint. Widening every other link may add cost without adding throughput. The lens is an outside aid for setting priorities, not a step inside the playbook.
A unit economics lens asks what each tool costs against the work it supports. The System Inventory Sheet records monthly cost as one of its five fields. The diagnostic supplies the reading, and the owner supplies the economic judgment.
Suppose a founder-led operation adds a new platform to answer a reporting complaint. The new-integration signal then routes to the Cyber, Data Privacy, and Security module, which requires a privacy impact assessment before connect, plus CFO and CISO signoff evidence. The PIA status signal from that module blocks go-live until the assessment completes. A Shadow IT Containment red also requires net-new platform spend to fit an Agile Capital Allocation funding tier.
Frequently Asked Questions
- What are the five dimensions scored by the Integrated Tech Stack Diagnostic?
- The diagnostic scores Architecture Pattern Fit, System Inventory Completeness, Data Quality Monitor Performance, Change Control Governance, and Shadow IT Containment. Each dimension carries a weight of 0.20 per dimension. Those readings combine into one weighted composite score on the 0 to 5 scale.
- What does a red composite score route to?
- A red score proposes the owning remediation playbook for the red dimension. The red band runs from 0.0 up to but not including 2.0. Leadership confirms the proposal at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first. Safety routes act on the first reading instead of waiting for confirmation.
- What is the margin required to change a color on a 0 to 5 scale?
- The margin is 0.25 points on the 0 to 5 scale. On the AERI 0 to 100 scale, the margin is 5 points. A color changes only when a score clears the band edge by that margin, or holds for two consecutive scorings. The rule keeps one reading near an edge from moving the color on its own.
- How long is the duration of the Hub-and-Spoke Consolidation Sprint playbook?
- The Hub-and-Spoke Consolidation Sprint runs 8 weeks, and that duration starts when leadership confirms the route. It builds the System Inventory Sheet for every tool and maps all point-to-point connections. The single blueprint must pass the 60-second new-hire test, and the Integration Steward works at 10% FTE minimum with a COO sponsor.
- What triggers the Data Quality Monitor Standup playbook?
- Data Quality Monitor Performance red triggers it, along with a data-quality red routed in from the Intelligent Foundations, KPI Precision Grid, Client Success Loop, Sales Velocity Engine, or Core Execution module. The playbook instruments the three published checks and triages first-week findings at the source system. The Integration Steward owns the run, which lasts 3 weeks.
- What does an owner do next after the diagnostic returns a red score?
- World Consulting Group implements the Integrated Tech Stack Diagnostic as part of its VWCG OS service. The first step of the engagement is a scoring pass of the five dimensions against the written anchors. Leadership then confirms each proposed red route at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first.
