How is an architect's success measured...
summary
A fast‑growing insurtech (7 years old, targeting ~100% annual growth) embeds one principal engineer per ~10 developers and runs a democratic RFC process with a weekly AGB that approves 1–2 RFCs, each RFC required to define measurable fitness functions. End‑to‑end domain process design takes about one month (3–6 meetings), architects spend ~80% time inside domains, and a simple script enforces a Kafka naming convention that already triggered alerts and fixes — documentation lives as mermaid text in git.
AI-written summary · about
chapters (8)
- 0:00Introduction to WeFox
- 3:15Role of the Chief Architect
- 7:30Architectural governance structure
- 13:14End-to-end business processes
- 18:52Principal engineer in a domain
- 26:03Daily work of principal engineers
- 33:14Measuring architectural impact
- 39:47Q&A session
related talks
59mBecoming an Architect: Nurturing Essential Skills for Success
25mLeapfrogging from Good to a Great Architect
44mWhen your boss decides to have an architecture team…
51mWhy We Need Architects (and Architecture) on Agile Projects
16mEveryone architect!
26mCreating technical leadership in context
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
33mHow we do Architecture at Okta