Operations
GenAIOps Maturity Model
If your prototype is in production and you're not sure who runs it at 2am, this assessment is for you. The GenAIOps Maturity Model is a printable self-review across the six VOF pillars — quick enough to do in a meeting, deep enough to spark the conversation that needs to happen.
What's inside
- Printable scoring worksheet across six VOF pillars
- Five maturity levels with observable behaviors
- A first check and evidence record for every pillar
Who it's for
Engineering leaders moving from prototype to production. Useful for budget owners deciding whether to invest in operational discipline now or wait for the first incident.
Score evidence, then choose a next action
This Viewyonder self-review uses six VOF pillars and five levels. It is a discussion aid, not an external certification. Select one application and environment. Record an owner, date, evidence link and next action for every pillar. “Unknown” is a valid result when evidence is missing.
- Deployed but not run: the feature exists; ownership and evidence are missing. Name an owner and record the current path.
- Owned: responsibilities and a basic runbook exist. Exercise the relevant control in staging.
- Measured: repeatable checks and thresholds exist. Connect a failed check to a decision and a rollback.
- Controlled: changes are gated by evidence and recovery is exercised. Review missed incidents and coverage gaps.
- Continuously evolved: incidents and changing workloads feed regular retesting and improvements. Verify the review still changes decisions.
Operational Excellence
Evidence to look for: A named owner can deploy, observe and roll back a change.
First useful check: Run a staging rollback and record who makes the decision.
Level / Unknown: _____ · Evidence: _____ · Owner: _____ · Next review: _____
Reliability
Evidence to look for: Failure, timeout and provider-unavailable paths have useful fallbacks.
First useful check: Exercise one provider timeout and inspect the user outcome.
Level / Unknown: _____ · Evidence: _____ · Owner: _____ · Next review: _____
Security
Evidence to look for: Identity and permissions constrain data and tool actions outside the model.
First useful check: Retest one out-of-role action with a synthetic identity.
Level / Unknown: _____ · Evidence: _____ · Owner: _____ · Next review: _____
Performance Efficiency
Evidence to look for: Latency and throughput are measured against task needs.
First useful check: Measure the slowest representative path under a bounded load.
Level / Unknown: _____ · Evidence: _____ · Owner: _____ · Next review: _____
Cost Intelligence
Evidence to look for: Cost includes retries, tools and review per accepted task.
First useful check: Complete the token economics workbook for one period.
Level / Unknown: _____ · Evidence: _____ · Owner: _____ · Next review: _____
Behavioural Assurance
Evidence to look for: Representative evaluations detect regressions after changes.
First useful check: Run a known failing case and confirm it blocks an unsafe promotion.
Level / Unknown: _____ · Evidence: _____ · Owner: _____ · Next review: _____
Use the result
Choose the highest level for which you can demonstrate all required evidence, including the preceding levels; do not award a level on intention alone. Keep the six results visible instead of hiding a weak security or reliability result inside an average. Select one improvement that reduces a real operating risk, name its owner and agree a retest date.
Illustrative example: a team has a rollback runbook but has never exercised it. Its Operational Excellence result is Owned, not Controlled. The next action is a staging rollback with a retained result. No client outcome is implied.
Print this page or save it as PDF for a workshop. Use the VOF reading index for supporting material.