The operating rhythm here is a weekly routing huddle with Friday close-out, three monthly reviews, and a 14-day cycle every 90 days. The Core Execution Cadence Diagnostic scores six dimensions of that rhythm on a 0 to 5 scale. Each red dimension proposes its owning remediation playbook.
Where the Operating Rhythm Breaks Between Plan and Action
The Core Execution Cadence Diagnostic scores Core Execution, one module of the VWCG OS, against written anchors. Those anchors describe a broken operating rhythm in concrete terms, not in general complaints. At a score of 1, diagnostics have not re-run in 6 or more months, and quarters start on old data. The heat-map updates, yet no downstream parameter ever changes, and the system stays static.
Priorities come from negotiation or founder preference, and the diagnostics sit ignored by the leadership team. Weekly meetings turn into discussion forums, issues get resolved in the room or not at all, and no close-out happens. Diagnostics run on stale, unverified data, and the preparation checks never happen at all.
The wrong question asks who dropped the ball on a stalled initiative during the last month. A better question asks which of the six dimensions sits at its low anchor today. That shift turns blame into a reading that the team can check against written anchors.
Consider a hypothetical mid-market services firm that sets quarter priorities by negotiation rather than evidence. Diagnostic-Driven Priority Sourcing describes that exact state at its score of 1. At a score of 3, priorities reference the heat-map, but judgment-set items slip in unchallenged. At a score of 5, every quarter priority names its source cells, and persistent reds and worsened cells get addressed first.
The Anti-Pattern of the Reactive Quarter
A reactive quarter shows up in Weekly Routing Hygiene, one of the four dimensions weighted at 0.15 each. The dimension checks whether the huddle routes red metrics to owning modules instead of resolving them in the room. It also checks whether the Friday close-out happens and whether the team tracks action closure.
At a score of 3, routing happens for obvious cases, and borderline issues get debated in the room. The Friday close-out at that middle anchor happens only sporadically, not every week. At a score of 5, the huddle is routing-only, and every red metric lands in a module protocol. At that top anchor, the Friday close-out never misses a single week.
Imagine a hypothetical founder-led operation where the weekly huddle resolves every issue inside the room. Red metrics never reach the modules that own them, which matches the low anchor for this dimension. A red reading here routes to the Weekly and Monthly Rhythm Restoration playbook and to huddle format restoration in the KPI Precision Grid module.
Diagnose Before Reacting
The diagnostic scores six dimensions on a 0 to 5 scale against written anchors. The composite score is a weighted sum of those six separate dimension scores.
Two dimensions carry a weight of 0.20 each in that weighted sum. Diagnostic Re-Run Discipline and Parameter Cascade Execution hold those two heavier weights. The other four dimensions carry a weight of 0.15 each in the same calculation.
Scorer agreement has not yet passed the reliability test, a status the routing rules state openly. A route that fires from a scored dimension is a proposal until leadership confirms it. Confirmation comes at the next monthly governance review or the Phase 3 review of the Core Execution module, whichever comes first. The stated duration of a playbook starts at that confirmation, not at the original reading.
The Diagnostic Framework and Its Six Dimensions
Diagnostic Re-Run Discipline checks whether the full Intelligent Foundations diagnostic re-ran on schedule in each of the last two quarters. It also checks whether all 14 dimensions produced fresh scores and whether the cycle finished inside the days 1 to 3 window.
Parameter Cascade Execution counts documented parameter changes per quarter and traces them to heat-map cell changes. The tracked parameters include governance intensity, automation permissions, and timelines for each quarter. At a score of 5, every heat-map delta produces a documented parameter change or an explicit hold decision with reason.
Pre-Diagnostic Preparation checks whether the weeks 11 to 12 preparation ran before the last two recalibrations. That preparation covers three checks: SOP currency, data integrity, and verified client health scores. At a score of 5, all three checks finish every quarter before the first phase begins.
A reader can bring outside lenses to these six dimensions without changing the instrument itself. The balanced scorecard offers one such lens for comparing weighted measures across a leadership agenda. Theory of constraints offers another, prompting a reader to ask which red dimension limits the rest. RACI, applied separately by the reader, can clarify who answers for each recorded review decision.
Scoring Bands and Routing
The composite score falls into one of three bands on the 0 to 5 weighted scale. Red runs from 0.0 up to but not including 2.0 on that scale. Amber is 2.0 to 3.5 inclusive, and green is above 3.5 up to and including 5.0. The bands cover the full scale with no gaps and no overlaps.
A red dimension fires its routes and proposes its owning remediation playbook. Safety routes set AI mode, the Privacy Impact Assessment rule, or classification and response windows in the Cyber, Data Privacy, and Security module. Those safety routes tighten on the first reading and loosen only after an independent re-score clears the edge. Every amber dimension routes to the Cadence Monitoring (Amber Path) playbook with 30-day pulse checks.
Green dimensions hold and receive quarterly monitoring through the Core Execution module. Green Weekly Routing Hygiene gets weekly monitoring, and green Monthly Governance Completeness gets monthly monitoring instead.
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 0 to 5 scales and 5 points on the AERI 0 to 100 scale.
Suppose Weekly Routing Hygiene scores red when the module instruments are scored in weeks 11 to 12. That red fires two routes, one to the Weekly and Monthly Rhythm Restoration playbook and one to huddle format restoration. A route that restores the cadence itself acts on the reading at once. Any other route from a scored dimension waits for leadership confirmation before its stated duration starts.
The Four-Phase Cycle That Carries the Quarter
The published quarter runs a 14-day four-phase cycle every 90 days. Phase one re-runs the full Intelligent Foundations diagnostic on days 1 to 3 and produces 14 fresh dimension scores. On days 4 to 5, the second phase updates the heat-map with a quarter diff.
The third phase executes the parameter cascade across the 11 routed modules on days 6 to 8. On days 9 to 14, the fourth phase sets quarter priorities from red, worsened, and persistent cells. Every cell delta produces a documented parameter change or an explicit hold with reason. Every quarter priority names its source cells in writing, and the full cycle record archives for diligence readiness in the Exit and Acquisition Layer module.
The Quarterly Recalibration Cycle playbook runs this cycle as a standing quarterly duty. A red score on Diagnostic Re-Run Discipline, Parameter Cascade Execution, or Diagnostic-Driven Priority Sourcing also triggers it. The CEO owns the playbook, with the COO as cycle steward, for 14 days every 90 days.
An owner who is also weighing supply chain management consulting for mid-market growth can still apply one test from this cycle. Does every quarter priority name its source cells, or did negotiation set the list this quarter?
An owner comparing crisis management consulting firms after a hard quarter can ask that same question first.
Restoring the Weekly and Monthly Operating Rhythm
The Weekly and Monthly Rhythm Restoration playbook triggers when Weekly Routing Hygiene, Monthly Governance Completeness, or Pre-Diagnostic Preparation scores red. The COO owns it, and its stated duration is 4 weeks to restore. It audits the last 8 weeks of huddles, close-outs, and monthly reviews. It then re-contracts the weekly rhythm and the three named monthly reviews in writing with calendar holds.
The playbook runs two restored cycles with the COO attending as format enforcer. It rebuilds the weeks 11 to 12 preparation checklist with named owners. It reports rhythm health to the Intelligent Foundations heat-map at the next recalibration. When failure persists, the playbook escalates it to a DNA accountability check.
The outcome requires two consecutive clean weeks of huddle plus close-out. It also requires one clean month with all three reviews and decision logs. A preparation checklist with named owners and an active drift log complete the outcome. After that, the operating rhythm runs under the Cadence Monitoring (Amber Path) playbook.
An owner who is reviewing revenue management consulting can apply value-based pricing and unit economics as separate outside lenses. Neither lens belongs to this diagnostic or its playbooks, and each answers a different question about the business.
How Playbooks Open, Queue, and Close
Every playbook follows one lifecycle: open, running, met or missed, escalated, and closed. A trigger that arrives while a playbook is open is logged against the open run. Each owner runs at most three red playbooks at once, so a third red still opens. A fourth red and any later red queue, ranked by how many modules the red dimension routes into.
Safety playbooks never queue, whatever the count of open red playbooks for that owner. A route that changes a mode, a cadence, or a data feed runs under the standing playbook of its module. Standing duties that a met red playbook set up continue there and do not count toward the cap.
An outcome met, with an independent re-score at amber or better, closes the run. The next queued red for that same owner then opens in its place. Someone other than the playbook owner always re-scores the dimension.
An outcome missed at the end of its stated duration escalates to the manager of the owner. It also joins the next quarter planning agenda of the Core Execution module. For a playbook the CEO owns, escalation goes to the board instead.
A reader can apply VRIO separately to ask whether a steady cadence counts as a rare capability. Teams that already use OKR can compare their objectives with the source cells each quarter priority names. None of these outside lenses changes the weights, bands, or routes of the diagnostic itself.
Frequently Asked Questions
- What is the Core Execution Cadence Diagnostic?
- The Core Execution Cadence Diagnostic scores six dimensions on a 0 to 5 scale against written anchors. A weighted sum turns those six readings into one composite score. That composite falls into a red, amber, or green band. A red dimension proposes its owning remediation playbook, and every amber dimension routes to monitoring with 30-day pulse checks.
- How are the six dimensions weighted?
- The weighted sum gives two dimensions a weight of 0.20 each. Those are Diagnostic Re-Run Discipline and Parameter Cascade Execution. The other four dimensions carry a weight of 0.15 each. They cover priority sourcing, weekly routing hygiene, monthly governance completeness, and pre-diagnostic preparation.
- What are the three scoring bands and their ranges?
- Red is 0.0 up to but not including 2.0. Amber is 2.0 to 3.5 inclusive. Green is above 3.5 up to and including 5.0. The bands cover the full scale with no gaps and no overlaps. A color changes only when a score clears the band edge by 0.25 points or holds for two consecutive scorings.
- What happens when a dimension scores in the red band?
- A red dimension proposes the owning remediation playbook. Cadence-restoring routes act on the reading. Other routes from a scored dimension wait for leadership confirmation at the next monthly governance review or the Phase 3 review of the Core Execution module, whichever comes first. Each owner runs at most three red playbooks at once, so a fourth queues.
- What is the 14-day four-phase cycle?
- The cycle runs every 90 days. The first phase re-runs the full Intelligent Foundations diagnostic on days 1 to 3. On days 4 to 5, the second phase updates the heat-map. Days 6 to 8 carry the parameter cascade across the 11 routed modules. Days 9 to 14 set quarter priorities from red, worsened, and persistent cells.
- How does World Consulting Group help an owner act on a broken execution cadence?
- World Consulting Group offers the Core Execution Cadence Diagnostic and its remediation playbooks as an implementation service. The first step of the engagement is a scoring pass of the six dimensions against the written anchors. That pass produces the composite score and the band for each dimension, which decide the routes that follow.
