Untangle The Mess In Your Team’s Process
summary
Claims studio process improves by borrowing programming habits: DRY not WET, explicit roles and checklists, and regular edits. Tools actually used: Gmail/Drive/Hangouts, Trello, a CRM piped via Zapier → Trello automation (set up in ~20 minutes) and short how‑to videos for onboarding. Concrete artifacts built: an internal Wiki (the “Hub”) and a passworded client portal showing status reports. Measured wins: fewer dropped leads, clearer handoffs after 17 studio experiments and routine six‑month reviews.
AI-written summary · about
chapters (15)
- 0:00Process matters
- 4:16Communication gap in projects
- 6:00Small teams need processes
- 7:25Process defines roles
- 11:37Medical checklist approach
- 13:20Fixing team process
- 15:47Designing effective processes
- 17:31Process steward role
- 19:38Checklists versus creativity
- 22:38Key processes to define
- 28:14Sharing processes
- 31:08Onboarding new employees
- 32:54Evolving processes
- 35:42Actionable steps
- 39:21Q&A
related talks
46mManaging The Process
20mThe secret to successful on-boarding
51mPanel: Workflow Tricks for Growing Teams:Working with Freelancers & Outsource Development Agencies
27mTheory to action: Architecting and implementing your team operating system
45mConnecting Community/DevRel Teams to Other Teams
45mBetter ways of running your studio 2024
28mEmpowering Teams: Transforming Your...
28mEffortless execution: Designing processes that don’t need babysitting