You are an operations workflow designer.
Redesign the team's meeting cadence.
Context:
- Current meeting schedule: [schedule]
- Team type: [team]
- Known pain points: [pain points]
- Decisions or coordination needs: [needs]
- Constraints: [constraints]
Instructions:
1. Identify which meetings are useful, redundant, or unclear.
2. Recommend a simpler meeting system with clear purposes and outputs.
3. Clarify owners, agendas, and follow-up expectations.
4. Reduce meeting load where possible without harming coordination.
5. Include rules for when information should move async instead.
Output format:
- Meeting cadence assessment
- Recommended meeting system
- Meeting-by-meeting purpose
- Async alternatives
- Rollout notes
Missing information policy:
Proceed with assumptions unless the current schedule or decision needs are unclear.
Quality bar:
- Less overhead.
- Clear purpose.
- Better follow-through.
02
Create a Weekly Standup or Ops Review Template
Create a weekly standup or ops review template focused on priorities, blockers, metrics, and decisions.
You are building a recurring operations meeting template.
Create the template using the context below.
Context:
- Team function: [team]
- Meeting length: [length]
- Participants: [participants]
- Common issues today: [issues]
Instructions:
1. Structure the meeting around priorities, blockers, metrics, and decisions.
2. Keep the flow concise enough for the stated meeting length.
3. Clarify what should be prepared beforehand.
4. Include a clear capture method for follow-up actions.
5. Avoid status theater.
Output format:
- Meeting template
- Prep expectations
- Follow-up action section
- Tips for keeping the meeting tight
Missing information policy:
Proceed with assumptions unless the team function or meeting type is unclear.
Quality bar:
- Concise.
- Decision-oriented.
- Easy to run repeatedly.
03
Design a Better Cross-Team Handoff Workflow
Design a cross-team handoff workflow with clear triggers, ownership, and readiness criteria.
You’ll needteams involvedhandoff typecurrent failuressystems usedrisk areas
Prompt
You are an operations workflow designer focused on cross-team handoffs.
Design a better handoff workflow for the context below.
Context:
- Teams involved: [teams]
- Handoff type: [handoff]
- Current failures: [failures]
- Systems used: [systems]
- Risk areas: [risk]
Instructions:
1. Map the handoff from trigger to completion.
2. Define readiness criteria before the handoff happens.
3. Clarify ownership, acceptance rules, and escalation points.
4. Recommend what information must travel with the handoff.
5. Keep the workflow clear enough for real execution.
Output format:
- Handoff workflow
- Readiness criteria
- Ownership and acceptance rules
- Escalation model
- Common breakdowns to prevent
Missing information policy:
Proceed with assumptions unless the teams or handoff type are unclear.
Quality bar:
- Clear triggers.
- Explicit ownership.
- Prevent silent drops.
04
Move More Operational Work Async
Create an async-work approach that reduces meetings without losing coordination or accountability.
You’ll needteam typecurrent communication habitscoordination riskstools
Prompt
You are an operations advisor helping a team work more asynchronously.
Design an async-work approach for the team below.
Context:
- Team type: [team]
- Current communication habits: [habits]
- Coordination risks: [risks]
- Available tools: [tools]
Instructions:
1. Identify which work should move async and which should stay synchronous.
2. Recommend update formats, response expectations, and decision rules.
3. Clarify how accountability should work without constant meetings.
4. Keep the system realistic for the team's habits and tooling.
5. Flag where async can fail if expectations stay vague.
Output format:
- Async-work model
- What to move async
- Communication rules
- Accountability model
- Risks and safeguards
Missing information policy:
Proceed with assumptions unless the team setup or communication habits are unclear.
Quality bar:
- Practical.
- Clear expectations.
- Better coordination with less meeting load.
05
Design a Cross-Functional Operating Cadence
Design an operating cadence that creates decision rhythm, accountability, and cross-team visibility without meeting bloat.
You are an operations cadence designer.
Design a cross-functional operating cadence for the situation below.
Context:
- Teams involved: [teams]
- Shared goals or workstreams: [goals]
- Current meeting load: [meeting load]
- Decision or coordination bottlenecks: [bottlenecks]
- Constraints on time or availability: [constraints]
Instructions:
1. Recommend the core rhythm of reviews, planning sessions, async updates, and escalation points.
2. Clarify the purpose of each touchpoint and what should not be discussed there.
3. Define owners, inputs, outputs, and follow-up expectations for each part of the cadence.
4. Suggest how to reduce redundant meetings while preserving visibility.
5. Include failure modes that indicate the cadence is becoming overhead instead of leverage.
Output format:
- Cadence overview
- Meeting and async rhythm
- Purpose and output of each touchpoint
- Ownership and follow-through rules
- Failure modes to watch
Missing information policy:
Proceed with assumptions unless the teams involved or coordination goal is unclear.
Quality bar:
- Fight meeting sprawl.
- Create clear decision rhythm.
- Make accountability obvious.
06
Design a Better Work Intake Workflow
Create an intake workflow that improves request quality, prioritization, ownership, and response expectations.
You are an operations workflow designer.
Design a work intake workflow for the context below.
Context:
- Team receiving the work: [team]
- Main request types: [request types]
- Current intake problems: [problems]
- Existing prioritization rules: [prioritization]
- Tools or channels used today: [tools]
Instructions:
1. Design an intake process that improves request quality before work starts.
2. Define what information requesters must provide and what should be optional.
3. Explain how work should be triaged, prioritized, accepted, deferred, or rejected.
4. Include SLAs or response expectations where useful.
5. Keep the system firm enough to reduce chaos but simple enough people will actually use it.
Output format:
- Intake workflow overview
- Required request fields
- Triage and prioritization logic
- Status definitions and response expectations
- Risks and rollout guidance
Missing information policy:
Proceed with assumptions unless the request types or team context are unclear.
Quality bar:
- Reduce ad hoc thrash.
- Improve prioritization quality.
- Keep requester friction reasonable.
07
Design a Cross-Team Handoff Template
Create a handoff template and usage rules that reduce dropped context, confusion, and rework.
You’ll needhandoff scenarioteams involvedcommon failure pointsrequired detailstool or channel
Prompt
You are an operations handoff designer.
Design a cross-team handoff template for the situation below.
Context:
- Handoff scenario: [scenario]
- Teams involved: [teams]
- Common failure points: [failure points]
- Required details or approvals: [required details]
- Tool or channel used for handoff: [tool]
Instructions:
1. Create a handoff template that captures the minimum complete context the receiving team needs.
2. Define ownership before, during, and after the handoff.
3. Include decision points, blockers, due dates, and escalation rules where useful.
4. Explain how to avoid overloading the template with low-value fields.
5. Add usage guidance so the template becomes an operating habit rather than shelfware.
Output format:
- Handoff template
- Field guidance
- Ownership and timing rules
- Escalation guidance
- Adoption notes
Missing information policy:
Proceed with assumptions unless the handoff scenario or teams involved are unclear.
Quality bar:
- Reduce rework.
- Make ownership explicit.
- Keep the template lean enough to use consistently.
08
Create an Executive Morning Brief from Fragmented Updates
Turn fragmented updates into a morning brief with priorities, risks, decisions, and follow-ups.
You’ll needupdates or source notesbusiness contextcurrent prioritiesknown risksaudiencetime horizon
Prompt
You are an executive operations partner assembling a morning brief.
Create the brief using the context below.
Context:
- Updates or source notes: [updates]
- Business or team context: [business context]
- Current company or team priorities: [priorities]
- Known risks, blockers, or escalations: [risks]
- Intended audience: [audience]
- Time horizon for this brief: [time horizon]
Instructions:
1. Sift signal from noise and surface only the updates that matter to executive decision-making.
2. Separate urgent issues, important watch items, and background context.
3. Highlight what needs a decision, follow-up, or owner today.
4. Note conflicts, missing information, or ambiguous status where leadership could misread the situation.
5. Keep the brief concise enough to use at the start of the day.
Output format:
- Top priorities today
- Critical risks or watch items
- Decisions or approvals needed
- Follow-ups by owner
- Context worth knowing but not acting on yet
Missing information policy:
Proceed with assumptions unless the source updates or intended audience are unclear.
Quality bar:
- Prioritize signal over completeness.
- Make action and ownership obvious.
- Keep it brief enough for actual executive use.
09
Build an Afternoon Priority Reset for a Busy Leader
Create an afternoon reset plan that reorders priorities, protects strategic work, and drops low-value tasks.
You’ll needtoday's current tasksnew developmentsremaining capacityhard deadlinesstrategic prioritiesdelegation options
Prompt
You are an operations chief of staff helping a leader reset priorities mid-day.
Build the reset plan using the context below.
Context:
- Current tasks or commitments for today: [tasks]
- New developments, interruptions, or requests: [developments]
- Remaining time or capacity today: [capacity]
- Hard deadlines or immovable commitments: [deadlines]
- Strategic priorities that must be protected: [strategic priorities]
- Delegation options or available support: [delegation]
Instructions:
1. Re-rank the remaining work based on business impact, urgency, and reversibility.
2. Identify what should be done now, delegated, deferred, or dropped.
3. Protect the highest-leverage strategic work from reactive busywork.
4. Make tradeoffs explicit rather than pretending everything still fits.
5. End with a realistic remainder-of-day plan.
Output format:
- Priority reset summary
- Do now
- Delegate
- Defer or drop
- Remainder-of-day plan
- Risks if lower-priority work is postponed
Missing information policy:
Proceed with assumptions unless the current workload or hard deadlines are unclear.
Quality bar:
- Clear tradeoffs.
- Protect strategic work.
- Realistic for the actual time left.
10
Create an End-of-Day Executive Wrap Brief
Turn a day of updates into an end-of-day brief with decisions, unresolved issues, and tomorrow's priorities.
You’ll needdaily updates or notestop priorities for the daydecisions madeopen issuesaudiencetomorrow context
Prompt
You are an executive operations partner preparing an end-of-day wrap brief.
Use the context below.
Context:
- Daily updates, notes, or source material: [updates]
- Top priorities for the day: [priorities]
- Decisions made or confirmed: [decisions]
- Open issues, misses, or unresolved items: [issues]
- Intended audience: [audience]
- Known priorities for tomorrow: [tomorrow]
Instructions:
1. Distill the day into the few updates leadership actually needs.
2. Separate completed movement from unresolved risk and carryover work.
3. Call out what changed materially, what remains unclear, and what must happen next.
4. Make tomorrow's starting point obvious.
5. Keep the brief concise and scan-friendly.
Output format:
- End-of-day summary
- What moved today
- Open issues or risks
- Decisions made
- Tomorrow's starting priorities
Missing information policy:
Proceed with assumptions unless the source updates or intended audience are unclear.
Quality bar:
- High signal.
- Clear carryover logic.
- Useful for tomorrow morning immediately.
11
Build a Daily Decision Queue for a Busy Leadership Team
Create a daily decision queue that separates urgent approvals, strategic calls, and lower-value noise.
You are organizing a leadership team's daily decision queue.
Use the context below.
Context:
- Pending decisions or asks: [decisions]
- Team or business context: [team]
- Urgency signals or deadlines: [urgency]
- Known owners or approvers: [owners]
- Decision deadlines or dependencies: [deadlines]
- Current strategic priorities: [priorities]
Instructions:
1. Sort the decisions by urgency, impact, and reversibility.
2. Separate true leadership decisions from decisions that should be delegated or clarified first.
3. Flag bottlenecks, missing inputs, and decisions that are likely to recur.
4. Recommend the order in which the queue should be handled today.
5. Keep the queue simple enough to use in real time.
Output format:
- Decision queue overview
- Handle now
- Delegate or push down
- Need more information
- Decisions to batch later
Missing information policy:
Proceed with assumptions unless the pending decisions or deadlines are unclear.
Quality bar:
- Sharp prioritization.
- Clear ownership.
- Reduced decision noise.
12
Create a Leadership Meeting Prep Pack from Scattered Context
Turn scattered context into a leadership meeting prep pack with agenda, decisions, risks, and discussion priorities.
You’ll needmeeting purposescattered notes or threadsparticipantsdecisions neededrisks or tensionstime available
Prompt
You are assembling a leadership meeting prep pack.
Use the context below.
Context:
- Meeting purpose: [purpose]
- Scattered notes, updates, or threads: [notes]
- Participants: [participants]
- Decisions needed: [decisions]
- Risks, tensions, or unresolved issues: [risks]
- Time available: [time]
Instructions:
1. Consolidate the context into a prep pack that makes the meeting easier to run well.
2. Surface the most important decisions, discussion points, and pre-read context.
3. Distinguish background information from items requiring active discussion.
4. Flag missing inputs that could waste the meeting.
5. Keep the pack concise enough for real pre-read use.
Output format:
- Meeting objective
- Participants and context
- Decisions required
- Discussion priorities
- Risks, missing info, or prep gaps
Missing information policy:
Proceed with assumptions unless the meeting purpose or decisions needed are unclear.
Quality bar:
- Good meeting leverage.
- Decision-ready framing.
- Minimal pre-read bloat.
13
Turn a Leadership Meeting into a Clear Action Tracker
Turn a leadership meeting into an action tracker with owners, deadlines, dependencies, and unresolved questions.
You are converting a leadership meeting into an action tracker.
Use the context below.
Context:
- Meeting notes or transcript summary: [notes]
- Decisions made or proposed: [decisions]
- Participants or owners involved: [participants]
- Follow-up expectations: [follow-up]
- Deadlines or target timing: [deadlines]
- Known blockers or dependencies: [blockers]
Instructions:
1. Extract the real actions, not just discussion topics.
2. Assign clear owners and expected timing where possible.
3. Separate committed decisions from unresolved issues.
4. Call out blockers, dependencies, and items that need escalation.
5. Make the tracker usable for the next check-in.
Output format:
- Action tracker summary
- Actions by owner
- Deadlines and dependencies
- Unresolved items
- Recommended next review point
Missing information policy:
Proceed with assumptions unless the meeting notes or ownership context are unclear.
Quality bar:
- Real actions, not vague reminders.
- Clear owners.
- Next review is obvious.
14
Design a Chief-of-Staff Follow-Up System After Leadership Meetings
Design a follow-up system after leadership meetings with action tracking, nudges, and escalation rules.
You are designing a chief-of-staff style follow-up system.
Use the context below.
Context:
- Types of leadership meetings: [meetings]
- Current follow-up problems: [problems]
- Owners or teams involved: [owners]
- Tools or systems used today: [tools]
- Desired review cadence: [cadence]
- Escalation or accountability needs: [escalation]
Instructions:
1. Design a follow-up system that captures actions, owners, deadlines, and status changes.
2. Include lightweight nudges, reviews, and escalation points.
3. Keep the system tight enough to be maintained consistently.
4. Clarify what should be tracked, what should be summarized, and what should be escalated.
5. Avoid process overhead that kills adoption.
Output format:
- System overview
- Workflow steps
- Tracking structure
- Review and escalation logic
- Adoption risks and safeguards
Missing information policy:
Proceed with assumptions unless the meeting types or current follow-up problems are unclear.
Quality bar:
- High accountability.
- Low unnecessary overhead.
- Easy to maintain weekly.
15
Create a Cross-Functional Readout Brief for Leadership
Create a cross-functional readout brief that summarizes progress, friction, dependencies, and decisions needed.
You are preparing a cross-functional readout brief for leadership.
Use the context below.
Context:
- Team updates or source material: [updates]
- Shared initiative or operating context: [initiative]
- Dependencies across teams: [dependencies]
- Current risks or friction: [risks]
- Leadership audience: [audience]
- Decisions or support needed: [decisions]
Instructions:
1. Summarize the state of the work across functions without collapsing into generic status language.
2. Surface where alignment is strong and where coordination is breaking down.
3. Highlight dependencies, blockers, and leadership-level intervention points.
4. Keep the readout concise enough for executive review.
5. End with clear asks if applicable.
Output format:
- Readout summary
- Progress by function
- Cross-functional dependencies
- Friction or blockers
- Leadership asks or decisions
Missing information policy:
Proceed with assumptions unless the initiative or audience is unclear.
Quality bar:
- Clear cross-functional signal.
- Leadership relevance.
- Low status-report bloat.
16
Turn Project Status Noise into a Signal-First Leadership Brief
Turn project status noise into a signal-first brief with progress, risk, dependencies, and leadership implications.
You are turning project status updates into a signal-first leadership brief.
Use the context below.
Context:
- Project updates, threads, or status notes: [updates]
- Project goal or scope: [goal]
- Known risks or concerns: [risks]
- Critical dependencies: [dependencies]
- Intended audience: [audience]
- Upcoming decisions or deadlines: [decisions]
Instructions:
1. Strip out low-value reporting detail and surface what matters.
2. Clarify progress, slippage, risk, and decision implications.
3. Distinguish what is merely busy from what is materially important.
4. Flag false confidence, ambiguity, or missing ownership where relevant.
5. Make the final brief usable for a leadership readout.
Output format:
- Signal summary
- What is on track
- What is at risk
- Dependencies and decisions
- Recommended leadership attention points
Missing information policy:
Proceed with assumptions unless the project goal or updates are unclear.
Quality bar:
- Signal-first framing.
- Clear leadership implications.
- No bulk reporting.
17
Design a Weekly Leadership Review Cadence
Design a weekly leadership review cadence with agenda logic, inputs, decisions, and follow-up rhythm.
You’ll needteam contextcurrent review problemstopics to coverstakeholderstime constraintsdesired outcomes
Prompt
You are designing a weekly leadership review cadence.
Use the context below.
Context:
- Team or business context: [team]
- Current review problems: [problems]
- Topics or signals that should be covered: [topics]
- Stakeholders involved: [stakeholders]
- Time constraints: [time]
- Desired outcomes from the review: [outcomes]
Instructions:
1. Design a weekly review rhythm that balances information sharing, decisions, and follow-up.
2. Clarify what should happen before, during, and after the review.
3. Keep the cadence tight enough to maintain discipline without creating ceremony.
4. Include how risks, blockers, and carryover items should surface.
5. Make the design realistic for busy operators.
Output format:
- Review cadence overview
- Pre-read and input requirements
- Meeting structure
- Follow-up rhythm
- Failure modes and safeguards
Missing information policy:
Proceed with assumptions unless the team context or desired outcomes are unclear.
Quality bar:
- Tight cadence design.
- Useful decision flow.
- Sustainable weekly usage.
18
Design a Review Meeting Around Decisions Instead of Status
Design a review meeting around decisions instead of status with agenda logic, pre-read expectations, and discussion rules.
You’ll needcurrent meeting formatparticipantsdecisions typically neededstatus overload problemstime constraintsdesired outcomes
Prompt
You are redesigning a review meeting around decisions instead of status.
Use the context below.
Context:
- Current meeting format: [format]
- Participants: [participants]
- Decisions typically needed: [decisions]
- Status overload problems: [problems]
- Time constraints: [time]
- Desired outcomes: [outcomes]
Instructions:
1. Redesign the meeting so discussion time is spent on decisions, tradeoffs, and blockers.
2. Push status into pre-read or brief summary form wherever possible.
3. Clarify what should happen before, during, and after the meeting.
4. Define rules that keep the meeting from sliding back into status recitation.
5. Keep the design realistic for the team.
Output format:
- Meeting redesign summary
- Pre-read expectations
- Decision-focused agenda structure
- In-meeting rules
- Follow-up logic
Missing information policy:
Proceed with assumptions unless the current format or desired outcomes are unclear.
Quality bar:
- Decision-first design.
- Less status clutter.
- Practical meeting discipline.
19
Write a Brief Explaining a Priority Conflict Across Teams
Write a brief explaining a priority conflict across teams with causes, tradeoffs, and decision needs.
You are writing a brief explaining a priority conflict across teams.
Use the context below.
Context:
- Priority conflict or competing demands: [conflict]
- Teams involved: [teams]
- Business impact: [impact]
- Tradeoffs involved: [tradeoffs]
- Current blockers or friction: [blockers]
- Decision or alignment needed: [decision]
Instructions:
1. Explain the conflict clearly without blaming either side.
2. Clarify what each side is optimizing for and why the conflict exists.
3. Surface the business tradeoffs and risks if no decision is made.
4. Make the required leadership decision or alignment step explicit.
5. Keep the brief concise enough for fast review.
Output format:
- Conflict summary
- What each side is optimizing for
- Tradeoffs and risks
- Decision needed
- Recommended next step
Missing information policy:
Proceed with assumptions unless the conflict or decision needed is unclear.
Quality bar:
- Clear tradeoff framing.
- Low blame.
- Fast decision usefulness.
20
Create a Next-Week Focus Brief for Leadership
Create a next-week focus brief for leadership with priorities, risks, dependencies, and watchpoints.
You’ll needcurrent status or end-of-week notesnext week's prioritiesknown risksdependenciesleadership audienceimportant timing
Prompt
You are creating a next-week focus brief for leadership.
Use the context below.
Context:
- Current status or end-of-week notes: [status]
- Next week's priorities: [priorities]
- Known risks or fragile areas: [risks]
- Dependencies or critical handoffs: [dependencies]
- Leadership audience: [audience]
- Important timing or deadlines: [timing]
Instructions:
1. Translate the coming week into a concise leadership focus brief.
2. Clarify what should matter most, what could wobble, and what needs attention early.
3. Surface cross-functional dependencies and timing pressure.
4. Keep the brief forward-looking and action-oriented.
5. Avoid generic planning language and low-value filler.
Output format:
- Next-week focus summary
- Top priorities
- Risks and fragile points
- Dependencies and timing notes
- Early leadership attention items
Missing information policy:
Proceed with assumptions unless the next week's priorities or audience are unclear.
Quality bar:
- Forward-looking signal.
- Clear timing awareness.
- Action-oriented brevity.
21
Create a Standard Format for High-Signal Status Updates
Create a standard format for high-signal status updates with movement, risk, and decision relevance.
You are creating a standard format for high-signal status updates.
Use the context below.
Context:
- Team or workflow context: [team]
- Current status-update problems: [problems]
- Leadership or stakeholder audience: [audience]
- Common update topics: [topics]
- Update cadence: [cadence]
- Desired decisions or review outcomes: [decisions]
Instructions:
1. Create a standard update format that prioritizes signal over volume.
2. Include what changed, what is at risk, and what needs support.
3. Make the format easy to repeat and easy to scan.
4. Reduce vague language and low-value recap.
5. Keep the template aligned to stakeholder decisions.
Output format:
- Status update template
- Guidance on each section
- Example phrasing rules
- Common mistakes to avoid
Missing information policy:
Proceed with assumptions unless the audience or update cadence are unclear.
Quality bar:
- Signal-first structure.
- Repeatable format.
- Stakeholder usefulness.
22
Build a Weekly Operating Review Template Focused on Decisions
Build a weekly operating review template focused on decisions, tradeoffs, risks, and action ownership.
You are building a weekly operating review template focused on decisions.
Use the context below.
Context:
- Business or team context: [context]
- Topics usually reviewed each week: [topics]
- Common review failures or frustrations: [failures]
- Leadership audience: [audience]
- Review cadence: [cadence]
- Desired outcomes: [outcomes]
Instructions:
1. Structure the review around decisions, tradeoffs, and unresolved issues.
2. Clarify what belongs in pre-read versus live discussion.
3. Make ownership and follow-up explicit.
4. Avoid turning the template into a bloated reporting artifact.
5. Keep the design sustainable for weekly use.
Output format:
- Review template
- Notes on what each section should capture
- Pre-read guidance
- Follow-up guidance
Missing information policy:
Proceed with assumptions unless the business context or desired outcomes are unclear.
Quality bar:
- Decision-centered.
- Low reporting bloat.
- Sustainable weekly use.
23
Audit an Operating Rhythm for Dead Meetings and Missed Follow-Through
Audit an operating rhythm for dead meetings, weak ownership, repetitive status loops, and missed follow-through.
You are auditing an operating rhythm for dead meetings and missed follow-through.
Use the context below.
Context:
- Current operating rhythm or cadence: [rhythm]
- Meetings involved: [meetings]
- Known deadweight or repetitive status loops: [deadweight]
- Ownership issues: [ownership]
- Follow-through problems: [follow-through]
- Desired operating outcomes: [outcomes]
Instructions:
1. Identify where the rhythm is generating ceremony instead of coordination value.
2. Distinguish meetings that are deadweight from meetings that are just badly run.
3. Surface where ownership and follow-through break down.
4. Recommend the most important changes to simplify and strengthen the rhythm.
5. Keep the audit concrete and operational.
Output format:
- Rhythm audit summary
- Dead or weak cadence points
- Ownership and follow-through issues
- Recommended changes
- Risks if unchanged
Missing information policy:
Proceed with assumptions unless the current rhythm or desired outcomes are unclear.
Quality bar:
- Ceremony reduction.
- Ownership clarity.
- Practical cadence improvement.
24
Build a Checklist for Preparing Decisions Before Leadership Review
Build a checklist for preparing decisions before leadership review with context, options, tradeoffs, and owner clarity.
You are building a checklist for preparing decisions before leadership review.
Use the context below.
Context:
- Types of decisions being prepared: [decision types]
- Current prep failures or weak spots: [failures]
- Leadership expectations: [expectations]
- Stakeholders involved: [stakeholders]
- Common missing information: [missing info]
- Time pressure or cadence: [time pressure]
Instructions:
1. Define what should be ready before a decision reaches leadership review.
2. Include context, options, tradeoffs, owner clarity, and unresolved questions.
3. Prevent low-quality decision prep from consuming live meeting time.
4. Keep the checklist concise enough to be used repeatedly.
5. Focus on decision readiness, not bureaucratic completeness.
Output format:
- Decision-prep checklist
- Why each item matters
- Common prep failures to avoid
Missing information policy:
Proceed with assumptions unless the decision types or leadership expectations are unclear.
Quality bar:
- Decision readiness.
- Repeatable use.
- Low bureaucracy.