---
title: "The Backlog Was Already There. Nobody Had Written It Down."
canonical: https://dxdev.com/blog/2026-08-10_the-backlog-was-already-in-the-chat/
datePublished: 2026-08-10
---
## Where the plan actually lived

My partner and I run a shared venture out of a chat channel. Decisions get made there. Ideas get dropped there. Someone asks a question, three tangents follow, and eventually somebody circles back and answers it, or doesn't. For months, if either of us wanted to know where things stood, the answer was to scroll back and read.

The backlog was never missing. It was sitting right there in the conversation. It just wasn't shaped like anything a person could act on at a glance.

## Why asking people to file their own thoughts doesn't work

The obvious fix looks like discipline: ask everyone to stop and log a proper task the moment they raise one, instead of just talking. That sounds reasonable until you actually try to live inside it. The value of a working conversation is that people can say whatever's on their mind without stopping to format it correctly first. The moment you make someone pause mid-thought to file it properly, you've made the channel worse at the one thing it's good at, which is letting people actually talk.

## What changed

Instead of asking people to sort their own thoughts in the moment, a system was built to do that sorting afterward, as a separate pass. Every message gets kept exactly as it was said, never edited later. Then something reads back through that record and proposes individual pieces of work, each one tied to the literal line it came from, so nothing gets invented that wasn't actually said. Those proposed pieces then get grouped into something that looks like a real task list, and a person reviews the result before anything counts as real.

The first real run pulled 270 individual pieces out of a real conversation history. 190 of them turned into an organized set of 17 tasks. The rest were genuinely just talk, an opinion or a passing note that never needed to become a task, and leaving those alone was the system doing its job correctly, not missing something.

## What a person still has to say yes to

Nothing in this pipeline gets to act on its own. Every proposed piece of work, and every grouping of those pieces into a task, lands in front of a person before it becomes part of the real record. The one place this got tightened further: bulk approval, where a person clears a whole batch of low-risk items at once to save time, is blocked outright for anything that reads like an actual decision or a real commitment. Those always get looked at individually, and even the bulk path itself won't run until someone has actually seen and confirmed a real sample from the batch first.

## The rule worth keeping

If your team's real plan lives inside a conversation and nowhere else, the fix isn't asking people to stop talking naturally so they can file things correctly. Let the conversation stay a conversation. Build the sorting into a separate pass that reads it back later, and keep a person in charge of what actually becomes real work. The backlog is probably already there. It just needs someone, or something, reading it back with the patience nobody has in the moment.