Collaboration
Cross-team friction usually comes from unclear goals, interfaces, and late feedback. RACI-lite and sync cadence reduce thrash.
Three kickoff questions
| Question | Output |
|---|---|
| What does success look like? | 1–3 verifiable criteria |
| Who decides what? | RACI or DRI list |
| When do we sync? | Standup / weekly / milestone review |
RACI-lite
| Role | Meaning |
|---|---|
| R Responsible | Does the work |
| A Accountable | Final call (one A per item) |
| C Consulted | Input before |
| I Informed | Tell after |
Example: feature launch—eng R, PM A, legal C, support I.
Sync cadence
| Meeting | Length | Purpose |
|---|---|---|
| Standup | 15 min | Blockers, today |
| Deep sync | 45 min | Options, decisions |
| Retro | 30 min | What to keep/change |
No agenda = waste; decline with: “Can we async in a doc first?”
Peer conflict playbook
- Private, within 48 h, SBI feedback.
- Resource fight → bring Accountable to prioritize.
- Personal attack → log facts; manager/HR per policy.
Remote checklist
- Time zones and response SLA in wiki/README
- Decisions in one thread
- Major changes @ DRI + Accountable
- Camera optional; big calls often better on video