← Blog

Collaboration

Realtime collaboration etiquette on a shared canvas

Presence is powerful — and chaotic — unless the team agrees on a few simple norms.

Sam Ortega · 2026-05-09 · 7 min read

Announce before you rearrange

Realtime presence lets everyone see who is on the board. That is useful until five cursors start dragging the same group. A simple norm helps: if you are about to restructure a shared area, drop a short note or say it in the call first.

Local experiments belong in a personal sandbox or a clearly marked “scratch” lane. Surprise redesigns mid-meeting create social debt even when the new layout is better.

If you need to move a large region, duplicate it first when the stakes are high. People forgive exploration more than irreversible thrash.

Facilitation roles in live sessions

Assign a driver and a scribe. The driver pans and focuses attention. The scribe captures decisions. Everyone else comments with stickies instead of hijacking the viewport.

When facilitation is shared, rotate deliberately. Unspoken competition for the “camera” of the canvas creates thrash. A timer helps: ten minutes of open editing, then a facilitated synthesis pass.

Remote teammates benefit when the driver narrates zoom changes. Silence plus sudden pans feels like watching someone else browse without context.

Conflict is a product of unclear ownership

If two people edit the same paragraph-like object, pause and decide ownership for that region. Spatial ownership — “Priya owns the left column today” — reduces merge drama more than hoping for perfect conflict resolution.

Use selection and groups as social signals: if something is grouped and labeled, treat it as intentional. If you disagree with a structure, propose an alternate cluster nearby instead of silently undoing someone else’s work.

Document the working agreements once. Pin them. Norms that live only in someone’s head do not scale past five people.

Leave the board better than you found it

After a live session, spend three minutes aligning titles, deleting duplicate stickies, and writing the decision note. Realtime energy fades; the board remains.

Async collaborators should arrive to clarity, not forensic archaeology. If the session produced a TalkTrack, link it near the decision. If it produced only vibes, write the missing sentence before you leave.

If conflict keeps repeating in the same region, the board is telling you the ownership model is wrong. Split the document, appoint a steward, or move exploratory work out of the shared lane. Social friction is often a layout problem in disguise.

Cantuva collaboration works best when presence is paired with manners. Try these norms on your next shared session — your future async readers will thank you, and your live sessions will feel less like cursor combat.

Bring this into your next session

Open Cantuva and keep ideas, docs, and decisions on one canvas.

Start free

Related posts