Turn different teams' views into one cross-functional action plan
Combines input from several teams into one plan with shared goals, clear owners per team, handoffs, and dates.
The prompt
Turn the different teams' perspectives into one cross-functional action plan.
Shared goal: [WHAT WE ARE TRYING TO ACHIEVE, and by when]
Each team's input: [PASTE proposals, priorities, constraints, concerns - labeled by team]
Constraints: [budget, people, deadlines, systems]
Decision-maker or sponsor: [NAME or ROLE]
Steps:
1. Summarize each team's position in 2-3 lines: what they want, what they need from others, what they worry about.
2. Find the overlaps and the trade-offs. Where views conflict, propose a resolution and mark it [NEEDS SPONSOR DECISION] if teams can't settle it themselves.
3. Build one plan: workstreams, actions, one owning team per action, and the handoffs between teams.
4. Make every cross-team handoff explicit: what is handed over, when, and what "ready" means.
5. Set a simple rhythm to keep it on track (e.g. a weekly 30-minute cross-team check-in and a shared tracker).
Return:
1. One-paragraph plan summary with the goal and success measures.
2. Action plan table: # | Action | Owning team | Supporting teams | Due | Depends on | Success measure.
3. Handoff list: From | To | What | When | Definition of ready.
4. Open trade-offs and decisions needed.
5. A short Teams or Slack post introducing the plan and asking each team lead to confirm their actions by a date.
Don't commit any team to work or dates they haven't offered. Mark suggested commitments [PROPOSED - confirm with team].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- WHAT WE ARE TRYING TO ACHIEVE, and by when
- budget, people, deadlines, systems
- NAME or ROLE
- NEEDS SPONSOR DECISION
- PROPOSED - confirm with team
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Build a preventive maintenance schedule for my equipmentA maintenance plan that sets tasks and intervals per asset, balances workload, and tracks compliance.
- Turn company goals into a quarterly operations planA quarterly plan that translates company priorities into operations objectives, initiatives, metrics, and owners.
- Set up a preventive maintenance schedule for my fleetA PM program by vehicle class with service intervals, inspection checklists, parts planning, and downtime scheduling.
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.