For years, management thinkers assumed that there were inevitable trade-offs between efficiency and flexibility — and that the right organizational design for each was different. But it’s possible to design an organization’s work in ways that simultaneously offer agility and efficiency — if you know how.

You can hardly pick up a business publication without reading about the ever-increasing pace of change in technologies and markets and the consequent need for more adaptable organizations. Given the imperative of adaptability, it is not surprising that few words have received more attention in recent conversations about management and leadership than “agile.”1 Organizations ranging from large corporations like General Electric Co. to tiny startups are trying to be both flexible and fast in the ways that they react to new technology and changing market conditions.2

The word “agile” appears to have been first applied to thinking about software by 17 developers in 2001.3 Having experimented with more iterative, less process-laden approaches to developing new applications for several decades, the group codified its experience in an agile manifesto. “We are uncovering better ways of developing software by doing it and helping others do it,” they wrote. In software development, agile now has a variety of manifestations, including scrum, extreme programming, and feature-driven development.4 The results have been significant. A variety of studies show that agile software development methods can generate a significant improvement over their more traditional predecessors.5

But what does this mean outside of software? Can agile methods be successfully applied to other types of work? Many proponents (a number of whom started in the software industry) argue that the answer is yes, and a growing collection of books, papers, and blog posts suggests how it might be done.6 The evidence, however, remains limited to date, and a recent article by two of agile’s founders cautions against applying agile indiscriminately.7 The blogosphere is also replete with discussions of an ongoing agile backlash.

To provide some practical advice to business leaders trying to understand what agile might mean for their organizations, we take a different approach. Our research suggests that in applying agile methods from the software industry to other domains, managers often confuse practices and principles. When agile methods work, they do so because the associated practices manifest key behavioral principles in the context of software development. But, successful as those practices can be when developing software, there is no guarantee that they will work in other contexts. The key to transferring a set of practices from one domain to another is to first understand why they work and then to modify them in ways that both match the new context and preserve the underlying principles.

The goal of this article is to help you understand several key work design principles that undergird not only agile practices in software but also Toyota Motor Corp.’s well-known production system in manufacturing. Once you understand these underlying work design principles — through a framework we call dynamic work design — you can create work processes in your own organization that are both more flexible and more efficient. (See “About the Research.”)

About the Research Our dynamic work design framework originated more than 20 years ago when two of the authors worked together to improve both manufacturing and product development at Harley-Davidson Inc. (At the time, one of the authors [Don Kieffer] was leading Harley-Davidson’s largest engine development project, and another [Nelson Repenning] was doing research on failures in new product development.) Following the principles of action research, in the ensuing decades we have regularly iterated between trying to help organizations improve their work design and building a theory grounded in the underlying social science for why these interventions did or did not work. Over the years, we have done dozens of projects in a variety of industries, including oil and gas, software, and genetic sequencing. We have also supervised more than 1,000 work design projects done by executives in our courses at MIT.



Stability vs. Uncertainty

Academics and managers alike long believed that organizations had to make trade-offs between flexibility and efficiency. A central notion in the academic theory on organizational design is contingency, the idea that organizations and their associated processes need to be designed to match the nature of the work they do. One of the most common variables in contingency theory is the degree of uncertainty in the surrounding environment (often also conceptualized as the need for innovation). When both the competitive environment and the associated work are stable and well understood, contingency theory suggests that organizations will do best with highly structured, mechanistic designs. In contrast, when facing highly uncertain situations that require ongoing adaptation, the theory suggests that organizations will do better with more flexible, organic designs.8

An early advocate of the mechanistic approach to work design was Frederick Winslow Taylor, author of the 1911 book The Principles of Scientific Management .9 Taylor’s essential insight was simply that if work is regularly repeated, it can also be studied and improved. In stable, well-understood environments, it is thus often best to organize work in ways that leverage the efficiency that comes with repetition. For example, in a modern factory, well-defined tasks are specified, and the work proceeds serially, moving from one carefully constructed and defined set of activities to the next. There is little need for collaboration in these settings, and the organizational structure that surrounds stable and repeatable work tends to be hierarchical to ensure that everybody follows the prescribed work design. The cost of such efficiency is adaptability. Due to the high degree of routinization and formalization, mechanistic process designs are difficult to change in response to new requirements. Though efficient, a mechanistic design is not agile.

When, however, the environment is unstable and uncertain, discrete tasks are harder to define, and therefore organizations cannot rely on a sequence of clearly defined steps. For example, product development teams often face challenges for which there is little precedent. Contingency theory holds that in unpredictable environments like new product development, organizations rely more on things like training and collaboration and less on routinization and careful specification. Developing a breakthrough product or service usually can’t be organized like a factory assembly line. Marketing experts may develop a set of initial requirements, which are then passed on to designers and engineers, but the requirements often evolve through multiple iterations as designers and engineers determine what is technically feasible. Consequently, effective development processes often require ongoing real-time collaboration, rather than rote adherence to a set of sequentially organized steps.

Though the contingency theory was first developed more than 50 years ago, its basic insights reappear frequently in contemporary management thinking. Many flavors of process-focused improvement, such as total quality management, Six Sigma, and business process reengineering, are extensions to Taylor’s fundamental insight that work that is repeated can also be improved. Recently, the increasingly popular design thinking approach can be thought of as a charge to tackle ambiguous, uncertain tasks with a more collaborative, less hierarchical work design.10 In general, contingency theory gives managers a straightforward approach to designing work: Assess the stability of the competitive environment and the resulting work, and then pick the best mix of defined tasks and collaboration to fit the challenge at hand. (See “A Traditional Approach to Work Design.”) If the work being designed consists of well-defined tasks (for example, assembling components), then it is best to organize it serially, or, as we label the cell on the bottom left, using the “factory” mode. Conversely, if the work is highly ambiguous and requires ongoing interaction (for example, designing new products), then the work is best organized collaboratively, or, as we label the cell on the top right, in “studio” mode.

A Traditional Approach to Work Design



Though powerful, this approach to work design is not entirely satisfying for two reasons. First, it describes an unpalatable trade-off: Work done using the serial factory design isn’t very flexible, making it hard to adapt to changes in external conditions, and work done using the collaborative studio approach often isn’t very efficient. Second, few types of work perfectly fit the archetype of well-defined or ambiguous work. Even the most routine work has the occasional moment of surprise, and conversely, even the most novel work, such as designing a new product or service, often requires executing routine analysis and testing activities that support each creative iteration. Academic theory notwithstanding, real work is a constantly evolving mix of routine and uncertainty.

At first glance, agile methods appear to fall more toward the collaborative side of the work spectrum. However, our research suggests a different interpretation. The conventional approach to process and organizational design is almost entirely static, implicitly presuming that once a piece of work has been designed, everything will go as planned. In contrast, a dynamic approach to work design suggests viewing work as an ever-evolving response to the hiccups and shortfalls that are inevitable in real organizations. As we will describe later in this article, agile methods actually transcend the traditional serial vs. collaborative work framework by creating better mechanisms for moving between the two basic ways of organizing work. By identifying mechanisms to cycle back and forth between well-defined factory-style tasks and collaborative studio modes when appropriate, an agile approach can considerably reduce the trade-off between efficiency and adaptability.

Research Updates From MIT SMR Get weekly updates on how global companies are managing in a changing world. subscribe Please enter a valid email address Thank you for signing up Privacy Policy

Dynamic Work Design at Toyota

What does this look like in practice? Consider a well-known example of work and organizational design, Toyota’s Andon cord. Work on Toyota assembly lines is the epitome of the serial, mechanistic design. Tasks are precisely specified, often detailing specific arm and hand movements and the time that each action should take. In a plant we visited recently, training for a specific role began with the trainee learning to pick up four bolts at a time — not three and not five. Only when the trainee could pick up four bolts regularly was she allowed to learn the next motion. But, despite an attention to detail that would have made Taylor proud, sometimes things go awry. In the Toyota scheme, a worker noticing such an issue is supposed to pull what’s known as the Andon cord (or push a button) to stop the production line and fix the problem.

While the management literature has correctly highlighted the importance of allowing employees to stop the line,11 what happens after the cord is pulled might be more important. During a recent visit we took to a Toyota supplier in Toyota City, Japan, we observed that one operator on the factory floor was struggling to complete her task in the allotted time, and so she hit a yellow button, causing an alarm to sound and a light to flash. (This factory has replaced the Andon cord with a yellow button at each operator’s station.) Within seconds, the line’s supervisor arrived and assisted the operator in resolving the issue that was preventing her from following the prescribed process. In less than a minute, the operator, now able to hit her target, returned to her normal routine, and the supervisor went back to other activities.

What, from a work design perspective, happened in this short episode? Initially, the operator was working in the “factory” mode, executing well-defined work to a clearly specified time target. (See the box on the lower left in the exhibit “Dynamic Work Design at a Toyota Supplier.”) But when something in that careful design broke down, the operator couldn’t complete her task in the allotted time. Once the problem occurred, the operator had two options for responding. She could have found an ad hoc adjustment, a workaround or shortcut that would allow her to keep working. But this choice often leads to highly dysfunctional outcomes.12 Alternatively, as we observed, she could push the button, stop the work, and ask for help. By summoning the supervisor to help, pushing the button temporarily changed the work design. The system briefly left the mechanistic, serial mode in favor of a more organic, collaborative approach focused on problem resolution. Once the problem was resolved, the operator returned to her normal task and to the serial work design.

Dynamic Work Design at a Toyota Supplier



The Toyota production system might at first appear to be the ultimate in mechanistic design, but a closer look suggests something far more dynamic. When a worker pulls the Andon cord, the system actually moves between two modes based on the state of the work. Though the nature of the work couldn’t be more different, such movement between the two modes is also the key to understanding the success of agile software development.

Agile as Dynamic Work Design

As we discussed earlier, the last two decades have witnessed a significant change in the conduct of software development. Whereas software was once largely developed using what is known as the waterfall approach, agile methods have become increasingly popular. From a dynamic work design perspective, the waterfall and agile approaches differ significantly.

In the waterfall approach, the software development cycle is typically divided into a few major phases. A project might include a requirements phase, an architecture development phase, a detailed coding phase, and a testing and installation phase. A waterfall project typically cycles between three basic modes of work. First, the bulk of the time is spent by software architects and engineers working individually or in small groups, completing whatever the specific phase requires. Second, typically on a weekly basis, those people leave their individual work to come together for a project meeting, where they report on their progress, check to ensure mutual compatibility, and adapt to any changes in direction provided by leadership. Third, at the end of each phase, there is a more significant review, often known as a “phase-gate review,” in which senior leaders do a detailed check to determine whether the project is ready to exit that phase and move to the next. Development cycles for other types of non-software projects often work similarly.13

Agile development processes organize the work differently. For example, in the scrum approach14 (one version of agile), the work is not divided into a few major phases but rather into multiple short “sprints” (often one to two weeks in length) focused on completing all of the work necessary to deliver a small but working piece of software. At the end of each sprint, the end user tests the new functionality to determine whether or not it meets the specified need.

Like the waterfall method, the agile approach to software development also has three basic work modes — individual work, team meetings, and customer reviews — but it cycles among them very differently. First, proponents of agile suggest meeting daily — thus moving from individual work to teamwork and back every day — in the form of a stand-up or scrum meeting, where team members report on the day’s progress, their plans for the next day, and perceived impediments to progress. Second, agile recommends that at the end of each sprint, the team lets the customer test the newly added functionality. Finally, in something akin to the Andon cord, some versions of agile also include an immediate escalation to the entire team when a piece of code does not pass the appropriate automated testing, effectively again moving the system from individual work to the team collaboration mode.

Viewed from a dynamic work design perspective, agile offers two potential benefits over waterfall. First, in waterfall development, the frequency of collaborative episodes is usually too low, both among the team members and between the team and its customers. A developer working for a week or two without a check-in could waste considerable effort before it’s clear that he or she has made a mistake or gone off course. In practice, developers often do not wait this long and informally check in with supervisors or teammates. While seemingly functional, these check-ins can lead to a situation in which the entire team is not working from a common base of information about the state of the project. In such cases, the operating mode starts to migrate from the box on the lower left, the “factory” mode, to the one on the lower right, where ambiguous work is organized serially. This results in costly and slow iteration, which we call ineffective iteration. (See “Dysfunctional Dynamics.”) Research suggests that in R&D processes, this mode can be highly inefficient.15 Similarly, checking in with more senior leadership only in the form of periodic phase-gate reviews means that the entire team could work for months before realizing that it is not meeting management’s expectations, thus also potentially causing rework.

Dysfunctional Dynamics What happens when organizations don’t do a good job of cycling between factory and studio modes of work? We have observed two related failure modes, ineffective iteration and wasted attention. When they are combined, they create a truly unproductive work design — one we have dubbed the axis of frustration. (See “The Axis of Frustration.”) Ineffective Iteration. Consider first what happens when elements of the work in question are highly ambiguous but are nonetheless organized serially (captured in the box in the lower right-hand corner). Relative to a more collaborative design, this approach tends to create slow and costly iteration. The lack of speed comes because the ambiguity must travel among participants to be resolved, thus requiring multiple rounds, each of which takes time. Worse, when knowledge work is designed serially, many of these interactions take place through email or text messaging. Research suggests both that such communication modes are less effective for reducing ambiguity than face-to-face communication and that those sending such messages are unaware of those limits.i Trying to resolve ambiguity via email or text messaging tends to create more misunderstandings and often necessitates multiple iterations. Wasted Attention. On the flip side, organizing well-defined work in a collaborative fashion also creates inefficiency. If the work is clearly defined, then it doesn’t benefit from a collaborative approach, and collaboration just multiplies the cost. Worse, too much collaboration may prevent the efficiencies that come with the learning curve that emerges when people repeat the same task.ii The Axis of Frustration. Whereas functional work processes move between the factory and studio modes, our research suggests that absent careful design attention, processes can devolve to the point where they move between the failure modes described above, oscillating between wasted attention and ineffective iteration — the dynamic we call the axis of frustration. Getting stuck on the axis of frustration typically starts with time pressure — a project is behind schedule or a more repetitive process is not delivering on its targets. When people feel they are behind, they don’t want to take the time to shift into collaborative studio mode for problem-solving, preferring to stay in the factory box on the lower left and “just get the work done.” The consequence of this decision is to leave one or more problems unresolved, whether it is an element of a product design that doesn’t work or a defect in a manufactured product. Eventually, these problems will be discovered, usually by an activity downstream from the one that generated it. And, if this problem is not then solved in collaborative studio mode (again due to time pressure) but instead sent back for rework, then the system has effectively moved from the box on the lower left to the box on the lower right and is now in “ineffective iteration” mode. The consequence of ineffective iteration is that the process becomes increasingly inefficient and incapable of meeting its targets. Senior leaders are, of course, unlikely to stand idly by and will eventually intervene. Unfortunately, the typical intervention is often to scrutinize the offending process in more detail, usually in the form of more frequent and more detailed review meetings. (As a manager we once interviewed said, “I knew my project was in trouble when I was required to give hourly updates.”) But the form of those reviews makes all the difference. If they are well designed and focus on resolving the key problems that are causing the iteration, then they can move the system back to a more productive cycling between factory and studio modes. Such interventions, however, are the exception rather than the rule. The Axis of Frustration Most work processes have not been designed with escalation mechanisms in mind. So, when senior managers want to intervene and scrutinize a project, they don’t know where to look and want to review everything. The result of such scrutiny is long review meetings, the majority of which focus on elements of the process that are just fine, thereby trapping the process in the upper left-hand box, “wasted attention.” Worse, long review meetings and the preparation that they require steal time and resources from actual work, thus intensifying the time pressure that prevented a proper shift between work modes in the first place. Without careful attention to the mechanisms that move a process between the individual and collaborative modes, processes can increasingly cycle between ineffective iteration and wasted attention, basically moving between frantically trying to solve (or at least hide) the latest problem before the next review, and endless, soul-destroying review meetings that never get to solving the problems that would really make a difference.

The agile approach to software development also improves the quality of the time that developers spend working alone. The focus on developing pieces of functionality means that both the team and the customer are never more than a few weeks away from a piece of software that can be used, making it far easier to assess whether it meets the customer’s need. In contrast, in waterfall, the early phases are characterized by long lists of requirements and features, but there is nothing to try or test. It’s not surprising that waterfall methods often lead to projects in which major defects and other shortfalls are discovered very late in the development cycle and require costly rework.16

Applying Dynamic Work Design

Both the Toyota production system and agile-based software methods are thus examples of what we call good dynamic work design. In contrast to traditional static approaches, dynamic work design recognizes the inevitability of change and builds in mechanisms to respond to that. Once managers recognize the necessity of moving between more individual and more collaborative modes of work, they can build on four principles to create shifting mechanisms that are well matched to the work of their organization.

1. Separate well-defined and ambiguous work. Begin by clearly separating well-defined and ambiguous tasks. Trying to handle both types of work in the same process often leads to trouble. (See “Dysfunctional Dynamics.”) Often, the two types can be separated by inspection, but if not, then look for the signature element of ambiguous work, iteration. When work is well defined, it can be moved to the next stage like the baton a relay runner hands off. When done correctly, it doesn’t need to come back. In contrast, when work is ambiguous, even the best effort often needs to be revisited. If you find that a particular task often requires multiple iterations through the same set of steps, that’s a good sign that you are confronting ambiguity inefficiently.

2. Break processes into smaller units of work that are more frequently checked. If you strip away all the hype, the agility of any work process — meaning its ability to both adjust the work due to changing external conditions and resolve defects — boils down to the frequency and effectiveness with which the output is assessed. In both traditional, pre-Toyota manufacturing and waterfall software development, the assessments are infrequent and not particularly effective. Consequently, both approaches tend to be slow to adjust to changes in the external environment, and quality will be achieved only through slow and costly rework cycles. In contrast, when assessments are frequent and effective, the process will be highly adaptable and quality will improve rapidly. The fundamental recipe for improved process agility is this: smaller units of work, more frequently checked.

3. Identify the chain of individuals who support those doing the work. It is also important to identify the help chain — the sequence of people who support those doing the work. In manufacturing, the help chain starts with a machine operator and extends from foremen to supervisors all the way up to the plant manager. In software, the help chain often begins with an engineer and moves through the team leader to more senior managers, ultimately ending with the customer. It is critical, in our experience, that you identify the chains of individuals who do and support the work, not their roles, departments, or functions. Increasing agility requires knowing whom to call when there is a problem or feedback is needed.

4. Introduce triggers and checks that move work into a collaborative mode. Once you understand the help chain, you have two basic mechanisms for activating it: triggers and checks. A trigger is a test that reveals defects or misalignment and then moves the work from a factory mode to a more collaborative mode. In our opening example, the Toyota operator’s inability to complete the assembly task on time triggered her pushing a button and then receiving help from a supervisor. A check involves a prescheduled point when the work is moved to a more collaborative environment for assessment. In agile software development, this shift happens daily in stand-up meetings where the team quickly assesses the current state of the project. Completing a sprint creates a second opportunity, this time to check in with the customer.

Improving Procurement Performance

Using this dynamic work design framework within a company can lead to significant improvements in both efficiency and adaptability. Consider the case of a company we’ll call “RefineCo,” which owns several oil refineries and distribution terminals in the United States. The company had a procurement organization that was uncompetitive by almost any benchmark. RefineCo paid more for similar parts and services than its competitors, and the procurement group’s overhead costs were higher than the industry average. Even more troubling, when critical parts were not delivered to a refinery, it often turned out that the location was on “credit hold” due to an inability to pay the supplier in a timely fashion. Every participant in the system, from senior management down to the shipping and receiving clerks, was frustrated.

The procurement system at each of RefineCo’s sites worked roughly as follows. To purchase an item or service from an outside vendor, an employee would enter the requirements into the electronic procurement system, which would then appear as a request to the central procurement function. The staff in the procurement office would then review the request and issue a purchase order. That order would go to the supplier. When the product arrived at the refinery or the service was completed, a packing slip or service order verification slip would be generated, which would also be entered into the procurement system. Later, the supplier would generate an invoice that was also entered into the system. The electronic system would then perform a three-way match to verify that everything was done correctly: The purchase order should match the verification receipt, which, in turn, should match the invoice. If there was not a three-way match, the invoice would be “kicked out” of the system and the supplier would not get paid until the discrepancy was resolved.

The job of resolving those discrepancies fell to the staff in the refinery’s purchasing office. Unfortunately, the products and services procured frequently failed the three-way match, leading to both an overburdened purchasing department and frustrated suppliers. Though the refinery was part of a large and successful company, it was frequently on credit hold with its suppliers for failure to pay invoices on time, making it difficult for the staff to do their jobs and run the plant safely. The dedicated procurement staff worked 10-plus hours per day and had hired temporary workers to help manage the backlog, but they were still falling behind.

Most of the members of the procurement team complained bitterly about being “overworked” and how “screwed up the system was.” Nobody saw any opportunity for improvement beyond adding what appeared to be much-needed staff. For us, the critical moment in our work with the procurement staff came when one of the longtime team members explained that a good purchase request contained “all the information I need” and could be turned into an official purchase order in “five to 10 minutes.” A difficult one, however, lacked key pieces of information and might require one to two hours to process as the purchasing staff traded emails with both the requesting unit and the supplier. Despite this effort, difficult purchase orders were usually the ones that failed the three-way matching process and got kicked out of the system. Further investigation revealed that the purchase order system was completely gridlocked with the kicked-out orders, and the team spent much of its time trying to clear the backlog. The system had descended into the classic “expediting” or “firefighting” trap: There were so many purchase orders in process that the turnaround time for any given one was very long. But long turnaround times created unhappy customers and suppliers who constantly called to complain and ask about their particular order or payment. Consequently, the procurement team was constantly reprioritizing its work and reacting to whichever customer or supplier was most unhappy.

Our first insight came in recognizing that the procurement team was engaged in two different types of work that corresponded to what we call serial “factory” work and collaborative “studio” work. When the requested item was standard and all the needed information was provided, a single person could easily process the request without collaboration; then, once the purchase order was entered, it would easily flow through the system, just like an item on an assembly line. However, standard requests flowed easily through the system only if the request came with the correct information. If it did not, then it could require several rounds of iteration, usually via email, to issue the purchase order. So the purchasing function created a simple checklist that described a good purchase request. The idea was to ensure that standard orders would always arrive with the correct information. To give the various departments an incentive to use the checklist, the purchasing function promised that any request received by 7 a.m. with the proper information would result in a purchase order being issued by 2 p.m. that day. At that time, a one-day turnaround was unheard of because every order simply went into the “to do” pile. The purchasing department also created a simple trigger to improve productivity: Purchase orders that were missing items on the checklist would be immediately returned to the requesting unit.

The second part of the intervention came in recognizing that not every request could be supported in factory mode. In the existing system, neither the requesters nor the purchasing staff distinguished between a standard request and a novel one. Thus, when a request for a new product or service showed up, the agent would do his or her best to process it, typically requiring multiple emails with the requester, often over several days, to nail down all the relevant information. In many cases, when the agents couldn’t get the information they needed, they would make their best guess and then submit an incomplete or incorrect purchase order. This, too, created additional iteration, as the supplier, unsure of what was being requested, would call or email the agent. The purchasing process was thus living in the lower right-hand box of our matrix, attempting to accomplish ambiguous work in a serial fashion and thereby creating slow and expensive iteration.

Creating an effective collaborative studio mode to handle the complex purchase orders required two changes in work design. First, the team created a clear trigger: If a request was nonstandard, then it was moved into a separate pile and not dealt with immediately. Second, each day at 2 p.m., the team would work together to process the more complex cases. By working collaboratively (in studio mode), they were able to resolve many of the more complex cases without additional intervention — somebody on the team might have seen a similar order before. Also, having a face-to-face meeting was far more efficient than the endless chain of email that it replaced. And, if additional information was needed, the team could schedule a phone call in the time window after 2 p.m., rather than send an email, again reducing the number of expensive iterations.

The results of these two changes were significant. Creating a factory mode for the standard orders allowed the team to make good on its “in by 7, out by 2” promise almost immediately, generating an immense amount of goodwill with the requesters. Spending the afternoon in studio mode also sped the processing of the complex orders. The two changes created enough space that the team was able to use studio time to not only process the more complex requests but also work through the backlog of unresolved older orders. In the end, due to the efficiency improvements, the procurement team reduced its staff by the equivalent of two full-time staff members, while providing far faster and more reliable service. These process improvement insights were then applied to the company’s other U.S. sites and, as of this writing, RefineCo pays more than 90% of its invoices on time, resulting in a far happier collection of suppliers.

Look for Best Principles

Managers and consultants are often obsessed with the search for best practices — those activities that appear to separate leading organizations from the rest of the pack. The idea behind this search is that once identified, best practices can be adopted by other organizations, which will then experience similar gains in performance. While there is certainly some truth to this idea, the supporting evidence is decidedly mixed. Organizations frequently struggle to implement new tools and practices and rarely experience similar gains in performance. In many industries, the performance gap between the top and middle performers remains stubbornly difficult to close. A key reason for these failures is simply that organizations are complex configurations of people and technology, and a set of tools or practices that works well in one context might not be equally effective for a major competitor — even if that competitor is located just down the street.

Best practices are “best” when they manifest an underlying behavior principle in a way that is well matched to the organization that uses them. Toyota’s famed Andon cord and the localized problem-solving it catalyzes work by capitalizing on the efficiency that comes from individual repetition and the innovation that comes with collaborative problem-solving. Conversely, agile development methods work by channeling the creativity of software engineers through frequent team meetings and customer interactions. More generally, organizations become more adaptable when they find defects and misalignments sooner. A dynamic approach to contingency, supported by triggers and checks, can open the path to creating practices that support increased agility in the work of your organization.

About the Authors Nelson P. Repenning is the School of Management Distinguished Professor of System Dynamics and Organization Studies at the MIT Sloan School of Management in Cambridge, Massachusetts, where he currently serves as the associate dean for leadership and special projects and the faculty director of MIT’s Leadership Center. Don Kieffer is a senior lecturer in operations management at the MIT Sloan School and a founder of ShiftGear Work Design, a consulting firm based in Cambridge. James Repenning is the managing partner at ShiftGear Work Design.

References 1. A quick trip to the web reveals multiple manifestations, including “agile principles,” “enterprise agile,” “agile organizations,” and a variety of suggestions, including the charge to “apply agile development to every aspect of business.” See, for example, S.D. Goldstein, “Apply Agile Development to Every Aspect of Business,” Mint, Dec. 4, 2016, www.livemint.com. 2. D. Leonard and R. Clough, “How GE Exorcised the Ghost of Jack Welch to Become a 124-Year-Old Startup,” Bloomberg, March 17, 2016, www.bloomberg.com. 3. See their manifesto here: https://agilemanifesto.org. 4. For a summary, see F.S. Glaiel, A. Moulton, and S.E. Madnick, “Agile Project Dynamics: A System Dynamics Investigation of Agile Software Development Methods,” Massachusetts Institute of Technology, Engineering Systems Division working paper, October 2014, available at http://dspace.mit.edu. 5. See C.J. Stettina and J. Hörz, “Agile Portfolio Management: An Empirical Perspective on the Practice in Use,” International Journal of Project Management 33, no. 1 (January 2015): 140-152; J. Sutherland and J.J. Sutherland, “Scrum: The Art of Doing Twice the Work in Half the Time” (New York: Crown Business, 2014); and D. West and T. Grant, “Agile Development: Mainstream Adoption Has Changed Agility,” Forrester, Jan. 20, 2010, www.forrester.com. 6. See, for example, M.E. Moreira, “Being Agile: Your Roadmap to Successful Adoption of Agile” (New York: Apress, 2013). 7. D.K. Rigby, J. Sutherland, and H. Takeuchi, “Embracing Agile,” Harvard Business Review 94, no. 5 (May 2016): 40-50. 8. The classic descriptions of contingency theory can be found in T. Burns and G.M. Stalker, “The Management of Innovation,” rev. ed. (Oxford, U.K.: Oxford University Press, 1994) and in P.R. Lawrence and J.W. Lorsch, “Organization and Environment: Managing Differentiation and Integration,” rev. ed. (Boston: Harvard Business School Press, 1986). An updated summary can be found in several textbooks, including R.M. Burton, B. Eriksen, D.D. Håkonsson, and C.C. Snow “Organization Design: The Evolving State-of-the-Art” (New York: Springer Science+Business Media, 2006). 9. F.W. Taylor, “The Principles of Scientific Management” (New York and London: Harper & Brothers, 1911). 10. T. Brown, “Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation” (New York: HarperBusiness, 2009). 11. J. Liker, M. Hoseus, and the Center for Quality People and Organizations, “Toyota Culture: The Heart and Soul of the Toyota Way” (New York: McGraw-Hill Education, 2008). 12. See, for example, N.R. Repenning and J.D. Sterman, “Capability Traps and Self-Confirming Attribution Errors in the Dynamics of Process Improvement,” Administrative Science Quarterly 47, no. 2 (June 2002): 265-295; and N. Leveson, “A Systems Approach to Risk Management Through Leading Safety Indicators,” Reliability Engineering and System Safety 136 (April 2015): 17-34. 13. K.T. Ulrich and S.D. Eppinger, “Product Design and Development,” 6th ed. (New York: McGraw-Hill Education, 2016). 14. Sutherland and Sutherland, “Scrum”; and Scrum Guides, www.scrumguides.org. 15. L.A. Perlow, “The Time Famine: Toward a Sociology of Work Time,” Administrative Science Quarterly 44, no. 1 (March 1999): 57-81. 16. See Sutherland and Sutherland, “Scrum”; and J. Kamensky, “Digging Out of the Digital Stone Age,” Government Executive, March 9, 2017, www.govexec.com. i. N. Epley and J. Kruger, “When What You Type Isn’t What They Read: The Perseverance of Stereotypes and Expectancies Over E-Mail,” Journal of Experimental Social Psychology 41, no. 4 (July 2005): 414-422. ii. L. Argote and D. Epple, “Learning Curves in Manufacturing,” Science 247, no. 4945 (Feb. 23, 1990): 920-924.