Doing Agile Right

02The Secret to Balancing Order and Flexibility

We often mistakenly believe that becoming a fast-moving, innovative company means completely destroying all rules, standard procedures, and traditional hierarchies. There is a pervasive myth in the business world that an agile organization is a chaotic, free-flowing environment where everyone does whatever they want, whenever they want. However, Darrell K. Rigby and Sarah Elk argue passionately that true organizational success actually relies on a delicate, intentional balance between stable routines and dynamic innovation. The goal is not to eradicate bureaucracy entirely, but rather to put it in its proper place so that it supports the business instead of choking it. To fully grasp this concept, we must first understand that bureaucracy was not invented to make people miserable. Originally, bureaucratic systems were designed to ensure fairness, consistency, and extreme efficiency in repetitive tasks. If a company needs to manufacture one million identical microchips, or process payroll for fifty thousand employees across different tax jurisdictions, it absolutely requires strict rules, checklists, and standardized procedures. You certainly do not want an "agile" payroll department that tries experimental new ways of calculating your paycheck every two weeks to see how you feel about it. For these types of operations, rigid consistency is not just good; it is entirely essential for the survival of the business. The authors introduce a highly effective framework for thinking about this balance, dividing the activities of a company into two distinct categories: running the business and changing the business. Running the business involves all the daily, repetitive operations that keep the lights on and generate current revenue. This area thrives on standardization, Six Sigma efficiency, and traditional management hierarchies. Changing the business, on the other hand, involves creating new products, entering new markets, and solving complex, unprecedented problems. This area requires cross-functional teams, rapid experimentation, and the freedom to fail. The fundamental error that most companies make is trying to manage both of these entirely different areas with the exact same set of rules. Think about how a massive, high-end restaurant operates on a busy Saturday night. The kitchen is a perfect example of balancing order and flexibility. The processes for ordering ingredients, storing meat at the correct temperature, and washing the dishes are highly bureaucratic. There are strict health codes and precise measurements that must be followed without exception. However, when the head chef is trying to invent a brand new seasonal dish, the approach becomes highly agile. The chef experiments with different flavor profiles, tastes the results, asks the sous-chefs for their opinions, and continuously refines the recipe until it is perfect. If the restaurant applied the dishwashing rules to the recipe invention process, the food would be incredibly boring. If they applied the creative invention process to food safety, people would get sick. Both systems must exist side by side, perfectly complementing one another. A powerful real-world example from the book is the massive transformation undertaken by the global engineering and technology company, Bosch. As a company famous for its precision engineering in automotive parts and household appliances, Bosch had a deeply ingrained culture of traditional planning and strict hierarchies. This culture was fantastic for manufacturing reliable spark plugs by the millions. However, as the world shifted toward the Internet of Things and connected software devices, Bosch realized that their traditional, slow-moving development cycles were causing them to fall behind nimble tech startups. They knew they needed to become agile, but they also knew they could not afford to disrupt their highly profitable core manufacturing business. Instead of forcing a company-wide agile mandate that would have thrown their factories into chaos, Bosch took a highly thoughtful, dual-track approach. They carefully mapped out the entire organization to identify which departments were primarily focused on running the business and which were focused on changing the business. For the teams developing new software and connected devices, Bosch removed the traditional bureaucratic hurdles. They created cross-functional agile teams, gave them the freedom to experiment, and allowed them to work in rapid sprints. Meanwhile, the manufacturing plants and supply chain logistics teams continued to use their highly optimized, traditional methods, gradually incorporating agile concepts only where it made sense to improve daily efficiency. This separation is what the authors refer to as building an "agile enterprise." An agile enterprise is not an organization where every single person is on an agile team. Rather, it is an organization that knows exactly when to use agile methods and when to rely on traditional management. It creates a seamless interface between the fast-moving innovation teams and the stable operational teams. For instance, when an agile team at Bosch invents a new sensor, they eventually have to hand that design over to the manufacturing team to produce it at scale. By establishing clear communication channels and mutual respect between these two different ways of working, the company ensures that brilliant innovations do not get lost in the transition to mass production. Achieving this balance requires leaders to act as organizational architects. They must constantly monitor the friction between the agile teams and the traditional departments. Often, the bureaucracy will try to naturally creep back in and suffocate the agile teams with requests for detailed status reports and year-long predictions. Leaders must aggressively protect the agile teams from this bureaucratic creep, while also ensuring that the agile teams do not disrupt the critical daily operations of the company. It is a continuous, dynamic balancing act. By embracing the idea that order and flexibility are not enemies, but rather two sides of the same highly successful coin, organizations can build a foundation that is both incredibly stable and limitlessly innovative.

Continue reading with LeapAhead app

Full summary is waiting for you in the app

Continue reading