Self-organizing development at Springest with Holacracy
summary
Company-wide Holacracy plus quarterly OKRs run through Asana produces a rigid-but-evolving governance: each person holds about seven roles on average, circles have purposes and a lead-link who sets strategy, and a created prior role curates a project pool with a mandatory “why now” for every project. Projects use a template that auto-generates tasks; resource distribution is explicit (example: provider focus 30% / user 10% / technical 15%). Measured results include a KR like 625 bookable providers baseline and above-average TinyPulse happiness for the product circle.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:36Current Organizational Structure
- 2:44The Alignment Circle
- 24:06Security
- 26:14Day-to-Day Execution
- 26:56Preparation Phase
- 32:20The Future
- 36:36Smooth Operations Circle
- 36:50Onboarding
related talks
59mLeading self-organizing teams
47mCorrelations between DevOps and Holacracy
38mThe Different Perspectives needed for Self-organization
31mHarmonizing Across Product & Engineering (Cross Team Collab)
54mSelf-governing teams through SoFA (Sociocracy for All)
24mTeamwork is difficult, can Sociocracy help?
26mHow to Design Orgs That Scale
25mNavigating the Waters: Balancing Open Source Activities in Corporate Environments