Architects, Bridgers, Catalysts
A new innovation leadership model proposes three distinct roles — Architects (design systems), Bridgers (connect silos), and Catalysts (scale movements) — to structure teams for disciplined experimentation and psychological safety. The framing helps clarify leadership behaviors needed to move from isolated projects to company‑scale innovation argued.
Genius at Scale was published on March 3, 2026 by Harvard Business Review Press. library.hbs.edu Adopt a three-part executive update: a 90‑day trendline of system and journey KPIs, a two‑item blocker map that names owners and estimated impact, and a single scale trigger with a dollar‑to‑scale estimate and launch owner — practices aligned with journey‑level metrics guidance from Optimizely (Dec 23, 2024) and dependency‑mapping templates from Atlassian. optimizely.com Run a monthly leadership review (every 30 days) that aggregates weekly operational inputs into a one‑page scorecard, then surface the top items into a 90‑day quarterly retrospective; operational‑cadence frameworks and monthly business review playbooks recommend this weekly→monthly→quarterly flow. moxo.com Present experiments in leadership forums with sample size, effect size, and time‑to‑confidence alongside an explicit estimate of business impact (dollars, latency, or user growth); an MIT/Harvard primer on online experimentation and industry playbooks call out these specific experiment‑reporting fields. hdsr.mitpress.mit.edu Make cross‑team dependencies visible with a standardized dependency map that records owner, type of impact, and mitigation plan; Atlassian’s dependency‑mapping playbook prescribes exactly these fields and ownerships for unblockage. atlassian.com Benchmark experiment performance against industry baselines (Statsig’s benchmarking guide, Dec 3, 2025) and feed those benchmarks into a leadership strategy dashboard tied to OKRs and monthly scorecard reviews as recommended by Microsoft’s Viva Goals guidance. statsig.com The book’s research drew on leaders across 24 industries and 23 countries, and its authors argue for turning episodic pilots into repeatable, organization‑level capabilities — a framing that supports replacing ad‑hoc status updates with the structured artifacts and cadences above. exed.hbs.edu
