Project Kickoffs That Actually Work

I'm kicking off a new project. Generate a complete kickoff package from this description.\n\nPROJECT: [project name]\nDESCRIPTION: [what we're doing and why — 2-3 sentences is fine]\nSPONSOR: [who's funding/authorizing this]\nLEAD: [who's managing day-to-day]\nTEAM: [who's involved — names or roles]\nTIMELINE: [any hard deadlines or rough timeframe]\nBUDGET: [if applicable]\nSUCCESS LOOKS LIKE: [what does done look like? how will we measure success?]\n\nGenerate:\n\n1. PROJECT BRIEF (1 page)\n- Objective: what we're doing and why, in one paragraph\n- Scope: what's in and what's explicitly out\n- Success criteria: measurable outcomes\n- Key assumptions\n- Known risks\n\n2. TIMELINE WITH MILESTONES\n- Break the project into phases\n- Key milestones with target dates\n- Dependencies between phases\n- Buffer: where should we build in slack?\n\n3. RACI MATRIX\n- For each major deliverable or decision: who is Responsible, Accountable, Consulted, Informed\n- Use the team members I listed above\n\n4. RISK REGISTER\n- Top 5 risks: what could go wrong?\n- For each: likelihood (H/M/L), impact (H/M/L), mitigation plan, owner\n\n5. KICKOFF MEETING AGENDA\n- 30-minute agenda for the kickoff meeting\n- Key questions to align on\n- Decisions that need to be made in the meeting\n- Action items to assign

We're launching a new [product/feature]. Generate a launch kickoff package.\n\nWHAT WE'RE LAUNCHING: [description]\nLAUNCH DATE: [target date]\nAUDIENCE: [who this is for]\nTEAM INVOLVED: [list roles/people]\n\nGenerate the standard kickoff package (brief, timeline, RACI, risks) plus these launch-specific elements:\n\n1. LAUNCH CHECKLIST by function:\n- Product: feature complete, QA, documentation\n- Marketing: landing page, email sequence, social, PR, blog post\n- Sales: battlecard, demo script, pricing update, FAQ\n- CS: support docs, known issues, escalation path\n- Engineering: monitoring, rollback plan, performance benchmarks\n\n2. GO/NO-GO CRITERIA\n- What must be true for us to launch on the target date?\n- What would cause us to delay?\n- Who makes the final go/no-go call?\n\n3. LAUNCH DAY RUN SHEET\n- Hour-by-hour plan for launch day\n- Who's monitoring what\n- Communication plan: internal and external\n\n4. POST-LAUNCH PLAN\n- First 48 hours: what to watch\n- First week: success metrics check\n- First month: full retrospective

We're migrating from [old tool] to [new tool]. Generate a migration kickoff package.\n\nWHAT WE'RE MIGRATING: [what the tool does for us]\nUSERS AFFECTED: [how many people, which teams]\nDATA TO MIGRATE: [what data needs to move]\nTIMELINE: [when this needs to be done]\nWHY WE'RE SWITCHING: [the driver for the change]\n\nGenerate the standard kickoff package plus these migration-specific elements:\n\n1. DATA MIGRATION PLAN\n- What data moves, what gets archived, what gets left behind\n- Data mapping: old tool fields → new tool fields\n- Cleanup needed before migration\n- Validation plan: how to verify data integrity after migration\n\n2. PARALLEL RUN PLAN\n- How long will both tools run simultaneously?\n- What happens in the old tool vs. new tool during parallel run?\n- Cut-over criteria: when do we turn off the old tool?\n\n3. TRAINING PLAN\n- Who needs training? By when?\n- Training format: live sessions, documentation, or both?\n- Power users who can help others after training\n\n4. ROLLBACK PLAN\n- What triggers a rollback?\n- How do we rollback if the migration fails?\n- Data preservation during rollback\n\n5. COMMUNICATION PLAN\n- Announce timeline: when do affected users find out?\n- Weekly updates during migration\n- Support channels for questions and issues

We're evaluating vendors for [what you need]. Generate a vendor evaluation kickoff package.\n\nWHAT WE NEED: [the capability or tool]\nWHY NOW: [what triggered this evaluation]\nBUDGET: [range]\nTIMELINE FOR DECISION: [when we need to decide]\nDECISION MAKERS: [who's involved in the choice]\n\nGenerate:\n\n1. REQUIREMENTS DOCUMENT\n- Must-have requirements (deal breakers)\n- Nice-to-have requirements (differentiators)\n- Technical requirements (integration, security, performance)\n- Business requirements (pricing model, contract terms, support)\n\n2. EVALUATION SCORECARD\n- Scoring criteria with weights\n- Rating scale (1-5 with definitions for each level)\n- Template I can fill in for each vendor\n\n3. VENDOR SHORTLIST CRITERIA\n- How do we narrow from a long list to 3-5 finalists?\n- Red flags that immediately disqualify a vendor\n\n4. EVALUATION PROCESS\n- Step-by-step timeline: research → shortlist → demos → reference checks → decision\n- Questions to ask in each demo\n- Reference check questions\n- How we'll make the final decision (consensus, scoring, executive call)\n\n5. DECISION MEMO TEMPLATE\n- Template for documenting the final decision and rationale\n- Comparison table: finalists side by side\n- Risk assessment for the chosen vendor

Generate a RACI matrix for this project.\n\nPROJECT: [project name]\nTEAM MEMBERS: [list everyone involved with their role]\n\nMAJOR DELIVERABLES/DECISIONS:\n[List the key deliverables, milestones, or decisions — or describe the project and I'll identify them]\n\nFor each deliverable or decision, assign:\n- R (Responsible): Who does the work\n- A (Accountable): Who makes the final call (only ONE person per row)\n- C (Consulted): Who provides input before the decision\n- I (Informed): Who needs to know after the decision\n\nRules:\n- Every row must have exactly one A\n- The A and R can be the same person for small teams\n- Flag any row where someone is both C and A (conflict of interest)\n- Flag any person who is R on more than 5 items (overloaded)\n\nOutput as a clean table I can paste into a doc or spreadsheet.

Generate a weekly status update for our project.\n\nPROJECT: [project name]\nORIGINAL TIMELINE: [key milestones and dates from the kickoff]\n\nTHIS WEEK'S PROGRESS:\n[Brain dump what happened this week — what got done, what didn't, any issues]\n\nGenerate a status update with:\n1. STATUS: Green / Yellow / Red (with one-sentence explanation)\n2. COMPLETED THIS WEEK: bullet list\n3. PLANNED FOR NEXT WEEK: bullet list\n4. BLOCKERS: anything preventing progress, with who needs to unblock it\n5. RISKS: any new risks that emerged, or existing risks that changed in likelihood\n6. TIMELINE CHECK: are we still on track for our milestones? If not, what's the revised estimate?\n7. DECISIONS NEEDED: any decisions the team or sponsor needs to make this week\n\nKeep it under 1 page. Executives should be able to read this in 2 minutes.