How to Help Teams Interact in a Remote-First World - A Team API Role Play Example
summary
Shows a concrete pattern called Team API plus templates from the Remote Team Interactions workbook and applies them in a role play that fixes a real problem: engineers can’t find who handles database provisioning because Slack channels are poorly named. The exercise renames opaque channels (example: “pluto-request” → descriptive provisioning channel), documents responsibilities, and adds dependency hooks so requests route correctly, reducing cognitive load and misdirected tickets in the simulation and producing measurable faster resolution in the example.
AI-written summary · about
related talks
05mCreating Belonging in Remote Teams
05mCreating Belonging in Remote Teams
39mPerks and Pitfalls of Building a Remote First Team
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
32mBuild Teams as an Engineer
31mAsynchronous Remote Work
30mBuilding and Leading Remote Teams
44mHow To Lead a Remote Team