Main idea

Four separately stabilised notes — the ticket becomes an output of the product context, product memory must preserve the trade-offs, knowledge becomes an asset if it is accessible, an insights repository is worth the link between raw material, themes, decisions and evidence — assemble into one sentence that holds them all: the product manager becomes a context architect when the ticket stops being the centre of product work.

That sentence is not the article, and it contains almost none of it: no examples, no transitions, no development. It supplies something else, and it is what is most often missing when you open an empty document — the intellectual skeleton, that is, what the text has to establish and in what order the already written ideas follow one another in it.

Writing then changes in nature. It no longer consists of discovering what you want to say while saying it, but of unrolling a line of reasoning whose pieces are laid out and whose arrangement is decided.

Why it matters

This is the moment a corpus of notes stops being a stock and becomes a means of production. Many note bases stay unused not because they lack material, but because nothing articulates that material towards a text: the thesis is that missing link.

It also lowers the cost of starting, which is the highest one. A thesis assembled from notes avoids both the blank page and the improvised outline, and lets you begin with any section.

Nuances and limits

The skeleton is not the text, and mistaking one for the other produces skeletal articles that string claims together without ever showing anything. What is still missing — examples, objections, rhythm — is exactly the work of writing.

And a thesis can give a seductive architecture to an article that had no reason to exist: standing up is not the same as being useful to someone.

Open questions

• What do you do with a solid thesis when writing reveals, halfway through, that one of the assembled notes does not say what you were making it say?