Replace "just ping me" with paths, owners, and reply windows
"Just ping me" sounds helpful. It makes the speaker the router for every question. Knowledge stays private. Time zones punish anyone not staring at chat. The team looks responsive and still rediscovers the same answers weekly.
A communication system names where requests go, who owns them, and when a reply is due. Helpfulness is leaving a path behind - not leaving your DMs open. Publish a path table (status / decision / how-to / blocker / access), keep office hours as a release valve, and spend sixty seconds improving the doc after every novel answer. Primer: async communication for distributed teams. What breaks without paths: bus factor of one; priority inversion where loud pings beat quiet important work; unfair hours (response expectations across time zones); decisions that vanish in DMs.
Replace pings with named paths, owners, and reply windows
| Need | Instead of ping | Path | Owner | Reply window (GetToWork rule of thumb) |
|---|---|---|---|---|
| Status | "Any update?" DM | Ticket comment or written status | Ticket owner | Next local business day unless blocking |
| Decision | Ambush huddle | Short options doc + ask-by date | Named decision owner | By the ask-by date in UTC |
| How-to | "Got a sec?" | FAQ / runbook link | Doc maintainer | Doc first; office hours if stuck |
| Blocker | Soft complaint | Explicit blocker update with impact | Team lead or on-call if production | Overlap hours or page path |
| Access | "Can you add me?" | Access ticket with manager approval | Access rotation | Two business days; rush via on-call |
Publish the table where newcomers look. Then model it: if leaders still answer unstructured DMs privately, the table is fiction.
Worked before / after: deploy questions
Before: Channel culture is "just ping Ana if deploy looks weird." Five people ping Ana weekly. Ana answers in DMs. The sixth person still has no idea. Ana's focus blocks die. Onboarding tells new hires to ping Ana for access too.
After: Channel topic links runbook R3. Ticket queue owns access requests with a two-business-day window. On-call owns production-impacting deploy failures via page path. Ana's reply when someone DMs anyway: "Follow R3; if customers impacted, page on-call; otherwise note in #ops with screenshot - I review in the 14:00 UTC overlap." Sixty seconds after answering a novel question, Ana updates R3 so the next person gets the link.
Metric that matters: repeat deploy questions per month, not Ana's DM response time. Praise "reduced deploy questions by updating R3" in standup equal to feature work.
Worked before / after: founder line-jump
Before: Client CEO DMs the engineer for status while the PM owns the project. Two sources of truth diverge. Engineer context-switches mid-feature. PM learns late.
After: SOW names channels: status in ticket, urgent production via phone tree, preferences via PM. Engineer redirects once politely: "Logged on TICKET-88 and copied Maya (PM); details there." Repeat redirects in public until the path sticks. Personal WhatsApp is not a support portal.
Written requests beat ambiguous pings
Ask teams to post requests with: goal, context link, needed-by (UTC), what they tried. Ping without structure forces the receiver to interview the sender - unpaid coordination tax.
Office hours as release valve: two weekly slots where live help is welcome. Outside slots, async paths. Satisfies people who like talk without making talk the default infrastructure.
Escalation is not insult. "This is blocked production - use page" protects IC focus. Support queues belong in tools with SLAs, not in engineering DMs. On-call is scheduled, compensated, and bounded. Ping-me is none of those.
When you answer once, improve the doc
When you answer a ping, spend sixty seconds improving the doc or channel topic. Next ping becomes "see section 3." Graduate decisions and how-tos into durable notes linked from the work item (document team decisions without bureaucracy).
Track repeat questions for a month. GetToWork rule of thumb: any question asked three times in a month deserves a doc section, FAQ line, or ticket template - not a third DM answer. Managers who route all questions through one senior engineer burn that person's focus blocks and hide team-wide documentation gaps. Rotate "doc fix" ownership the same way you rotate on-call.
Bad vs good helpfulness
| Bad | Good |
|---|---|
| Instant DM replies as identity | Documented paths + overlap hours |
| Being the human search engine | Pointing to the doc, then improving the doc |
| Always-available badge | Posted hours: available all day is a bad system |
| Sales "quick tech" DMs anytime | Named pre-sales slot or shared FAQ |
| Interns told "ping X" | Onboarding checklist + access ticket SLA |
When ping is still correct
Novel incidents, sensitive personnel issues, true pairing on hard problems - ping or call is fine. Sometimes a person is stuck emotionally, not informationally; a short live conversation is kindness. Default for recurring work should still be system-first.
Async-first companies still ping when stressed. Redirect in public: "Logged on TICKET; details there" until the culture learns the path. Expect grumbling week two. Expect relief week six when focus returns.
Freelancers who give personal phone access for "quick questions" sell infinite context switching. Move clients to ticket or email with a response window in the SOW. Urgent paths exist for true blockers, not preference changes.
Migration week plan (replace ping-me without a rebellion)
Day 1: Post the paths table in the channel topic and onboarding doc. Announce office hours.
Day 2-5: Leaders redirect every unstructured DM once in public with a link - no private exception for friends.
Week 2: Log repeat questions in a shared note. Any question appearing three times gets a doc section before Friday.
Week 3: Measure: DM volume to the old human router, time-to-first-contribution for the newest hire, and number of runbook updates. Celebrate doc fixes in standup equal to features.
Week 4: Retire "just ping me" from bios and welcome messages. Replace with "start at PATH; office hours SLOT; emergencies PAGE."
Expect grumbling. People who liked being the hero feel demoted. Reframe: the hero move is leaving a system that works when you are on vacation.
Sales and engineering boundary belongs in the same table: "quick tech answer" DMs train chaos. Named pre-sales slot or shared FAQ. New managers who ping for status instead of reading the written update need retraining to the status doc - same as everyone else.
Security and access: ticket with manager approval, never "ping me your password." Vendor partners get support email and emergency phone - not your personal WhatsApp. Social chat channels can satisfy human connection without making every human the API.
Intern season often spikes pings because docs are stale. Assign doc fixes as intern projects fed by the repeat-questions log. Each redirected ping with a link is a brick in the system; each repeated private answer is a brick removed.
Ping-me culture is a loan against future throughput. Pay it down with paths, owners, and visible hours. Success is fewer repeat questions and faster time-to-first-contribution for new hires - not fastest Slack response time.