Skip to content

Cross-Team Dependency Tracker

Example prompt: "Every morning, check Asana for tasks labelled 'waiting-on-external'. For each one, post a reminder in the relevant team's Slack channel and email the dependency owner if it's been waiting more than 3 days."

How to automate cross-team dependency tracking with GloriaMundo

The Problem

Cross-team dependencies are where projects quietly stall. A design team is waiting on copy from marketing. Engineering needs an API key from the platform team. A client deliverable is held up because legal has not signed off. Each dependency lives in someone else's task board, and the team waiting has no visibility into when it will be resolved. The usual approach is to chase people on Slack, which works once but is easy to forget on day two and day three. By the time the blocked task surfaces in a standup, it has often been stuck for a week, and the knock-on delay is already baked in.

How GloriaMundo Solves It

We build a daily workflow that scans your project board for tasks marked as blocked on an external dependency. An integration step queries Asana for all tasks with a "waiting-on-external" label (or equivalent). A code step calculates how long each task has been in this state and groups them by the team responsible for unblocking. For dependencies under 3 days old, the workflow posts a polite reminder in the relevant team's Slack channel. For those 3 or more days old, it sends an email to the dependency owner with the task details, how long it has been waiting, and a direct link. Glass Box preview shows you every message and email before they go out, so you can adjust the tone or skip items that you know are already being handled.

Example Workflow Steps

  1. Trigger (scheduled): Runs every morning at 9:30 AM.
  2. Step 1 (integration): Query Asana for all tasks with the "waiting-on-external" label — task name, assignee, blocking team, date the label was added, and task link.
  3. Step 2 (code): Calculate the number of days each task has been waiting. Group tasks by the team responsible for resolving the dependency.
  4. Step 3 (conditional): For tasks waiting fewer than 3 days, route to Slack reminder. For tasks waiting 3+ days, route to email escalation.
  5. Step 4 (integration): Post a grouped reminder to each relevant team's Slack channel listing the tasks waiting on them, with links.
  6. Step 5 (integration): For 3+ day dependencies, send an email via Gmail to the dependency owner with the task name, days waiting, assignee who is blocked, and a link to the task.

Integrations Used

  • Asana — source of dependency data, queried daily for tasks with blocking labels
  • Slack — delivers grouped reminders to team channels for recent dependencies
  • Gmail — sends escalation emails to dependency owners for items stuck 3+ days

Who This Is For

Project managers, programme managers, and delivery leads coordinating work across 3 or more teams where handoffs and dependencies are a regular source of delay. Common in product companies with separate design, engineering, and marketing teams, and in agencies managing multi-discipline client projects.

Time & Cost Saved

Tracking cross-team dependencies manually — checking task boards, chasing people on Slack, keeping a spreadsheet of who owes what — takes 15-25 minutes per day for a PM managing multiple projects. Over a month, that is 5-8 hours. More importantly, the automated daily cadence means nothing falls through the cracks: a dependency that would otherwise sit unnoticed for a week gets surfaced on day one and escalated on day three.