Doordash — SLA and Channel Routing
Owner: Brylle Girang
Created: 2026-04-01
Related: Doordash Workflow Plan · PR Scan Guide · Packaging Guide
Delivery SLAs by tier
| Tier | Format | SLA | Clock starts |
|---|---|---|---|
| Tier 1 — Quick Tip | Weekly digest | Held until Thursday digest — no individual SLA | PR detection on Thursday scan |
| Tier 2 — Workflow Update | Standalone Slack post | 5 business days | PR detection on Thursday scan |
| Tier 3 — New System | Forge page + Zoom Clip | Scheduled with relevant team — no fixed SLA | Confirmed with team lead |
SLA breach: If a Tier 2 item is not delivered within 5 business days, the Tier 2 SLA follow-up automation (see PR Scan Guide) posts a reminder to #learning-and-development. L&D resolves or escalates.
Channel routing
Primary channel
Status: TBD — decision required before M3.1 (April 17, 2026).
Candidates under evaluation:
| Option | Pros | Cons |
|---|---|---|
#ai-learning (existing) | Team already monitors it; no new channel fatigue | Mixed with questions and discussion; updates can get buried |
#platform-updates (new dedicated) | Clean signal; easy to mute for non-engineering roles | Requires adoption of a new channel |
#general or #announcements | Maximum visibility | Too noisy for weekly cadence; not update-specific |
| The Forge (push notification) | Permanent home; integrated with the tool | Push mechanism not yet confirmed in The Forge |
Decision criteria: Where does the team already pay attention, and what format forces the update into their workflow rather than asking them to seek it out?
Owner of the decision: Brylle Girang, confirmed with Uttam before April 17.
Once decided, update this line: Primary channel: [CHANNEL NAME] and update the Thursday automation prompt in the PR Scan Guide accordingly.
Secondary channel: The Forge
All Tier 2 and Tier 3 updates get a permanent Forge page under:
The Forge → L&D → Platform Updates / Changelog
The Forge is the long-lived reference. Slack is the push notification. If someone misses the Slack post, the Forge page is where they find it later.
Tier 1 items (quick tips) do not require a Forge page — the digest is ephemeral by design.
Audience targeting
| Audience | Routing |
|---|---|
| All team members | Primary channel (TBD) |
| Data service line only | Data SL channel + cross-post brief notice to primary |
| AI service line only | AI SL channel + cross-post brief notice to primary |
| CSO / GTM only | GTM channel + cross-post brief notice to primary |
| Platform team | Tag directly in the relevant Slack post or Forge page |
Cadence summary
| What | When | Owner |
|---|---|---|
| Weekly PR scan | Thursday morning | Cursor automation (or Brylle manually until live) |
| Tier 1 weekly digest | Thursday (same day as scan) | Cursor automation (or Brylle) |
| Tier 2 Slack post | Within 5 business days of scan | Brylle (or SL champion for SL-specific updates) |
| Tier 3 Forge page + Zoom Clip | Scheduled — no fixed SLA | Brylle + relevant team lead |
| Changelog update | Same day as each delivery | Cursor automation (or Brylle) |
| SLA breach reminder | Tuesday following Thursday scan | Cursor automation |
SLA exceptions
The following are valid reasons to push a Tier 2 delivery past the 5-day SLA. Log the reason in the changelog.
- The PR description is missing and engineer follow-up is needed
- The update is service-line-specific and the SL champion needs to review the draft before posting
- A related Tier 3 is in progress and the Tier 2 will be rolled into it for coherence
Tier 1 items never have an SLA exception — they wait for the next Thursday digest if they miss the current one.