Slack Scope Creep

What is this situation?

Slack Scope Creep — it starts with one “quick question” in a channel that was supposed to be for updates, not new work. You are at your desk, on your laptop between meetings, and a coworker tags you with a small ask that sounds too minor to push back on; then a manager replies in the thread, adds another person, drops in a “while we’re here,” and suddenly the task has changed shape without ever becoming an official project. The work is not on the roadmap, not in the ticket queue, not reflected in your deadlines, but it still has a timestamp, a public thread, and your name attached to it. People use soft language so it feels casual: “could you just,” “when you get a sec,” “no rush,” even though everyone can see the channel and the expectation is already forming. By the afternoon, you are switching between the thing you were hired to do and three extra asks that were never scoped, never prioritised, and never traded against anything else. The app follows you home through mobile notifications, late edits, emoji reactions, and follow-up pings that keep the work alive after the workday is supposed to be over. What wears you down is not one message; it is the way informal access becomes informal authority, turning your attention into a shared resource anyone can pull from, much like the figure in the Seven of Wands, bracing on uneven ground while staffs keep rising toward him from every side.

Why it's not you?

The problem is not that you are bad at saying no or too slow to keep up. Slack Scope Creep happens when a workplace uses chat as a back door for unplanned, unowned, unprioritized work. Those “tiny” asks create a system where the workload expands without anyone formally admitting that it has expanded.