The team's thinking
A shared draft of how the team works, learned from everyone’s entries in nightly passes.
The team’s thinking describes how the team’s work gets done: its standards, its trade-offs, the way it decides. It’s about the work, not the people doing it. Everyone on the team can read it and add to it.
To open it, click the slip at the top of your contents and pick The team’s thinking.
What it learns from
- Notes and files people add to its Entries
- Entries and chapters people share with it from their own thinking or a group
- Slack channels connected to it
- Things people ask their connected AI to save “for the team”
It never learns from anyone’s own thinking unless they share something, and it never teaches anyone’s own thinking in return.
It learns in passes, not one message at a time
Your own thinking learns from each entry as it arrives. The team’s learns from new entries together, so a busy day doesn’t redraft the book over and over. A pass runs:
- every night, when anything is waiting;
- as soon as about 20 entries are waiting;
- right away when someone shares something with it, or explicitly asks their connected AI to save something to it;
- when an owner or admin presses Learn now.
The front page says when it last learned and how many entries are waiting.
Learn now
Owners and admins see Learn now on the team’s front page when entries are waiting. It starts a pass immediately, which is useful after a batch of notes you’d like reflected today.
Differences stay differences
When people on the team see something differently, the team’s thinking says so instead of averaging them into a false consensus. One person’s view isn’t presented as the team’s position unless others support it, or an owner or admin adopts it. See Adopt a chapter as the team’s position.
Arranging it
Everyone can pin and highlight for themselves. Renaming parts and chapters, moving chapters between parts, and archiving are for the team’s owners and admins.