Weekly AI Operations Review Cadence

You are an expert AI operations manager specializing in AI workflow governance, prompt quality review, adoption tracking, incident review, risk control, improvement backlog management, and team operating cadence.

Your task is to design a weekly AI operations review cadence that helps a team monitor AI workflow quality, adoption, incidents, risks, ownership, and continuous improvement.

Context:
Team or organization: [Team or organization]
Active AI workflows: [Active AI workflows]
Adoption metrics: [Adoption metrics]
Quality issues: [Quality issues]
Incidents or near misses: [Incidents or near misses]
Prompt backlog: [Prompt backlog]
Owners: [Owners]
Review meeting length: [Review meeting length]
Decision rights: [Decision rights]
Improvement goals: [Improvement goals]

Important constraints:

* Do not treat AI adoption as a one-time rollout.
* Do not invent metrics, incidents, adoption data, user feedback, policies, or workflow performance.
* Separate known facts from assumptions.
* Make the cadence practical for a real team to run every week.
* Focus on decisions, ownership, follow-up, and measurable improvement, not just reporting.
* Include human review gates for high-risk AI workflows involving customers, legal, finance, privacy, security, medical, hiring, education, public claims, or production automation.
* Avoid generic meeting advice.
* Make every recommendation specific to the provided team, workflows, risks, owners, and improvement goals.
* If information is missing, state the assumption clearly before giving recommendations.

Task:

1. Summarize the AI operations context.
   Explain:

* Team or organization involved
* Active AI workflows under review
* Current adoption signals
* Main quality concerns
* Known incidents or near misses
* Current prompt or workflow backlog
* Owners and decision rights
* Improvement goals for the review cadence

2. Define the purpose of the weekly review.
   Clarify:

* Why the review exists
* What decisions it should produce
* What it should not become
* Which workflows should be reviewed weekly
* Which issues should be escalated outside the meeting
* What success looks like after 4 to 6 weeks

3. Create the weekly review agenda.
   Design a practical agenda based on the meeting length.

Include:

* Opening status review
* Adoption metrics review
* AI workflow quality review
* Incident and near-miss review
* Prompt performance review
* Risk and human-review queue
* Improvement backlog review
* Owner commitments
* Decision log
* Closing action summary

For each agenda item, include:

* Time allocation
* Owner
* Inputs needed
* Decision expected
* Output or artifact produced

4. Define the AI operations metrics dashboard.
   Recommend metrics for:

* Usage and adoption
* Prompt quality
* Output accuracy
* Human edits or corrections
* User satisfaction or feedback
* Workflow completion rate
* Failed or escalated AI outputs
* Incidents and near misses
* Time saved, where measurable
* Review backlog size
* Improvement cycle time

For each metric, include:

* What it measures
* Data source
* Owner
* Review frequency
* Warning threshold
* Action trigger

5. Create an incident and quality review process.
   Define how the team should review:

* Incorrect AI outputs
* Hallucinated claims
* Privacy or data-handling concerns
* Customer-facing mistakes
* Automation failures
* Prompt ambiguity
* Model overconfidence
* Missing human review
* Repeated manual corrections
* Escalations from users or team members

For each issue type, recommend:

* Severity level
* Immediate response
* Root cause question
* Owner
* Follow-up action
* Prevention step

6. Build the prompt and workflow improvement backlog.
   Create a backlog structure with:

* Improvement item
* Source of issue
* Affected workflow
* Risk level
* Expected benefit
* Effort level
* Priority
* Owner
* Due date
* Definition of done

Group backlog items into:

* Fix now
* Improve soon
* Monitor
* Defer
* Remove or retire

7. Define decision rights and escalation rules.
   Clarify:

* Who can approve prompt changes
* Who can approve workflow changes
* Who can pause an AI workflow
* Who must review high-risk outputs
* What must be escalated to leadership
* What must be escalated to legal, compliance, privacy, security, finance, or product
* What can be handled by the workflow owner

8. Create owner follow-up plan.
   For each owner, define:

* Assigned workflows
* Open issues
* Decisions needed
* Improvements due
* Metrics to report
* Risks to monitor
* Next review commitment

9. Create the weekly AI ops scorecard.
   Design a simple scorecard with:

* Green: working well
* Yellow: needs attention
* Red: needs immediate action
* Paused: should not continue until reviewed

Apply the scorecard to each active AI workflow.

10. Provide a 30-day improvement plan.
    Create a practical 4-week plan for improving AI operations.

Include:

* Week 1 priorities
* Week 2 priorities
* Week 3 priorities
* Week 4 priorities
* Expected progress
* Review checkpoints
* Risks to watch

Output format:

## AI Operations Context

## Weekly Review Purpose

## Weekly Review Agenda

## AI Operations Metrics Dashboard

## Incident and Quality Review Process

## Prompt and Workflow Improvement Backlog

## Decision Rights and Escalation Rules

## Owner Follow-Up Plan

## Weekly AI Ops Scorecard

## 30-Day Improvement Plan

## Final Recommendations

Verification:
Before finalizing, check that:

* The cadence produces decisions and improvements, not just status updates.
* Metrics are practical and tied to action triggers.
* Incidents and quality issues have review paths.
* Owners and decision rights are clearly assigned.
* High-risk AI workflows include human review gates.
* The improvement backlog is prioritized.
* The weekly scorecard is simple enough to use repeatedly.
* Missing inputs and assumptions are clearly listed.

Begin the weekly AI operations review cadence now.