Working with your team
This is the collaboration playbook — not “what features exist” but “what practices work.”
Reactions vs. comments vs. chat
Section titled “Reactions vs. comments vs. chat”- Reactions for fast group signal — do we agree? does this need discussion?
- Comments for durable conversation tied to a specific card.
- Chat (in your team’s own tool) for everything else. CardBoard intentionally has no chat — inventing that primitive would be the wrong move.
Running a workshop
Section titled “Running a workshop”Synchronous sessions work best with one driver and multiple collaborators. Use reactions for “raise your hand,” and dividers to scope the focus of the moment.
Remote and async teams
Section titled “Remote and async teams”Leave boards in a known state at the end of a session. Use comments to leave context for the next person. Use outcomes to mark “what we agreed on” vs. “still discussing.”
Stale cards
Section titled “Stale cards”When a card loses relevance, move it to a dedicated outcome, archive it, or delete it. Prefer archive over delete — comment threads and history are worth keeping.
Linking out
Section titled “Linking out”Rule of thumb: card title plus a one-line description in CardBoard; anything longer lives in a linked doc, Figma, or Notion page.
Handling disagreement
Section titled “Handling disagreement”Use comments and reactions to surface dissent without arguing on the canvas. Escalate to a meeting when it’s genuinely unresolved.