The prompt
Score 10 of 10, Excellent
Use it when Your project depends on work from a team you do not manage, and you need a firm date from them without souring the relationship.
- {{other_team_lead}}
- {{other_team}}
- {{plan_deadline}}
- {{work_needed}}
- {{why_needed}}
- {{needed_by}}
- {{history}}
- {{offer}}
- {{channel}}
- {{word_limit}}
Full prompt and why it works
Prompt
Write a message to {{other_team_lead}}, who leads {{other_team}}, asking them to commit to a date for the work below that my project depends on, so that I can confirm our plan by {{plan_deadline}}. I do not manage this team and they have their own priorities, so the message has to make the request easy to say yes to and easy to answer. What we need from them: {{work_needed}} Why we need it, and what it unblocks: {{why_needed}} The latest date that keeps our plan on track: {{needed_by}} What has been said or agreed so far, if anything: """ {{history}} """ What we can offer to make it easier (help, flexibility on scope, a smaller first piece): {{offer}} How I will send it: {{channel}} Structure: 1. The ask in the first two sentences: what we need, by when, and that we are asking them to confirm a date. 2. Why it matters: what it unblocks, in one or two sentences, in terms of the shared goal or the customer rather than our own schedule. 3. What we can do to help. 4. A clear question that is easy to answer: confirm the date, propose another, or say what they would need in order to commit. 5. When I will follow up. Keep it under {{word_limit}} words. It should sound like a peer asking for help, direct and respectful. A good message gets either a date or a clear reason why not in a single reply. For example, the form of the closing question: "Can you let me know by Thursday whether the API change can land by the 14th, or what date would work and what you'd need from us?" This example shows the form only. Do not copy in managers, hint at escalation, or imply their team has let us down, because the goal is a commitment, not a record of blame. Do not overstate the impact beyond what I have written. If what we need is vague in the details above, for example with no clear definition of done, point that out before the draft and suggest what to add, since a vague request gets a vague date.
Variables
- {{other_team_lead}}
- The person you are writing to, by name or role.
- {{other_team}}
- Their team, for example "the data platform team".
- {{plan_deadline}}
- When you must confirm your own plan, for example "the steering meeting on the 20th".
- {{work_needed}}
- Exactly what you need from them, and what done looks like.
- {{why_needed}}
- What it unblocks, for example "the customer pilot cannot start without the new export".
- {{needed_by}}
- The latest date that keeps your plan on track.
- {{history}}
- Earlier messages or meeting notes about this request. Write "none" if this is the first ask.
- {{offer}}
- What you can do in return, for example "one of our engineers can pair on it". Write "nothing" if you have nothing to offer.
- {{channel}}
- How you will send it, for example email or a direct message.
- {{word_limit}}
- The maximum length, for example 150.
Why it works
- Who it's for. It is written for a peer you cannot direct, so it has to make a yes easy and frame the need around the shared goal rather than your schedule.
- What to avoid. No copied managers, escalation hints or blame, which tend to get a defensive answer rather than a date.
- If unsure. A request with no clear definition of done is flagged before drafting, because a vague ask only ever gets a vague commitment.