Senior Partner & Managing Director
Companies are revolutionizing how people work. Now they need to transform how managers manage.
Sooner or later, every technological revolution gives rise to an organizational revolution. To realize the potential of new technologies, companies devise new ways of working; those that fail to adapt end up losing in the marketplace. The steam engine was fully exploited only with the development of the early factory system, the process technologies of the late 19th and early 20th centuries with the development of scientific management.
Now, business is in the midst of a wholesale digital transformation. Companies across the economy are using digital technologies and advanced analytics to unlock new sources of economic value and achieve step-function improvements in customer focus, productivity, flexibility, and speed. Parallel to this digital transformation is an organizational revolution-in-the-making, transforming not just what companies do but how they do it.
Take, for example, the recent popularity and rapid spread of agile. The term is shorthand for a variety of approaches to organizing work that emphasize small, self-managed, multidisciplinary teams with end-to-end control of product development, service delivery, and other business tasks; rapid cycles of activity known as sprints; and a test-and-iterate approach to performing work.
Agile started in software development, but as software and digital applications become more and more central to a broad array of industries—finance, retail, even industrial sectors being transformed by the Internet of Things—the approach has spread far beyond the software industry. And companies are increasingly applying the agile model to nonsoftware activities such as marketing, customer service, and other traditional business functions.
Agile is only the most recent example of work innovations emphasizing autonomous, self-managed teams. Other approaches that companies have been experimenting with in recent years go by a bewildering variety of names: lean, holacracy, the polycratic organization, and the exponential organization, to list a few.
But in this organizational revolution-in-the-making, a critical piece is missing. Companies lack a compelling model for the role of management.
Some agile champions seem to assume that the approach makes management irrelevant or even obsolete. “Why Do Managers Hate Agile?” reads the title of a commentary in Forbes by an agile consultant. His answer: because agile inevitably (and rightly) undermines their status, power, and control. In a world of self-organizing, autonomous teams, a lot of what passes for traditional management is no longer necessary. Or as the title of a webinar on the subject puts it, “(In Agile) Where Do All the Managers Go?”
Such perspectives circle around the right question: how do managers create value in the new work environment? But I think they have the answer exactly backwards. They embrace a traditional concept of management only to declare it irrelevant to the new way of working.
The challenge of the organizational revolution represented by agile and other new approaches is not that they make management somehow irrelevant or obsolete. Quite the opposite: they make management more important than ever before. But they also transform what managers—from the very top of the organization to the frontline of the business—have to do and how they need to work. In some cases, they even redefine who needs to be a manager.
Until organizations develop a management model that is equal to the challenges of the organizational revolution taking place today, that revolution won’t be successful.
Developing the new managerial model will require a shift in how managers conceive of their role. Put simply, they need to stop thinking of themselves as the master designers of hardwired organizational structures, processes, rules, and procedures. Instead, they need to become the everyday orchestrators of a flexible and dynamic behavioral system, one that unleashes employees’ autonomy and initiative, and puts it in the service of more effective cooperation to achieve the organization’s goals.
I call this shift “bringing managers back to work.”
“Wait a minute,” you may be thinking. “Aren’t managers already working—coming to work earlier and staying later, their days consumed with meetings, conference calls, emails, and reports, their weekends spent trying to catch up?” It’s true. Most managers are putting in more effort and more hours than ever before. But fewer and fewer are actually creating value.
To understand why, it pays to look back to the origins of professional management. Ever since Frederick Winslow Taylor introduced his theory of scientific management in the early 20th century, a key principle of modern management has been the radical separation of design and execution. Managers set strategy, plan, and define and allocate work tasks; they establish formal organizational structures, procedures, and incentive systems, and then monitor employees’ performance against them. Employees execute according to the strategy and the plan, their actions governed by the organization’s rules, procedures, and incentives.
This command-and-control model worked reasonably well in relatively stable environments. It also had the advantage of being easy to scale in the new era of mass markets served by mass production. It led to the specialization of functions and hierarchical management as we know it today.
Whatever its advantages, command-and-control management is singularly ineffective at addressing the distinguishing feature of today’s business environment: the exponential increase in business complexity.2 There are many dimensions of that growing complexity: the proliferation of (sometimes conflicting) performance requirements; the increase of customer segments, local markets, and competitors; the growth in the number of relevant stakeholders and business partners; the multiplication of categories of specialized knowledge and expertise; the faster pace of innovation and change; the higher levels of uncertainty and volatility.3
Business complexity may sound like a problem. In fact, it is an enormous opportunity—if organizations can take advantage of it. The more complex the business, the more ways to create value by breaking compromises among heretofore conflicting objectives or goals and by combining diverse skills and capabilities in unprecedented ways.
However, this is precisely where the command-and-control model becomes an obstacle. At the foundation of the separation of design and execution is the idea of rules, in the sense of formal procedures. The assumption is that if managers design the formal procedures carefully and employees follow them obediently, then people’s work will predictably deliver the desired performance outcomes. In a relatively simple business environment, this assumption works well enough.
As complexity increases, however, the correspondence between the organization’s formal procedures and its business outcomes begins to fall apart. It is in the nature of business complexity to impose competing performance requirements on the organization. Products need to be affordable but also of high quality. Manufacturing plants have to be efficient but also safe. Business processes require speed but also reliability. The challenge is to reconcile these requirements, so that achieving any one of them doesn’t preclude achieving the others, and, ultimately, to discover solutions that exploit synergies across them all. But there is no “super-rule” that will tell people the best way to balance conflicting goals.
Even worse, in a futile attempt to control complexity, many organizations design more rules, processes, and guidelines for each new performance objective. The paradoxical result is an increase in organizational complicatedness—that is, the proliferation of contradictory rules and instructions—which causes people to lose their sense of direction and to escalate decisions to committees or to senior leaders, who have no direct knowledge of the issues at hand. The growing coordination burden means that more and more managers end up spending the lion’s share of their time managing the complicatedness, not the work itself. In the process, they become ever further removed from the genuinely value-adding activities that constitute the work of the organization. (See “How Complicatedness Erodes Productivity.”)
The digital revolution transforming business today is greatly accelerating the growth in business complexity, introducing new channels, new types of capabilities, new ways to create business value. It is also definitively exposing the dysfunctionality of the traditional separation of design and execution. Work innovations like agile are founded on the recognition that in a business environment characterized by competing performance requirements, more ways to create value, and continuous innovation, work tasks cannot really be “designed”—in the sense of programmed in advance according to a set of formal procedures. Nor, once designed, can they be “executed”—in the sense of performed according to an unchanging plan. Rather, work under conditions of complexity is all about discovery.
The key to effective performance in complex work environments is to unleash individual autonomy and initiative so as to maximize people’s freedom to exercise judgment in the completion of a task. But since no single individual or work group will have all the answers, it also requires creating an environment where people have an interest in deploying their autonomy in the service of cooperation with others for the greater good of the organization.4
This combination of autonomy and cooperation doesn’t happen on its own. Rather, it requires a particular kind of management. Instead of focusing on formal procedures, managers must pay attention to the behavioral dynamics that shape organizational performance: why people do what they do; how they understand their individual goals, the resources available to them to achieve those goals, the constraints that stand in their way; and how individual behaviors combine (often in unanticipated ways) to produce the collective behavior underlying performance. What’s more, because managers themselves are actors in the behavioral system, they need to know how to intervene in that system in order to foster more effective cooperation. (See the exhibit.) And to do that, they must get much closer to the actual work.
To guide their intervention in the behavioral system, managers need to cultivate a new skill set, consisting of three high-level tasks.
Let’s consider each task in turn.
In the new work environment, the separation of design and execution is replaced by the combination of framing and acting. Rather than design tasks, managers “frame” objectives and goals. That framing sets the context that allows employees not so much to execute but to “act”—that is, exercise initiative guided by strategic goals, not rigid processes and rules; operate more autonomously, making decisions in the moment in response to changing circumstances and unanticipated obstacles or opportunities; and work together to make the tradeoffs that will create the most value over time.
But managers don’t just need to frame; they too must act. Put another way, in a more dynamic and fluid business environment, the all-important framing that managers do must take place through action—that is, through their ongoing intervention in the organization’s behavioral system. Framing doesn’t happen once; it happens continually, in close interaction with employees, and in response to the constantly changing circumstances thrown up by the work people do and the challenges they face in the ongoing effort to create value.
Why is framing through action so essential in the new work environment? Partly it is a function of what drives behavior in organizations. As the decisions people make and the actions they take become ever more critical to performance, it’s important to understand that, despite the assumptions of the command-and-control model, people’s behavior doesn’t follow automatically from the organization’s formal structures, processes, and rules. Rather, their behavior depends on how they use those features to achieve their personal objectives and goals. In some cases, they may see the organization’s formal structures, processes, and rules as resources to achieve ends that are very different from what the organization intends. In other situations, they may view them as constraints to be worked around in pursuit of their own objectives. If managers hope to influence these complex behavioral dynamics, they need to be present, close to where work actually happens.
Take, for example, the concept of the agile sprint. People usually focus on the time dimension of sprints—rapid cycles of work of relatively short duration. To be sure, the time dimension is important. But just because a company organizes work cycles in sprints doesn’t necessarily mean that people will run their fastest. What makes a sprint a good sprint is not just the time allocated to it but what people achieve and the quality of their effort. If they don’t give their best, even the shortest sprint will be little more than another iteration of routine work. In other words, it is the team members who determine whether a sprint is really a sprint. It’s not enough for managers simply to design the new work processes—including agile or any other system for autonomous, self-managed teams. Rather, they need to create a context in which team members are motivated to put their best effort into the work of team.
Framing through action is also necessary because, as mentioned earlier, the more complex the business, the more difficult it is to make rules that will apply in any and every situation. Put simply, complexity “rules out rules” as an effective means for managing organizational tasks. Therefore, for managers to frame in a way that’s realistic and useful to the organization, they need to be involved in the action. The less framing through rules is effective, the more managers need to frame through action.
A third reason framing through action is essential is that increasingly complex tasks often require the integration of new kinds of specialized expertise and roles. My colleagues and I call this the paradox of specialization: the more complex work becomes, the greater the need for focused and deep content knowledge in a proliferating number of areas. The greater the number of highly specialized functions and units, however, the more the need for cooperation across those functions and units—and yet, the harder it is to get people to think, work, and interact beyond their own specialized functional mindsets.5 It is impossible for any manager to grasp in advance the full range of knowledge and capabilities that needs to be brought to bear to create value. Therefore, they must be present in the moment, interacting with the organization’s cross-functional teams as they apply their diverse capabilities to perform a complex task.
Finally, framing through action is a requirement when creating value depends on more intricate forms of cooperation, as it does in any environment of high complexity. But the more cooperation is necessary, the less possible it is to isolate the contribution of any particular individual and, therefore, the harder it becomes to measure people’s performance by means of individual KPIs. The fact is, cooperation often comes at the expense of individual performance—in which case, individual KPIs and the incentives associated with them end up functioning as disincentives to the more effective cooperation the organization needs.
Typically, organizations try to address this dilemma by evaluating people, in part, on a proxy for cooperation: the collective performance of their work group, team, or unit. But the problem of free-riding—when individuals don’t pull their weight—will always be present, and no metric will capture it. Thus, the only way to evaluate people’s performance is if managers exercise judgment based on their observations of the actual behavioral dynamics of the group—who cooperates effectively and who does not. To exercise that judgment effectively, they need to be close to the work.
All of the above explains why framing through action is the general principle of management in the new work environment. What that principle means concretely, however, depends on where a manager is located in the organization.
At the frontline of any organization, value gets created by teams. People with diverse perspectives and capabilities pool their expertise and their efforts to come up with the best solutions for meeting customers’ needs and achieving organizational goals. The role of management at the level of the frontline team is to integrate the work of various team members around the task at hand—that is, to make sure cooperation happens, people work together productively on the task, and they make the tradeoffs necessary to create value across multiple performance objectives.
Take, for example, the product owner of an agile team. Unlike traditional project managers, whose chief responsibility is to deliver a product on time and on budget, product owners orchestrate a complex process of discovery that eventually leads to a product or service that creates value for the customer and the company. Striking that balance requires navigating many tradeoffs. The head of product development at a leading internet company described this to me in terms of managing four types of risk:
The various practices of agile—rapid prototyping, user testing, and the like—are designed to help teams manage these risks and balance the tradeoffs across competing performance requirements. In this respect, the agile product owner is on the frontline of management in the new work environment.
And yet, proponents of agile almost never talk about product owners as managers. After all, agile product owners don’t have a formal reporting relationship with their team members. They aren’t responsible for members’ performance evaluations (although they sometimes provide input), nor do they determine a team member’s career progression.
But to conclude that product owners aren’t managers is to view the new way of working from the perspective of the old command-and-control model. It assumes that being a manager is a function of having a defined position in the hierarchy or being in charge of the structures, processes, and systems that, in theory, determine people’s performance.
The problem with this perspective is that it completely misses the essential task of frontline management in the new work environment, which is less about “managing people” (in the sense of reporting relationships, career progression, performance evaluation, and the like) than it is about “managing behavior” (in the sense of creating an environment in which people find it desirable to devote their full effort to the task at hand, to exercise initiative, to cooperate constructively with their colleagues). And managing that behavioral context is precisely what an effective product owner must do.
It’s an extremely challenging job. For one thing, the product owner can’t simply order his team members to do whatever he thinks they ought to do. The product development head puts it this way:
“The job of the product owner is not to make the right decisions; it’s to make sure the right decisions get made by the team.”
The product owner is what I call an integrator. He or she is responsible for managing effective cooperation—that is, for integrating all the diverse perspectives and capabilities of team members around the task.
What allows the agile product owner to be an effective integrator? The answer is power, but not the kind of power that comes from being someone’s supervisor or controlling his or her career progression. Rather, it is the power that comes from the capacity to make a difference in the goals or “stakes” that matter to individual team members. When a product owner has control (or, at a minimum, influence) over those key uncertainties, he or she has power in the behavioral system of the group and, therefore, is able to function as an effective integrator.
The product development head had an evocative way of describing this dynamic. Product owners, he said, “need to be able to tell a compelling story about the work.” For example, they must be able to convince team members that they are solving an important problem for users or that they are working on interesting technology or that the product, if successful, will have a significant impact on the company’s business. If product owners are unable to make the case persuasively, they are unlikely to attract the best people to the team or motivate them to do their best work. Telling a good story, creating a strong vision of the future, and tying that vision to business returns are how product owners frame through action and integrate the work of the team around the task.
One important source of power for agile product owners, reinforcing their ability to tell a compelling story about the work, is their role as a proxy for the customer (either the actual end customer or an internal customer such as the business owner). Product owners lead the “story mapping” exercise that defines the desired functionality of the product and the business value it is meant to deliver to the user. This user story frames the all-important question: What are we trying to accomplish? Product owners also are responsible for maintaining the product backlog, which sets the priorities that guide the team’s work in each sprint (What do we need to do next?). Finally, product owners also decide whether a particular feature meets the product’s acceptance criteria, thus determining when the feature is declared “done,” so the team can move on to the next items on the product backlog list. The control of these key uncertainties gives product owners the power to orchestrate cooperation among team members.
Agile practices like story mapping, scrums, and retrospectives; artifacts like user stories and product backlogs; even concepts like minimum viable products and sprints are all mechanisms for framing through action. They function as continuous feedback loops that make it easier to integrate the various contributions of team members around the task and, thus, are resources available to product owners in their role as integrator.
But such mechanisms don’t function automatically. For instance, even the most exciting or important project is going to have to navigate a variety of constraints in which not all necessary tasks will be equally exciting. In such situations, managers need to have sufficient power to induce people to accept adjustments to their individual goals (for example, their desire to work on the most interesting tasks or challenging technology) for the greater good of the team.
The problem with not conceiving the product owner role as explicitly managerial is that product owners can become disempowered. When that happens, they cannot be effective integrators and the work of the agile teams can become dysfunctional. (For an example, see “When Product Owners Lose Power: The Case of the Software Startup.”)
The Case of the Software Startup
A rapidly growing internet startup organized the company around agile teams. The teams, which allowed the company to respond quickly to rapidly changing customer needs, helped the company establish a dominant position in its category. With rapid growth, however, the teams hit a speed bump. Senior management was hard-pressed to identify the reasons why.
The symptoms of the problem were clear enough: growing conflicts between product owners and team members and between the teams and the company’s equivalent of functions. Even more disturbing was the sharp increase in job dissatisfaction, which led to high turnover among product owners. What had been an attractive and sought-after role had become a job that many of the best people in the company were starting to avoid—so much so that the positions were hard to fill.
An analysis of the company’s behavioral system suggested that the product owners were suffering from a significant erosion of their power. In the early years, the overwhelming business imperative was to get a mass audience to download and use the company’s apps—what managers at the company called “reach.” Maximizing reach was essential to creating the network effects that drive value in most internet businesses.
The imperative of rapidly expanding reach was a key source of power for the product owners. They represented the customer on the agile teams; therefore, they were in a position to have a decisive influence on what constituted an exciting and attractive app from the customer’s perspective. This gave the product owners considerable power over the stakes that really mattered to team members: being involved in an exciting project, creating great applications that would drive growth, being a visible contributor on a project important to the company’s future.
But with success came increasing complexity. As the business grew and product lines multiplied, the company had to develop new technological and business capabilities. Even more important, the critical business imperative began to shift from reach to monetization. It wasn’t enough anymore to deliver great products to a rapidly expanding audience. Increasingly, the company had to do so in a way that leveraged its evolving technological infrastructure and platforms so they were economically and technologically sustainable.
These changes greatly increased the need for team members to adjust their individual goals in the interest of greater cooperation. Take the example of the dilemma that programmers call “tech debt”—the tradeoff between choosing the easy technical solution today to meet customers’ needs (at the cost of rework later on) and taking the time to develop a more robust and standardized solution that can be used across multiple products and platforms. The monetization imperative required the software company to squarely face the tech debt issue. Doing so greatly complicated the work of the agile teams. Business owners weren’t asking for a solution to tech debt; they just wanted an attractive product, even if its functionality wasn’t particularly scalable across the organization’s tech platforms. Team members weren’t so excited about working on solutions to tech debt either; it was far less “sexy” than creating the next killer app.
All of a sudden, the job of the product owner was getting harder; these individuals no longer had enough power to effectively orchestrate cooperation in their teams. One product owner put the dilemma this way:
“In the old days, it was easy to get everyone to pull together for the good of the business. Now, we are more dependent on our team members than they are on us.”
Senior managers at the company are still struggling with what has become a critical managerial challenge: how to give product owners the organizational resources they need to be effective integrators. Maybe, in addition to being the proxy for the customer, they need to be the proxy for the company’s senior system architects so that their teams can make better tradeoffs between meeting customers’ needs and addressing tech debt. Or maybe the solution is to increase cooperation among the company’s business owners, so they are forced to meet their customers’ needs in ways that are scalable across multiple platforms.
A third approach might be to make the business owners more dependent on the perspectives and needs of the system architects, so they start taking them into account—for example, by creating a career path in which some business owners eventually rotate into the system architect role and some system architects rotate into the business owner role.
Getting to the right answer will require senior executives at the software company first to acknowledge that the product owners are critical frontline managers in the behavioral system and, second, to manage that system more explicitly and consciously.
Recently, I asked a senior manager at a company that was implementing agile teams how he saw his role in the process. “I set up the teams,” he told me, “and then just get out of the way.”
The statement contains an important element of truth. A key principle of agile is that those closest to the work are in the best position to make decisions about how to develop the product or service in question and how to prioritize tasks and objectives over time. Nothing is more certain to disrupt an agile implementation than senior managers who try to retain control over the process or otherwise direct how teams do their jobs.
And yet, the manager’s statement underestimates the complexity of the senior management role in the new work environment. Ceding control to self-managed teams doesn’t mean abandoning them. Senior executives, just like frontline managers, have a critical and ongoing “framing through action” role to play. When they get it wrong, the result can be the worst of both worlds—simultaneously too much control and too little enabling engagement and support—which can undermine the effectiveness of the new way of working.
The role of the senior manager in an agile organization is not to determine the content of people’s work. Rather, it is to provide the context for that work. That means helping employees understand how their immediate objectives relate to the organization’s strategic and business goals. Senior managers need to articulate a robust strategic context that teams can use as a “North Star” that aligns their autonomy to those goals, guiding them as they exercise their initiative. In the absence of such a strategic context, just setting up agile teams is unlikely to create business value. (For an example, see “A Failure of Strategic Framing: The Case of the Media Company.”)
The Case of the Media Company
A media company was struggling with the rapid digitization of its business. Translating its traditional nondigital content into new digital media and channels was wreaking havoc with the company’s product development process. Precisely at the time when the company needed to speed up the development and release of new products, it faced delays and poor quality.
To address the problem, the company organized its growing staff of software and digital experts into agile teams and introduced the full range of agile roles and practices—product owners, sprints, and the like. And yet, despite the fact that the company was now “doing agile” (or, at least, so executives thought), the delays and poor quality persisted, leading to disagreements and infighting between the company’s traditional product organization and its new technology organization.
The problem was that senior managers fundamentally misunderstood the nature of the business challenge they faced. They thought they had a software design problem—digital product development was taking too long and the functionality of the resulting products wasn’t good enough. Therefore, they conceived of agile primarily as a way to improve software development. They organized the new software talent in their technology organization into agile teams but neglected to include on the teams the all-important content experts from the company’s product organization.
The real challenge facing the company, however, was not just to deliver better software—it was to use digitization to deliver better business value. And that required more seamless integration between the traditional product organization and the new technology organization. Senior management’s poor framing of the ultimate objective meant that the composition of the agile teams was radically incomplete. To deliver that value efficiently and effectively required creating the right context for cooperation between the product side and the technology side. But since content experts weren’t included on the teams, the teams were in no position to make that cooperation happen.
The failure of the senior managers at the media company wasn’t just a failure of framing; it was also a failure of acting. Because they were distant from the actual work of the new agile teams, they were unable to see that the delays and poor performance were merely symptoms of a much bigger problem (poor team design). Instead, they blamed the delays and poor quality on the teams, and so, whenever there was a conflict or disagreement between functional managers and the teams’ product owners, senior management tended to override the teams.
This put the product owners in an impossible situation. Because their teams didn’t include the content specialists, they didn’t have influence over the full range of skills and expertise necessary to meet customer needs. And because they were continually second-guessed by senior management, they didn’t have true autonomy. Team members remained beholden to their functional managers, who evaluated their performance and set their incentive compensation. As a result of all these factors, there was insufficient reciprocity among team members, a lack of necessary feedback loops inside the teams—and, therefore, ineffective cooperation. But the problem at the media company was not so much—or not only—a failure of the agile teams. It was a failure of senior management.
Of course, senior managers will never be as close to the work as frontline managers are. Nevertheless, framing through action at the senior level also involves bringing managers back to work. The first step is to realize that while senior managers’ distance from the teams in which the work of the organization takes place may be a constraint (unless they make it their business to inform themselves, they often don’t really know what is going on), it is also, potentially, a resource. After all, managers at the top of the organization have a broader perspective on business imperatives, the challenges the company faces in the external environment, and, therefore, the objectives it needs to achieve. And because they are not caught up in the granular details of the work, they often see things that others do not. You might say they have more “cognitive room for maneuver,” which puts them in a position to supercharge team performance—for example, by asking the right questions, challenging matter-of-fact assumptions, or providing a broader context and new information.
The trick is to make their distance and the perspective it brings “present” to their people and their teams. Senior executives make distance present, first, by setting rich objectives. In complex environments where organizations are pursuing multiple goals, it’s critical that performance targets reflect the complexity of those goals and acknowledge the tradeoffs necessary to achieve them. Rich objectives tend to increase the sense of reciprocity among actors—the mutual conviction that they have a shared interest in cooperation and that each actor’s success depends on the success of others.
But setting rich objectives is not enough. Senior managers have to represent those objectives by regularly interacting with teams and being present as a sounding board and “thought partner.” They need to be engaged enough with the work of teams to have at least a first-order understanding of the on-the-ground obstacles, to recognize potential missteps, and to help teams course-correct. What’s more, they need to be open enough to learn from teams’ experiences over time so that the organization’s strategic vision is informed by the latest innovations from the frontline. For example, at one large company undergoing an agile transformation, the CEO and his senior team dedicated a full day a week to these interactions in order to get the program up and running.
Clearly, effective senior management in an agile organization involves far more than simply “getting out of the way.” It requires active and ongoing engagement and managerial presence. When the tasks of work are complex, there are no shortcuts. Senior managers need to spend the time necessary to shape an organizational context that will allow people to focus on value. And that requires bringing senior managers, as well, back to work. (For an example, see “Framing Rich Objectives: The Case of the Luxury Goods Company.”)
The Case of the Luxury Goods Company
The senior executives of a major division at a luxury goods company were worried that their operations could not keep up with a rapidly changing competitive environment. Time to market for new product launches and critical global marketing campaigns was unacceptably slow. Even worse, senior executives felt like they were losing control over a key source of their competitive differentiation: the quality of their products.
The problems were partly a result of the growing complexity of the business. The luxury goods business was increasingly global, which meant a proliferation of new product categories, more (and more differentiated) local markets, faster product cycles, and many new locally based niche competitors. To deal with the complexity, the organization had put a lot of new managerial layers in place, but with two paradoxical results. First, cooperation plummeted; people in the division’s functions reacted to the growth in business complexity and organizational complicatedness by putting their heads down and focusing on optimizing their local objectives, not on the business as a whole. Second, new layers of management coordination had the effect of distancing senior executives from the division’s work. By the time critical information got to them, it was often too late to do anything about it—which contributed to their sense of losing control.
As the division’s executives considered agile as a way to organize work, they quickly realized that it wasn’t enough just to introduce agile-like teams, practices, and principles. They needed to get their people to buy in to the goals of the agile effort. Otherwise, what motivation did they have to give their best and work together to help the new approach succeed? It was like the principle of unit cohesion in the military: soldiers will do the impossible for their comrades if they bond around a shared cause. The division head put it this way:
“Let’s find a good reason to go to war.”
The division head and her team spent a great deal of time and effort framing the objectives of the agile effort and translating them into specific goals that were meaningful to the new agile teams. For years, the company had been talking about its brand in expansive and aspirational terms: to be the top luxury goods brand in the world and to empower customers by giving them control over their presentation of self, to help them feel good by looking good. But this aspiration, however noble, was too abstract, too disconnected from the work people did every day. What would it take for them to be really motivated to deliver on that aspiration?
The key, the senior team decided, was to frame the effort as a way for the company to reestablish its leadership in the industry. Doing so depended on winning back the company’s dominance in a product category that had long been a source of the company’s competitive advantage but in which its market position had slipped in recent years. That, already, was a more specific objective. But the management team pushed its framing even further: to become number one in the category required major changes in the company’s business in two key markets: China, where the company had not had a presence, and the US, where the company had suffered major declines in recent years.
This ever finer set of objectives helped identify the specific markets, product categories, and products that would be the focus of the agile effort. It also got people excited about the new approach to working together. They weren’t just solving operational problems; they were helping the company regain its status. But achieving that would require significant improvement in the efficiency and effectiveness of the organization’s product development and marketing. The agile effort was a means to that end, not the end itself.
The division head didn’t stop at framing these ambitious objectives. She enacted that framing through her interactions with the new agile teams. Once the teams were launched, the division head regularly engaged with them to convince people that their efforts would yield a big payoff. They weren’t just developing new products and marketing campaigns; they were creating the company’s future. Nor did she rely on second-hand reports to gauge the teams’ progress. She showed up for the weekly retrospectives to make sure that people knew she cared about their efforts and that she was sufficiently informed of the tough tradeoffs the teams faced to be able to give meaningful direction, early enough, on how best to resolve them. In effect, she created a virtuous cycle in which senior management engagement, empowered by the right information at the right moment, far from undermining team autonomy, supercharged it—and, in this way, added value to the work of the teams.
One sign of that added value: so far, the new agile teams have met every project milestone substantially faster than in the past. At the same time, people are more engaged and more committed to cooperating with one another to achieve objectives that none could achieve on their own. There is more and better information sharing. And the products and marketing campaigns the company is launching are of higher quality than those of their competitors and more differentiated in the marketplace.
Bringing managers back to work has profound organizational implications. It will likely transform how companies select, develop, and promote managers.
Take, for example, the matter of career paths. In the old command-and-control environment, the typical managerial career path consisted of a progressive increase in an individual’s span of control in a single domain or activity—R&D, say, or operations, or marketing. It was only at the very top of the organizational hierarchy that executives had to cope with the complexity that comes from managing across distinct silos.
In the new work environment, by contrast, career progression is likely to be characterized more by an expansion in responsibility for managing the organization as a behavioral system. An individual’s advancement will depend on his or her capacity to manage behavior in organizational contexts of ever increasing complexity, defined by the number of competing requirements for creating value and by the diversity of the specialized profiles of the employees involved.
It will require considerable attention and effort for any organization, given its unique organizational context, to figure out the most effective practices for bringing managers back to work: to plan the experiences that will allow managers to develop the skills they will need, to establish pathways for career progression, and so on. The temptation, as always, will be to want to design everything in advance and then leave the new structures and processes to function on their own.
But that would just repeat the mistakes of the old command-and-control model. As one CEO put it, “The perfect agile organization can’t be designed, but it can be developed.” Doing so requires the continuous fine-tuning of the organization as a behavioral system.
Elsewhere, my colleagues and I have written about six simple rules that managers can start following today to begin this fine-tuning.6 These are light-touch interventions to improve people’s capacity for effective cooperation without falling into the trap of organizational complicatedness. They are directly relevant to how managers should think about implementing agile or any other work innovation. They are also critical to how managers themselves need to work in the new environment.
To nurture an organization’s behavioral system, managers must first understand the behavioral dynamics that drive company performance—why people do what they do. For any performance-related problem or goal, managers should ask:
Increasingly, managers need to be evaluated on the quality of their answers to these questions. Why? Because the more executives at all levels routinely ask them, the more clearly they will understand the behavioral dynamics of the organization. And the more clearly they understand those dynamics, the more they will be in a position to intervene in the behavioral system to encourage more effective cooperation.
One such intervention is to identify and reinforce the natural integrators in the organization. Integrators are individuals or work units that rely on cooperation to get work done. Their role is particularly critical in complex work environments. Reinforcing them means, first, recognizing the managerial nature of the role and, then, giving those who occupy it (for example, the product owners of agile teams) sufficient power to influence the behavior of others so they are willing to cooperate with one another.
Power is often a dirty word in the new work environment because in the traditional organization, power is associated with hierarchy. I have a different way of thinking about it. Power is really only the capacity of one person to make a difference on issues that matter to someone else, and it is an inevitable feature of organizational life whether managers recognize it or not. What’s more, the way power is distributed in an organization is an important enabler of (or constraint on) effective performance. Sometimes, increasing the total quantity of power in the behavioral system can lead to more effective cooperation. It’s akin to increasing the number of cards in a deck. The greater the number of cards, the greater the variety of moves that each player can make. In the same way, expanding people’s behavioral options mobilizes them to find the best ways to satisfy the multiple requirements of a complex task.
Reciprocity is the mutual conviction among people in a behavioral system that they have a shared interest in cooperation and that each actor’s success depends on the success of others. Another key intervention is to create mechanisms for making the necessary interdependencies among employees more visible. For example, setting rich performance objectives that go beyond purely individual objectives to include the impact of an individual’s behavior on the performance of others is one way to increase the sense of reciprocity among actors in the behavioral system.
Another way managers can nurture the behavioral system is to create feedback loops that expose people directly to the consequences in the future of the decisions they make and the actions they take today. For example, managers can lengthen the amount of time a particular group of people have to work together so that they are “all in the same boat.” This is the basic principle behind the cross-functional agile team as a work unit. Or organizations can speed up the frequency of deadlines or targets—the basic idea behind a sprint. Another way to extend the shadow of the future is to force people to “walk in another’s shoes”—for example, by designing career paths so that people know that they will experience in their next assignments the consequences of the decisions they make today.
The final rule is to factor cooperation more heavily into the rewards, both financial and nonfinancial, that the organization distributes to employees.
Earlier, I described how difficult it is to measure cooperation. At first glance, managers may view this difficulty as a limitation or constraint. In fact, it is a key resource for re-establishing the fundamental integrity of their role, because it means that in the new work environment, there is no alternative to the continual exercise of managerial judgment. No system, no metric, no rubric will be able to assess the effectiveness of cooperation among a group of people better than a human being exercising his or her judgment, and it is the responsibility of the manager to do so, rewarding those who cooperate well and ensuring that those who do not bear the consequences.
Of course, precisely because managerial judgment is so critical in the new, more fluid, more autonomous and self-managed work environment, it is also critical that that judgment be informed. It’s no longer good enough for managers to make judgments from afar, on the basis of second-hand information and reports (let alone their own biases). To evaluate the quality of cooperation, they must experience up close how the organization and its people are working.
The growing importance of managerial judgment in work environments of increasing complexity is yet another reason for bringing managers back to work.