How-to: Request Help from Another Department Without a Black Hole
Cross-team asks die in three ways: sent to a channel with no owner, missing the “why now,” or arriving as a surprise deadline. A clean ask names the person, the outcome, the effort class, and the date, and it offers a graceful no. That is how work moves across departments without resentment.
Time box: 15 minutes to write, find the right owner, and send. Spend most of it on clarity, not on softening language into mush.
Context hub: how departments work together. Role hubs: Individual Contributor, New Manager. If the ask is sales-related capacity, learn the language in how sales works.
When to use / when not
Use when:
– You need another team’s time, access, data, review, or decision
– Your work is blocked or will be blocked within a known window
– You can describe done-looks-like in one sentence
Do not use when:
– You have not checked self-serve docs, dashboards, or prior tickets
– You are dumping a vague “can you help with this project?”
– The real need is an executive priority call (escalate the tradeoff, not a random IC)
– You are trying to bypass your manager’s sequencing on purpose
Prep
- Outcome: what “done” means (artifact, access, decision)
- Why it matters: customer, revenue risk, compliance, date
- Owner candidate: named human, not
#help-everyone - Effort class: tiny (<30 min), small (hours), medium (days), needs intake
- Due date with reason: “by Thu” plus what slips if not
- Links: ticket, doc, screenshot, acceptance criteria
- Thanks + escape hatch: how they can decline or redirect
Map stakeholders lightly if this is a recurring dependency; do not boil the ocean for a one-line data pull.
Steps
- Find the right door (5 min). Team intake form, on-call, team lead, or documented owner. Ask your manager if unsure rather than spamming three channels.
- Draft the ask (7 min). Use the template. Cut adjectives.
- Send once to the owner; CC sparingly (2 min). Link the ticket if your company requires it.
- Set a nudge point on your calendar before the due date.
- If no response: one bump, then escalate to their lead with the original ask attached, not a rewrite that changes scope.
Related: email that gets a decision when the other team must choose A/B, and scope creep pushback when their “yes” invents work for you.
Script (what to say / send)
Core template:
Hi [Name] - cross-team ask for [Team].
Outcome needed: [one sentence done-looks-like]
Why it matters: [customer/date/risk]
Effort guess: [tiny / small / medium] - correct me if wrong
Needed by: [date/time] because [dependency]
Links: [ticket/doc]
I can offer: [context call, acceptance tests, draft, cover on Slack]
Please reply with: Accept / Accept with later date / Redirect to [person] / Can’t take this
Thanks - [You], [Team]
Channel version: same fields, fewer lines. @ the owner.
Bump:
Bumping the ask below ahead of [date]. Still need Accept / later date / redirect / can’t. If I should go through [intake/lead], point me there.
Escalate with grace:
Hi [Lead], I sent the below to [Name] on [date] with no reply. Can you help route? Happy to adjust scope or timing. Original ask attached unchanged.
Output artifact
Ask Log (simple table):
| Date | Team | Owner | Outcome | Due | Status | Notes |
|---|---|---|---|---|---|---|
Patterns in this log feed better intake conversations and quarterly priority resets with your manager (quarterly priority reset).
Watch-outs
- Drive-by @here. Urgent for you is not a fire drill for a whole department.
- Fake tiny. Calling a week of work “quick” burns trust permanently.
- Moving due dates silently. If your date changes, update them; do not cry wolf.
- Scope creep after yes. When they accept, freeze the outcome in the ticket.
- Political CCs. Copying someone’s boss on the first ask reads as an ambush unless that is the documented path.
- Ignoring intake. If the team has a form, use it. Side DMs create invisible queues.
Finance, HR, and Sales each have different SLAs and languages. For money impacts, skim finance for non-finance managers. For people-process asks, use how HR works. Directors coordinating multi-team bets can keep a weekly stack of these asks visible in leadership forums (Director / VP hub).
Strong cross-team asks also include what you already tried. One line of “Checked [doc/dashboard/ticket search]; still need X” signals respect for their time and reduces the bounce of “did you look at the FAQ?” If the other team uses sprint intake, submit there and paste the same fields so you are not running a shadow process in Slack.
When you are the receiving team, answer with Accept / later date / redirect / can’t within your published SLA. Silence is the black hole. A fast “can’t” with a redirect is more professional than a slow maybe. Leaders can model this in staff meetings by reviewing one stuck cross-team ask each week and unblocking ownership in public.
Done looks like: a named owner, a clear outcome, an honest effort class, and a reply that is Accept, Redirect, or Can’t, not silence.