Bibliography & Resources

The foundational text on systems thinking. Meadows’ central argument — that system structure produces system behavior — is the intellectual basis for understanding why organizational dysfunctions persist despite the presence of talented, motivated people working to fix them.

The book that identified the problem this one is built to solve. Christensen showed why well-run companies, doing everything competent management prescribes, still miss the innovations that displace them: the resource-allocation logic that serves today’s best customers is the same logic that hides tomorrow’s opportunity. His own remedy was to spin out a separate unit; this book argues that the defense can be built into the whole operating model instead.

The paper that introduced the ‘agile has won’ framing and articulated the shift from agile as a role to agile as a skill set. Essential context for where the industry stands.

O’Reilly argues that AI transformation is less about tools than about the leader who uses them. His Traits, Tasks, Tools framework — start with who you are, identify what can be automated or amplified, then choose the tools — is a practical on-ramp for any executive in the AI moment. A natural companion to this book’s organizational focus.

The foundational Cynefin article. If you read one HBR piece to accompany this introduction, make it this one.

The comprehensive guide to the Cynefin framework for those who want to go deep.

A sharp, direct post that addresses the most common OKR mistake: using OKRs as a substitute for strategy rather than as a translation of strategy.

Written in 1984, The Goal introduced the Theory of Constraints and the idea that bottlenecks determine a system’s overall throughput. The inventory-on-the-floor analogy in this chapter draws directly on the book’s lessons. Required reading for anyone serious about flow.

A framework-agnostic set of values and principles for organizations scaling agile. Its central value — high-performing organization over high-performing teams — captures the book’s systems-thinking argument in a single phrase.

The author’s articulation of the seven mindsets and cultures that define truly agile organizations. The companion piece to this book from the team perspective.

A research-backed manifesto for applying agility at the enterprise level, grounded in C-suite surveys with 700+ responses and interviews with 30+ executives. One of the most current and credible documents in the enterprise agility space.

The source of the Business Agility definition that anchors this book. Their annual State of Business Agility research tracks global progress across organizations.

Kerievsky is also the creator of Modern Agile, a framework grounded in four principles that distill agile thinking to its human essentials. Joy of Agility extends that thinking through six mantras and real-world stories, arguing that agility is a timeless way of being rather than a set of roles and rituals.

A solid starting point for the history and evolution of VUCA as a concept, from its U.S. Army War College origins to its adoption in business strategy.

The foundational text for this chapter. Rumelt’s distinction between real strategy and the fluffy goals-dressed-as-strategy that most organizations produce is among the clearest and most practical frameworks in business literature.

The definitive treatment of strategy as an integrated choice. Martin’s five-choice cascade is the most practical tool for making strategic choices explicit at every level of the organization. The fifth choice — what management systems must support this — is the direct precursor to everything in this operating model.

The companion to Martin’s cascade. While Martin focuses on external strategic choices, Sinek argues that the winning aspiration — the ‘why’ — must come first. Organizations that lead with purpose attract the talent, customers, and commitment needed to execute strategy.

The talk that introduced the Golden Circle to the world. With over 60 million views on TED.com, it tells you something about how hungry people are for the idea that purpose precedes plan. Worth watching before any leadership strategy session.

The most practical guide to customer-centric OKRs available. Gothelf and Seiden show how to write OKRs that express genuine outcomes — changes in human behavior — rather than disguised to-do lists.

Home of the Lean Product Canvas — the one-page tool that aligns team-level work with product strategy and organizational OKRs. Essential for anyone working at the product group layer.

The book that popularized OKRs in the modern business world. Best read alongside Gothelf’s work — Doerr explains the what and why of OKRs; Gothelf explains how to avoid the most common failure modes.

A short, sharp book that lays the conceptual foundation for outcome-based management. If you read one book to prepare for the OKR conversation with your leadership team, make it this one.

The most practical guide to WIP, time theft, and invisible work. The organizational WIP limit concept in this chapter draws directly on DeGrandis’s work.

A sharp, freely available blog post worth sharing with any leadership team about to start an OKR process.

A sharp reminder that OKRs are direction-setting tools, not backlogs. If your team’s Key Results read like a to-do list, the article explains exactly why — and what to ask instead.

Framework-agnostic values and principles for organizations scaling agile. Its central value — high-performing organization over high-performing teams — captures the book’s systems-thinking argument in a single phrase. See also: Chapter 13 (Team Topologies).

The most up-to-date research-backed document on enterprise agility. Its principle, ‘govern with guardrails, not gatekeepers,’ maps directly to the governance illustration in this chapter. See also: Chapter 16 (Psychological Safety) and Chapter 13 (Team Topologies).

The book that brought OKRs to mainstream business leadership. Rich with stories from Google, Intel, Bono’s ONE campaign, and more. Best read alongside Gothelf’s work to balance inspiration with practical failure modes.

The talk that made OKRs part of mainstream leadership vocabulary. Doerr’s personal story of learning from Andy Grove at Intel and bringing the system to Google is worth the eighteen minutes.

The most human and practical OKR book available, written as a business fable about a failing tea startup. Wodtke’s weekly cadence framework, health metrics concept, and the simple discipline of keeping one Objective have influenced more successful OKR implementations than any other single resource.

The definitive guide to customer-centric OKRs. Where Doerr explains the what and why, Gothelf and Seiden show how to write Key Results that capture genuine changes in customer behavior rather than feature deliveries.

Short, sharp, and essential. The conceptual foundation of outcome-based management. If you read one book to prepare your leadership team for the OKR conversation, it is this one.

The clearest concise treatment of the strategy-first principle. Worth sharing with any leadership team before they begin writing OKRs.

For teams that say, ‘we can’t measure that,’ Hubbard’s central argument is that almost anything can be measured if you clarify what a measurement would look like. An excellent companion for teams writing Key Results for the first time.

The foundational text for this chapter. Perri’s naming of the build trap is the clearest diagnostic available to organizations that have confused shipping features with creating value. Her treatment of product strategy as the path out is equally practical.

Short, sharp, and essential. The conceptual foundation for output vs. outcome thinking. If you share one book with a leadership team before beginning the Part Two journey, this is it. Seiden makes the distinction concrete and impossible to unsee.

The customer-centric OKR guide that bridges Part One (strategy) and Part Two (product thinking). It shows how to write Key Results that reflect genuine changes in customer behavior rather than feature deliveries.

The classic business novel that makes invisible waste visible. Its factory-floor inventory metaphor is the lens that makes the build trap’s hidden costs legible to operational and financial leaders who don’t yet think in product terms.

The practitioner companion to Design Thinking and the Triple Diamond. The most accessible entry point for teams beginning to work the left diamond — rigorously understanding the problem space before committing to any solution.

Eighteen minutes that will change how your team thinks about the discipline of design. The philosophical foundation of human-centered design, told by one of its originators at IDEO and the Stanford d.school.

The most current research-backed document on enterprise agility. Its principle that leaders should approve problem spaces rather than solutions is the executive framing for everything this chapter argues.

The leadership text in Cagan’s trilogy. Written explicitly for leaders, not product managers. The empowered teams model this chapter describes lives here in full — including what leaders must stop doing as clearly as what they must start doing.

The most recent and operationally relevant. Cagan’s treatment of the full Product Operating Model transition addresses the organizational requirements of this change. If Empowered is about one team, Transformed is about the whole company.

The foundational vocabulary. Where Empowered speaks to leaders, Inspired speaks to practitioners. Essential context for understanding what great product management looks like from the inside and what it requires of leaders to make possible.

The academic foundation for the double-loop learning concept in this chapter. Dense but worth the effort for leaders who want the intellectual grounding for the distinction between solving today’s problems and redesigning the system that keeps producing them.

The origin of the 94/6 estimate and the foundational case that the overwhelming majority of an organization’s problems are built into the system — management’s responsibility — not the fault of the people inside it. Deming’s argument is the root system beneath this chapter: if the system produces the results, then questioning the system, not the people, is the only leverage that scales.

The enterprise-scale articulation of everything this chapter argues. The research behind it — 700+ C-suite respondents — lends weight to the principle that decision-making authority belongs closest to the work.

The primary text for this chapter and the most operationally specific book on product discovery. Torres’s opportunity solution tree, weekly interview cadence, and assumption-testing framework are not theoretical constructs — they are a practical system teams can begin implementing immediately. The companion blog at producttalk.org is equally essential.

The philosophical ancestor of continuous discovery. Ries’s build-measure-learn loop established that every product release should be treated as an experiment and every customer interaction as a source of learning. Torres operationalizes this more specifically, but the underlying orientation traces back to this.

Cagan’s most recent book addresses the full Product Operating Model transition, including what leaders must do to enable continuous discovery at scale. The empowered teams framework in Chapter 4 and the discovery discipline in this chapter are designed to work together.

The strategic frame explaining why continuous discovery is a leadership discipline, not just a product practice. Gothelf and Seiden argue that organizations that listen to customers continuously and respond to what they learn are fundamentally more adaptive than those that don’t.

Zappos’s story is the most vivid illustration of what customer obsession looks like as an organizational value rather than a product practice. Hsieh’s account of building the company’s culture around the customer experience is a useful provocation for leaders who want discovery to extend beyond the product team.

The original post that introduced the term. Cagan later noted that he stopped using it because it led teams to focus on process over principles. Both the original and his follow-up ‘Process vs. Model’ are worth reading for the fuller picture.

The primary text for the Jobs to Be Done framework. Christensen’s milkshake story is the most famous illustration, but the book’s real contribution is its rigorous methodology for identifying the job a customer is hiring for — and the competitive landscape that emerges once you see it correctly.

Kersten’s Flow Framework translates value stream concepts into software and technology delivery. It serves as the bridge between this chapter and Part Three. If the two-maps diagnostic has revealed where your flow is broken, Project to Product is where to start thinking about how to measure and fix it.

The most comprehensive practitioner guide to customer journey mapping available. Particularly strong in multi-channel and multi-stakeholder environments — the complex customer experience that a bank, healthcare organization, or enterprise software company actually has to navigate.

The original VSM manual. Manufacturing-rooted yet foundational. The waste categories it names translate directly into knowledge work once you stop looking for physical inventory and start looking for invisible queues.

The most accessible book-length treatment of value stream mapping for service and knowledge work environments. Written explicitly for office and service contexts, not for manufacturing floors. Frames VSM as a leadership alignment tool before presenting it as a process improvement tool.

A practical guide to organizing product work around the customer’s experience rather than a flat backlog. Patton’s method forces teams to trace the full sequence of actions a customer takes to accomplish a goal — keeping the narrative intact and revealing what must be built first. A team-level tool that grows directly from the customer-centered thinking this chapter argues for.

The most authoritative account of how Stanley’s Quencher went from near-discontinuation to a $750 million revenue driver. The clearest real-world illustration of the underserved-strength signal this chapter describes — a company whose journey map was being drawn by outsiders before the company thought to look.

The foundational text for applying systems thinking to delivery. Written as a business novel, it makes the Theory of Constraints visceral rather than abstract. The factory-floor setting translates directly to knowledge work once you stop looking for physical inventory and start looking for the invisible queues.

The most practical treatment of invisible work and WIP. DeGrandis’s five categories of work that steal capacity without appearing on any dashboard are immediately recognizable to anyone who has worked in a product organization. Required reading before your next capacity planning conversation.

The reframe this chapter closes with is developed in full. Smart’s account of agile transformation at Barclays is the most accessible treatment for senior leaders of why better outcomes — not agile adoption — are the right goal.

The experience report behind the book. Twenty-two minutes of Smart walking through the Barclays transformation in real time — descaling work, measuring Flow Efficiency, and balancing speed against control in one of the world’s most regulated industries.

Fifteen minutes that have shaped the thinking of more product practitioners than almost any other piece of content. The cutting-the-tail concept belongs in any discussion of outcome-over-scope thinking. Watch it with your product team.

The foundational text for the Flow Framework. Kersten’s account of how large organizations fail to connect technology investment to business outcomes — and his framework for fixing it — is the most operationally specific treatment of value stream measurement available to technology leaders.

For teams and leaders who want to delve deeper into the mathematics of flow, Vacanti’s treatment of cycle time distributions, Monte Carlo simulation, and service level agreements is the most rigorous practitioner-level treatment of flow metrics available.

The companion text to this chapter’s discussion of Flow Efficiency. DeGrandis’s five categories of invisible work — particularly the treatment of WIP as the root cause that amplifies everything else — are essential for any leader who wants to understand why their teams feel busy while delivery is slow.

The book behind the ‘can’t unsee lean waste’ observation in this chapter. The original VSM manual — manufacturing-rooted yet foundational. Reading it after creating your own flow maps produces the exact recognition he describes: the waste was always there.

Four minutes that make WIP limits intuitive. Toyota metaphor applied to Kanban. Required reading before any conversation about why limiting work in progress speeds things up rather than slowing them down.

The Nationwide Insurance Flow Time analysis — which shows that only 2.5% of a 120-day feature delivery was active development time — appears around the 21-minute mark. The full talk covers the Flow Framework metrics in depth.

The primary text for this chapter. Dense and rigorous — Reinertsen writes for practitioners seeking the full economic framework, not an accessible summary. The chapters on Cost of Delay, batch size, and queue theory are the most important. Read them slowly.

The cutting-the-tail concept is the practical economic argument for delivering value over accumulating features. Watch it with anyone who believes that shipping everything scoped is the definition of done.

The originator of the Now / Next / Later roadmap format. Her article, ‘I Invented the Now-Next-Later Roadmap,’ explains the thinking behind the format and is the most direct source for anyone who wants to understand it fully. Worth reading before your next roadmap conversation with senior stakeholders.

The Theory of Constraints origin story. The factory-floor setting makes queue dynamics and bottleneck economics visceral in a way that abstract frameworks cannot. The constraint analysis in this novel is the intellectual ancestor of everything Reinertsen formalizes.

The practical companion to the batch-size discussion. DeGrandis’s treatment of WIP as invisible inventory — and her techniques for making it visible — is the operational how-to Reinertsen’s framework calls for.

The most direct treatment of the project-to-product funding problem, written for the executive reader. Schwartz’s argument that the contractor-control relationship between IT and the business is the root cause of most transformation failures is the clearest articulation available of why changing the funding model is a governance change, not an accounting exercise.

The primary text. Over a decade of research, rigorous methodology, and findings that have held up across independent replications. Read the methodology section alongside the findings. The statistical approach is part of what makes the conclusions credible to skeptical audiences.

The foundational text that defined the engineering practices later validated at scale by the DORA research. If Accelerate explains why these practices matter, Continuous Delivery explains what they are. Essential background for any engineering leader seeking to understand what elite performance is built on.

The practitioner guide to implementing the technical practices identified by the DORA research. Where Accelerate describes what elite performers do, the DevOps Handbook explains how to build them. Essential for engineering leaders who want to translate the research into an improvement roadmap.

The business novel that introduced DevOps concepts to a generation of technology leaders. Reading it after Accelerate gives the research a human and organizational context. The protagonist’s journey from firefighting to flow is the most accessible illustration of the data.

The original source for the pathological/bureaucratic/generative model later validated at scale by the DORA research. Westrum’s insight — that how an organization handles information and bad news predicts its performance — is the cultural dimension underpinning the technical practices in this chapter.

The ongoing research program, now maintained by Google Cloud. It includes annual State of DevOps reports, benchmarking tools, and the most current performance band data. The website is the primary reference for current baselines and updated research findings.

The original paper. Four pages. Freely available online. The observation at its center has been cited in every serious discussion of organizational design and software architecture for fifty years. Read the original before reading any commentary about it.

The foundational text for the Star Model introduced at the end of this chapter. Galbraith’s five-element framework is the most rigorous treatment of organizational design available. The insight that structure is only one of five interdependent elements is the most important idea in Part Four.

The most accessible applied treatment of the Star Model for practitioners. Kates and Kesler translate Galbraith’s framework into a diagnostic and design methodology for working leaders. Essential companion to the next two chapters.

The military-to-business case for why traditional hierarchies fail in complex environments. McChrystal’s account of transforming JSOC is the most compelling large-scale evidence that networked, decentralized structures outperform siloed ones in uncertain conditions.

The book that builds the most practical vocabulary for deliberately applying Conway’s Law. The inverse Conway maneuver — designing your organization to match the architecture you want — is fully developed here. Chapter 12 covers the framework in depth.

The primary text. Four team types, three interaction modes, and the cognitive load principle that ties them together. The companion website includes assessment tools and interaction-mode cards for leadership teams beginning the design conversation.

The military-to-business case for decentralized, networked team structures. McChrystal’s account of transforming JSOC is the most compelling large-scale evidence for what Team Topologies argues at the product team level.

Team design is the structural element of a larger system. Galbraith’s Star Model — covered in full in Chapter 13 — provides the context for why structural changes need to be accompanied by changes to processes, rewards, and people practices to achieve lasting results.

The research connection between team structure and delivery performance. The DORA finding that loosely coupled architectures — which require the deliberate team design described in this chapter — produce both higher Deployment Frequency and lower Change Failure Rates is the empirical case for the inverse Conway maneuver.

The foundational text for the Star Model. Galbraith’s five-element framework is the most rigorous treatment of organizational design as a complete system. The insight that no single element can be changed in isolation is the most important idea in this chapter.

The most accessible applied treatment of the Star Model for practitioners. Kates and Kesler translate Galbraith’s framework into a diagnostic and design methodology. Particularly useful for the sequencing question: which element to address first and in what order to build coherence.

The primary text for the rewards section. Pink’s synthesis of Deci and Ryan’s self-determination theory is the most accessible explanation of why contingent rewards undermine intrinsic motivation in complex knowledge work.

Marquet’s second book addresses the specific language patterns that undermine the people practices described in this chapter. His ‘Complete’ play is directly applicable to the goal-writing and career development conversation guidance in this chapter.

The annual budgeting and performance management process actively undermines the adaptive organization. Hope and Fraser’s core argument — that fixed performance contracts focus managers on making the numbers rather than making a difference — applies as directly to agile transformations today as when the book was published.

The definitive practitioner’s guide to VSM beyond manufacturing. Martin’s framing of VSM as a leadership alignment tool — not just a process improvement technique — makes this book essential for executives. The subtitle says it precisely: this is about aligning leadership, not just mapping flows.

The primary text for the product-over-project argument at the organizational level. Kersten’s Flow Framework and his treatment of value streams as the organizing principle for technology investment connect directly to the product taxonomy question this chapter poses.

At scale, the same team design principles from Chapter 12 apply to how product groups relate to one another — stream-aligned, platform, enabling, and complicated-subsystem patterns exist at both the portfolio and team levels.

Kotter’s argument for the dual operating system — a hierarchy running alongside a more fluid network structure — is the most practical reframe for leaders who feel the tension between organizational stability and adaptive flow. It pairs directly with the value stream and product taxonomy argument this chapter makes.

A novel that teaches constraint theory — the insight that a system’s output is determined by its bottleneck, not by the efficiency of individual steps. Essential background for understanding why local optimization leads to system-level failure and why value stream thinking matters.

The most framework-agnostic treatment of organizational scaling available. Its core value — high-performing organizations over high-performing teams — is the argument this chapter makes at the product taxonomy level.

The most widely adopted scaling framework. It is worth understanding in detail before either adopting or critiquing it. The ART and solution train concepts described in this chapter are fully documented on the SAFe website. The framework itself is more nuanced than most implementations of it.

The operational guide to the self-management structure that represents the far end of the autonomy spectrum. It is worth understanding as a contrast to the more moderate empowered-teams model and as a proof of concept that radical decentralization is operationally achievable.

The six plays. More abstract yet more immediately applicable to knowledge work. The distinction between blue work (thinking, deciding) and red work (executing, doing) is the intellectual foundation for knowing when intent-based leadership matters most.

The Santa Fe story is the most persuasive available case study on intent-based leadership because the stakes make the failure modes of command-and-control viscerally real.

Required viewing. Marquet’s definition of leadership as embedding the capacity for greatness in people and practices, while decoupling it from the leader’s personality, is the clearest available statement of the servant leader’s operating objective.

The foundational text. Greenleaf’s argument that the servant leader is servant first — and that this is a conscious choice rather than an innate quality — is the philosophical root of the chapter’s arguments.

The conversational mechanism of the enabling leader. Schein’s argument that asking is itself a trust-building act — and that most leaders ask far less than they believe — is the practical complement to Marquet’s language framework.

Seven questions that make the leader-as-coach posture a learnable, daily practice. The most actionable companion to this chapter’s behavioral prescriptions.

The psychological interior of the shift. Brown’s research on courage, vulnerability, and the conditions for trust directly informs the behavioral change described in this chapter.

The source material for the How Do You Lead exercise. David Verble’s work on leader standard work and humble inquiry offers the most direct application of lean thinking to leadership behavior.

The primary text. Edmondson’s research spans healthcare, technology, and manufacturing, and her four-quadrant safety-accountability model is the most actionable diagnostic tool available. The case studies make the abstract argument concrete across industries.

The generative-culture half of the psychological-safety argument. Westrum’s behavioral markers — information flow, shared responsibility, and inquiry over blame — are what Edmondson’s psychological safety enables.

The conversational mechanism of safety. Schein’s argument that asking is itself a trust-building act — and that most leaders ask far less than they think — complements Edmondson’s safety framework at the individual interaction level.

The personal interior of safety. Brown’s research on vulnerability, courage, and the conditions for trust connects the leader’s inner work to the team’s outer experience. Chapters 15 and 16 present different expressions of the same underlying insight.

The DORA research connection. Forsgren’s finding that Westrum’s generative culture predicts software delivery performance provides the empirical case for treating psychological safety as a business metric, not just an HR initiative.

The primary text. Kotter’s eight-step model remains the most widely cited framework for large-scale organizational change. The 2012 updated edition includes reflections on the twenty years of transformation that followed the original publication.

Kotter’s focused treatment of the urgency problem. His distinction between genuine urgency and false urgency — frantic activity that mimics urgency but is actually a defense against change — is one of the most useful diagnostic tools for plateau diagnosis.

A sharp diagnosis of why org design is a leadership and culture problem before it is a structural one. Cutler names the asymmetry that most org design writing avoids: product defines the narrative at relatively low cost if wrong; tech has to live in it. Directly relevant to the two-system problem and to why the fault line between old and new worlds is felt most acutely at the team level.

Cutler’s application of the Lucas Critique to organizational transformation: when you change a regime, all the relationships calibrated under the old regime break down. The most analytically precise framing for why resistance to transformation is rational, not stubborn — and why stewardship of the new model must be practiced continuously, not installed once.

The source of the ‘frameworks are tools, not talismans’ line. Bastow diagnoses the scaffold-for-the-work mistake with a practitioner’s directness and outlines a recovery path for transformations stalled in process theater. Pair it with the Kniberg whitepaper below.

Three minutes. The First Follower insight — that the second person to join matters more than the person who started — is the most concise available illustration of why the guiding coalition is more important than the transformation leader.

The connection between safety and transformation. Transformations stall partly because people stop speaking the truth about what is not working. Edmondson’s framework for creating the conditions for honest conversation is directly applicable to the plateau problem.

SAFe is the most widely adopted scaling framework in enterprise agile. It is worth understanding thoroughly before adopting or critiquing it. The transformation roadmap and PI planning model are described in full on the SAFe website.

The original whitepaper described how Spotify organized its engineering at the time. Kniberg was explicit that this was a snapshot, not a prescription — a caution most organizations ignored. His 2015 follow-up post (‘Don’t copy the Spotify model’) extended the warning. Read both together.

The foundational text. The five disciplines — personal mastery, mental models, shared vision, team learning, and systems thinking — remain the most rigorous framework for building organizations that learn.

Where The Fifth Discipline makes the case, the Fieldbook provides the practice. Co-authored with colleagues from MIT and the Innovation Associates, it offers concrete exercises, facilitation tools, and organizational practices for each of the five disciplines.

The most accessible introduction to Ackoff’s body of work, written in the last year of his life. Short, sharp, and structured around the management ‘f-Laws.’ Worth reading alongside Senge: where Senge gives systems thinking its frame, Ackoff gives it its teeth.

The most direct available treatment of how culture is built. Horowitz’s argument — that culture is the cumulative product of what leaders do under pressure, not what they say in calm moments — is the necessary complement to Senge’s disciplines.

The intellectual foundation for the mental models discipline and the double-loop learning concept introduced in Chapter 4. Dense but rewarding for leaders seeking the theoretical grounding for the distinction between learning within a system and learning to change the system.

While Senge defines the disciplines of a learning organization, Kim and Spear provide the mechanisms for building one. Their three-part framework — slowify, simplify, and amplify — gives leaders concrete levers that The Fifth Discipline points to but never quite hands them. The most actionable companion to Senge available.

The empirical link between safety and learning. Edmondson’s research shows that teams cannot learn from failure in unsafe environments — they hide it. A learning organization requires psychological safety as its foundational condition.

The creator of Modern Agile — four principles that distill agility to its human essentials: Make People Awesome, Make Safety a Prerequisite, Experiment and Learn Rapidly, Deliver Value Continuously. The Make People Awesome principle offers the most human-centered reframing of the leader’s job in the agile literature.

Co-founded by Evan Leybourn, the book’s foreword author. BAI is the source of the Business Agility definition that anchors this chapter’s closing argument. Their Tomorrow-Ready DNA model (formerly the Domains of Business Agility) — five domains, eighteen capabilities, and eighty-plus observable behaviors — offers the most comprehensive empirical view of what a fully adaptive organization looks like.

This chapter draws directly on the guiding coalition argument. The middle of the organization — the managers and directors in daily contact with the work — is where Kotter’s coalition either forms or fails to form. The eight-step model is covered more fully in Chapter 17.

The most direct treatment of how culture is built. Horowitz’s argument — that culture is the cumulative product of what leaders do under pressure, not what they say in calm moments — anchors this chapter. Every small decision compounds. The question is which direction.

Kulak and Li argue that enterprise agility is not a framework rollout — it is a shift from a machine-model organization to a living, learning, value-focused human system. A useful companion for leaders seeking the systems-thinking foundation for the leadership argument in Part Five.