Notes before tickets

Most product tools start where the work is already legible: a ticket, a spec, a prioritized list. That is convenient for the system, but it skips the moment where the work actually begins — the uneasy note you write to yourself at the end of a call, the contradiction you keep noticing, the question you are not ready to answer.

The cost of forcing structure too early

When the only available home for an idea is a ticket, one of two things happens. Either the idea gets squeezed into a shape it is not ready for (“Define the onboarding interview” — for a thought that was really about uncertainty), or it never gets written down, and you lose it to the chat thread you will not search again.

A note is allowed to be uncertain. A ticket is not.

The Duet Method keeps these apart on purpose. Explore on the left is a free-running feed — no required fields, no labels, no “what is this?” prompt mid-thought. Decide on the right is where an idea earns its shape: a task, a spec, a decision, or more room to think. Once decided, the work lands in a horizon — Now, Next, or Later — so the thinking and the sequencing each have their own place.

What changes when you protect the note

The interesting thing is not the note itself. It is what happens when the team can see the reasoning behind a decision later — why the onboarding interview exists, what tension it was resolving. That context is the difference between a ticket that gets built and a product choice that gets understood.

So: give the half-formed thought a home before it has a type. The structure can wait until the idea is ready, and not a moment sooner.