"Crisis Engineering" with Layer Aleph

Mikey Dickerson, Matthew Weaver, and Marina Kniss discuss their book *Crisis Engineering*, arguing that major organizational change is only possible during crises when normal sense-making collapses. They explain how leaders can steer this chaos to implement rapid, transformative shifts in complex systems, drawing from their experiences at Google, the US Digital Service, and the VA. The episode also covers career advice for engineers seeking influence and the ethical implications of leveraging crisis dynamics for change.

Topics discussed

Introduction and guest backgrounds Defining crisis engineering and the book's premise Clarifying the concept: managing existing crises Sense-making and social processes in complex systems Personal experiences with ransomware and data breaches The difficulty of changing habituated behavior Lessons from the Healthcare.gov crisis Why executive attention alone is not enough Critique of 'The Phoenix Project' and destabilization Reorganization as a last resort for leadership Advice for employees during organizational crises Counseling on career changes and job dissatisfaction The irony of Jira engineers and workplace misery Preparing for future AI-driven crises Navigating power dynamics in crisis war rooms Career transitions after crisis resolution Public sector stagnation and lack of clarity Taking action despite ambiguous outcomes Debunking the 'apocalypse' narrative of job hopping Corporate culture and the prohibition of fun Typical duration of crisis interventions Rapid impact assessment in early days Balancing technical fixes with psychological shepherding Variability in technical expertise across clients Challenges with large consulting firms like Deloitte Over-engineering and structural procurement issues The difficulty of government hiring and procurement Historical context of government tech hiring pilots Risks of streamlined hiring in broken systems The importance of specific hiring targets Pitching career risks to potential hires Reputation of Australian bureaucratic bodies Media silence on government inefficiency Complexity and failure in nuclear reactor design Debating the feasibility of complex technologies Comparing nuclear and coal industry safety records Long-term environmental effects of nuclear incidents Fear mongering and opposition to nuclear power Assessing tail risks and worst-case scenarios Limits of institutional change during crises Increasing frequency of critical circumstances Accepting poor management outcomes Self-aggrandizement and the importance of the work The resurgence of systems theory and cybernetics The spread of USDS models globally International expansion and first overseas gig Executive sign-off and resource allocation Building trust with individual contributors Simple fixes like fixing the coffee machine Core principles of successful consulting The myth of the 'adult in the room' The unreliability of information in crises The failure of agile theater The psychology of the operations center Ensuring executive engagement from day one Disguising tools to avoid resistance Recreating past successes and process imitation Techno-babble and misinformation in leadership Malicious use of technical jargon The reality of AI efficiency promises Business model and client selection Critique of generic UI framework advice The trajectory of frontend framework complexity Embracing anti-fragility and agile concepts The timelessness and depth of the book Balancing profound ideas with colloquial language Critique of 'business erotica' and one-villain narratives

Episode summaries and topics are generated from the audio by Castria — a free podcast app that skips ads automatically. IP Geolocation by DB-IP

"Crisis Engineering" with Layer Aleph

Summary

Topics discussed