Main idea

Jira, Notion and their equivalents remain card tools: items, statuses, fields, comments. They coordinate an already decided action correctly. They are weak at building product thinking, and the built-in agents that rephrase a ticket or offer a summary don't change that nature — improving a piece of text is not thinking.

The work of reflection happens upstream, in a space that holds sources, transcribed interviews, notes, glossaries, decisions, standards, product data, analyses, customer signals, and the links between what the product does and what it doesn't. The tracking tool then becomes an output chain: you push information into it once it is ready to be worked on collectively.

Why it matters

This redefines what you expect from a management tool. You stop reproaching it for not helping you think — that isn't its role — and you stop looking through its features for an answer to a need that sits elsewhere in the chain.

It also shifts the investment. Enriching the upstream layer returns something no improvement to a ticket's description field ever will.

Nuances and limits

The separation is clean on paper and porous in practice: a discussion in a ticket's comments regularly produces a decision that exists nowhere else, and nobody carries it back upstream.

And two spaces instead of one presuppose that someone keeps the second one up; badly kept, it becomes a third place to search.

Open questions

• How do you recover the decisions born in a tracking tool's comments without letting them die there?