The work before the work

Every product team knows the feeling. The roadmap is full, the sprint is planned, the tickets are groomed—and yet the most important question is still hanging in the air: are we building the right thing?

Execution tools are excellent at answering “how” and “when.” They are conspicuously bad at answering “what” and “why.” That’s not a bug in those tools; it’s a boundary. The moment an idea becomes a ticket, it has already survived a long, informal journey through conversations, documents, and someone’s head. That journey—the work before the work—is where product quality is actually decided.

Ideas die in the wrong containers

A half-formed thought doesn’t belong in a ticket tracker. It has no owner, no estimate, no acceptance criteria—so the tracker rejects it, and the thought goes to a meeting note, a chat thread, or nowhere at all. By the time it resurfaces, the context that made it interesting is gone.

The reverse is just as true: a committed decision doesn’t belong in a notes app. It needs a home where its reasoning and alternatives stay attached, so the team doesn’t relitigate it three months later.

Different stages of an idea need different containers. Forcing one container on all of them is how good thinking gets lost.

Capture before classification

The cheapest way to protect an early idea is to let it exist without demanding an answer. What is this? Who owns it? When is it due? These are good questions—asked too early, they kill the thought they’re applied to.

Duet starts with a single Idea field. No labels, no per-note decisions. You write the tension, the question, the half-formed direction, and it’s safe. Classification comes later, deliberately, when the idea has earned enough shape to be triaged.

A deliberate translation

Moving an idea into committed work should feel like a translation, not a drag-and-drop. In Duet, triaging an idea means making an explicit choice: turn it into a task, start a spec, park it, or send it back for more thought. Each choice is a small commitment—and that friction is the point. It keeps the build queue full of things that have actually been thought through, rather than everything anyone ever typed.

The building still happens in your own tools. Duet just makes sure the right thing reaches them.