AI-DLC Governance & Metrics Dashboard
Delivery is still happening. Is it still actually AI-DLC?
A recurring Excel workbook (v1.1) for teams already running AI-DLC in production, completed weekly or monthly by a Programme Manager or AI-DLC Coach. It tracks 11 operational indicators across Bolt delivery, Mob ritual health, gate integrity, and quality/outcome metrics — rolling them into a single Delivery Health Score and a sharper Ritual Discipline Flag purpose-built to catch methodology drift before it shows up in defect counts. Includes a full .pdf User Guide. No macros, no code, no external data connections.
Delivered as an Excel workbook with a full User Guide. Download immediately after purchase.
■ Instant download · ■ No macros · ■ Excel 2016+
The AI-DLC Governance & Metrics Dashboard is a recurring Excel tracker completed weekly or monthly by a Programme Manager or AI-DLC Coach. It tracks 11 operational indicators across Bolt delivery, Mob ritual health, gate integrity, and quality/outcome metrics, rolling them into a Delivery Health Score (1–3 scale: HEALTHY, WATCH, AT RISK) and a Ritual Discipline Flag that fires only when Mob Elaboration attendance, Mob Construction attendance, and the Human Validation Gate Pass Rate are all three simultaneously degraded — the specific signature of AI-DLC quietly drifting into an AI-managed or AI-assisted anti-pattern.
Delivery still happening isn’t proof the methodology is still intact.
Once an organisation is live on AI-DLC, the operating risk shifts. The question stops being “will this work” and becomes “is this still actually AI-DLC, or has it quietly degraded into an AI-assisted anti-pattern” — rituals skipped under delivery pressure, gates rubber-stamped, context left stale. Without a recurring instrument, that drift is invisible until quality or velocity visibly suffers.
These failures are invisible on a delivery burndown. They become visible in an audit, an incident, or a quarter of declining quality no one flagged in time. This dashboard is the recurring instrument that catches drift while it is still cheap to correct.
Two linked trackers. One Governance Dashboard. Two decisive signals.
11 indicators, split across delivery/ritual health and quality/outcome, roll into a Delivery Health Score and a sharper Ritual Discipline Flag purpose-built to catch methodology drift early. Every RAG threshold references a target your own organisation sets on the Settings tab — there are no fixed industry defaults.
Bolt & Ritual Tracker · 6 Indicators · Completed Each Reporting PeriodRitual Discipline Flag — a deliberately sharper, separate signal. It fires only when Mob Elaboration attendance, Mob Construction attendance, AND the Human Validation Gate Pass Rate are all three simultaneously Amber or Red. A single weak indicator among these three does not trigger it — this specific combination is the signature of AI-DLC quietly degrading into an anti-pattern, not an isolated bad week. When it fires, treat it as a governance escalation to the AI-DLC Coach and engineering leadership, not a line item in a status report.
- Delivery Health Score
- All 11 indicators converted to a 3/2/1 scale (Green=3, Amber=2, Red=1) and averaged, equally weighted, into a single 1–3 figure. 2.5–3.0 is HEALTHY, 2.0–2.49 is WATCH, below 2.0 is AT RISK.
- Ritual Discipline Flag
- A sharper signal, separate from the Delivery Health Score, that fires only on the simultaneous three-way combination of Mob Elaboration attendance, Mob Construction attendance, and Human Validation Gate Pass Rate all being Amber or Red — the documented signature of AI-DLC drifting into an AI-managed or AI-assisted anti-pattern.
Every tab, explained.
One Microsoft Excel workbook (.xlsx) containing six tabs. Only Settings, the two tracker tabs (Input A/Input B columns), the Historical Log, and the Portfolio Rollup panel take input — everything else on the Governance Dashboard is locked and calculated.
Governance & Metrics Dashboard vs. the rest of the AI-DLC product line.
This is one instrument in a set of three, each answering a different question at a different cadence. Using the wrong one for the moment you’re in is the most common way governance gaps go unnoticed.
| Instrument | Question It Answers | Cadence |
|---|---|---|
| AI-DLC Pilot Selection & Portfolio Segmentation | Which team or system should we start with? | One-time gate, before selection |
| Viksya AI-DLC Governance & Metrics Dashboard | Is anything wrong right now — is the methodology still intact? | Weekly or monthly, ongoing |
| AI-DLC Maturity Model & Benchmarking | How well are we actually operating, and are we improving? | Periodic, typically quarterly |
| Ad hoc status reporting (no instrument) | Whatever gets mentioned in a stand-up or steering deck | Irregular, no RAG thresholds |
Built for whoever owns the number each period — and whoever has to act on it.
Own completing the tracker each period and presenting the Governance Dashboard to leadership, without needing an ML engineering background.
Own the Quality & Outcome Tracker inputs — defect escape rate, rework rate, coverage trend, and time-to-value.
Review the Governance Dashboard output each period and escalate specifically when the Ritual Discipline Flag fires.
Bring a standardised operational pulse into AI-DLC engagements across multiple clients instead of building bespoke status tracking.
Run one workbook instance per team and consolidate headline figures through the Portfolio Rollup panel for programme-level reporting.
One-time gate before this: the AI-DLC Pilot Selection & Portfolio Segmentation Tool selects which team or system this dashboard should first be run against. (Placeholder link — product not yet published.)
View Pilot Selection Tool →Feeds back into: the AI-DLC ROI & Business Case Calculator — this tracker's real measured data should progressively replace that calculator's early assumptions. (Placeholder link — product not yet published.)
View ROI & Business Case Calculator →Deeper, periodic counterpart: the AI-DLC Maturity Model & Benchmarking Tool asks how well the team is operating on a quarterly cadence, distinct from this tool's weekly/monthly pulse. (Placeholder link — product not yet published.)
View Maturity Model →New to the vocabulary? Bolt, Mob Elaboration, Mob Construction, Human Validation Gate, and Unit of Work are all defined terms this dashboard's indicators reference directly.
View AI-DLC Dictionary →What makes this a governance instrument, not a status report.
What this dashboard is not.
This is the recurring operational pulse for teams already live on AI-DLC. It is not a substitute for the one-time gate before adoption, or the deeper periodic diagnostic once a team matures.
What you need to run it.
Questions buyers ask before their first reporting period.
Our Delivery Health Score looks fine, but something still feels off. What are we missing?
Check the Ritual Discipline Flag separately from the Health Score — it is designed precisely for this situation. A team can maintain a HEALTHY average score while ritual attendance and gate integrity are quietly eroding together, if enough of the other 8 indicators stay Green. Always read both signals, not the Health Score alone.
Should we adjust our targets on Settings if we keep coming in Amber?
Only after investigating why, not as a default response. A persistently missed Mob Attendance target usually means a scheduling or organisational commitment problem worth solving directly, not a target that was wrong from the start. Loosening thresholds to make the dashboard look healthier defeats the purpose of the tool.
Why does Test Coverage Delta default to Green with no prior period logged?
Because a single data point cannot show a trend, and this indicator specifically flags decline, not absolute level. If the current coverage level is concerning regardless of trend, that should surface through your own team's engineering judgement and, over time, through the Defect Escape Rate indicator.
We missed logging a period. Does that break anything?
It breaks the trend calculation for Test Coverage Delta and Time-to-Value in the following period, since both read the most recently logged row in the Historical Log. It does not corrupt any other data. Log the current period as normal and the trend comparison resumes from that point.
How is this different from the Maturity Model & Benchmarking Tool?
This tool is a lightweight, high-frequency operational pulse — weekly or monthly, 11 threshold-based indicators, designed to catch drift quickly. The Maturity Model is a deeper, less frequent diagnostic, typically quarterly, across six behaviourally-anchored maturity dimensions, designed to answer how well a team is actually operating and whether it is improving. Use both — they serve different cadences and different questions.
Can this be used across multiple teams?
This workbook tracks one team per instance. For a multi-team programme, maintain one saved copy per team, and use the Portfolio Rollup panel on the Governance Dashboard to manually consolidate each team's headline figures into a single programme-level view.
Is a User Guide included?
Yes. A fully formatted .pdf User Guide is included in the download. It covers all 6 tabs, all 11 indicator definitions and RAG logic, a worked example showing how the Ritual Discipline Flag does and doesn't fire, and governance escalation and version-control guidance.
Delivery is still happening. Confirm the methodology still is too.
Download, complete Settings, and run your first reporting period before drift becomes a quarter of declining quality.
■ Instant download · ■ No subscription · ■ Yours to adapt for internal governance use