Using architecture groups to scale people and technology
summary
InVision grows from tens to hundreds of engineers and creates an architecture group of ~15 rotating reps to push standards, run weekly Kanban-tracked rituals, use OKRs, and host office hours that draw 50–60 attendees; they build an engineering handbook, run cross-team working groups, record Zooms, and adopt a “one to zero” speaker queue. Outcome: handbook and BCPs shipped, better cross-team discovery, persistent problem of time commitment, and a plan to staff a dedicated team of three.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:21What is an architecture group
- 3:33Set a purpose
- 5:06Choose the right people
- 7:01Rituals
- 8:42One to Zero
- 11:26Architecture Groups
- 12:26Leadership
- 15:04Working group
- 16:06Working group process
- 19:30Retro
- 25:37Level setting
related talks
16mEveryone architect!
16mEnlarge your team!
26mCreating technical leadership in context
15mManaging During Growth & Change
53mScaling Engineering by Hacking Conway's Law
24mThe Secret to Scaling a Team? Strategic Architecture
25mLeapfrogging from Good to a Great Architect
53mThe art of scaling an Engineering Organization