December 15, 2019

295 words 2 mins read

The Goldilocks zone of lightweight architectural governance

The Goldilocks zone of lightweight architectural governance

Jonny LeRoy details two architectural failure modes: hierarchical command and control from ivory tower architects with strict approvals and rigorous control gates, and chaos with every team doing whatever they want with close to zero governance. Jonny then explores the "Goldilocks" zone that ensures organizational risks and opportunities are handled while giving teams as much autonomy as possible.

Talk Title The Goldilocks zone of lightweight architectural governance
Speakers Jonny LeRoy (ThoughtWorks)
Conference O’Reilly Software Architecture Conference
Conf Tag Engineering the Future of Software
Location New York, New York
Date February 4-6, 2019
URL Talk Page
Slides Talk Slides
Video

Organizations are shifting from centralized control and planning to adaptive approaches focusing on time to market, delegated autonomy and freedom to experiment. In this new world, we’re seeing two different failure modes: the first is hierarchical command and control from ivory tower architects with strict lists of approved tools and rigorous control gates for design reviews at various stages; at the opposite end of the spectrum is chaos, with every team doing whatever they want and close to zero governance. Jonny LeRoy explores the “Goldilocks” zone that makes sure organizational risks and opportunities are handled while still giving teams as much autonomy as possible within those constraints. Drawing on ThoughtWorks’s recent client experience, Jonny delves into some of the strategies and approaches for creating the Goldilocks zone of lightweight governance, including automating compliance; focusing on vision, principles, and constraints; enrolling gatekeepers as collaborators; paved roads and the pit of success; using a tech radar as a lightweight governance tool; and ADRs for visibility. Along the way, Jonny discusses how to help architects become comfortable with evolution, the org design implications, how to be responsive to skill levels on teams, and how to think about innovation zones.

comments powered by Disqus