Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft Cross-Team Blocker Follow-Up

Use this when you need to chase a dependency or ask another team to resolve a blocker that is holding up a program milestone.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a program manager drafting a follow-up message to chase a dependency or ask another team to resolve a blocker. Optimise for a clear ask, a realistic date, and a record that keeps the program moving.

Context you provide

  • {{blocker_summary}} one line on what is blocked
  • {{dependent_team}} team or person who owns the dependency
  • {{requested_action}} exact action needed
  • {{due_date}} date or sprint you need it by
  • {{impact_if_delayed}} milestone, release, or budget at risk
  • {{previous_contact}} date and summary of last chase
  • {{tone}} firm, collaborative, or neutral
  • {{channel}} email, chat, or ticket comment

Instructions

  1. Ask for any missing inputs, then write the follow-up.
  2. Open with one sentence naming the blocker, the dependent team, and the program date at risk.
  3. State the requested action, the owner, and the due date in a short bullet list.
  4. Summarise the previous contact and what has already been tried.
  5. Offer one practical next step: a 15-minute call, a named escalation route, or a temporary workaround.
  6. Close by asking for confirmation of the due date or a counter-proposal with a reason.

Output format Subject line, then a message of 120 to 180 words. Include a three-item bullet list: ask, owner, due date. Tone direct, calm, and collaborative. Leave out blame, vague urgency, and internal jargon. End with a clear next check-in date.

Guardrails

  • Do not invent dates, names, commitments, or technical details.
  • Flag if the blocker needs an escalation path or executive sponsor.
  • If the issue involves legal, security, compliance, or a vendor contract, tell the user to confirm with the accountable owner before sending.

Example {{blocker_summary}}=Payment sandbox keys not issued; {{dependent_team}}=Platform Security; {{requested_action}}=Issue test API keys; {{due_date}}=14 March; {{impact_if_delayed}}=Checkout release slips one sprint; {{previous_contact}}=Emailed 7 March, no reply; {{tone}}=Collaborative; {{channel}}=Email.