AI Initiative Scale, Stop, or Redesign Decision Brief

Prepare a decision brief for one AI initiative. The objective is to recommend scale, hold, redesign, or stop using only the evidence provided, while making uncertainty, missing information, and decision authority explicit.

Inputs to use:
- Initiative name: [Initiative name]
- Decision owner: [Decision owner]
- Pilot or operating scope and timeframe: [Pilot or operating scope and timeframe]
- Evidence package: [Evidence package]
- Current constraints and non-negotiables: [Current constraints and non-negotiables]
- Decision options under consideration: [Decision options under consideration]
- Next decision date or trigger: [Next decision date or trigger]

Evidence discipline:
- Distinguish observed evidence from inference. Do not treat anecdotes, forecasts, vendor claims, or unverified internal estimates as confirmed facts.
- Do not claim that a source, approval, test, control, incident review, financial model, or system inspection was completed unless the evidence package shows it.
- If evidence is missing, state what is missing, why it matters, and the minimum evidence needed for a safer decision.
- Preserve uncertainty. Use confidence levels only when tied to evidence quality.
- Stay within decision-support authority: produce a recommendation and decision conditions; do not imply approval unless the accountable owner has already approved it in the evidence.
- Avoid generic AI governance commentary. Focus on this initiative’s value, adoption, controls, reliability, dependencies, economics, risk boundaries, and reversibility.

Decision standard:
Recommend exactly one primary disposition: Scale, Hold, Redesign, or Stop.
Use these meanings:
- Scale: expand use because value, adoption, controls, reliability, economics, dependencies, and reversibility are acceptable within defined boundaries.
- Hold: continue limited operation or pause expansion because evidence is incomplete or conditions are not yet met, but the initiative may still be viable.
- Redesign: materially change workflow, model approach, controls, operating model, vendor setup, data inputs, or user experience before further expansion.
- Stop: end or sunset the initiative because evidence does not support continued investment or risk is unacceptable relative to value and reversibility.

Deliver the brief in the following format:

1. Decision frame
- Initiative: state the initiative and operating scope.
- Decision needed: state the decision being made now.
- Accountable owner: identify the decision owner and any role-specific verifiers needed, such as product owner, data owner, security reviewer, legal/compliance owner, finance owner, operations owner, or release owner.
- Authority boundary: state what this brief can recommend versus what requires owner approval.
- Time boundary: state the next decision date or trigger.

2. Decision evidence map
Create a table with these columns: Decision dimension, Observed evidence, Inference or assumption, Evidence strength, Missing information, Decision implication.
Include these dimensions at minimum:
- Intended business value
- Realized value or leading indicators
- User adoption and workflow fit
- Output quality and reliability
- Control effectiveness and exception handling
- Data, model, vendor, and system dependencies
- Security, privacy, compliance, and policy constraints
- Operating support and ownership capacity
- Scale economics and marginal cost
- Reversibility, rollback, and exit cost

3. Gate-by-gate disposition
For each gate, assign Pass, Conditional Pass, Fail, or Insufficient Evidence. Explain the reason in 2 to 4 sentences per gate.
Gates:
- Value gate: evidence of meaningful value relative to effort and alternatives.
- Adoption gate: users, operators, or customers can and do use it in the intended workflow.
- Control gate: risks, permissions, review paths, exceptions, and accountability are workable.
- Reliability gate: quality, availability, latency, and failure modes are acceptable for the use case.
- Dependency gate: critical data, vendor, model, integration, and staffing dependencies are known and manageable.
- Economics gate: scale costs, support costs, and expected benefits remain acceptable beyond the pilot.
- Reversibility gate: the initiative can be rolled back, contained, or sunset without unacceptable disruption.

4. Counterfactual options
Compare the realistic options, not just the preferred one. Include at least:
- Scale now
- Hold in current scope
- Redesign before expansion
- Stop or sunset
- Non-AI or lower-automation alternative
For each option, provide: what would happen, expected upside, main downside, investment or effort required, risk exposure, reversibility, and what evidence would make this option stronger or weaker.

5. Scale economics and risk boundaries
Provide a practical scale boundary, even if the recommendation is not to scale.
Include:
- Unit or marginal cost drivers, using provided evidence only.
- Expected cost changes at expanded volume.
- Support, monitoring, exception handling, and owner workload implications.
- Benefits that are evidenced versus speculative.
- Risk ceilings that should not be exceeded.
- Required controls before expansion.
- Stop-loss triggers or rollback conditions.
- Any financial assumptions that the finance owner should verify before approval.

6. Recommendation
State one primary recommendation: Scale, Hold, Redesign, or Stop.
Then provide:
- Rationale tied to the gates and evidence map.
- Conditions required before execution.
- Evidence that argues against the recommendation.
- Residual risks the owner would knowingly accept.
- What would change the recommendation.

7. Authorized next-decision brief
Create an owner-ready next-decision plan with:
- Decision to be requested from [Decision owner].
- Roles that should verify specific parts of the brief before action, such as finance owner for economics, security reviewer for security boundaries, data owner for data use, product owner for workflow value, operations owner for support readiness, and legal/compliance owner where applicable.
- Immediate actions, responsible role, due date or trigger, and required evidence of completion.
- Metrics or observations to collect before the next decision.
- Completion checks that would show the recommendation has been executed or is ready for escalation.
- Explicit statement of any unresolved blockers.

Final quality check before answering:
- The brief decides the fate of one operating initiative; it does not prioritize a portfolio.
- Observations and inferences are clearly separated.
- Missing information is visible and decision-relevant.
- The recommendation is bounded by economics, risk, controls, dependencies, and reversibility.
- No unavailable inspection, approval, test, or execution is claimed.