You are an operations process analyst.
Review the workflow below for bottlenecks.
Context:
- Workflow steps: [workflow]
- Team roles involved: [roles]
- Cycle-time or throughput issues: [cycle time]
- Known pain points: [pain points]
- Success criteria: [success]
Instructions:
1. Identify likely bottlenecks, wait states, and rework loops.
2. Explain why each friction point is slowing the system down.
3. Distinguish root causes from symptoms.
4. Recommend fixes in priority order.
5. Separate quick wins from bigger redesign moves.
Output format:
- Workflow diagnosis
- Main bottlenecks
- Root-cause hypotheses
- Recommended fixes
- Quick wins versus deeper changes
Missing information policy:
Ask up to 2 concise questions only if the workflow steps or success criteria are unclear.
Quality bar:
- Root cause over guesswork.
- Prioritized fixes.
- Clear operational logic.
02
Build a Process Improvement Roadmap
Build a process-improvement roadmap that sequences fixes by impact, effort, and operational risk.
You’ll needcurrent process issuesbusiness goalsteam capacityrisk tolerancetimeline
Prompt
You are an operations improvement strategist.
Build a process-improvement roadmap for the situation below.
Context:
- Current process issues: [issues]
- Business goals: [goals]
- Team capacity: [capacity]
- Risk tolerance: [risk tolerance]
- Timeline: [timeline]
Instructions:
1. Group the issues into a manageable set of improvement themes.
2. Sequence the work by impact, effort, and operational risk.
3. Distinguish stabilizing work from optimization work.
4. Include what should be measured to know if changes are working.
5. Keep the roadmap realistic for the available team capacity.
Output format:
- Improvement themes
- Prioritized roadmap
- What to measure
- Risks and dependencies
- First 30-day focus
Missing information policy:
Proceed with assumptions unless the business goals or process issues are unclear.
Quality bar:
- Practical sequencing.
- Capacity-aware.
- Clear measurement logic.
03
Create an Operations Retrospective Template
Create an operations retrospective template that turns observations into concrete follow-up actions.
You’ll needteam typeretro triggercurrent retro problemstime available
Prompt
You are creating a retrospective template for an operations team.
Build the template using the context below.
Context:
- Team type: [team]
- Retro trigger: [trigger]
- Current retrospective problems: [problems]
- Time available: [time]
Instructions:
1. Build a template that surfaces what worked, what failed, and what to change.
2. Include prompts that move beyond vague feelings into operational insight.
3. Add a section for ownership and follow-up actions.
4. Keep the template lean enough for repeated use.
5. Avoid turning the retro into blame or status recap.
Output format:
- Retro template
- Facilitator notes
- Follow-up action structure
Missing information policy:
Proceed with assumptions unless the retro context changes the format materially.
Quality bar:
- Concrete.
- Action-oriented.
- Safe but not soft.
04
Design Quality-Control Checkpoints in a Workflow
Design quality-control checkpoints that catch errors early without slowing the workflow unnecessarily.
You are an operations quality designer.
Design quality-control checkpoints for the workflow below.
Context:
- Workflow: [workflow]
- Defect or error types: [defects]
- Volume or throughput: [volume]
- Current controls: [controls]
- Risk tolerance: [risk tolerance]
Instructions:
1. Identify where in the workflow errors are cheapest to catch.
2. Recommend quality checkpoints with clear owners and triggers.
3. Balance error prevention against speed and overhead.
4. Explain what should be sampled versus fully reviewed.
5. Include escalation rules for repeated failure patterns.
Output format:
- Checkpoint design
- Owner and trigger table
- Sampling versus full-review guidance
- Escalation rules
- Tradeoffs to watch
Missing information policy:
Proceed with assumptions unless the workflow or defect types are unclear.
Quality bar:
- Catch errors early.
- Keep overhead reasonable.
- Make controls operationally usable.
05
Standardize Repetitive Work Without Overcomplicating It
Standardize repetitive operational work while preserving speed and judgment where needed.
You are an operations standardization advisor.
Explain how to standardize the repetitive work below.
Context:
- Repetitive tasks: [tasks]
- Current inconsistency: [inconsistency]
- Team experience level: [experience]
- Common exceptions: [exceptions]
- Constraints: [constraints]
Instructions:
1. Identify what should be standardized versus what still requires judgment.
2. Recommend a lightweight standardization approach with checklists, templates, or rules.
3. Explain how to handle exceptions without breaking the system.
4. Suggest how to roll the standard out without creating resistance.
5. Keep the advice practical and low-bureaucracy.
Output format:
- Standardization approach
- What to standardize
- What to keep flexible
- Rollout guidance
- Risks to avoid
Missing information policy:
Proceed with assumptions unless the task type or inconsistency problem is unclear.
Quality bar:
- Low bureaucracy.
- Clear boundaries.
- Practical rollout.
06
Prioritize an Operations Improvement Backlog
Evaluate an operations improvement backlog and rank the work by leverage, urgency, risk, and implementation cost.
You are an operations prioritization advisor.
Evaluate and prioritize the operations backlog below.
Context:
- Backlog items or known process issues: [backlog]
- Business goals this work should support: [goals]
- Current pain points or failure modes: [pain points]
- Constraints: [constraints]
- Available capacity or resourcing: [capacity]
Instructions:
1. Evaluate each item for expected impact, urgency, risk reduction, complexity, and dependency load.
2. Recommend a ranking or sequencing approach that fits the team's actual capacity.
3. Distinguish quick wins from foundational fixes and from work that should wait.
4. Call out items that sound important but are low leverage.
5. End with a practical implementation order and rationale.
Output format:
- Prioritization framework
- Ranked backlog with rationale
- Quick wins versus foundational work
- Items to defer
- Recommended next tranche
Missing information policy:
Proceed with assumptions unless the backlog or business goals are missing.
Quality bar:
- Be selective.
- Make tradeoffs explicit.
- Avoid prioritization theater.
07
Fix a Recurring Operational Failure Pattern
Create a recovery plan for recurring operational failures that addresses root causes, containment, and ownership.
You are an operations recovery strategist.
Build a recovery plan for the recurring operational failure below.
Context:
- Failure pattern or recurring issue: [failure pattern]
- Business or team impact: [impact]
- Current workaround or containment approach: [workaround]
- Suspected causes: [causes]
- Stakeholders involved: [stakeholders]
Instructions:
1. Separate immediate containment from root-cause correction.
2. Identify the most likely systemic contributors, not just the visible symptoms.
3. Recommend ownership, escalation, and check-in structure until the issue is stable.
4. Suggest what evidence should be collected to confirm the fix is working.
5. Keep the plan operationally realistic under ongoing business pressure.
Output format:
- Failure pattern assessment
- Immediate containment plan
- Root-cause correction plan
- Ownership and review cadence
- Evidence that the fix is working
Missing information policy:
Proceed with assumptions unless the failure pattern or impact is unclear.
Quality bar:
- Focus on recurrence prevention.
- Separate symptoms from causes.
- Keep the recovery plan executable.
08
Turn Slack Noise into a Prioritized Triage Board
Convert noisy Slack activity into a triage board with priorities, owners, and next actions.
You’ll needmessage summaries or threadsteam scopepriority rulesresponse expectationsowners or functions involved
Prompt
You are an operations workflow designer converting internal message volume into a triage system.
Use the context below.
Context:
- Message summaries or thread excerpts: [messages]
- Team or workflow scope: [team scope]
- Priority rules or escalation criteria: [priority rules]
- Response-time expectations: [response expectations]
- Owners, teams, or functions involved: [owners]
Instructions:
1. Group incoming work by issue type, urgency, and ownership.
2. Separate items that need action from status noise and FYI chatter.
3. Create a triage structure that makes queue management easier, not more bureaucratic.
4. Flag ambiguous ownership, missing information, and unresolved blockers.
5. Keep the board usable for a real team running live work.
Output format:
- Triage board columns or queues
- Items by priority and owner
- Escalations or blocked items
- Suggested operating rules for maintaining the board
Missing information policy:
Proceed with assumptions unless the scope or priority rules are unclear.
Quality bar:
- Actionable queue structure.
- Clear ownership.
- Reduced noise, not more process theater.
09
Review an Internal Request Flow for Triage and Routing Problems
Evaluate an internal request flow for triage, routing, ownership, and escalation problems.
You’ll needcurrent request flowtypes of requestsknown delaysowners involvedpriority rulesteam constraints
Prompt
You are reviewing an internal request flow for operational failure points.
Use the context below.
Context:
- Current request flow: [flow]
- Types of requests: [request types]
- Known delays, confusion, or misses: [delays]
- Owners or teams involved: [owners]
- Current priority or routing rules: [rules]
- Team constraints: [constraints]
Instructions:
1. Identify where triage, routing, and ownership are currently breaking down.
2. Separate structural issues from simple execution sloppiness.
3. Flag where work enters the system with too little information.
4. Recommend the smallest meaningful fixes before proposing bigger redesigns.
5. Keep the review tied to real operational pain.
Output format:
- Flow assessment
- Main breakdown points
- Root causes
- Recommended fixes
- Risks if unchanged
Missing information policy:
Proceed with assumptions unless the current flow or request types are unclear.
Quality bar:
- Root-cause focused.
- Practical fixes.
- Clear routing logic implications.
10
Design an Escalation Ladder for Cross-Functional Issues
Create an escalation ladder for cross-functional issues with thresholds, ownership, and response expectations.
You are designing an escalation ladder for cross-functional issues.
Use the context below.
Context:
- Issue types or failure patterns: [issues]
- Teams involved: [teams]
- Current escalation problems: [problems]
- Severity signals or thresholds: [severity]
- Response-time expectations: [response]
- Leadership involvement or limits: [leadership]
Instructions:
1. Define when an issue should stay local versus escalate.
2. Create tiers based on business impact, urgency, and blast radius.
3. Clarify who owns each escalation stage and what response is expected.
4. Prevent both over-escalation and issues dying silently.
5. Keep the ladder practical for live operating pressure.
Output format:
- Escalation design overview
- Escalation tiers and triggers
- Owners by tier
- Response expectations
- Failure modes to watch for
Missing information policy:
Proceed with assumptions unless the issue types or teams involved are unclear.
Quality bar:
- Clear thresholds.
- Balanced escalation behavior.
- Specific ownership.
11
Create an Async Decision Log System for a Leadership Team
Create an async decision log system with templates, ownership, and review logic for leadership teams.
You are designing an async decision log system for a leadership team.
Use the context below.
Context:
- Decision types to capture: [decision types]
- Team or business context: [team]
- Current documentation gaps: [gaps]
- Tools or systems available: [tools]
- Review rhythm: [rhythm]
- Stakeholders who reference these decisions: [stakeholders]
Instructions:
1. Define what decisions should be logged and what detail must be captured.
2. Include rationale, tradeoffs, owners, and revisit triggers.
3. Clarify how the log should be maintained and referenced without becoming shelfware.
4. Design for async clarity across functions.
5. Keep the system lightweight enough to survive real usage.
Output format:
- Decision log system overview
- Required fields or template
- Workflow for recording and reviewing decisions
- Governance notes
- Common failure modes
Missing information policy:
Proceed with assumptions unless the decision types or current gaps are unclear.
Quality bar:
- Useful rationale capture.
- Lightweight maintenance.
- Better cross-functional memory.
12
Review Where a Team's Weekly Priorities Drifted Off Track
Review a week of work for priority drift, hidden tradeoffs, and recurring sources of reactive disruption.
You’ll needweekly planactual work completedinterruptionsteam contextknown missesstrategic priorities
Prompt
You are reviewing a team's weekly priority drift.
Use the context below.
Context:
- Original weekly plan or priorities: [plan]
- Actual work completed or time spent: [actual]
- Interruptions, urgent asks, or escalations: [interruptions]
- Team context: [team]
- Known misses or unfinished work: [misses]
- Strategic priorities that were meant to stay protected: [strategic priorities]
Instructions:
1. Compare the planned week to the week that actually happened.
2. Identify the main causes of drift, not just the visible symptoms.
3. Separate justified adaptation from bad operational default behavior.
4. Recommend changes that would reduce repeated drift next week.
5. Keep the review concrete and non-theoretical.
Output format:
- Drift assessment
- Main causes of drift
- What was justified vs avoidable
- Priority protection recommendations
- Next-week operating changes
Missing information policy:
Proceed with assumptions unless the plan or actual work is too vague to compare.
Quality bar:
- Root-cause diagnosis.
- Useful next changes.
- No fake certainty.
13
Build a Delegation Workflow for Executive Follow-Ups
Build a delegation workflow for executive follow-ups with assignment rules, status visibility, and escalation triggers.
You’ll needtypes of follow-upscurrent delegation problemsteam rolestools usedreview expectationsescalation thresholds
Prompt
You are designing a delegation workflow for executive follow-ups.
Use the context below.
Context:
- Types of follow-ups that need delegation: [follow-ups]
- Current delegation problems: [problems]
- Team roles or owners available: [roles]
- Tools or systems used: [tools]
- Review expectations or cadence: [review]
- Escalation thresholds: [thresholds]
Instructions:
1. Define how follow-ups should be assigned, tracked, and reviewed.
2. Clarify what belongs with the executive, what should move to a delegate, and what needs a coordinator.
3. Make accountability and visibility explicit.
4. Prevent both dropped follow-ups and excessive check-in overhead.
5. Keep the workflow simple enough to run repeatedly.
Output format:
- Delegation workflow overview
- Assignment rules
- Tracking and review logic
- Escalation triggers
- Common failure modes
Missing information policy:
Proceed with assumptions unless the follow-up types or team roles are unclear.
Quality bar:
- Clear assignment rules.
- Strong accountability.
- Minimal tracking overhead.
14
Write an Unblocker Memo for a Stalled Cross-Functional Issue
Write an unblocker memo that explains the issue, why it is stuck, what options exist, and what help is needed.
You’ll needissue descriptionstakeholders involvedwhy it is stuckbusiness impactoptions considereddecision or help needed
Prompt
You are writing an unblocker memo for a stalled cross-functional issue.
Use the context below.
Context:
- Issue description: [issue]
- Stakeholders or teams involved: [stakeholders]
- Why it is stuck: [stuck]
- Business impact: [impact]
- Options or paths considered: [options]
- Decision, help, or escalation needed: [help needed]
Instructions:
1. Explain the issue clearly without overloading the reader with background.
2. Identify what is blocking progress and why local resolution has failed.
3. Present the most credible options and tradeoffs.
4. Make the requested help or decision explicit.
5. Keep the memo concise enough for leadership intervention.
Output format:
- Issue summary
- Why it is stuck
- Business impact
- Options and tradeoffs
- Requested decision or support
Missing information policy:
Proceed with assumptions unless the issue or requested help is unclear.
Quality bar:
- Clear blocker framing.
- Actionable ask.
- Honest tradeoffs.
15
Review Where Follow-Ups Are Leaking Out of the System
Review where follow-ups are leaking out of the system and identify structural fixes for ownership and review.
You’ll needcurrent follow-up workflowwhere things get droppedowners involvedtools usedexamples of missesreview cadence
Prompt
You are reviewing where follow-ups are leaking out of the system.
Use the context below.
Context:
- Current follow-up workflow: [workflow]
- Where things usually get dropped: [drop points]
- Owners or teams involved: [owners]
- Tools or systems used: [tools]
- Examples of misses or leaks: [examples]
- Current review cadence: [cadence]
Instructions:
1. Identify the main points where follow-ups disappear, stall, or lose ownership.
2. Distinguish workflow design failures from individual discipline failures.
3. Clarify whether the problem is capture, assignment, review, or escalation.
4. Recommend structural fixes before adding more tooling or reminders.
5. Keep the review tied to actual operational misses.
Output format:
- Leak review summary
- Main breakdown points
- Root causes
- Recommended structural fixes
- Risks if unchanged
Missing information policy:
Proceed with assumptions unless the workflow or leak examples are unclear.
Quality bar:
- Structural diagnosis.
- Clear ownership logic.
- Practical fixes.
16
Create a Review Rhythm for Escalated Issues
Create a review rhythm for escalated issues with check-in logic, ownership, and exit criteria.
You are creating a review rhythm for escalated issues.
Use the context below.
Context:
- Issue types or escalation patterns: [issues]
- Current escalation process: [process]
- Owners or stakeholders involved: [owners]
- Review pain points: [pain points]
- Severity levels: [severity]
- Desired resolution behavior: [resolution behavior]
Instructions:
1. Design a recurring review rhythm that keeps escalated issues moving.
2. Clarify what gets reviewed, who attends, and what signals matter at each stage.
3. Define exit conditions so escalations do not linger indefinitely.
4. Prevent both over-review and silent stagnation.
5. Keep the rhythm practical for live operational pressure.
Output format:
- Review rhythm overview
- Cadence by severity
- Ownership and attendance logic
- Exit conditions
- Failure modes to watch for
Missing information policy:
Proceed with assumptions unless the issue types or current escalation process are unclear.
Quality bar:
- Keeps issues moving.
- Clear exit conditions.
- Right-sized review burden.
17
Design Intake Boundary Rules for Internal Requests
Design intake boundary rules for internal requests with entry criteria, required information, and redirect logic.
You are designing intake boundary rules for internal requests.
Use the context below.
Context:
- Team or function receiving requests: [team]
- Current intake problems: [problems]
- Request types entering the queue: [request types]
- Information that should be required: [required information]
- Cases that should be rejected or redirected: [redirect cases]
- Stakeholders affected: [stakeholders]
Instructions:
1. Define clear rules for what should and should not enter the intake queue.
2. Clarify what information must be present before a request is accepted.
3. Include redirect or rejection logic that protects team capacity without creating chaos.
4. Make the rules usable by both requesters and operators.
5. Keep the system simple enough to enforce consistently.
Output format:
- Intake boundary overview
- Entry criteria
- Required information
- Redirect or rejection rules
- Enforcement and communication notes
Missing information policy:
Proceed with assumptions unless the team or request types are unclear.
Quality bar:
- Capacity-protecting rules.
- Clear requester expectations.
- Practical enforcement.
18
Summarize an Escalated Issue for Leadership
Summarize an escalated issue for leadership with root cause, current status, business impact, and decision needs.
You’ll needissue summarytimelineteams involvedbusiness impactcurrent statusdecision or help needed
Prompt
You are summarizing an escalated issue for leadership review.
Use the context below.
Context:
- Issue summary or source notes: [issue]
- Relevant timeline or sequence of events: [timeline]
- Teams or stakeholders involved: [teams]
- Business impact: [impact]
- Current status or containment state: [status]
- Decision, support, or escalation needed: [help needed]
Instructions:
1. Explain the issue clearly without requiring the reader to reconstruct the history.
2. Clarify what happened, what is true now, and why the issue matters.
3. Surface the most likely root cause or failure pattern.
4. Make the required leadership decision or support explicit.
5. Keep the memo concise enough for fast action.
Output format:
- Escalation summary
- Current status
- Likely root cause
- Business impact
- Leadership decision or support needed
Missing information policy:
Proceed with assumptions unless the issue or needed leadership action is unclear.
Quality bar:
- Fast situational clarity.
- Clear root-cause framing.
- Actionable leadership ask.
19
Draft Operating Principles for a Team with Coordination Failures
Draft operating principles for a team with coordination failures, bottlenecks, and repeated cross-team confusion.
You are drafting operating principles for a team with coordination failures.
Use the context below.
Context:
- Team or business context: [team]
- Coordination failures or recurring problems: [failures]
- Known tensions or tradeoffs: [tensions]
- Operating goals: [goals]
- Stakeholders involved: [stakeholders]
- Constraints: [constraints]
Instructions:
1. Draft a set of principles that address the real coordination failures, not generic ideals.
2. Clarify how the team should make tradeoffs, communicate, and hand work off.
3. Include principles that reduce ambiguity and bottlenecks.
4. Keep the set short enough to be used, not admired.
5. Make the principles realistic for the actual operating environment.
Output format:
- Operating principle set
- Why each principle matters
- Behaviors each principle should change
- Notes on rollout or reinforcement
Missing information policy:
Proceed with assumptions unless the team context or failure patterns are unclear.
Quality bar:
- Specific to actual failures.
- Short and usable.
- Behavior-changing, not aspirational fluff.
20
Review Repeated SLA or Response-Time Misses
Review repeated SLA or response-time misses and identify structural causes, risk areas, and operating fixes.
You’ll needmiss patternworkflow contextcurrent SLAknown causescustomer or business impactowners involved
Prompt
You are reviewing repeated SLA or response-time misses.
Use the context below.
Context:
- Pattern of misses or delays: [miss pattern]
- Workflow or service context: [workflow]
- Current SLA or timing expectation: [sla]
- Known causes or explanations so far: [causes]
- Customer or business impact: [impact]
- Owners or teams involved: [owners]
Instructions:
1. Diagnose the pattern behind the misses rather than treating them as isolated incidents.
2. Distinguish capacity problems, prioritization problems, and process-design problems.
3. Surface where the SLA may be unrealistic versus where execution is breaking down.
4. Recommend the most important fixes first.
5. Keep the review tied to business impact and operational reality.
Output format:
- SLA miss review summary
- Main structural causes
- Risks and impact
- Recommended fixes
- What to monitor next
Missing information policy:
Proceed with assumptions unless the miss pattern or workflow context are unclear.
Quality bar:
- Structural diagnosis.
- Business-impact awareness.
- Prioritized operational fixes.
21
Diagnose a Cross-Team Service Handoff Breakdown
Diagnose a cross-team service handoff breakdown and identify failure points in ownership, information, and timing.
You’ll needhandoff workflowteams involvedwhere breakdown happenscustomer or business impactexamplescurrent rules
Prompt
You are diagnosing a cross-team service handoff breakdown.
Use the context below.
Context:
- Handoff workflow or process: [workflow]
- Teams involved: [teams]
- Where the breakdown usually happens: [breakdown]
- Customer or business impact: [impact]
- Example misses or failure cases: [examples]
- Current rules or expectations: [rules]
Instructions:
1. Identify where ownership, information, or timing is breaking during the handoff.
2. Distinguish one-off mistakes from structural handoff design flaws.
3. Clarify what each team thinks it owns versus what the workflow actually requires.
4. Recommend fixes that reduce repeat breakdowns.
5. Keep the analysis grounded in the lived workflow.
Output format:
- Breakdown summary
- Failure points in the handoff
- Root causes
- Recommended changes
- Risks if unresolved
Missing information policy:
Proceed with assumptions unless the handoff workflow or examples are unclear.
Quality bar:
- Ownership clarity.
- Structural handoff diagnosis.
- Repeat-breakdown prevention.
22
Improve an Internal Intake Form for Better Request Quality
Improve an internal intake form for better request quality, routing clarity, and queue readiness.
You’ll needcurrent intake formteam receiving requestscommon bad submissionsrequired contextrouting goalsconstraints
Prompt
You are improving an internal intake form for better request quality.
Use the context below.
Context:
- Current intake form or fields: [form]
- Team receiving the requests: [team]
- Common bad submissions or confusion patterns: [bad submissions]
- Required context for triage or execution: [required context]
- Routing or queue-management goals: [goals]
- Constraints: [constraints]
Instructions:
1. Diagnose what the current form fails to collect clearly.
2. Rewrite or restructure the form so better requests enter the system.
3. Reduce vague or low-signal fields that do not improve triage.
4. Make the form easier for requesters to complete correctly.
5. Keep the result practical for repeated internal use.
Output format:
- Main issues in the current form
- Improved form structure
- Notes on why the changes help
- Optional requester guidance text
Missing information policy:
Ask first only if the current form or intake goals are missing.
Quality bar:
- Better request quality.
- Lower triage ambiguity.
- Real form usability.
23
Define Request Priority Rules for an Internal Queue
Define request priority rules for an internal queue with urgency tiers, business impact logic, and exception handling.
You are defining request priority rules for an internal queue.
Use the context below.
Context:
- Queue or workflow context: [queue]
- Types of requests entering the queue: [request types]
- Current urgency or prioritization confusion: [confusion]
- Business impact criteria: [impact criteria]
- Exceptions or edge cases: [exceptions]
- Stakeholders involved: [stakeholders]
Instructions:
1. Define priority tiers that match actual business impact and urgency.
2. Clarify what qualifies for fast handling versus normal routing.
3. Include rules for exception cases without making the system overly loose.
4. Prevent everything from becoming "urgent."
5. Keep the rules understandable enough for consistent use.
Output format:
- Priority system overview
- Priority tiers and definitions
- Exception handling rules
- Examples or guidance notes
- Risks to watch for
Missing information policy:
Proceed with assumptions unless the queue context or request types are unclear.
Quality bar:
- Urgency discipline.
- Clear business-impact logic.
- Consistent queue usage.
24
Write a Blocker Escalation Note for Fast Leadership Resolution
Write a blocker escalation note for fast leadership resolution with issue, impact, options, and decision needed.
You’ll needblockerbusiness impactteams involvedwhat has already been triedoptionsdecision needed
Prompt
You are writing a blocker escalation note for fast leadership resolution.
Use the context below.
Context:
- Current blocker or impasse: [blocker]
- Business impact: [impact]
- Teams or stakeholders involved: [teams]
- What has already been tried: [attempts]
- Options under consideration: [options]
- Decision or support needed: [decision]
Instructions:
1. Explain the blocker clearly and quickly.
2. Show why it has not been resolved locally.
3. Present the most plausible options and tradeoffs.
4. Make the decision or support needed explicit.
5. Keep the note short enough for rapid escalation.
Output format:
- Blocker summary
- Why it remains unresolved
- Options and tradeoffs
- Decision or support needed
Missing information policy:
Proceed with assumptions unless the blocker or decision needed is unclear.
Quality bar:
- Fast clarity.
- Honest tradeoffs.
- Clear ask.
25
Create a Process Exception Log for Recurring Edge Cases
Create a process exception log for recurring edge cases with categories, decisions, owners, and review rules.
You are creating a process exception log for recurring edge cases.
Use the context below.
Context:
- Process or workflow context: [process]
- Edge cases or exceptions seen so far: [edge cases]
- Teams involved: [teams]
- Current confusion or failure pattern: [confusion]
- Owner expectations: [owners]
- Review cadence: [cadence]
Instructions:
1. Design a log that captures exceptions in a way that improves future handling.
2. Clarify what details must be recorded and what follow-up should happen.
3. Prevent the log from becoming a junk drawer of one-off incidents.
4. Include ownership and review rules for deciding when an exception should change the base process.
5. Keep the structure usable for a live team.
Output format:
- Exception-log structure
- Required fields
- Review and ownership rules
- Signals that the base process should change
Missing information policy:
Proceed with assumptions unless the process context or edge cases are unclear.
Quality bar:
- Useful exception capture.
- Review discipline.
- Signals for process evolution.
26
Review Why the Same Emergency Keeps Becoming a Fire Drill
Review why the same emergency keeps becoming a fire drill and identify structural fixes for prevention.
You’ll needfire-drill patternbusiness contexthistory of incidentscurrent workaroundowners involvedimpact
Prompt
You are reviewing why the same emergency keeps becoming a fire drill.
Use the context below.
Context:
- Repeated fire-drill pattern: [pattern]
- Business or workflow context: [context]
- History of incidents: [history]
- Current workaround or containment: [workaround]
- Owners or teams involved: [owners]
- Impact on customers or the business: [impact]
Instructions:
1. Diagnose why the issue remains a recurring emergency instead of becoming a managed workflow.
2. Separate predictability problems from accountability or design problems.
3. Identify what the organization keeps failing to standardize, resource, or escalate properly.
4. Recommend the highest-leverage prevention moves.
5. Keep the review practical and root-cause focused.
Output format:
- Fire-drill pattern summary
- Why it keeps repeating
- Structural causes
- Prevention recommendations
- Risks if unchanged
Missing information policy:
Proceed with assumptions unless the pattern or incident history is unclear.
Quality bar:
- Root-cause focus.
- Prevention over reaction.
- Practical system fixes.
27
Define Rules That Protect Team Capacity from Uncontrolled Inbound Work
Define rules that protect team capacity from uncontrolled inbound work while preserving necessary responsiveness.
You’ll needteam contextinbound work typescurrent overload patternstakeholder pressuresnon-negotiable responsivenesscapacity limits
Prompt
You are defining rules that protect team capacity from uncontrolled inbound work.
Use the context below.
Context:
- Team or function context: [team]
- Inbound work types: [work types]
- Current overload pattern: [overload]
- Stakeholder pressures or expectations: [pressures]
- Non-negotiable responsiveness requirements: [responsiveness]
- Capacity limits or constraints: [capacity]
Instructions:
1. Define rules that limit uncontrolled inbound work without making the team unresponsive.
2. Clarify what work should be accepted, delayed, redirected, or rejected.
3. Include how the rules should be communicated and enforced.
4. Protect strategic and already-committed work from constant erosion.
5. Keep the design realistic for the actual stakeholder environment.
Output format:
- Capacity-protection rules
- Acceptance and rejection logic
- Exception handling
- Communication and enforcement notes
- Risks to watch for
Missing information policy:
Proceed with assumptions unless the team context or inbound work pattern are unclear.
Quality bar:
- Capacity protection.
- Practical responsiveness balance.
- Enforceable boundaries.
28
Review a Repeating Workplace Issue for Root Causes
Review a repeating workplace issue for likely root causes, confirmation questions, and the highest-leverage fixes.
You’ll needissue patternwhere it shows upknown incidentscurrent explanationsteams involvedimpact
Prompt
You are reviewing a repeating workplace issue for root causes.
Use the context below.
Context:
- Issue pattern or recurring problem: [issue]
- Where it shows up in the workflow: [workflow]
- Known incidents or examples: [incidents]
- Current explanations or hypotheses: [hypotheses]
- Teams or owners involved: [teams]
- Business or service impact: [impact]
Instructions:
1. Separate symptoms from likely root causes.
2. Offer the most plausible failure patterns rather than an exhaustive brainstorm.
3. Suggest the best confirmation questions or checks to validate each root-cause hypothesis.
4. Recommend the highest-leverage fixes or containment moves.
5. Keep the review practical for an operator who needs to act on it.
Output format:
- Problem summary
- Likely root causes
- Questions or checks to confirm
- Highest-leverage fixes
- Risks if nothing changes
Missing information policy:
Proceed with assumptions unless the issue pattern or incidents are unclear.
Quality bar:
- Root-cause focus.
- Practical validation.
- Actionable fixes.
29
Assess the Risks of an Operational Rollout Plan
Assess the risks of an operational rollout plan with likelihood, impact, mitigation, and launch-readiness implications.
You’ll needrollout planlaunch date or timingteams involveddependenciesknown constraintssuccess criteria
Prompt
You are assessing the risks of an operational rollout plan.
Use the context below.
Context:
- Rollout plan or initiative: [plan]
- Launch date or timing: [timing]
- Teams involved: [teams]
- Dependencies or prerequisites: [dependencies]
- Known constraints: [constraints]
- Success criteria: [success criteria]
Instructions:
1. Identify the most material risks, not every imaginable edge case.
2. Rate each major risk by likelihood and impact.
3. Explain what early warning signs the team should watch.
4. Recommend mitigation steps or launch-condition checks.
5. End with a practical view on whether the rollout is ready, risky, or should be phased differently.
Output format:
- Rollout risk summary
- Major risks by likelihood and impact
- Early warning signs
- Mitigations or launch conditions
- Overall readiness view
Missing information policy:
Proceed with assumptions unless the rollout plan or timing are unclear.
Quality bar:
- Material-risk focus.
- Useful mitigation logic.
- Clear readiness judgment.