Thank God it's Open Friday
summary
Company-wide Open Space runs every other Friday (10:00–16:00), funded as 10% of our time, with 100+ people from product, legal, accounting and support pitching slots, pairing, and posting notes to Yammer. It replaces ad hoc NDS attempts, surfaces and fixes maintenance bugs, sparks cross-team features and pattern-library work, and collapses meetings into actionable sessions. The built ritual proves repeatable: attendance, searchable notes and shipped fixes show it actually works as advertised, not just a promise.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:15What is Open Friday
- 3:49Scrum challenges and silos
- 7:19Unsustainable pace and debt
- 11:38Slack time solutions
- 14:26ZipGate’s Sprint break
- 17:18NES failure and trust issues
- 21:54Lessons learned and evolution
- 24:21Open Space Technology discovery
- 27:31Open Space in practice
- 30:25Transition to Open Friday
- 33:16Why Open Friday works
- 36:36Benefits and advantages
- 40:10Cross-department collaboration
- 43:26High energy and fun
- 44:07Implementation tips
- 45:20Q&A
related talks
06mHow Sonar Builds a Culture of Innovation and Accountability
15mGrowing at Work with Community-oriented Development
40mSoftware Delivery - 10% time the pros and cons?
26mNavigating Open Source: Establishing an OSPO for Organizational Success
03mVideo resumen
17mCreating a knowledge-sharing culture
24mTeam Building : It's Social Time!
24mAgile working in a slow-moving world