In every product team I’ve worked with, engineering is fast and research is fast. The artefact in the middle — the brief — is the thing that takes weeks. It is gathered in meetings, drafted in Notion, reviewed in Slack, signed off in another meeting, and finally shipped to engineering as a 3,000-word document that everyone read once and then immediately misremembered.
The brief is not the problem. The problem is that the brief is a separate artefact from the evidence that justifies it. Once it’s written, the link back to the call notes and the decision memos and the support tickets that shaped it is social — it lives in the head of the PM who wrote it. When that PM leaves, or when the brief is read six months later, the evidence trail is invisible. The conclusion remains, looking authoritative; the reasoning is a rumour.
The brief as the bottleneck
The cost of this pattern is not the time to write the brief. It’s the time to re-derivethe brief six months later when the team asks “why did we agree to do this?” or “is this still the right call?”. Without the trail back to the evidence, every strategic question becomes an archaeology project. Teams either repeat the dig or skip it and trust the old conclusion. Both are expensive.
“If you can’t see what you used to believe, you can’t see what you’ve learned.”
Cultivate OS is, more than anything else, the deletion of the brief as a separate artefact. Winnow keeps the evidence and the foundations together; recommendations cite the lines that justify them inline. There is no separate brief to review and sign off on. The recommendation is the brief, and the evidence is one click away.
What this enables
An AI builder reading a Cultivate recommendation gets the strategic context attached — not as a prompt the PM had to compose, but as a citation trail the builder can read. The engineer reading the recommendation in six months can click through to the call that motivated it. The product manager picking up the project from a colleague can see the hypotheses that were tested and the ones that were refuted.
The Cultivate methodology calls this the paper trail. It’s a calm, deliberate idea — much less exciting than automation, much less viral than 10× velocity. But it’s the difference between a team that gets faster the longer it runs and a team that gets slower the longer it runs.
The brief was the bottleneck. We’re going to delete it.