This is the category we’re most excited about.
The best way to learn Totem isn’t the docs — it’s seeing how other teams actually use it. A well-structured workspace from a 4-person startup looks completely different from one built by a 40-person product org, and both are valid.
So: share yours.
What to post here
- Your Space and Collection structure, and why you organized it that way
- Tag hierarchies that have worked well (or ones you tried and abandoned)
- How you run standups, sprints, or planning cycles inside Totem
- Document templates you’ve built that others could copy
- Workflows that replaced another tool entirely
- Keyboard shortcuts or UI tricks that aren’t obvious
A few setups worth knowing about
The “one Space per team” model
Each team (Product, Engineering, Marketing, Ops) gets its own Space. Cross-team work lives in a shared Space with restricted collections. Clean, predictable, scales well past 20 people.
The “one Space per project” model
Better for agencies or project-based teams. Each client or project is a Space. Archive it when the project ends. Your active workspace stays lean.
The sprint-inside-docs approach
Some teams keep their sprint board and their spec document in the same Collection — tasks linked directly to the section of the doc they relate to. Less context-switching, especially useful for product and engineering working closely together.
To get started
Reply to this post with a quick description of how your team is set up — even just a few sentences. We’ll use the best ones as examples in our onboarding guides (with your permission).