Skip to content

Keep requests from being dropped

Use this when: People ask “What happened to my request?” several times a week.

Each step has a chance of failure, and those chances compound. The percentages below are illustrative:

Step Possible failure
A makes a request B misses the message: 5%
B copies it into a task Task omitted: 5%; due date omitted: 15%
B checks their tasks Task overlooked: 10%

Reminders may reduce the chance of a mistake at each step, but the number of steps stays the same. Removing a step eliminates one opportunity for failure.

The handoff from chat to a task management tool is fragile. As long as someone copies requests manually, some will be missed.

Connect Slack so a message becomes a task with one emoji reaction, with no copying (Create tasks from Slack).

  1. What: A title and description
  2. By when: A calendar date, rather than “sometime this week”
  3. Who: Assignees and a ball holder

“Someone, sometime this week” leaves both responsibility and timing undecided.

3. Enable due-date and start-date reminders first

Section titled “3. Enable due-date and start-date reminders first”

Enable due-date and start-date notifications under Board settings → Slack so missed deadlines become visible automatically.

4. Review tasks without due dates every week

Section titled “4. Review tasks without due dates every week”

Check the tasks without due dates in Insights → Overview. They cannot be detected as overdue, so reminders will not catch them. The fewer there are, the more the overdue reminders catch.

Treat omissions as a process problem, not a personal failing. If people expect blame, they stop reporting missed work, and the process cannot improve.

When a request is dropped, find the step where it happened and ask whether that step can be removed.