Watkins Md 2012 How Managers Become Leaders Harvard Business Review June 6572
Reprint: R1206C Few managerial transitions are more difficult than making the move from leading a function to leading an entire enterprise for the first time. The scope and complexity of the chore increase dramatically, in ways that can exit executives feeling overwhelmed and uncertain. It truly is different at the top. But how, exactly? Career transition skillful Michael Watkins set out to explore that question in an extensive series of interviews with leadership mentors, Hour professionals, and newly minted unit heads. What he institute was that at this turning point, executives must navigate a tricky set of changes in their leadership focus and skills. Watkins calls these the 7 seismic shifts. New enterprise leaders must move from being a specialist to a generalist; from analyzing data to integrating cognition from multiple sources; and from implementing tactics to developing strategies. They also need to transform themselves from bricklayers into organizational architects; from trouble solvers into agenda setters; and from warriors intent on beating the contest into diplomats who engage with a full range of stakeholders. Finally, leaders must motility out from the wings and become used to living on center phase in the full spotlight. To make the transition, managers have to acquire new capabilities quickly. And though what got them to the top may no longer be enough, there are steps that they and their organizations can have to prepare them to succeed.
Artwork: Adam Ekbergs State Roads 2005, ink-jet print
Harald (not his real proper noun) is a high-potential leader with 15 years of experience at a leading European chemical company. He started every bit an assistant product manager in the plastics unit and was quickly transferred to Hong Kong to help fix the unit's new Asian business center. As sales there soared, he soon won a promotion to sales manager. Three years later he returned to Europe every bit the marketing and sales director for Europe, the Heart East, and Africa, overseeing a grouping of 80 professionals. Continuing his string of successes, he was promoted to vice president of marketing and sales for the polyethylene partition, responsible for several lines of products, related services, and a staff of virtually 200.
All of Harald'south hard work culminated in his appointment every bit the head of the company'southward plastic resins unit, a business with more than than three,000 employees worldwide. Quite intentionally, the company had assigned him to run a small but thriving business with a strong team. The idea was to give him the opportunity to motion beyond managing sales and marketing, get his artillery effectually an entire business, learn what it meant to head upward a unit with the help of his more-experienced team, and take his leadership skills to the next level in a situation gratuitous from complicating problems or crises. The setup seemed perfect, but a few months into the new position, Harald was struggling mightily.
Similar Harald, many rising stars trip when they shift from leading a part to leading an enterprise and for the first time taking responsibility for a P&L and oversight of executives across corporate functions. Information technology truly is different at the top. To find out how, I took an in-depth look at this critical turning bespeak, conducting an extensive series of interviews with more than 40 executives, including managers who had adult high-potential talent, senior HR professionals, and individuals who had recently fabricated the motility to enterprise leadership for the first time.
What I found is that to make the transition successfully, executives must navigate a tricky set of changes in their leadership focus and skills, which I call the 7 seismic shifts. They must acquire to move from specialist to generalist, analyst to integrator, tactician to strategist, mason to architect, problem solver to agenda setter, warrior to diplomat, and supporting cast fellow member to atomic number 82 role. Like so many of his peers, Harald had trouble negotiating most of these shifts. To see what makes them so difficult, let's follow him through each of them, as he confronts unnerving surprises, makes unwarranted assumptions, encounters entirely new demands on his time and imagination, makes decisions in ignorance, and learns from his mistakes.
Specialist to Generalist
Harald's immediate challenge was shifting from leading a unmarried function to overseeing the full set of business organization functions. In his first couple of months, this shift left him feeling disoriented and less confident in his ability to make good judgments. Then he barbarous into a archetype trap—overmanaging the role he knew well and undermanaging the others. Fortunately for Harald, this became crystal clear when his vice president of HR gave him some edgeless feedback most his relationship with his sales and marketing VP: "You lot are driving Claire crazy. Y'all need to requite her some space."
Harald's tendency to stay in his functional comfort zone is an understandable reaction to the stresses of moving up to a much broader role. It would be wonderful if newly appointed enterprise leaders were world-course experts in all business functions, only of course they never are. In some instances they take gained experience by rotating through diverse functions or working on cross-functional projects, which certainly helps. (See the sidebar "How to Develop Stiff Enterprise Leaders.") But the reality is that the move to enterprise leadership always requires executives who've been specialists to apace plow into generalists who know enough about all the functions to run their businesses.
What is "enough"? Enterprise leaders must exist able to (i) make decisions that are good for the concern as a whole and (2) evaluate the talent on their teams. To do both they demand to recognize that business functions are distinct managerial subcultures, each with its own mental models and language. Effective leaders empathise the different ways that professionals in finance, marketing, operations, Hr, and R&D approach business issues, and the various tools (discounted cash flow, customer segmentation, procedure flow, succession planning, phase gates, and the like) that each discipline applies. Leaders must be able to speak the language of all the functions and interpret for them when necessary. And critically, leaders must know the right questions to ask and the right metrics for evaluating and recruiting people to manage areas in which they themselves are not experts.
The good news for Harald was that, in addition to assigning him to a high-performing unit, his visitor had strong systems in place for evaluating and developing talent in central functions. These included well-crafted systems for functioning reviews and 360-degree feedback, and for collecting input from corporate functions. His heads of finance and Hour, for instance, while reporting direct to him, also had dotted-line reporting relationships with their respective corporate departments, which assisted Harald with their evaluation and evolution. And so he had enough of resources to help him empathize what "excellence" meant for each function.
By investing directly in creating standardized evaluation schemes for each function, companies can ensure that new enterprise leaders get the lay of the land faster. But even if their firms don't have such systems, aspiring enterprise leaders tin prepare themselves past edifice relationships with colleagues in other functions, seeking to larn from them (perchance in substitution for insight into their own functions) and then that they can develop their ain templates.
Analyst to Integrator
The primary responsibleness of functional leaders is to recruit, develop, and manage people who focus in analytical depth on specific business activities. An enterprise leader's job is to manage and integrate the collective knowledge of those functional teams to solve important organizational problems.
Harald found himself struggling with this shift early on every bit he sought to address the many competing demands of the business organisation. His sales and marketing VP, for example, wanted to aggressively go to market with a new product, while his head of operations worried that production couldn't be ramped upwards chop-chop enough to meet the sales staff's demand scenarios. Harald's team expected him to residuum the needs of the supply side of the business (operations) with those of its demand side (sales and marketing), to know when to focus on the quarterly business organisation results (finance) and when to invest in the future (R&D), to decide how much attention to devote to execution and how much to innovation, and to make many other such calls.
Over again, executives need general knowledge of the diverse functions to resolve such competing problems, only that isn't plenty. The skills required have less to do with analysis and more to practise with understanding how to make trade-offs and explain the rationale for those decisions. Here, too, previous experience with cross-functional or new-product development teams would stand newly minted enterprise leaders in practiced stead, as would a previous apprenticeship every bit a chief of staff to a senior executive. But ultimately, as Harald establish, there is no substitute for actually making the calls and learning from their outcome.
There is no substitute for actually making the calls and learning from their outcome.
Tactician to Strategist
In his early months, Harald threw himself into the myriad details of the business. Existence tactical was seductive—the activities were so concrete and the results so immediate. Consequently, he lost himself in the day-to-24-hour interval flow of attending meetings, making decisions, and pushing projects frontward.
The problem with this, of grade, was that a cadre function of Harald's new role was to be strategist-in-chief for the unit he now led. To practice that, he had to let get of many of the details and free his mind and his time to focus on college-level matters. More than generally, he needed to prefer a strategic mind-set up.
How do tactically strong leaders learn to develop such a mind-fix? Past cultivating three skills: level shifting, pattern recognition, and mental simulation. Level shifting is the ability to move fluidly among levels of assay—to know when to focus on the details, when to focus on the big picture, and how the two relate. Pattern recognition is the ability to discern of import causal relationships and other meaning patterns in a complex business and its environs—that is, to separate the signal from the dissonance. Mental simulation is the power to conceptualize how exterior parties (competitors, regulators, the media, central members of the public) will respond to what you do, to predict their actions and reactions in social club to define the best course to have. In Harald's first year, for instance, an Asian competitor introduced a lower-cost substitute for a key resin product his unit made. Harald needed not simply to consider the immediate threat but as well to think expansively most what the competitor's future intentions might be. Was the Asian company going to use this low-end product to forge strong client relationships and progressively offering a broader range of products? If so, what options should Harald's unit pursue? How would the competitor answer to what Harald chose to practise? Those were not questions he had been responsible for as caput of marketing and sales. In the stop, subsequently analyzing various courses of action with his senior team, he chose to lower prices, forgoing some current profits in an endeavor to tedious the loss of market share—a move he did non alive to regret.
Are strategic thinkers born or made? The answer is both. There'south no doubt that strategic thinking, like any other skill, can be improved with training. But the ability to shift through different levels of assay, recognize patterns, and construct mental models requires some natural propensity. One of the paradoxes of leadership development is that people earn promotions to senior functional levels predominantly past existence good at blocking and tackling, just employees with strategic talent may struggle at lower levels because they focus less on the details. Darwinian forces tin can winnow strategic thinkers out of the developmental pipeline likewise soon if companies don't prefer explicit policies to place and to some degree protect them in their early careers.
Bricklayer to Architect
Besides frequently, senior executives fiddle in the profession of organizational design without a license—and end up committing malpractice. They come into their first enterprise-level role itching to make their marker then target elements of the organization that seem relatively easy to change, like strategy or structure, without completely understanding the effect their moves will have on the organization as a whole.
About four months into his new role, for example, Harald concluded that he needed to restructure the business to focus more than on customers and less on production lines. Information technology was natural for him, every bit a former head of sales and marketing, to retrieve this way. In his eyes it was obvious that the business was too rooted in product development and operations and that its structure was an outdated legacy of the way the unit had been founded and grown. And so he was surprised when his restructuring proposal was met first with stunned silence from his team and then with vociferous opposition. It rapidly became articulate that the existing structure in this successful division was linked in intricate and nonobvious ways to its key processes and talent bases. To sell the company's chemicals, for instance, the salespeople needed to have deep product knowledge and the power to consult with customers on applications. A shift to a client-focused approach would take required them to sell a broader range of complex products and learn huge amounts of new expertise. Then while a move to a customer-focused structure had potential benefits, certain trade-offs needed to be evaluated. Implementation would, for instance, require significant adjustments to processes and substantial investments in employee retraining. These changes demanded a neat deal of thought and analysis.
This article also appears in:
As leaders movement upwardly to the enterprise level, they go responsible for designing and altering the architecture of their system—its strategy, structure, processes, and skill bases. To be constructive organizational architects, they need to think in terms of systems. They must understand how the fundamental elements of the organization fit together and non naively believe, as Harald in one case did, that they tin can alter ane element without thinking through the implications for all the others. Harald learned this the hard way because nix in his experience equally a functional leader had afforded him the opportunity to recall about an organization every bit a arrangement. Nor did he have enough experience with large-scale organizational change to develop those insights from observation.
In this Harald was typical: Enterprise leaders need to know the principles of organizational alter and modify management, including the mechanics of organizational design, business process improvement, and transition direction. Yet few rising executives get whatsoever formal training in these domains, leaving most of them ill equipped to exist the architects of their organizations—or even to be educated consumers of the work of organizational development professionals. Here Harald was over again fortunate in having—and having the sense to rely on—an experienced staff that offered him cogent advice about the many interdependencies he had not originally considered. Not all new enterprise leaders are that lucky, of class. Simply if their companies take invested in sending them to executive instruction programs that teach organizational change, they'll be improve prepared for this shift.
Trouble Solver to Calendar Setter
Many managers are promoted to senior levels on the strength of their ability to ready problems. When they become enterprise leaders, still, they must focus less on solving problems and more on defining which problems the arrangement should be tackling.
To exercise that, Harald had to perceive the full range of opportunities and threats facing his business organisation, and focus the attention of his team on only the well-nigh important ones. He also had to identify the "white spaces"—issues that don't fall neatly into any one function simply are yet important to the business, such as diversity.
The number of concerns Harald now had to consider was head-spinning. When he had run sales and marketing, he had gained some appreciation for how difficult it was for business heads to prioritize all the issues thrown at them in any given day, week, or month. Still, he was surprised by the scope and complexity of some of the problems at this level. He wasn't sure how to allocate his time and immediately felt overloaded. He knew he needed to delegate more, only he wasn't articulate yet about which tasks and assignments he could safely get out to others.
You may exist surprised by the intensity of the attention at center stage and the almost constant need to go along up your baby-sit.
The skills he had honed as a functional leader—mastery of sales and marketing tools and techniques, organizational know-how, and even the ability to mobilize talent and promote teamwork—were not enough. To work out which bug his team should focus on—that is, to set the agenda—he had to learn to navigate a far more uncertain and ambiguous environment than he was used to. He as well needed to learn to communicate priorities in ways his arrangement could respond to. Given his sales and marketing background, Harald struggled less with how to communicate his calendar. The challenge was figuring out what that agenda was. To some caste he just had to learn from experience, but here again he was aided by the members of his team, who pressed him for guidance on issues they knew he needed to consider. He too could rely on the company's almanac planning procedure, which provided a structure for defining central goals for his unit of measurement.
Warrior to Diplomat
In his previous roles, Harald had focused primarily on marshaling the troops to defeat the contest. Now he institute himself devoting a surprising amount of time to influencing a host of external constituencies, including regulators, the media, investors, and NGOs. His back up staff was bombarded with requests for his time: Could he participate in industry or authorities forums sponsored past the government affairs section? Would he be willing to sit for an interview with an editor from a leading business concern publication? Could he meet with a key group of institutional investors? Some of these groups he was familiar with; others non at all. Simply what was entirely new to him was his responsibility not just to interact with diverse stakeholders just also to proactively address their concerns in means that meshed with the firm'due south interests. Niggling of Harald'due south previous experience prepared him for the challenges of being a corporate diplomat.
What practice constructive corporate diplomats do? They use the tools of diplomacy—negotiation, persuasion, conflict management, and alliance building—to shape the external business organisation environment to support their strategic objectives. In the process they oft notice themselves collaborating with people with whom they compete aggressively in the market place every day.
To practise this well, enterprise leaders need to embrace a new mind-set up—to look for means that interests can or do marshal, understand how decisions are made in different kinds of organizations, and develop effective strategies for influencing others. They must too understand how to recruit and manage employees of a kind that they have probably never supervised before: professionals in key supporting functions such every bit government relations and corporate communications. And they must recognize that these employees' initiatives take longer horizons than the ongoing business organization, with its focus on quarterly or fifty-fifty annual results, does. Initiatives like a entrada to shape the development of government regulation tin can take years to unfold. Information technology took Harald a while to understand this, equally his staffers educated him about how painstakingly they managed issues over protracted periods of time and how they periodically bemoaned the results when someone took his center off the brawl.
Supporting Cast Fellow member to Pb Part
Finally, becoming an enterprise leader means moving to middle stage under the bright lights. The intensity of the attention and the nigh constant need to keep up his baby-sit caught Harald by surprise. He was somewhat shocked to notice how much stock people placed in what he said and did. Not long after he outset took the task, for case, he met with his vice president of R&D and mused about a new manner of packaging an existing product. Ii weeks later a preliminary feasibility report for it appeared on his desk-bound.
In part, this shift is about having a much greater impact as a role model. Managers at all levels are role models to some degree. Only at the enterprise level, their influence is magnified, as everyone looks to them for vision, inspiration, and cues near the "right" behaviors and attitudes. For good or ill, the personal styles and quirks of senior leaders are infectious, whether they are observed directly by employees or indirectly transmitted from their reports to the level below and on down through the organization. This effect can't really be avoided, but enterprise leaders can make it less inadvertent by cultivating more than self-awareness and taking the time to develop empathy with subordinates' viewpoints. Later all, it wasn't so long agone that they were the subordinates, drawing these kinds of inferences from their ain bosses' behavior.
And so there is the question of what it means, practically speaking, to pb large groups of people—how to define a compelling vision and share it in an inspiring way. Harald, already a strong communicator who was used to selling ideas along with products, however needed to accommodate his thinking in this regard (though perhaps less and then than some of his counterparts). In his previous task he had maintained a reasonable degree of personal, albeit sometimes sporadic, contact with about of his employees. Now that he was overseeing 3,000-plus people scattered around the globe, that was just impossible.
The implications of this became clear every bit he worked with his team to craft the annual strategy. When the time came to communicate information technology to the organization, he realized that he couldn't simply leave and sell it himself; he had to work more through his direct reports and find other channels, such equally video, for spreading the word. And after touring most of the unit's facilities, Harald besides worried that he'd never really exist able to figure out what was happening on the front lines. So rather than see just with leaders when he made site visits, he instituted brown-bag lunches with small groups of frontline employees and tuned in to online word groups in which employees could comment on the company.For the nigh part, the seven shifts involve switching from left-brain, analytical thinking to correct-brain conceptual mind-sets. But that doesn't hateful enterprise leaders never spend fourth dimension on tactics or on functional concerns. It's just that they spend far, far less time on those responsibilities than they used to in their previous roles. In fact, information technology'south ofttimes helpful for enterprise leaders to engage someone else—a principal of staff, a chief operating officer, or a project manager—to focus on execution, as a way to free upwards fourth dimension for their new role.
As for Harald, his story ended well. He was fortunate to be working for a visitor that believed in leadership development and to have an experienced team that was able—and willing—to give him effective counsel. So despite the many bumps in the road, the concern continued to thrive, and Harald eventually found his stride equally an enterprise leader. 3 years later, armed with all this experience, he was asked to take over a much larger, struggling unit of the company and initiated a successful turnaround. Reflecting back, he says, "The skills that got you lot where you are may not be the requisite skills to go yous to where y'all demand to go. This doesn't discount the accomplishments of your past, but they will not be everything you need for the side by side leg of the journey."
A version of this commodity appeared in the June 2012 outcome of Harvard Business Review.
brownhiscriand1971.blogspot.com
Source: https://hbr.org/2012/06/how-managers-become-leaders
0 Response to "Watkins Md 2012 How Managers Become Leaders Harvard Business Review June 6572"
Post a Comment