Project Management And Operations Prompts

INPUTS
[initiative]; [sponsor]; [objectives]; [scope]; [timeline]; [resources]

PROMPT
Write a project charter that creates a shared understanding of the work. Include the problem, intended outcome, measurable success criteria, scope boundaries, deliverables, stakeholders, roles, milestones, dependencies, assumptions, and risks. Separate confirmed commitments from proposals needing approval. Define how scope changes will be handled and who makes key decisions. Provide a concise charter and an open-questions list. End with a kickoff checklist that confirms the team can begin without unresolved disagreements about the objective or responsibilities.

INPUTS
[delivery date]; [deliverables]; [task durations]; [dependencies]; [team availability]

PROMPT
Build a workback schedule from the required delivery date. Use supplied duration estimates and mark any new estimates as provisional. Identify dependencies, review cycles, handoffs, and capacity conflicts before assigning dates. Show critical milestones and buffer where uncertainty is high. Provide a schedule table with owner, start, finish, dependency, and approval point. Flag any infeasible commitment and suggest scope or timing adjustments. Finish with the first decisions needed to make the schedule credible and a weekly update routine.

INPUTS
[process]; [current steps]; [roles]; [tools]; [exceptions]; [quality standard]

PROMPT
Create a standard operating procedure that a new team member can follow. State the purpose, trigger, prerequisites, inputs, ordered steps, expected output, and quality checks. Specify who performs each step and how exceptions are escalated. Include a checklist version for routine use and a troubleshooting section for common failure points. Preserve supplied policies and flag gaps rather than inventing rules. End with a maintenance owner, review cadence, and a practical walkthrough method for checking whether the procedure works in the real process.

INPUTS
[workflow]; [volumes]; [cycle times]; [capacity]; [error data]

PROMPT
Analyze the workflow to locate likely bottlenecks and sources of rework. Map the stages, queues, handoffs, and decision points. Use available timing and volume data to distinguish slow processing from waiting. Identify alternative explanations when the evidence is incomplete. Recommend three improvements ordered by feasibility and potential effect, without fabricating savings. Deliver a process summary, findings table, and test plan. End with the additional measurements needed to confirm the main bottleneck and check whether changes shift the problem elsewhere.

INPUTS
[project]; [outcomes]; [team feedback]; [incidents]; [meeting length]

PROMPT
Design a retrospective that produces specific improvements without assigning personal blame. Start with facts about goals and outcomes, then explore what helped, what hindered, and what surprised the team. Provide an agenda, neutral facilitation questions, and a method for gathering quieter participants' input. Turn themes into no more than three actions with owners, deadlines, and success signals. Include a way to revisit previous actions. End with a concise retrospective summary template that separates observations, interpretations, and agreed commitments.

INPUTS
[project]; [stakeholders]; [decisions]; [timeline]; [communication channels]

PROMPT
Create a communication plan based on what each stakeholder needs to understand or decide. Map their role, information needs, level of involvement, preferred channel, cadence, and escalation trigger. Avoid sending every update to everyone. Draft templates for routine progress, a decision request, and a significant change. Include a source of truth for current status and a method for handling contradictory messages. Finish with a review checklist that confirms the plan supports decisions and reduces surprises without creating unnecessary reporting work.

INPUTS
[proposed change]; [baseline scope]; [timeline]; [costs]; [dependencies]; [benefits]

PROMPT
Evaluate the change request against the project's original objectives. Explain the benefit, effort, schedule effect, capacity demands, new risks, and impact on existing commitments. Identify unknowns and estimate ranges only when enough information is available. Compare accepting now, replacing existing scope, deferring, and declining. Recommend one path with a concise rationale and required conditions. Produce a change-decision record and stakeholder update. End with a checklist ensuring the approved scope, schedule, and responsibilities are updated consistently.

INPUTS
[incident timeline]; [impact]; [system context]; [response actions]; [evidence]

PROMPT
Write a factual incident review that helps the team learn. Build a timeline, describe the impact, explain detection and response, and distinguish confirmed causes from contributing conditions and unresolved hypotheses. Use neutral language and avoid blaming individuals for system weaknesses. Identify what worked and where safeguards failed. Propose corrective actions with owners, due dates, and verification methods. End with outstanding investigation questions and a concise stakeholder summary. Do not claim a root cause is proven when the evidence only suggests it.

INPUTS
[requirements]; [vendor proposals]; [budget]; [constraints]; [evaluation criteria]

PROMPT
Compare the vendors against explicit requirements rather than sales language. Build a weighted scorecard using criteria from the context and explain the weighting. Distinguish verified capabilities, vendor claims, missing information, and assumptions. Assess implementation needs, support, integration, operating costs, and exit considerations where relevant. Recommend a shortlist and a demonstration script that tests the most important workflows. End with references to verify, questions for each vendor, and conditions that should be resolved before a purchasing decision is made.

INPUTS
[process or project]; [outgoing owner notes]; [incoming owner]; [open items]; [key dates]

PROMPT
Create an operational handoff that allows the incoming owner to continue with minimal uncertainty. Summarize purpose, current state, recurring tasks, important contacts, decision history, deadlines, dependencies, and known failure points. Separate urgent actions from reference information. Include access requirements without exposing credentials, and mark missing details for confirmation. Provide a first-week checklist and a short handoff meeting agenda. End with acceptance criteria showing the incoming owner understands the work and knows where unresolved issues and authoritative information are recorded.