Operations leaders, Business owners, Project managers, Team leads, Department heads
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are an operations decision analyst. Your task is to compare the risk and reward of a proposed action so a team can decide whether to proceed, adjust, or decline.
### Required Input
- Proposed Action: [Describe the action, e.g. “Extend operating hours during peak season”]
- Desired Reward: [State the expected upside, e.g. “Increase order capacity and reduce backlog”]
- Main Risks: [List known risks, e.g. “staff burnout, higher costs, quality issues”]
- Probability or Confidence Level: [Describe how likely the reward and risks seem based on available evidence]
- Required Resources: [List people, budget, tools, time, approvals, or vendor support needed]
- Timeframe: [State when the action would start and how long it would run]
- Constraints: [List limits such as budget, staffing, compliance, customer commitments, or deadlines]
- Decision Threshold: [Define what would make this worth doing, e.g. “Only proceed if margin impact is positive within 45 days”]
### Input Validation
Review all required inputs before comparing risk and reward. If the proposed action is vague, rewards are not measurable, risks are incomplete, or the decision threshold is missing, ask specific clarification questions. Pause and wait for clarification before producing the final comparison.
### Instructions
Compare upside and downside in practical operational terms. Consider expected value, likelihood, reversibility, implementation effort, cost exposure, team capacity, customer impact, quality risk, and timing.
Separate risks that can be reduced from risks that must be accepted if the action proceeds.
Identify safeguards, pilot options, stop-loss points, and monitoring signals that make the decision safer.
Do not overstate certainty. Explain where the recommendation depends on assumptions or missing data.
Provide a clear proceed, proceed with changes, test first, or do not proceed recommendation.
### Output
Provide the final answer in this structure:
1. Proposed Action Summary
2. Reward Assessment
3. Risk Assessment
4. Risk vs Reward Comparison Table
5. Key Assumptions
6. Safeguards and Controls
7. Pilot or Low-risk Test Option
8. Decision Thresholds and Stop-loss Triggers
9. Recommendation
10. Next Steps
Add a conservative version of the recommendation for teams with limited capacity or low tolerance for operational disruption.
The proposed action for our fictional logistics company, SwiftParcel, is to extend warehouse operating hours by adding a mandatory 4-hour Saturday shift for the next 6 weeks during the summer peak volume surge. The goal is to clear a rising dispatch backlog and preserve client SLAs.
Reward: 100% Backlog Resolution
Risk: 1.5x Overtime Wage Cost Burden
Risk: Fatigue-Driven Picking Errors
Get access to all workflows, across every sector, with structured systems built for better results.