CHAPTER 3
Building the Innovative Organization

Photograph of a puffer fish.

Innovation has nothing to do with how many R&D dollars you have … it’s not about money. It’s about the people you have, how you’re led, and how much you get it.

Steve Jobs, interview with Fortune Magazine, 1981 [1]

People are our greatest asset.” This phrase – or variations on it – has become one of the clichés of management presentations, mission statements, and annual reports throughout the world. Along with concepts such as “empowerment” and “team working,” it expresses a view of people being at the creative heart of the enterprise. But very often the reader of such words – and particularly those “people” about whom they are written – may have a more cynical view, seeing organizations still operating as if people were part of the problem rather than the key to its solution.

In the field of innovation, this theme is of central importance. It is clear from a wealth of psychological research that every human being comes with the capability to find and solve complex problems, and where such creative behavior can be harnessed among a group of people with differing skills and perspectives extraordinary things can be achieved. We can easily think of examples. At the individual level, innovation has always been about exceptional characters who combine energy, enthusiasm, and creative insight to invent and carry forward new concepts, such as James Dyson, with his alternative approaches to domestic appliance design; Spence Silver, the 3M chemist who discovered the nonsticky adhesive behind “Post-it” notes; and Shawn Fanning, the young programmer who wrote the Napster software and almost single-handedly shook the foundations of the music industry.

Innovation is increasingly about teamwork and the creative combination of different disciplines and perspectives. Whether it is in designing a new car in half the usual time; bringing a new computer game to market; establishing new ways of delivering old services such as banking, insurance, or travel services; or putting men and women routinely into space; the success comes from people working together in high-performance teams.

This effect, when multiplied across the organization, can yield surprising results. In his work on US companies, Jeffrey Pfeffer notes the strong correlation between proactive people management practices and the performance of firms in a variety of sectors [2]. A comprehensive review for the UK Chartered Institute of Personnel and Development suggested that “… more than 30 studies carried out in the UK and US since the early 1990s leave no room to doubt that there is a correlation between people management and business performance, that the relationship is positive, and that it is cumulative: the more and the more effective the practices, the better the result [3].” Similar studies confirm the pattern in German firms [4]. In a knowledge economy where creativity is at a premium, people really are the most important assets which a firm possesses. The management challenge is how to go about building the kind of organizations in which such innovative behavior can flourish.

This chapter deals with the creation and maintenance of an innovative organizational context, one whose structure and underlying culture – that is, the pattern of values and beliefs – support innovation. It is easy to find prescriptions for innovative organizations that highlight the need to eliminate stifling bureaucracy, unhelpful structures, brick walls blocking communication, and other factors stopping the flow of good ideas. However, we must be careful not to fall into the chaos trap – not all innovation works in organic, loose, informal environments, or “skunk works” – and these types of organization can sometimes act against the interests of successful innovation. We need to determine appropriate organization – that is, the most suitable organization given the operating contingencies. Too little order and structure may be as bad as too much.

Equally, “innovative organization” implies more than a structure or process; it is an integrated set of components that work together to create and reinforce the kind of environment that enables innovation to flourish. Studies of innovative organizations have been extensive, although many can be criticized for taking a narrow view, or for placing too much emphasis on a single prescription like “team working” or “loose structures.” Nevertheless, it is possible to draw out from these a set of components that appear linked with success; these are outlined in Table 3.1 and explored in the subsequent discussion.

TABLE 3.1 Components of the Innovative Organization

Component Key Features Example References
Shared vision, leadership, and the will to innovate Clearly articulated and shared sense of purpose
Stretching strategic intent
“Top management commitment”
[58]
Appropriate structure Organization design that enables creativity, learning, and interaction. Not always a loose “skunk works” model; key issue is finding appropriate balance between “organic and mechanistic” options for particular contingencies [915]
Key individuals Promoters, champions, gatekeepers, and other roles that energize or facilitate innovation [9,16,17]
Effective team working Appropriate use of teams (at local, cross-functional, and inter-organizational level) to solve problems
Requires investment in team selection and building
[1820]
High-involvement innovation Participation in organization-wide continuous improvement activity [21,22]
Creative climate Positive approach to creative ideas, supported by relevant motivation systems [7,8,23,24]
External focus Internal and external customer orientation [2527]
Extensive networking

3.1 Shared Vision, Leadership, and the Will to Innovate

Innovation is essentially about learning and change and is often disruptive, risky, and costly. So, as Case Study 3.1 shows, it is not surprising that individuals and organizations develop many different cognitive, behavioral, and structural ways of reinforcing the status quo. Innovation requires energy to overcome this inertia and the determination to change the order of things. We see this in the case of individual inventors who champion their ideas against the odds, in entrepreneurs who build businesses through risk-taking behavior, and in organizations that manage to challenge the accepted rules of the game.

The converse is also true – the “not-invented-here” problem, in which an organization fails to see the potential in a new idea, or decides that it does not fit with its current pattern of business. In other cases, the need for a change is perceived, but the strength or saliency of the threat is underestimated. For example, during the 1980s, General Motors found it difficult to appreciate and interpret the information about Japanese competition, preferring to believe that their access in US markets was due to unfair trade policies rather than recognizing the fundamental need for process innovation, which the “lean manufacturing” approach that was pioneered in Japan was bringing to the car industry [28]. Christensen, in his studies of hard drives [29], and Tripsas and Gravetti, in their analysis of the problems Polaroid faced in making the transition to digital imaging, provide powerful evidence to show the difficulties faced by the established firms in interpreting the signals associated with a new and potentially disruptive technology [30].

This is also where the concept of “core rigidities” becomes important [31]. We have become used to seeing core competencies as a source of strength within the organization, but the downside is that the mindset, which is being highly competent in doing certain things, can also block the organization from changing its mind. Thus, ideas that challenge the status quo face an uphill struggle to gain acceptance; innovation requires considerable energy and enthusiasm to overcome barriers of this kind. One of the concerns in successful innovative organizations is finding ways to ensure that individuals with good ideas are able to progress them without having to leave the organization to do so [9]. Chapter 12 discusses the theme of “intrapreneurship” in more detail.

Changing mindset and refocusing organizational energies require the articulation of a new vision, and there are many cases where this kind of leadership is credited with starting or turning round organizations. Examples include Bill Gates (Microsoft), Steve Jobs (Pixar/Apple) [10], Jeff Bezos (Amazon), Elon Musk (Tesla), and Andy Grove (Intel) [11]. While we must be careful of vacuous expressions of “mission” and “vision,” it is also clear that in cases like these there has been a clear sense of, and commitment to, shared organizational purpose arising from such leadership.

“Top management commitment” is a common prescription associated with successful innovation; the challenge is to translate the concept into reality by finding mechanisms that demonstrate and reinforce the sense of management involvement, commitment, enthusiasm, and support. In particular, there needs to be a long-term commitment to major projects, as opposed to seeking short-term returns. Since much of innovation is about uncertainty, it follows that returns may not emerge quickly and that there will be a need for “patient money.” This may not always be easy to provide, especially when demands for shorter term gains by shareholders have to be reconciled with long-term technology development plans. One way of dealing with this problem is to focus not only on returns on investment but also on other considerations such as future market penetration and growth or the strategic benefits. Research Note 3.1 and Case Study 3.2 provide examples of such leadership.

A part of this pattern is also the acceptance of risk by the top management. Innovation is inherently uncertain and will inevitably involve failures as well as successes. Thus, successful management requires that the organization be prepared to take risks and to accept failure as an opportunity for learning and development. This is not to say that unnecessary risks should be taken – rather, as Robert Cooper suggests, the inherent uncertainty in innovation should be reduced where possible through the use of information collection and research [12].

We should not confuse leadership and commitment with always being the active change agent. In many cases, innovation happens in spite of the senior management within an organization, and success emerges as a result of guerrilla tactics rather than a frontal assault on the problem. Much has been made of the dramatic turnaround in IBM’s fortunes under the leadership of Lou Gerstner who took the ailing giant firm from a crisis position to one of leadership in the IT services field and an acknowledged pioneer of e-business. But closer analysis reveals that the entry into e-business was the result of a bottom-up team initiative led by a programmer named Dave Grossman. It was his frustration with the lack of response from his line managers that eventually led to the establishment of a broad coalition of people within the company who were able to bring the idea into practice and establish IBM as a major e-business leader. The message for senior management is as much about leading by creating space and support within the organization as it is about direct involvement.

The contributions that the leaders make to the performance of their organizations can be significant. Upper echelons theory argues that decisions and choices by top management have an influence on the performance of an organization (positive or negative!), through their assessment of the environment, strategic decision making, and support for innovation. The results of different studies vary, but the reviews of research on leadership and performance suggest that the leadership directly influences around 15% of the differences found in the performance of businesses and contributes around an additional 35% through the choice of business strategy [13]. Therefore, both direct and indirect leadership can account for half of the variance in performance observed across organizations. At higher levels of management, the problems to be solved are more likely to be ill-defined, demanding leaders to conceptualize more.

Researchers have identified a long list of characteristics that might have something to do with being effective in certain situations, which typically include the following traits [14]:

  • bright, alert, and intelligent
  • seek responsibility and take charge
  • skillful in their task domain
  • administratively and socially competent
  • energetic, active, and resilient
  • good communicators

Although these lists may describe some characteristics of some leaders in certain situations, measures of these traits yield highly inconsistent relationships with being a good leader [15]. In short, there is no brief and universal list of enduring traits that all good leaders must possess under all conditions.

Studies in different contexts identify not only the technical expertize of leadership influencing group performance but also broader cognitive ability, such as creative problem-solving and information-processing skills. For example, studies of groups facing novel, ill-defined problems confirm that both expertize and cognitive-processing skills are key components of creative leadership and are both associated with effective performance of creative groups [32]. Moreover, this combination of expertize and cognitive capacity is critical for the evaluation of others’ ideas. A study of scientists found that they most valued their leader’s inputs at the early stages of a new project, when they were formulating their ideas, and defining the problems, and later at the stage where they needed feedback and insights into the implications of their work. Therefore, a key role of creative leadership in such environments is to provide feedback and evaluation, rather than to simply generate ideas [33]. This evaluative role is critical, but is typically seen as not being conducive to creativity and innovation, where the conventional advice is to suspend judgement to foster idea generation. Also, it suggests that the conventional linear view that evaluation follows idea generation may be wrong. Evaluation by creative leadership may precede idea generation and conceptual combination. Research Note 3.2 identifies the contribution of diversity in senior management teams.

The quality and nature of the leader–member exchange (LMX) has also been found to influence the creativity of subordinates [34]. A study of 238 knowledge workers from 26 project teams in high-technology firms identified not only a number of positive aspects of LMX, including monitoring, clarifying, and consulting, but also found that the frequency of negative LMX was as high as the positive, around a third of respondents reporting these [35]. Therefore, LMX can either enhance or undermine subordinates’ sense of competence and self-determination. However, the analysis of exchanges perceived to be negative and positive revealed that it was typically how something was done rather than what was done, which suggests that task and relationship behaviors in leadership support and LMX are intimately intertwined, and that negative behaviors can have a disproportionate negative influence. Research Note 3.3 shows how LMX contributes to individual innovation performance.

Intellectual stimulation by leaders has a stronger effect on the organizational performance under conditions of perceived uncertainty. Intellectual stimulation includes behaviors that increase others’ awareness of and interest in problems and develops their propensity and ability to tackle problems in new ways. It is also associated with the commitment to an organization [36]. Stratified system theory (SST) focuses on the cognitive aspects of leadership and argues that conceptual capacity is associated with superior performance in strategic decision making where there is a need to integrate complex information and think abstractly in order to assess the environment. It is also likely to demand a combination of these problem-solving capabilities and social skills, as leaders will depend upon others to identify and implement solutions [37]. This suggests that under conditions of environmental uncertainty, the contribution of leadership is not simply, or even primarily, to inspire or build confidence, but rather to solve problems and make appropriate strategic decisions.

Rafferty and Griffin propose other subdimensions to the concept of transformational leadership that may have a greater influence on creativity and innovation, including articulating a vision and inspirational communication [36]. They define a vision as “the expression of an idealized picture of the future based around organizational values,” and inspirational communication as “the expression of positive and encouraging messages about the organization, and statements that build motivation and confidence.” They found that the expression of a vision has a negative effect on followers’ confidence, unless accompanied with inspirational communication. Mission awareness increases the probability of success of R&D projects, but the effects are stronger at the earlier stages: in the planning and conceptual stage, mission awareness explained two-thirds of the subsequent project success [38]. Leadership clarity is associated with clear team objectives, high levels of participation, commitment to excellence, and support for innovation [39].

The creative leader needs to be much more than simply provide a passive, supportive role to encourage creative followers. Perceptual measures of leaders’ performance suggest that in a research environment the perception of a leader’s technical skill is the single best predictor of research group performance, explaining around half of innovation performance [40]. Keller found that the type of project moderates the relationships between leadership style and project success and found that transformational leadership was a stronger predictor in research projects than in development projects [41]. This strongly suggests that certain qualities of transformational leadership may be most appropriate under conditions of high complexity, uncertainty, or novelty, whereas a transactional style has a positive effect in an administrative context, but a negative effect in a research context [42]. Research Note 3.4 reviews the research on the components of innovation leadership and identifies the most significant characteristics needed.

3.2 Appropriate Organizational Structure

No matter how well developed the systems are for defining and developing innovative products and processes, they are unlikely to succeed unless the surrounding organizational context is favorable. Achieving this is not easy, and it involves creating the organizational structures and processes that enable technological change to thrive. For example, rigid hierarchical organizations in which there is a little integration between functions and where communication tends to be top-down and one-way in character are unlikely to be very supportive of the smooth information flows and cross-functional cooperation recognized as being important factors for success.

Much of the innovation research recognizes that the organizational structures are influenced by the nature of tasks to be performed within the organization. In essence, the less programmed and more uncertain the tasks, the greater the need for flexibility around the structuring of relationships [43]. For example, activities such as production, order processing, and purchasing are characterized by decision making that is subject to little variation. (Indeed in some cases, these decisions can be automated through employing particular decision rules embodied in computer systems.) But others require judgement and insight and vary considerably from day to day – and these include those decisions associated with innovation. Activities of this kind are unlikely to lend themselves to routine, structured, and formalized relationships, but instead require flexibility and extensive interaction. Several writers have noted this difference between what have been termed “programmed” and “nonprogrammed” decisions and argued that the greater the level of nonprogrammed decision making, the more the organization needs a loose and flexible structure [44].

In the late 1950s, considerable work was done on this problem by researchers Tom Burns and George Stalker, who outlined the characteristics of what they termed “organic” and “mechanistic” organizations [45]. The former are essentially environments suited to conditions of rapid change while the latter are more suited to stable conditions – although these represent poles on an ideal spectrum they do provide useful design guidelines about organizations for effective innovation. Other studies include those of Rosabeth Moss-Kanter [46] and Hesselbein et al. [5].

The relevance of Burns and Stalker’s model can be seen in an increasing number of cases where organizations have restructured to become less mechanistic. For example, General Electric in the United States underwent a painful but ultimately successful transformation, moving away from a rigid and mechanistic structure to a looser and decentralized form [11]. ABB, the Swiss–Swedish engineering group, developed a particular approach to their global business based on operating as a federation of small businesses, each of which retained much of the organic character of small firms [6]. Other examples of radical changes in structure include the Brazilian white goods firm Semco and the Danish hearing aid company Oticon [47]. But again we need to be careful – what works under one set of circumstances may diminish in value under others. While models such as that deployed by ABB helped at the time, later developments meant that these proved less appropriate and were insufficient to deal with new challenges emerging elsewhere in the business.

Related to this work has been another strand that looks at the relationship between different environments and organizational form. Once again, the evidence suggests that the higher the uncertainty and complexity in the environment, the greater the need for flexible structures and processes to deal with it [48]. This partly explains why some fast-growing sectors, for example, electronics or biotechnology, are often associated with more organic organizational forms, whereas mature industries often involve more mechanistic arrangements.

One important study in this connection was that originally carried out by Lawrence and Lorsch looking at product innovation. Their work showed that innovation success in mature industries such as food packaging and growing sectors such as plastics depended on having structures that were sufficiently differentiated (in terms of internal specialist groups) to meet the needs of a diverse marketplace. But success also depended on having the ability to link these specialist groups together effectively so as to respond quickly to market signals; they reviewed several variants on coordination mechanisms, some of which were more or less effective than others. Better coordination was associated with more flexible structures capable of rapid response [49].

We can see clear application of this principle in the current efforts to reduce “time to market” in a range of businesses [50]. Rapid product innovation and improved customer responsiveness are being achieved through extensive organizational change programs involving parallel working, early involvement of different functional specialists, closer market links and user involvement, and through the development of team working and other organizational aids to coordination.

Another strand of work, which has had a strong influence on the way we think about organizational design, was that originated by Joan Woodward associated with the nature of the industrial processes being carried out [51]. Her studies suggested that structures varied between industries with a relatively high degree of discretion (such as small batch manufacturing) through to those involving mass production where more hierarchical and heavily structured forms prevailed. Other variables and combinations, which have been studied for their influence on structure, include size, age, and company strategy [52]. In the 1970s, the extensive debate on organization structure began to resolve itself into a “contingency” model. In essence, this view argues that there is no single “best” structure, but that successful organizations tend to be those which develop the most suitable “fit” between structure and operating contingencies.

The Canadian writer Henry Mintzberg drew much of the work on structure together and proposed a series of archetypes that provide templates for the basic structural configurations into which firms are likely to fall [53]. These categories – and their implications for innovation management – are summarized in Table 3.2. Case Study 3.3 gives an example of the importance of organizational structure and the need to find appropriate models.

TABLE 3.2 Mintzberg’s Structural Archetypes

Therefore, a key challenge for managing innovation is one of fit – of getting the most appropriate structural form for the particular circumstances. The increasing importance of innovation and the consequent experience of high levels of change across the organization have begun to pose a challenge for organizational structures normally configured for stability. Thus, traditional machine bureaucracies – typified by the car assembly factory – are becoming more hybrid in nature, tending toward what might be termed a “machine adhocracy” with creativity and flexibility (within limits) being actively encouraged. The case of “lean production” with its emphasis on team working, participation in problem solving, flexible cells, and flattening of hierarchies is a good example, where there is significant loosening of the original model to enhance innovativeness [54].

Organization Archetype Key Features Innovation Implications
Simple structure Centralized organic type – centrally controlled but can respond quickly to changes in the environment. Usually small and often directly controlled by one person. Designed and controlled in the mind of the individual with whom decision-making authority rests. Strengths are speed of response and clarity of purpose. Weaknesses are the vulnerability to individual misjudgement or prejudice and resource limits on growth Small start-ups in high technology – “garage businesses” – are often simple structures. Strengths are in energy, enthusiasm, and entrepreneurial flair – simple structure innovating firms are often highly creative. Weaknesses are in long-term stability and growth and overdependence on key people who may not always be moving in the right business direction
Machine bureaucracy Centralized mechanistic organization controlled centrally by systems. A structure designed like a complex machine with people seen as cogs in the machine. Design stresses the function of the whole and specialization of the parts to the point where they are easily and quickly interchangeable. Their success comes from developing effective systems that simplify tasks and routinize behavior. Strengths of such systems are the ability to handle complex integrated processes like vehicle assembly. Weaknesses are the potential for alienation of individuals and the buildup of rigidities in inflexible systems Machine bureaucracies depend on specialists for innovation, and this is channelled into the overall design of the system. Examples include fast food (McDonald’s), mass production (Ford), and large-scale retailing (Tesco), in each of which there is considerable innovation, but concentrated on specialists and impacting at the system level. Strengths of machine bureaucracies are their stability and their focus of technical skills on designing the systems for complex tasks. Weaknesses are their rigidities and inflexibility in the face of rapid change and the limits on innovation arising from nonspecialists
Divisionalized form Decentralized organic form designed to adapt to local environmental challenges. Typically associated with larger organizations, this model involves specialization into semi-independent units. Examples would be strategic business units or operating divisions. Strengths of such a form are the ability to attack particular niches (regional, market, product, etc.) while drawing on central support. Weaknesses are the internal frictions between divisions and the center Innovation here often follows a “core and periphery” model in which R&D of interest to the generic nature is carried out in central facilities while more applied and specific work is carried out within the divisions. Strengths of this model include the ability to concentrate on developing competency in specific niches and to mobilize and share knowledge gained across the rest of the organization. Weaknesses include the “centrifugal pull” away from central R&D toward applied local efforts and the friction and competition between divisions that inhibits sharing of knowledge
Professional bureaucracy Decentralized mechanistic form, with power located with individuals but coordination via standards. This kind of organization is characterized by relatively high levels of professional skills and is typified by specialist teams in consultancies, hospitals, or legal firms. Control is largely achieved through consensus on standards (“professionalism”), and individuals possess a high degree of autonomy. Strengths of such an organization include high levels of professional skill and the ability to bring teams together This kind of structure typifies design and innovation consulting activity within and outside organizations. The formal R&D, IT, or engineering groups would be good examples of this, where technical and specialist excellence is valued. Strengths of this model are in technical ability and professional standards. Weaknesses include difficulty of managing individuals with high autonomy and knowledge power
Adhocracy Project type of organization designed to deal with instability and complexity. Adhocracies are not always long-lived, but offer a high degree of flexibility. Team based, not only with high levels of individual skill but also the ability to work together. Internal rules and structure are minimal and subordinate to getting the job done. Strengths of the model are its ability to cope with high levels of uncertainty and its creativity. Weaknesses include the inability to work together effectively due to unresolved conflicts and a lack of control due to lack of formal structures or standards This is the form most commonly associated with innovative project teams – for example, in new product development or major process change. The NASA project organization was one of the most effective adhocracies in the program to land a man on the moon; significantly the organization changed its structure almost once a year during the 10-year program, to ensure it was able to respond to the changing and uncertain nature of the project. Strengths of adhocracies are the high levels of creativity and flexibility – the “skunk works” model advocated in the literature. Weaknesses include lack of control and over commitment to the project at the expense of the wider organization
Mission oriented Emergent model associated with shared common values. This kind of organization is held together by members sharing a common and often altruistic purpose – for example, in voluntary and charity organizations. Strengths are high commitment and the ability of individuals to take initiatives without reference to others because of shared views about the overall goal. Weaknesses include lack of control and formal sanctions Mission-driven innovation can be highly successful, but requires energy and a clearly articulated sense of purpose. Aspects of total quality management and other value-driven organizational principles are associated with such organizations, with a quest for continuous improvement driven from within rather than in response to external stimulus. Strengths lie in the clear sense of common purpose and the empowerment of individuals to take initiatives in that direction. Weaknesses lie in overdependence on key visionaries to provide clear purpose and lack of “buy-in” to the corporate mission

3.3 Key Individuals

Another important element is the presence of key enabling figures. Such key figures or champions have been associated with many famous innovations – for example, the development of Pilkington’s float glass process or Edwin Land and the Polaroid photographic system [55]. Case Study 3.4 gives another example of the role of key individuals, James Dyson. One clear example of such individual contribution comes, of course, from start-up entrepreneurs who demonstrate considerable abilities not only around recognizing opportunities but also in configuring networks and finding resources to enable them to take those ideas forward.

There are, in fact, several roles that key figures can play, which have a bearing on the outcome of a project. First, there is the source of critical technical knowledge – often the inventor or team leader responsible for an invention. They will have the breadth of understanding of the technology behind the innovation and the ability to solve the many development problems likely to emerge in the long haul from laboratory or drawing board to full scale. The contribution here is not only of technical knowledge but it also involves inspiration when particular technological problems appear insoluble and motivation and commitment.

Influential though such technical champions might be, they may not be able to help an innovation progress unaided through the organization. Not all problems are technical in nature; other issues such as procuring resources or convincing sceptical or hostile critics elsewhere in the organization may need to be dealt with. Here our second key role emerges – that of organizational sponsor.

Typically, this person has power and influence and is able to pull the various strings of the organization (often from a seat on the board); in this way, many of the obstacles to an innovation’s progress can be removed or the path at least smoothed. Such sponsors do not necessarily need to have a detailed technical knowledge of the innovation (although this is clearly an asset), but they do need to believe in its potential.

Recent exploration of the product development process has highlighted the important role played by the team members and in particular the project team leader. There are close parallels to the champion model: influential roles range from what Clark and Fujimoto call “heavyweight” project managers who are deeply involved and have the organizational power to make sure things come together, through to the “lightweight” project manager whose involvement is more distant. Research on Japanese product development highlights the importance of the shusha or team leader; in some companies (such as Honda), the shusha is empowered to override even the decisions and views of the chief executive [56]! The important message here is to match the choice of project manager type to the requirements of the situation – and not to use the “sledgehammer” of a heavyweight manager for a simple task.

Key roles are not just on the technical and project management side: studies of innovation (going right back to Project SAPPHO and its replications) also highlighted the importance of the “business innovator,” someone who could represent and bring to bear the broader market or user perspective [16].

Although innovation history is full of examples where such key individuals – acting alone or in tandem – have had a marked influence on success, we should not forget that there is a downside as well. Negative champions – project assassins – can also be identified, whose influence on the outcome of an innovation project is also significant but in the direction of killing it off. For example, there may be internal political reasons why some parts of an organization do not wish for a particular innovation to progress – and through placing someone on the project team or through lobbying at board level or in other ways a number of obstacles can be placed in its way. Equally, our technical champion may not always be prepared to let go of their pet idea, even if the rest of the organization has decided that it is not a sensible direction in which to progress. Their ability to mobilize support and enthusiasm and to surmount obstacles within the organization can sometimes lead to wrong directions being pursued, or the continued chasing up what many in the organization see as a blind alley.

One other type of key individual is that of the “technological gatekeeper.” Innovation is about information and, as we saw earlier, success is strongly associated with good information flow and communication. Research has shown that such networking is often enabled by key individuals within the organization’s informal structure who act as “gatekeepers” – collecting information from various sources and passing it on to the relevant people who will be best able or most interested to use it. Thomas Allen, working at MIT, made a detailed study of the behavior of engineers during the large-scale technological developments surrounding the Apollo rocket program. His studies highlighted the importance of informal communications in successful innovation and drew particular attention to gatekeepers – who were not always in formal information management positions but who were well connected in the informal social structure of the organization – as key players in the process [17].

This role is becoming of increasing importance in the field of knowledge management where there is growing recognition that enabling effective sharing and communication of valuable knowledge resources is not simply something that can be accomplished by advanced IT and clever software – there is a strong interpersonal element [57]. Such approaches become particularly important in distributed or virtual teams where “managing knowledge spaces” and the flows across them are of significance [58]. Research Note 3.5 identifies different individual roles in promoting innovation within organizations.

3.4 High Involvement in Innovation

Whereas innovation is often seen as the province of specialists in R&D, marketing, design, or IT, the underlying creative skills and problem-solving abilities are possessed by everyone. If mechanisms can be found to focus such abilities on a regular basis across the entire company, the resulting innovative potential is enormous. Although each individual may only be able to develop limited, incremental innovations, the sum of these efforts can have far-reaching impacts.

A good illustration of this is the “quality miracle,” which was worked by the Japanese manufacturing industry in the postwar years, and which owed much to what they term kaizen – continuous improvement. Firms such as Toyota and Matsushita receive millions of suggestions for improvements every year from their employees – and the vast majority of these are implemented [59]. Individual case studies confirm this pattern in a number of countries. As one UK manager put it, “Our operating costs are reducing year on year due to improved efficiencies. We have seen a 35% reduction in costs within two and a half years by improving quality. There are an average of 21 ideas per employee today compared to nil in 1990. Our people have accomplished this.” Case Study 3.5 provides another example of high-involvement innovation.

Although high-involvement schemes of this kind received considerable publicity in the late twentieth century, associated with total quality management and lean production, they are not a new concept. For example, Denny’s Shipyard in Dumbarton, Scotland, had a system that asked workers (and rewarded them for) “any change by which work is rendered either superior in quality or more economical in cost” – back in 1871. John Patterson, founder of the National Cash Register Company in the USA, started a suggestion and reward scheme aimed at harnessing what he called “the hundred-headed brain” around 1894.

Since much of such employees’ involvement in innovation focuses on incremental changes, it is tempting to see its effects as marginal. Studies show, however, that when taken over an extended period, it is a significant factor in the strategic development of the organization [60].

Underpinning such continuous incremental innovation are higher levels of participation in innovation. For example:

  • In the field of quality management, it became clear that major advantages could accrue from better and more consistent quality in products and services. Crosby’s work on quality costs suggested the scale of the potential savings (typically 20–40% of total sales revenue), and the experience of many Japanese manufacturers during the postwar period provide convincing arguments in favor of this approach [61].
  • The concept of “lean thinking” has diffused widely during the past 20 years and is now applied in manufacturing and services as diverse as chemicals production, hospital management, and supermarket retailing [62]. It originally emerged from detailed studies of assembly plants in the car industry, which highlighted significant differences between the best and the average plants along a range of dimensions, including productivity, quality, and time. Efforts to identify the source of these significant advantages revealed that the major differences lay not in higher levels of capital investment or more modern equipment, but in the ways in which production was organized and managed [28]. The authors of the study concluded:
  • … our findings were eye-opening. The Japanese plants require one-half the effort of the American luxury-car plants, half the effort of the best European plant, a quarter of the effort of the average European plant, and one-sixth the effort of the worst European luxury car producer. At the same time, the Japanese plant greatly exceeds the quality level of all plants except one in Europe – and this European plant required four times the effort of the Japanese plant to assemble a comparable product…
  • Central to this alternative model was an emphasis on team working and participation in innovation.
  • The principles underlying “lean thinking” had originated in experiences with what were loosely called “Japanese manufacturing techniques [63].” This bundle of approaches (which included umbrella ideas like “just-in-time” and specific techniques like poke yoke) were credited with having helped Japanese manufacturers gain significant competitive edge in sectors as diverse as electronics, motor vehicles, and steel making [64]. Underpinning these techniques was a philosophy that stressed high levels of employee involvement in the innovation process, particularly through sustained incremental problem solving – kaizen [21].

The transferability of such ideas between locations and into different application areas has also been extensively researched. It is clear from these studies that the principles of “lean” manufacturing can be extended into supply and distribution chains into product development and R&D and into service activities and operations [65]. Nor is there any particular barrier in terms of national culture: high-involvement approaches to innovation have been successfully transplanted to a number of different locations. Case Study 3.6 charts the adoption of high-involvement innovation in different organizations.

Company level studies support this view. Ideas UK is an independent body that offers advice and guidance to firms wishing to establish and sustain employee involvement programs. It grew out of the UK Suggestion Schemes Association and offers an opportunity for firms to learn about and share experiences with high-involvement approaches. Its 2009 annual survey of around 160 organizational members highlighted cost savings of over £100m with the average implemented idea being worth £1400, giving a return on investment of around 5 to 1. Participation rates across the workforce are around 28%.

Specific examples include the Siemens Standard Drives (SSD) suggestion scheme that generates ideas that save the company about £750,000 a year. The electrical engineering giant receives about 4000 ideas per year, of which approximately 75% are implemented. Pharmaceutical company Pfizer’s scheme generates savings of around £250,000, and the Chessington World of Adventures’ ideas scheme saves around £50,000. Much depends on firm size, of course – for example, the BMW Mini plant managed savings close to £10m at its plant in Cowley which they attribute to employee involvement.

Similar data can be found in other countries – for example, a study conducted by the Employee Involvement Association in the United States suggested that companies can expect to save close to £200 annually per employee by implementing a suggestion system. Ideas America report around 6000 schemes operating. In Germany, specific company savings reported by Zentrums Ideen management include (2010 figures) Deutsche Post DHL €220m, Siemens €189m, and Volkswagen €94m. Importantly, the benefits are not confined to large firms – among SMEs were Takata Petri €6.3m, Herbier Antriebstechnik €3.1m, and Mitsubishi Polyester Film €1.8m. In a survey of 164 German and Austrian firms representing 1.5m workers, they found around 20% (326,000) workers involved and contributing just under 1 million ideas. Of these, two-thirds were implemented producing savings of €1.086bn. The investment needed to generate these was of the order of €109m giving an impressive rate of return. Table 3.3 summarizes these achievements.

TABLE 3.3 High-involvement Innovation in German and Austrian Companies

Source: Zentrums Ideenmanagement, 2011.

Key Characteristics
Ideas/100 workers 62
Participation rate 21%
Implementation rate (of ideas) 69%
Savings per worker (€) 622
Investment per worker (€) 69
Investment to realize each implemented idea (€) 175
Savings per implemented idea (€) 1540
Ideas per worker per year Average of 6, as high as 21

For example, survey data from across Europe suggest that the majority of larger organizations have begun its implementation. Another major survey involving over 1000 organizations in a total of seven countries provides a useful map of the take-up and experience with high-involvement innovation in manufacturing. Overall, around 80% of organizations were aware of the concept and its relevance, but its actual implementation, particularly in more developed forms involved, around half of the firms [66]. The average number of years that the firms had been working with high-involvement innovation on a systematic basis was 3.8, supporting the view that this is not a “quick fix” but something to be undertaken as a major strategic commitment. Indeed, those firms that were classified as “CI innovators” – operating well-developed high-involvement systems – had been working on this development for an average of nearly seven years. Research Note 3.6 identifies four enabling factors to support employee-led innovation.

Growing recognition of the potential has moved the management question away from whether or not to try out employee involvement to one of “how to make it happen?” The difficulty is less about getting started than about keeping it going long enough to make a real difference. Many organizations have experience in starting the process – getting an initial surge of ideas and enthusiasm during a “honeymoon” period – and then seeing it gradually ebb away until there is little or no HII activity. A quick “sheep dip” of training plus a bit of enthusiastic arm waving from the managing director isn’t likely to do much in the way of fundamentally changing “the way we do things around here” – the underlying culture – of the organization.

3.5 A Roadmap for the Journey

Research on implementing HII suggests that there are a number of stages in this journey, progressing in terms of the development of systems and capability to involve people and also in terms of the bottom-line benefits [22]. Each of these takes time to move through, and there is no guarantee that organizations will progress to the next level. Moving on means having to find ways of overcoming the particular obstacles associated with different stages, as shown in Figure 3.1.

Illustration of the five-stage high-involvement innovation model.

FIGURE 3.1 The five-stage high-involvement innovation model.

The first stage – level 1 – is what we might call “unconscious HII.” There is little, if any, HII activity going on, and when it does happen it is essentially random in nature and occasional in frequency. People do help to solve problems from time to time, but there is no formal attempt to mobilize or build on this activity. Not surprisingly, there is less impact associated with this kind of change.

Level 2 represents an organization’s first serious attempts to mobilize HII. It involves setting up a formal process for finding and solving problems in a structured and systematic way – and training and encouraging people to use it. Supporting this will be some form of reward/recognition arrangement to motivate and encourage continued participation. Ideas will be managed through some form of system for processing and progressing as many as possible and handling those that cannot be implemented. Underpinning the whole setup will be an infrastructure of appropriate mechanisms (teams, task forces, or whatever), facilitators, and some form of steering group to enable HII to take place and to monitor and adjust its operation over time. None of this can happen without top management support and commitment of resources to back that up. In order to maintain progress, there is a need to move to the next level of HII – concerned with strategic focus and systematic improvement.

Level 3 involves coupling the HII habit to the strategic goals of the organization such that all the various local-level improvement activities of teams and individuals can be aligned. Two key behaviors need to be added to the basic suite – those of strategy deployment and of monitoring and measuring. Strategy (or policy) deployment involves communicating the overall strategy of the organization and breaking it down into manageable objectives toward which HII activities in different areas can be targeted. Linked to this is the need to learn to monitor and measure the performance of a process and use this to drive the continuous improvement cycle. Level 3 activity represents the point at which HiII makes a significant impact on the bottom line – for example, in reducing throughput times, scrap rates, excess inventory, and so on. The majority of “success stories” in HII can be found at this level – but it is not the end of the journey.

One of the limits of level 3 HII is that the direction of activity is still largely set by management and within prescribed limits. Activities may take place at different levels, from individuals through small groups to cross-functional teams, but they are still largely responsive and steered externally. The move to level 4 introduces a new element – that of “empowerment” of individuals and groups to experiment and innovate on their own initiative.

Level 5 is a notional end point for the journey – a condition where everyone is fully involved in experimenting and improving things, in sharing knowledge, and in creating an active learning organization. Table 3.4 illustrates the key elements in each stage. In the end, the task is one of building a shared set of values that bind people in the organization together and enable them to participate in its development. As one manager put it in a UK study, “… we never use the word empowerment! You can’t empower people – you can only create the climate and structure in which they will take responsibility…” [46]. Case Study 3.7 provides an example of an organization developing through these different stages.

TABLE 3.4 Stages in the Evolution of HII Capability

Stage of Development Typical Characteristics
1. “Natural”/background HII Problem-solving random
No formal efforts or structure
Occasional bursts punctuated by inactivity and nonparticipation
Dominant mode of problem solving is by specialists
Short-term benefits
No strategic impact
2. Structured HII Formal attempts to create and sustain HII
Use of a formal problem-solving process
Use of participation
Training in basic HII tools
Structured idea management system
Recognition system
Often parallel system to operations
3. Goal-oriented HII All of the above, plus formal deployment of strategic goals
Monitoring and measurement of HII against these goals
Inline system
4. Proactive/empowered HII All of the above, plus responsibility for mechanisms, timing, and so on, devolved to problem-solving unit
Internally directed rather than externally directed HII
High levels of experimentation
5. Full HII capability – the learning organization HII as the dominant way of life
Automatic capture and sharing of learning
Everyone actively involved in innovation process
Incremental and radical innovation

3.6 Effective Team Working

It takes five years to develop a new car in this country. Heck, we won World War 2 in four years…” In the late 1980s, Ross Perot’s critical comment on the state of the United States car industry captured some of the frustration with existing ways of designing and building cars. In the years that followed, significant strides were made in reducing the development cycle, with Ford and Chrysler succeeding in dramatically reducing time and improving quality. Much of the advantage was gained through extensive team working; as Lew Varaldi, project manager of Ford’s Team Taurus project put it, “… it’s amazing the dedication and commitment you get from people…we will never go back to the old ways because we know so much about what they can bring to the party…” [67].

Experiments indicate that teams have more to offer than individuals in terms of both fluency of idea generation and in flexibility of solutions developed. Focusing this potential on innovation tasks is the prime driver for the trend toward high levels of team working – in project teams, in cross-functional and inter-organizational problem-solving groups and in cells and work groups where the focus is on incremental, adaptive innovation.

Many use the terms “group” and “team” interchangeably. In general, the word “group” refers to an assemblage of people who may just be near to each other. Groups can be a number of people who are regarded as some sort of unity or are classed together on account of any sort of similarity. For us, a team means a combination of individuals who come together or who have been brought together for a common purpose or goal in their organization. A team is a group that must collaborate in their professional work in some enterprise or on some assignment and share accountability or responsibility for obtaining results. There are a variety of ways to differentiate working groups from teams. One senior executive with whom we have worked described groups as individuals with nothing in common, except a zip/postal code. Teams, however, were characterized by a common vision.

Considerable work has been done on the characteristics of high-performance project teams for innovative tasks, and the main findings are that such teams rarely happen by accident [68]. They result from a combination of selection and investment in team building, allied to clear guidance on their roles and tasks, and a concentration on managing group process as well as task aspects [18]. For example, research within the Ashridge Management College developed a model for “superteams,” which includes components of building and managing the internal team and also its interfaces with the rest of the organization [19].

Holti, Neumann, and Standing provide a useful summary of the key factors involved in developing team working [69]. Although there is considerable current emphasis on team working, we should remember that teams are not always the answer. In particular, there are dangers in putting nominal teams together where unresolved conflicts, personality clashes, lack of effective group processes, and other factors can diminish their effectiveness. Tranfield et al. look at the issue of team working in a number of different contexts and highlight the importance of selecting and building the appropriate team for the task and the context [70].

Teams are increasingly being seen as a mechanism for bridging boundaries within the organization – and indeed, in dealing with inter-organizational issues. Cross-functional teams can bring together the different knowledge sets needed for tasks such as product development or process improvement – but they also represent a forum where often deep-rooted differences in perspectives can be resolved [71]. Lawrence and Lorsch in their pioneering study of differentiation and integration within organizations found that interdepartmental clashes were a major source of friction and contributed much to delays and difficulties in operations. Successful organizations were those which invested in multiple methods for integrating across groups – and the cross-functional team was one of the most valuable resources [49]. But, as we indicated above, building such teams is a major strategic task – they will not happen by accident, and they will require additional efforts to ensure that the implicit conflicts of values and beliefs are resolved effectively.

Self-managed teams working within a defined area of autonomy can be very effective, for example, Honeywell’s defence avionics factory reported a dramatic improvement in on-time delivery – from below 40% in the 1980s to 99% in 1996 – to the implementation of self-managing teams [72]. In the Netherlands, one of the most successful bus companies is Vancom Zuid-Limburg, used self-managing teams to both reduce costs and improve customer satisfaction ratings, and one manager now supervises over 40 drivers, compared to the industry average ratio of 1:8. Drivers are also encouraged to participate in problem finding and problem solving in areas such as maintenance, customer service, and planning [73].

Key elements in effective high-performance team working include:

  • clearly defined tasks and objectives
  • effective team leadership
  • good balance of team roles and match to individual behavioral style
  • effective conflict resolution mechanisms within the group
  • continuing liaison with external organization.

Teams typically go through four stages of development, popularly known as “forming, storming, norming, and performing [74].” That is, they are put together and then go through a phase of resolving internal differences and conflicts around leadership, objectives, and so on. Emerging from this process is a commitment to shared values and norms governing the way the team will work, and it is only after this stage that teams can move on to effective performance of their task.

Central to team performance is the makeup of the team itself, with good matching between the role requirements of the group and the behavioral preferences of the individuals involved. Belbin’s work has been influential here in providing an approach to team role matching, as discussed in Research Note 3.7. He classifies people into a number of preferred role types – for example, “the plant” (someone who is a source of new ideas), “the resource investigator,” “the shaper,” and the “completer/finisher” (see Research Note 3.7). Research has shown that the most effective teams are those with diversity in background, ability, and behavioral style. In one noted experiment, highly talented but similar people in “Apollo’ teams consistently performed less than the mixed, average groups [20].

With increased emphasis on cross-boundary and dispersed team activity, a series of new challenges are emerging. In the extreme case, a product development team might begin work in London, pass on to their US counterparts later in the day who in turn pass on to their far Eastern colleagues – effectively allowing a 24-hour nonstop development activity. This makes for higher productivity potential – but only if the issues around managing dispersed and virtual teams can be resolved. Similarly, the concept of sharing knowledge across boundaries depends on enabling structures and mechanisms [75].

Many people who have attempted to use groups for problem solving find out that using groups is not always easy, pleasurable, or effective. Table 3.5 summarizes some of the positive and negative aspects of using groups for innovation.

TABLE 3.5 Potential Assets and Liabilities of Using a Group

Source: S. Isaksen and J. Tidd, Meeting the innovation challenge. 2006, Chichester: John Wiley & Sons, Ltd.

Potential Assets of Using a Group Potential Liabilities of Using a Group
Greater availability of knowledge and information Social pressure toward uniform thought limits contributions and increases conformity
More opportunities for cross-fertilization; increasing the likelihood of building and improving upon ideas of others Group think: groups converge on options, which seem to have greatest agreement, regardless of quality
Wider range of experiences and perspectives upon which to draw Dominant individuals influence and exhibit an unequal amount of impact upon outcomes
Participation and involvement in problem solving increases understanding, acceptance, commitment, and ownership of outcomes Individuals are less accountable in groups allowing groups to make riskier decisions
More opportunities for group development; increasing cohesion, communication, and companionship Conflicting individual biases may cause unproductive levels of competition; leading to “winners” and “losers”

Research Note 3.8 examines how twelve different team practices contribute to innovation performance for radical projects.

Our own work on high-performance teams suggests, consistent with previous research, a number of characteristics that promote effective teamwork [7]:

  • A clear, common, and elevating goal. Having a clear and elevating goal means having understanding, mutual agreement, and identification with respect to the primary task a group faces. Active teamwork toward common goals happens when members of a group share a common vision of the desired future state. Creative teams have clear and common goals. The goals were not only clear and compelling but also open and challenging. Less creative teams have conflicting agendas, different missions, and no agreement on the end result. The tasks for the least creative teams were tightly constrained, considered routine, and were overly structured.
  • Results-driven structure. Individuals within high-performing teams feel productive when their efforts take place with a minimum of grief. Open communication, clear coordination of tasks, clear roles and accountabilities, monitoring performance, providing feedback, fact-based judgement, efficiency, and strong impartial management combine to create a results-driven structure.
  • Competent team members. Competent teams are composed of capable and conscientious members. Members must possess essential skills and abilities, a strong desire to contribute, be capable of collaborating effectively, and have a sense of responsible idealism. They must have knowledge in the domain surrounding the task (or some other domain that may be relevant) as well as with the process of working together. Creative teams recognize the diverse strengths and talents and use them accordingly.
  • Unified commitment. Having a shared commitment relates to the way the individual members of the group respond. Effective teams have an organizational unity: members display mutual support, dedication and faithfulness to the shared purpose and vision, and a productive degree of self-sacrifice to reach organizational goals. Team members enjoy contributing and celebrating their accomplishments.
  • Collaborative climate. Productive teamwork does not just happen. It requires a climate that supports cooperation and collaboration. This kind of situation is characterized by mutual trust, in which everyone feels comfortable discussing ideas, offering suggestions, and willing to consider multiple approaches.
  • Standards of excellence. Effective teams establish clear standards of excellence. They embrace individual commitment, motivation, self-esteem, individual performance, and constant improvement. Members of teams develop a clear and explicit understanding of the norms upon which they will rely.
  • External support and recognition. Team members need resources, rewards, recognition, popularity, and social success. Being liked and admired as individuals and respected for belonging and contributing to a team is often helpful in maintaining the high level of personal energy required for sustained performance. With the increasing use of cross-functional and inter-departmental teams within larger complex organizations, teams must be able to obtain approval and encouragement.
  • Principled leadership. Leadership is important for teamwork. Whether it is a formally appointed leader or leadership of the emergent kind, the people who exert influence and encourage the accomplishment of important things usually follow some basic principles. Leaders provide clear guidance, support and encouragement, and keep everyone working together and moving forward. Leaders also work to obtain support and resources from within and outside the group.
  • Appropriate use of the team. Teamwork is encouraged when the tasks and situations really call for that kind of activity. Sometimes the team itself must set clear boundaries on when and why it should be deployed. One of the easiest ways to destroy a productive team is to overuse it or use it when it is not appropriate to do so.
  • Participation in decision making. One of the best ways to encourage teamwork is to engage the members of the team in the process of identifying the challenges and opportunities for improvement, generating ideas, and transforming ideas into action. Participation in the process of problem solving and decision making actually builds teamwork and improves the likelihood of acceptance and implementation.
  • Team spirit. Effective teams know-how to have a good time, release tension, and relax their need for control. The focus at times is on developing friendship, engaging in tasks for mutual pleasure, and recreation. This internal team climate extends beyond the need for a collaborative climate. Creative teams have the ability to work together without major conflicts in personalities. There is a high degree of respect for the contributions of others. Less creative teams are characterized by animosity, jealousy, and political posturing.
  • Embracing appropriate change. Teams often face the challenges of organizing and defining tasks. In order for teams to remain productive, they must learn how to make necessary changes to procedures. When there is a fundamental change in how the team must operate, different values and preferences may need to be accommodated.

There are also many challenges to the effective management of teams. We have all seen teams that have “gone wrong.” Research Note 3.9 shows how the dominance of a single cognitive approach to team innovation can be counterproductive. As a team develops, there are certain aspects or guidelines that might be helpful to keep them on track. Hackman has identified a number of themes relevant to those who design, lead, and facilitate teams. In examining a variety of organizational work groups, he found some seemingly small factors that if overlooked in the management of teams will have large implications that tend to destroy the capability of a team to function. These small and often hidden “tripwires” to major problems include [76]:

  • Group versus team One of the mistakes that is often made when managing teams is to call the group a team, but to actually treat it as nothing more than a loose collection of individuals. This is similar to making it a team “because I said so.” It is important to be very clear about the underlying goal and reward structure. People are often asked to perform tasks as a team, but then have all evaluation of performance based on an individual level. This situation sends conflicting messages and may negatively affect the team performance.
  • Ends versus means Managing the source of authority for groups is a delicate balance. Just how much authority can you assign to the team to work out its own issues and challenges? Those who convene teams often “over manage” them by specifying the results as well as how the team should obtain them. The end, direction, or outer limit constraints ought to be specified, but the means to get there ought to be within the authority and responsibility of the group.
  • Structured freedom It is a major mistake to assemble a group of people and merely tell them in general and unclear terms what needs to be accomplished and then let them work out their own details. At times, the belief is that if teams are to be creative, they ought not be given any structure. It turns out that most groups would find a little structure quite enabling, if it were the right kind. Teams generally need a well-defined task. They need to be composed of an appropriately small number to be manageable but large enough to be diverse. They need clear limits as to the team’s authority and responsibility, and they need sufficient freedom to take initiative and make good use of their diversity. It’s about striking the right kind of balance between structure, authority, and boundaries – and freedom, autonomy, and initiative.
  • Support structures and systems Often challenging team objectives are set, but the organization fails to provide adequate support in order to make the objectives a reality. In general, high-performing teams need a reward system that recognizes and reinforces excellent team performance. They also need access to good quality and adequate information, as well as training in team-relevant tools and skills. Good team performance is also dependent on having an adequate level of material and financial resources to get the job done. Calling a group a team does not mean that they will automatically obtain all the support needed to accomplish the task.
  • Assumed competence Technical skills, domain-relevant expertise, and experience and abilities often explain why someone has been included within a group, but these are rarely the only competencies individuals need for effective team performance. Members will undoubtedly require explicit coaching on skills needed to work well in a team.

Research Note 3.10 reveals some of the challenges of multicultural development teams.

3.7 Creative Climate

“Microsoft’s only factory asset is the human imagination.”

– Bill Gates

Many great inventions came about as the result of lucky accidental discoveries – for example, Velcro fasteners, the adhesive behind “Post-it” notes or the principle of float glass manufacturing. But as Louis Pasteur observed, “chance favours the prepared mind” and we can usefully deploy our understanding of the creative process to help set up the conditions within which such “accidents” can take place.

Two important features of creativity are relevant in doing this. The first is to recognize that creativity is an attribute that everyone possesses – but their preferred style of expressing it varies widely [77]. Some people are comfortable with ideas that challenge the whole way in which the universe works, while others prefer smaller increments of change – ideas about how to improve the jobs they do or their working environment in small incremental steps. (This explains in part why so many “creative” people – artists, composers, scientists – are also seen as “difficult” or living outside the conventions of acceptable behavior.) This has major implications for how we manage creativity within the organization: innovation, as we have seen, involves bringing something new into widespread use, not just inventing it. While the initial flash may require a significant creative leap, much of the rest of the process will involve hundreds of small problem-finding and problem-solving exercises – each of which needs creative input. And though the former may need the skills or inspiration of a particular individual, the latter require the input of many different people over a sustained period of time. Developing the light bulb or the Post-it note or any successful innovation is actually the story of the combined creative endeavours of many individuals. Case Study 3.8 discusses the approach of Google.

Organizational structures are the visible artefacts of what can be termed an innovative culture – one in which innovation can thrive. Culture is a complex concept, but it basically equates to the pattern of shared values, beliefs, and agreed norms that shape the behavior – in other words, it is “the way we do things round here” in any organization. Schein suggests that culture can be understood in terms of three linked levels, with the deepest and most inaccessible being what each individual believes about the world – the “taken for granted” assumptions. These shape individual actions and the collective and socially negotiated version of these behaviors defines the dominant set of norms and values for the group. Finally, behavior in line with these norms creates a set of artefacts – structures, processes, symbols, etc. – which reinforce the pattern [78].

Given this model, it is clear that management cannot directly change culture, but it can intervene at the level of artefacts – by changing structures or processes – and by providing models and reinforcing preferred styles of behavior. Such “culture change” actions are now widely tried in the context of change programs toward total quality management and other models of organization which require more participative culture.

A number of writers have looked at the conditions under which creativity thrives or is suppressed [23]. Kanter [8] provides a list of environmental factors that contribute to stifling innovation; these include:

  • dominance of restrictive vertical relationships
  • poor lateral communications
  • limited tools and resources
  • top-down dictates
  • formal, restricted vehicles for change
  • reinforcement of a culture of inferiority (i.e., innovation always has to come from outside to be any good)
  • unfocused innovative activity
  • unsupported accounting practices.

The effect of these is to create and reinforce the behavioral norms that inhibit creativity and lead to a culture lacking in innovation. It follows from this that developing an innovative climate is not a simple matter since it consists of a complex web of behaviors and artefacts. And changing this culture is not likely to happen quickly or as a result of single initiatives (such as restructuring or mass training in a new technique).

Instead, building a creative climate involves systematic development of organizational structures, communication policies and procedures, reward and recognition systems, training policy, accounting and measurement systems, and deployment of strategy. Mechanisms for doing so in various different kinds of organizations and in different national cultures are described by a number of authors including Cook and Rickards [24].

Of particular relevance in this area is the design of effective reward systems. Many organizations have reward systems that reflect the performance of repeated tasks rather than encourage the development of new ideas. Progress is associated with “doing things by the book” rather than challenging and changing things. By contrast, innovative organizations look for ways to reward creative behavior and to encourage its emergence. Examples of reward systems include the establishment of a “dual ladder” that enables technologically innovative staff to progress within the organization without the necessity to move across management posts [79].

Research Note 3.11 examines the relative contributions of leadership and culture on new product development success. View 3.1 provides insights on organizational innovation from a leading innovation consultancy.

Climate versus Culture

Climate is defined as the recurring patterns of behavior, attitudes, and feelings that characterize life in the organization. These are the objectively shared perceptions that characterize life within a defined work unit or in the larger organization. Climate is distinct from culture in that it is more observable at a surface level within the organization and more amenable to change and improvement efforts. Culture refers to the deeper and more enduring values, norms, and beliefs within the organization.

The two terms, culture and climate, have been used interchangeably by many writers, researchers, and practitioners. We have found that the following distinctions may help those who are concerned with effecting change and transformation in organizations:

  • Different levels of analysis. Culture is a rather broad and inclusive concept. Climate can be seen as falling under the more general concept of culture. If your aim is to understand culture, then you need to look at the entire organization as a unit of analysis. If your focus is on climate, then you can use individuals and their shared perceptions of groups, divisions, or other levels of analysis. Climate is recursive or scalable.
  • Different disciplines are involved. Culture is within the domain of anthropology and climate falls within the domain of social psychology. The fact that the concepts come from different disciplines means that different methods and tools are used to study them.
  • Normative versus descriptive. Cultural dimensions have remained relatively descriptive, meaning that one set of values or hidden assumptions were neither better nor worse than another. This is because there is no universally held notion or definition of the best society. Climate is often more normative in that we are more often looking for environments that are not just different, but better for certain things. For example, we can examine different kinds of climates and compare the results against other measures or outcomes such as innovation, motivation, growth, and so on.
  • More easily observable and influenced. Climate is distinct from culture in that it is more observable at a surface level within the organization and more amenable to change and improvement efforts.

What is needed is a common sense set of levers for change that leaders can exert direct and deliberate influence over.

Climate and culture are different: traditionally, studies of organizational culture are more qualitative, whereas research on organizational climate is more quantitative, but a multidimensional approach helps to integrate the benefits of each perspective.

Research indicates that organizations exhibit larger differences in practices than values, for example, the levels of uncertainty avoidance.

Table 3.6 summarizes some research of how climate influences innovation. Many dimensions of climate have been shown to influence innovation and entrepreneurship, but here we discuss six of the most critical factors.

TABLE 3.6 Climate Factors Influencing Innovation

Source: Derived from Isaksen S. and J. Tidd, Meeting the innovation challenge. 2006, Chichester: John Wiley & Sons, Ltd.

Climate Factor Most Innovative (Score) Least Innovative (Score) Difference
Trust and openness 253  88 165
Challenge and involvement 260 100 160
Support and space for ideas 218  70 148
Conflict and debate 231  83 148
Risk-taking 210  65 145
Freedom 202 110  92

Trust and Openness

The trust and openness dimension refers to the emotional safety in relationships. These relationships are considered safe when people are seen as both competent and sharing a common set of values. When there is a strong level of trust, everyone in the organization dares to put forward ideas and opinions. Initiatives can be taken without fear of reprisals and ridicule in case of failure. The communication is open and straightforward. Where trust is missing, count on high expenses for mistakes that may result. People are also afraid of being exploited and robbed of their good ideas.

When trust and openness are too low, you may see people hoarding resources (i.e., information, software, materials, etc.). There may also be a lack of feedback on new ideas for fear of having concepts stolen. Management may not distribute the resources fairly among individuals or departments. However, trust can bind and blind. If trust and openness are too high, relationships may be so strong that time and resources at work are often spent on personal issues. It may also lead to a lack of questioning each other that, in turn, may lead to mistakes or less productive outcomes. Cliques may form where there are isolated “pockets” of high trust. In this case, it may help to develop forums for interdepartmental and intergroup exchange of information and ideas. Research Note 3.12 identifies some factors that influence knowledge sharing in teams.

Trust is partly the result of individuals’ own personality and experience, but can also be influenced by the organizational climate. For example, we know that the nature of rewards can affect some components of trust. Individual competitive rewards tend to reduce information sharing and raise suspicions of others’ motives, whereas group or cooperative rewards are more likely to promote information sharing and reduce suspicions of motives. Trust is also associated with employees having some degree of role autonomy. Role autonomy is the amount of discretion that employees have in interpreting and executing their jobs. Defining roles too narrowly constrains the decision-making latitude. Role autonomy can also be influenced by the degree to which organizational socialization encourages employees to internalize collective goals and values, for example, a so-called “clan” culture focuses on developing shared values, beliefs, and goals among members of an organization so that appropriate behaviors are reinforced and rewarded, rather than specifying task-related behaviors or outcomes. This approach is most appropriate when tasks are difficult to anticipate or codify, and it is difficult to assess the performance. Individual characteristics will also influence role autonomy, including the level of experience, competence, and power accumulated over time working for the organization.

Challenge and Involvement

Challenge and involvement are the degree to which people are involved in daily operations, long-term goals, and visions. High levels of challenge and involvement mean that people are intrinsically motivated and committed to making contributions to the success of the organization. The climate has a dynamic, electric, and inspiring quality. People find joy and meaningfulness in their work, and therefore they invest much energy. In the opposite situation, people are not engaged, and feelings of alienation and indifference are present. The common sentiment and attitude is apathy and lack of interest in work and interaction is both dull and listless.

If challenge and involvement are too low, you may see that people are apathetic about their work, are not generally interested in professional development, or are frustrated about the future of the organization. One of the ways to improve the situation might be to get people involved in interpreting the vision, mission, purpose, and goals of the organization for themselves and their work teams.

On the other hand, if the challenge and involvement are too high, you may observe that people are showing signs of “burn out,” they are unable to meet project goals and objectives, or they spend “too many” long hours at work. One of the reasons for this is that the work goals are too much of a stretch. A way to improve the situation is to examine and clarify strategic priorities.

Leaders who focus on work challenge and expertise rather than formal authority result in climates that are more likely to be assessed by members as being innovative and high performance. Studies suggest that output controls such as specific goals, recognition, and rewards have a positive association with innovation. A balance must be maintained between creating a climate in which subordinates feel supported and empowered, with the need to provide goals and influence the direction and agenda. Leaders who provide feedback that is high on developmental potential, for example, provide useful information for subordinates to improve, learn, and develop and results in higher levels of creativity.

Intellectual stimulation is one of the most underdeveloped components of leadership and includes behaviors that increase others’ awareness of and interest in problems and develops their propensity and ability to tackle problems in new ways. Intellectual stimulation by leaders can have a profound effect on organizational performance under conditions of perceived uncertainty and is also associated with commitment to an organization. Case Study 3.9 discusses how an organization strengthened its low levels of challenge and involvement.

Support and Space for Ideas

Idea time is the amount of time people can (and do) use for elaborating new ideas. In the high idea-time situation, possibilities exist to discuss and test impulses and fresh suggestions that are not planned or included in the task assignment and people tend to use these possibilities. When idea time is low, every minute is booked and specified. The time pressure makes thinking outside the instructions and planned routines impossible. Research confirms that individuals under time pressure are significantly less likely to be creative.

If there is insufficient time and space for generating new ideas, you may observe that people are only concerned with their current projects and tasks. They may exhibit an unhealthy level of stress. People see professional development and training as hindrances to their ability to complete daily tasks and projects. You may also see that management avoids new ideas because they will take time away from the completion of day-to-day projects and schedules. Conversely, if there is too much time and space for new ideas, you may observe that people are showing signs of boredom, that decisions are made through a slow, almost bureaucratic, process because there are too many ideas to evaluate, or the management of new ideas becomes such a task that short-term tasks and projects are not adequately completed.

This suggests that there is an optimum amount of time and space to promote creativity and innovation. The concept of organizational slack was developed to identify the difference between resources currently needed and the total resources available to an organization. When there is little environmental uncertainty or need for change, and the focus is simply on productivity; too much organizational slack represents a static inefficiency. However, when innovation and change are needed, slack can act as a dynamic shock absorber and allows scope for experimentation. This process tends to be self-reinforcing due to positive feedback between the environment and organization.

When successful, an organization generates more slack, which provides greater resource (people, time, money) for longer term, significant innovation; however, when an organization is less successful, or suffers a fall in performance, it tends to search for immediate and specific problems and their solution, which tends to reduce the slack necessary for longer-term innovation and growth.

The research confirms that an appropriate level of organizational slack is associated with superior performance over the longer term. For high-performance organizations, the relationship between organizational slack and performance is an inverted “U” shape or curvi-linear: too little slack, for example being too lean or too focused, does not allow sufficient time or resource for innovation, but too much slack provides little incentive or direction to innovation. However, for low-performance organizations any slack is simply absorbed, and therefore simply represents an inefficiency rather than an opportunity for innovation and growth. Managers too often view time as a constraint or measure of outcomes, rather than as a variable to influence, which can both trigger and facilitate innovation and change. By providing some, but limited, time and resources, individuals and groups can minimize the rigidity that comes from work overload and the laxness that stems from too much slack.

The message for senior management is as much about leading through creating space and support within the organization as it is about direct involvement.

Conflict and Debate

A conflict in an organization refers to the presence of personal, interpersonal, or emotional tensions. Although conflict is a negative dimension, all organizations have some level of personal tension.

Conflicts can occur over tasks, processes, or relationships. Task conflicts focus on disagreements about the goals and content of work, the “what?” needs to be done and “why?” Process conflicts are around “how?” to achieve a task, means, and methods. Relationship or affective conflicts are more emotional and are characterized by hostility and anger. In general, some tasks and process conflicts are constructive, helping to avoid groupthink and to consider more diverse opinions and alternative strategies. However, task and process conflicts have only a positive effect on performance in a climate of openness and collaborative communication; otherwise, it can degenerate into relationship conflict or avoidance. Relationship conflict is generally energy sapping and destructive, as emotional disagreements create anxiety and hostility.

If the level of conflict is too high, groups and individuals dislike or hate each other and the climate can be characterized by “warfare.” Plots and traps are common in the life of the organization. There is gossip and backbiting going on. You may observe gossiping at water coolers (including character assassination), information hoarding, open aggression, or people lying or exaggerating about their real needs. In these cases, you may need to take initiative to engender cooperation among key individuals or departments.

If conflict is too low, you may see that individuals lack any outward signs of motivation or are not interested in their tasks. Meetings are more about “tell” and not consensus. Deadlines may not be met. It could be that too many ineffective people are entrenched in an overly hierarchical structure. It may be necessary to restructure and identify leaders who possess the kinds of skills that are desired by the organization.

So the goal is not necessarily to minimize conflict and maximize consensus, but to maintain a level of constructive conflict consistent with the need for diversity and a range of different preferences and styles of creative problem solving. Group members with similar creative preferences and problem-solving styles are likely to be more harmonious but much less effective than those with mixed preferences and styles. So if the level of conflict is constructive, people behave in a more matured manner. They have psychological insight and exercise more control over their impulses and emotions.

Debate focuses on issues and ideas (as opposed to conflict that focuses on people and their relationships). Debate involves the productive use and respect for diversity of perspectives and points of view. Debate involves encounters, exchanges, or clashes among viewpoints, ideas, and differing experiences and knowledge. Many voices are heard, and people are keen on putting forward their ideas. Where debates are missing, people follow authoritarian patterns without questioning. When the score on the debate dimension is too low, you may see constant moaning and complaining about the way things are, rather than how the individual can improve the situation. Rather than open debate, you may see more infrequent and quiet one-on-one conversation in hallways.

However, if there is too much debate, you are likely to see more talk than implementation. Individuals will speak with little or no regard for the impact of their statements. The focus on conversation and debate becomes more on individualistic goals than on cooperative and consensus-based action. One reason for this may be too much diversity or people holding very different value systems. In these situations, it may be helpful to hold structured or facilitated discussions and affirm commonly held values. Research Note 3.13 explores how different types of diversity can encourage or hinder innovation. Case Study 3.10 shows how a medical devices company promoted greater cross-functional working and user insights to help develop new products.

Risk-taking

Tolerance of uncertainty and ambiguity constitute risk-taking. In a high risk-taking climate, bold new initiatives can be taken even when the outcomes are unknown. People feel that they can “take a gamble” on some of their ideas. People will often “go out on a limb” and be first to put an idea forward.

In a risk-avoiding climate, there is a cautious, hesitant mentality. People try to be on the “safe side.” They setup committees and they cover themselves in many ways before making a decision. If risk-taking is too low, employees offer few new ideas or few ideas that are well outside of what is considered safe or ordinary. In risk-avoiding organizations people complain about boring, low-energy jobs and are frustrated by a long, tedious process used to get ideas to action.

Conversely, if there is too much risk-taking, you will see that people are confused. There are too many ideas floating around, but few are sanctioned. People are frustrated because nothing is getting done. There are many loners doing their own thing in the organization and no evidence of teamwork. These conditions can be caused by individuals not feeling they need a consensus or buy-in from others on their team in their department or organization. A remedy might include some team building and improving the reward system to encourage cooperation rather than individualism or competition.

Research on new product and service development has identified a broad range of strategies for dealing with risk. Both individual characteristics and organizational climate influence perceptions of risk and propensities to avoid, accept or seek risks. Formal techniques such as failure mode and effects analysis (FMEA), potential problem analysis (PPA) and fault tree analysis (FTA) have a role, but the broader signals and support from the organizational climate are more important than the specific tools or methods used.

Freedom

Freedom is described as the independence in behavior exerted by the people in the organization. In a climate with much freedom, people are given autonomy to define much of their own work. They are able to exercise discretion in their day-to-day activities. They take the initiative to acquire and share information and make plans and decisions about their work. In a climate with little freedom, people work within strict guidelines and roles. They carry out their work in prescribed ways with a little room to redefine their tasks.

If there is not enough freedom, people demonstrate very little initiative for suggesting new and better ways of doing things. They may spend a great deal of time and energy obtaining permission and gaining support (internally and externally) or perform all their work “by the book” and focus too much on the exact requirements of what they are told to do. One of the many reasons could be that the leadership practices are very authoritarian or overly bureaucratic. It might be helpful to initiate a leadership improvement initiative including training, 360° feedback with coaching, skills of managing up, etc.

If there is too much freedom, you may observe people going off in their own independent directions. They have an unbalanced concern weighted toward themselves rather than the work group or organization. People may do things that demonstrate little or no concern for important policies/procedures, performing tasks differently and independently redefining how they are done each time. Research Note 3.14 compares how more formal organizational routines and everyday practices contribute to innovation.

3.8 Boundary-Spanning

A recurring theme in this book is the extent to which innovation has become an open process involving richer networks across and between organizations. This highlights a long-established characteristic of successful innovating organizations – an orientation that is essentially open to new stimuli from outside [80]. Such organizations have approaches that pick up and communicate signals through the organization.

Developing a sense of external orientation – for example, toward key customers or sources of major technological developments – and ensuring that this pervades organizational thinking at all levels are of considerable importance in building an innovative organization. For example, by developing a widespread awareness of customers – both internal and external – quality and innovation can be significantly improved. This approach contrasts sharply with the traditional model in which there was no provision for feedback or mutual adjustment [81]. Of course, not all industries have the same degree of customer involvement – and in many the dominant focus is more on technology. This does not mean that the customer focus is an irrelevant concept: the issue here is one of building relationships that enable clear and regular communication, providing inputs for problem solving and shared innovation [82].

But the idea of extending involvement goes far beyond customers and end users. Open innovation requires building such relationships with an extended cast of characters, including suppliers, collaborators, competitors, regulators, and multiple other players [83].

All of the earlier discussions presume that the organization in question is a single entity, a group of people are organized in a particular fashion toward some form of collective purpose. But increasingly we are seeing the individual enterprise becoming linked with others in some form of collective – a supply chain, an industrial cluster, a cooperative learning club or a product development consortium. Studies exploring this aspect of inter-firm behavior include learning in shared product development projects [25], in complex product system configuration [84], in technology fusion [85], in strategic alliances [86], in regional small-firm clusters [87], in sector consortia [88], in “topic networks [89],” and in industry associations [90].

Consider some examples:

  • Studies of “collective efficiency” have explored the phenomenon of clustering in a number of different contexts [91]. From this work, it is clear that the model is not just confined to parts of Italy, Spain, and Germany, but diffused around the world – and it is extremely effective under certain conditions. For example, one town (Sialkot) in Pakistan plays a dominant role in the world market for specialist surgical instruments made of stainless steel. From a core group of 300 small firms, supported by 1500 even smaller suppliers, 90% of production (1996) was exported and took a 20% share of the world market, second only to Germany. In another case, the Sinos valley in Brazil contains around 500 small-firm manufacturers of specialized, high-quality leather shoes. Between 1970 and 1990, their share of the world market rose from 0.3% to 12.5% and in 2006 they exported some 70% of the total production. In each case, the gains are seen as resulting from close interdependence in a cooperative network.
  • Similarly, there has been much discussion about the merits of technological collaboration, especially in the context of complex product systems development [92]. Innovation networks of this kind offer significant advantages in terms of assembling different knowledge sets and reducing the time and costs of development – but are again often difficult to implement [93].
  • Much has been written on the importance of developing cooperative rather than adversarial supply chain relationships [94]. But it is becoming increasingly clear that the kind of “collective efficiency” described earlier can operate in this context and contribute not only to improved process efficiency (higher quality, faster speed of response, etc.) but also to shared product development. The case of Toyota is a good illustration of this – the firm has continued to stay ahead despite increasing catch-up efforts on the part of Western firms and the consolidation of the industry. Much of this competitive edge can be attributed to its ability to create and maintain a high-performance knowledge-sharing network [95].
  • Networking represents a powerful solution to the resource problem – no longer is it necessary to have all the resources for innovation (particularly those involving specialized knowledge) under one roof provided you know where to obtain them and how to link up with them. The emergence of powerful information and communication technologies has further facilitated the move toward “open innovation” and “virtual organizations” that are increasingly a feature of the business landscape [96]. But experience and research suggest that without careful management of these – and the availability of a shared commitment to deal with them – the chances are that such networks will fail to perform effectively [26].
  • Studies of learning behavior in supply chains suggest considerable potential – one of the most notable examples being the case of the kyoryokukai (supplier associations) of Japanese manufacturers in the second half of the twentieth century [97]. Imai, in describing the product development in Japanese manufacturers, observes: “[Japanese firms exhibit] an almost fanatical devotion toward learning – both within organizational membership and with outside members of the inter-organizational network [98].” Lamming [27] identifies such learning as a key feature of lean supply, linking it with innovation in supply relationships. Marsh and Shaw describe collaborative learning experiences in the wine industry including elements of supply chain learning (SCL), while the AFFA study reports on other experiences in the agricultural and food sector in Australia [99]. In the case studies of SCL in the Dutch and the UK food industries, the construction sector and aerospace provided further examples of different modes of SCL organization [100]. Humphrey et al describe SCL emergence in a developing country context (India) [101].

However, as given in Chapter 7, obtaining the benefits of networking is not an automatic process – it requires considerable efforts in the area of coordination. Effective networks have what systems theorists call “emergent properties” – that is, the whole is greater than the sum of the parts. But the risk is high that simply throwing together a group of enterprises will lead to suboptimal performance with the whole being considerably less than the sum of the parts due to friction, poor communications, persistent conflicts over resources, or objectives, and so on.

A research on inter-organizational networking suggests that a number of core processes need managing in a network, effectively treating it as if it were a particular form of organization [102]. For example, a network with no clear routes for resolving conflicts is likely to be less effective than the one which has a clear and accepted set of norms – a “network culture” – which can handle the inevitable conflicts that emerge.

Building and operating networks can be facilitated by a variety of enabling inputs, for example, the use of advanced information and communication technologies may have a marked impact on the effectiveness with which information processing takes place. In particular, the research highlights a number of enabling elements that help to build and sustain effective networks, which include:

  • Key individuals – creating and sustaining networks depend on putting energy into their formation and operation. Studies of successful networks identify the role of key figures as champions and sponsors, providing leadership and direction, particularly in the tasks of bringing people together and giving a system-level sense of purpose [103]. Increasingly, the role of “network broker” is being played by individuals and agencies concerned with helping create networks on a regional or sectoral basis.
  • Facilitation – another important element is providing support to the process of networking but not necessarily acting as members of the network. Several studies indicate that such a neutral and catalytic role can help, particularly in the setup stages and in dealing with core operating processes like conflict resolution.
  • Key organizational roles – mirroring these individual roles are those played by key organizations – for example, a regional development agency organizing a cluster or a business association bringing together a sectoral network. Gereffi and others talk about the concept of network governance and identify the important roles played by key institutions such as major customers in buyer-driven supply chains [104]. Equally their absence can often limit the effectiveness of a network, for example, in research on supply-chain learning, the absence of a key governor limited the extent to which inter-organizational innovation could take place [105].

Case Study 3.11 shows how the company 3M has consistently developed and reinforced innovative behaviors and outcomes through a range of organizational practices and policies.

Summary

  • The organization of innovation is much more than a set of processes, tools, and techniques, and the successful practice of innovation demands the interaction and integration of three different levels of management: individual, collective, and climate.
  • At the personal or individual level, the key is to match the leadership styles with the task requirement and type of teams. General leadership requirements for innovative projects include expertise and experience relevant to the project, articulating a vision and inspirational communication, intellectual stimulation, and quality of LMX.
  • At the collective or social level, there is no universal best practice, but successful teams require clear, common, and elevating goals; unified commitment; cross-functional expertise; collaborative climate; external support; and recognition and participation in decision making.
  • At the context or climate level, there is no “best innovation culture,” but innovation is promoted or hindered by a number of factors, including trust and openness, challenge and involvement, support and space for ideas, conflict and debate, risk-taking, and freedom.

Chapter 3: Concept Check Questions

  1. Which of the following characteristics of innovation leadership may have a negative influence on innovation?
A. Possess high technical skills
B. Leader–member exchange (LMX)
C. Reward innovative behavior
D. Provide feedback and evaluation
Correct or Incorrect?

 

  1. Which of the following is NOT necessarily a feature of high‐performing teams?
A. Balance of team roles matched to individual behavioral style
B. Conflict resolution mechanisms within the group
C. Complete autonomy of decision‐making
D. Continuing liaison with the host organization
Correct or Incorrect?

 

  1. Cross-functional teams have many advantages, but they are not suitable for all types of project. In which of the following cases are they most effective?
A. To minimize the need for information processing
B. To maximize resource use and efficiency
C. For team building and reduced conflict
D. For novel, high‐risk and high‐value projects
Correct or Incorrect?

 

  1. Which of the following is NOT necessarily supportive of a creative culture and climate?
A. Training and resources
B. Trust and openness
C. Challenge and Involvement
D. Conflict and debate
Correct or Incorrect?

 

  1. Organizational culture is important for innovation, but the concept of organizational climate is preferable because:
A. Culture is not shared.
B. Culture can be directly observed.
C. Climate is more important than culture for innovation.
D. Climate is less difficult to measure and change.
Correct or Incorrect?

 

Further Reading

The field of organizational behavior is widely discussed and there are some good basic texts, such as D. Buchanan and A. Huczynski, Organizational Behaviour (8th edition, Pearson, 2013), which provides an excellent synthesis of the main issues, with a good balance of managerial and more critical social science approaches. Specific issues surrounding the development of innovative organizations are well treated by R. Leifer et al., Radical Innovation (Harvard Business School Press, 2000), and R. Kanter World Class (Simon & Schuster, 1996). We address the relationships between leadership, innovation, and organizational renewal more fully in our book Meeting the Innovation Challenge: Leadership for Transformation and Growth, by Scott Isaksen and Joe Tidd (John Wiley & Sons, Ltd., 2006).

Many books and articles look at specific aspects, for example: the development of creative climates, Lynda Gratton, Hot Spots: Why some companies buzz with energy and innovation, and others don’t (Prentice Hall, 2007); on Innovative Teams (20-Minute Manager Series), Harvard Business Review (2015); or continuous improvement, John Bessant’s High-Involvement Innovation (John Wiley & Sons, Ltd., 2003). R. Katz, The Human Side of Managing Technological Innovation (Oxford University Press, 2003) is an excellent collection of readings, and A.H. Van de Ven, D. Polley, H.L. Angle, and M.S. Poole, The Innovation Journey (Oxford University Press, 2008) provides a comprehensive review of a seminal study in the field, and includes a discussion of individual, group and organizational issues. The theme of creativity and the skills associated with it at individual, group and organizational level is discussed in detail in John Bessant and Ina Goller’s book “Creativity for innovation management,” (Routledge, 2017).

There are numerous books on innovative leaders and companies, mostly about Steve Jobs and Apple, but most lack balance and any critical insights. Good case studies of innovative organizations include E. Gundling, The 3M Way to Innovation: Balancing people and profit (Kodansha International, 2000), Corning and the Craft of Innovation by M. Graham and A. T. Shuldiner (Oxford University Press, 2001), Eric Schmidt How Google Works (John Murray, 2014), and J. Song and K. Lee The Samsung Way: Transformational Management Strategies from the World Leader in Innovation and Design (McGraw-Hill, 2014).

The “beyond boundaries” issue of networking is covered by several writers, most following the popular notion of “open innovation.” The notion was most popularized by Henry Chesbrough in Open Innovation (Harvard Business School Press, 2003), and has since spawned many similar discussions, but for more serious and critical reviews of the evidence and research can be found in Open Innovation: Researching a New Paradigm (edited by H. Chesbrough, W. Vanhaverbeke, and J. West, Oxford University Press, 2008), and Open Innovation Management, Research and Practice (edited by Joe Tidd, Imperial College Press, 2014).

Case Study

The Philips Lighting case highlights the organizational challenges of changing the degree and direction of innovation strategy.

References

  1. 1. Kirkpatrick, D., The second coming of Apple. Fortune, 1998. 138, 90.
  2. 2. Pfeffer, J., The human equation: Building profits by putting people first. 1998, Boston, MA: Harvard Business School Press.
  3. 3. Caulkin, S., Performance through people. 2001, London: Chartered Institute of Personnel and Development.
  4. 4. Huselid, M., The impact of human resource management practices on turnover, productivity and corporate financial performance. Academy of Management Journal, 1995. 38, 647–56.
  5. 5. Hesselbein, F., M. Goldsmith and R. Beckhard, eds., Organization of the future. 1997, San Francisco: Jossey Bass/The Drucker Foundation.
  6. 6. Champy, J. and N. Nohria, eds., Fast forward. 1996, Boston, MA: Harvard Business School Press.
  7. 7. Isaksen, S. and J. Tidd, Meeting the innovation challenge: Leadership for transformation and growth. 2006, Chichester: John Wiley & Sons, Ltd.
  8. 8. Kanter, R. ed., Innovation: Breakthrough thinking at 3M. 1997, DuPont, GE, New York: Pfizer and Rubbermaid, Harper Business.
  9. 9. Pinchot, G., Intrapreneuring in action – Why you don’t have to leave a corporation to become an entrepreneur. 1999, New York: Berrett-Koehler.
  10. 10. Financial Times, Patience of jobs pays off. Financial Times, 1995, p. 7.
  11. 11. Moody, F., Sing the body electronic. 1995, London: Hodder & Stoughton.
  12. 12. Cooper, R., Winning at new products. 3rd ed., 2001, London: Kogan Page.
  13. 13. Bowman, E.H. and C.E. Helfat, Does corporate strategy matter? Strategic Management Journal, 2001. 22, 1–23.
  14. 14. Clark, K.E. and M.B. Clark, Measures of leadership. 1990, Greensboro, NC: The Center for Creative Leadership; K.E. Clark, M.B. Clark, and D.P. Campbell, Impact of leadership. 1992, Greensboro, NC: The Center for Creative Leadership.
  15. 15. Mann, R.D., A review of the relationships between personality and performance in small groups. Psychological Bulletin, 1959. 56, 241–70.
  16. 16. Rothwell, R., Successful industrial innovation: Critical success factors for the 1990s. R&D Management, 1992. 22(3), 221–39.
  17. 17. Allen, T., Managing the flow of technology. 1977, Boston, MA: MIT Press.
  18. 18. Thamhain, H. and D. Wilemon, Building high performing engineering project teams. IEEE Transactions on Engineering Management, 1987. EM-34(3), 130–7.
  19. 19. Bixby, K., Superteams. 1987, London: Fontana
  20. 20. Belbin, M., Management teams – Why they succeed or fail. 2004, London: Butterworth-Heinemann.
  21. 21. Lillrank, P. and N. Kano, Continuous improvement; quality control circles in Japanese industry. 1990, Ann Arbor: University of Michigan Press.
  22. 22. Bessant, J., High Involvement innovation. 2003, Chichester: John Wiley & Sons, Ltd.
  23. 23. Leonard, D. and W. Swap, When sparks fly: Igniting creativity in groups. 1999, Boston, MA: Harvard Business School Press; Amabile, T., How to kill creativity. 1998, Harvard Business Review, September/October, 77–87.
  24. 24. Cook, P., Best practice creativity, 1999, Aldershot: Gower; Rickards, T., Creativity and problem solving at work. 1997, Aldershot: Gower.
  25. 25. Bozdogan, K., Architectural innovation in product development through early supplier integration. R&D Management, 1998. 28(3), 163–73; Oliver, N. and M. Blakeborough, Innovation networks: The view from the inside. In Grieve Smith, J. and J. Michie, eds., Innovation, cooperation and growth. 1998, Oxford: Oxford University Press.
  26. 26. Best, M., The new competitive advantage. 2001, Oxford: Oxford University Press.
  27. 27. Lamming, R., Beyond partnership. 1993, London: Prentice-Hall.
  28. 28. Womack, J., D. Jones, and D. Roos, The machine that changed the world. 1991, New York: Rawson Associates.
  29. 29. Christenson, C., The innovator’s dilemma. 1997, Boston, MA: Harvard Business School Press.
  30. 30. Tripsas, M. and G. Gavetti, Capabilities, cognition and inertia: Evidence from digital imaging. Strategic Management Journal, 2000. 21, 1147–61.
  31. 31. Leonard-Barton, D., Wellsprings of knowledge: Building and sustaining the sources of innovation. 1995, Boston, MA: Harvard Business School Press.
  32. 32. Connelly, M.S., J.A. Gilbert, S.J. Zaccaro, et al., Exploring the relationship of leader skills and knowledge to leader performance. The Leadership Quarterly, 2000, 11, 65–86; Zaccaro, S.J., J.A. Gilbert, K.K. Thor, and M.D. Mumford, et al., Assessment of leadership problem-solving capabilities. The Leadership Quarterly, 2000. 11, 37–64.
  33. 33. Farris, G.F., The effect of individual role on performance in creative groups. R&D Management, 1972. 3, 23–8; Ehrhart, M.G. and K.J. Klein, Predicting followers’ preferences for charismatic leadership: The influence of follower values and personality. The Leadership Quarterly, 2001. 12, 153–80.
  34. 34. Denti, L. and S. Hemlin, Modelling the link between LMX and individual innovation in R&D. International Journal of Innovation Management, 2016. 20(3), 1650038; Scott, S.G. and R.A. Bruce, Determinants of innovative behavior: A path model of individual innovation in the workplace. Academy of Management Journal, 1994. 37(3), 580–607.
  35. 35. Amabile, T.M., E.A. Schatzel, G.B. Moneta, and S.J. Kramer, Leader behaviors and the work environment for creativity: Perceived leader support. The Leadership Quarterly, 2004. 15(1), 5–32.
  36. 36. Rafferty, A.E. and M.A. Griffin, Dimensions of transformational leadership: Conceptual and empirical extensions. The Leadership Quarterly, 2004. 15(3), 329–54.
  37. 37. Mumford, M.D., S.J. Zaccaro, F.D. Harding, et al., Leadership skills for a changing world: Solving complex social problems. The Leadership Quarterly, 2000. 11, 11–35.
  38. 38. Pinto, J. and D. Slevin, Critical success factors in R&D projects. Research-Technology Management, 1989. 32, 12–18; Podsakoff, P.M., S.B. Mackenzie, J.B. Paine, and D.G. Bachrach, Organizational citizenship behaviors: A critical review of the theoretical and empirical literature and suggestions for future research. Journal of Management, 2000, 26(3), 513–63.
  39. 39. West, M.A., C.S. Borrill, J.F. Dawson, et al., Leadership clarity and team innovation in health care. The Leadership Quarterly, 2003. 14(4–5), 393–410.
  40. 40. Andrews, F.M. and G.F. Farris, Supervisory practices and innovation in scientific teams. Personnel Psychology, 1967. 20, 497–515; Barnowe, J.T., Leadership performance outcomes in research organizations. Organizational Behavior and Human Performance, 1975, 14, 264–80; Elkins, T. and R.T. Keller, Leadership in research and development organizations: A literature review and conceptual framework. The Leadership Quarterly, 2003. 14, 587–606.
  41. 41. Keller, R.T., Transformational leadership and performance of research and development project groups. Journal of Management, 1992. 18, 489–501.
  42. 42. Berson, Y. and J.D. Linton, An examination of the relationships between leadership style, quality, and employee satisfaction in R&D versus administrative environments. R&D Management, 2005. 35(1), 51–60.
  43. 43. Thompson, J., Organizations in action. 1967, New York: McGraw-Hill.
  44. 44. Perrow, C., A framework for the comparative analysis of organizations. American Sociological Review, 1967. 32, 194–208.
  45. 45. Burns, T. and G. Stalker, The management of innovation. 1961, London: Tavistock.
  46. 46. Kanter, R., The Change Masters, London: Unwin.
  47. 47. Semler, R., Maverick, Century Books. 1993, London; Kaplinsky, R., F. den Hertog, and B. Coriat, Europe’s next step. 1995, London: Frank Cass.
  48. 48. Miles, R. and C. Snow, Organizational strategy, structure and process. 1978, New York: McGraw-Hill; Lawrence, P. and P. Dyer, Renewing American Industry. 1983, New York: Free Press.
  49. 49. Lawrence, P. and J. Lorsch, Organization and environment. 1967, Boston, MA: Harvard University Press.
  50. 50. Stalk, G. and T. Hout, Competing against time: How time-based competition is reshaping global markets. 1990, New York: Free Press.
  51. 51. Woodward, J., Industrial organization: Theory and practice. 1965, Oxford: Oxford University Press.
  52. 52. Child, J., Organisations. 1980, London: Harper & Row.
  53. 53. Mintzberg, H., The structuring of organizations. 1979, Englewood Cliffs, NJ: Prentice-Hall.
  54. 54. Adler, P., The learning bureaucracy: NUMMI. In B. Staw and L. Cummings, eds., Research in organizational behavior. 1992, Greenwich, CT: JAI Press.
  55. 55. Nayak, P. and J. Ketteringham, Breakthroughs: How leadership and drive create commercial innovations that sweep the world, 1986, London: Mercury; Kidder, T., The soul of a new machine. 1981, Harmondsworth: Penguin.
  56. 56. Clark, K. and T. Fujimoto, Product development performance. 1992, Boston, MA: Harvard Business School Press.
  57. 57. Blackler, F., Knowledge, knowledge work and organizations. Organization Studies, 1995. 16(6), 1021–46; Sapsed, J. et al., Teamworking and knowledge management: A review of converging themes. International Journal of Management Reviews, 2002, 4(1).
  58. 58. Duarte, D. and N. Tennant Snyder, Mastering virtual teams. 1999, San Francisco: Jossey Bass.
  59. 59. Kaplinsky, R., Easternization: The spread of Japanese management techniques to developing countries. London: Frank Cass; Schroeder, D. and A. Robinson, America’s most successful export to Japan – continuous improvement programs. Sloan Management Review, 1991. 32(3), 67–81.
  60. 60. Figuereido, P., Technological learning and competitive performance. 2001, Cheltenham: Edward Elgar.
  61. 61. Deming, W., Out of the crisis. 1986, Boston, MA: MIT Press; Crosby, P., Quality is free. 1997, New York: McGraw-Hill; Dertouzos M., R. Lester, and L. Thurow, Made in America: Regaining the productive edge. 1989, Boston, MA: MIT Press; Garvin, D., Managing quality. 1988, New York: Free Press.
  62. 62. Womack, J. and D. Jones, Lean thinking. 1997, New York: Simon & Schuster.
  63. 63. Schonberger, R., Japanese manufacturing techniques: Nine hidden lessons in simplicity. 1982, New York: Free Press.
  64. 64. Shingo, S., A revolution in manufacturing: The SMED system. 1983, Boston, MA: Productivity Press; Suzaki, K., The new manufacturing challenge. 1988, New York: Free Press; Ishikure, K., Achieving Japanese productivity and quality levels at a US plant. Long Range Planning, 1988. 21(5), 10–17; Wickens, P., The road to Nissan: Flexibility, quality, teamwork. 1987, London: Macmillan.
  65. 65. Caffyn, S., Continuous improvement in the new product development process, Centre for Research in Innovation Management. 1998, Brighton: University of Brighton; Lamming, R., Beyond partnership. 1993, London: Prentice-Hall; Owen, M. and J. Morgan, Statistical process control in the office. 2000, Kenilworth: Greenfield Publishing.
  66. 66. Boer, H., A. Berger, R. Chapman, and F. Gertsen, CI changes: From suggestion box to the learning organisation. 1999, Aldershot: Ashgate.
  67. 67. Peters, T., Thriving on chaos, 1988, New York: Free Press.
  68. 68. Forrester, R. and A. Drexler, A model for team-based organization performance. Academy of Management Executive, 1999. 13(3), 36–49; Conway, S. and R. Forrester, Innovation and teamworking: Combining perspectives through a focus on team boundaries. 1999, Birmingham: University of Aston Business School.
  69. 69. Holti, R., J. Neumann, and H. Standing, Change everything at once: The Tavistock Institute’s guide to developing teamwork in manufacturing. 1995, London: Management Books 2000.
  70. 70. Tranfield, D. et al., Teamworked organizational engineering: Getting the most out of teamworking. Management Decision, 1998. 36(6), 378–84.
  71. 71. Bouncken, R., A. Brem, and S. Kraus, Multi-cultural teams as a source for creativity and innovation: The role of cultural diversity on team performance, International Journal of Innovation Management, 2016. 20(1), 1650012; Jassawalla, A. and H. Sashittal, Building collaborative cross-functional new product teams. Academy of Management Executive, 1999. 13(3), 50–3.
  72. 72. DTI, UK Software Purchasing Survey. 1996, London: Department of Trade and Industry.
  73. 73. Van Beusekom, M., Participation pays! Cases of successful companies with employee participation. 1996, The Hague: Netherlands Participation Institute.
  74. 74. Tuckman, B. and N. Jensen, Stages of small group development revisited. Group and Organizational Studies, 1977. 2, 419–27.
  75. 75. Smith, P. and E. Blanck, From experience: Leading dispersed teams. Journal of Product Innovation Management, 2002. 19, 294–304.
  76. 76. Hackman J. R. ed., Groups that work (and those that don’t): Creating conditions for effective teamwork. 1990, San Francisco: Jossey Bass.
  77. 77. Kirton, M., Adaptors and innovators. 1989, London: Routledge.
  78. 78. Stock, R.M. and N.L. Schnarr, Exploring the product innovation outcomes of corporate culture and executive leadership, International Journal of Innovation, 2016. 20(1), 1650009; Schein, E., Coming to a new awareness of organizational culture. Sloan Management Review, 1984. Winter, 3–16.
  79. 79. Badawy, M., Developing managerial skills in engineers and scientists, 1997, New York: John Wiley & Sons, Inc.
  80. 80. Carter, C. and B. Williams, Industry and technical progress. 1957, Oxford: Oxford University Press.
  81. 81. Oakland, J., Total quality management. 1989, London: Pitman.
  82. 82. Schonberger, R., Building a chain of customers. 1990, New York: Free Press.
  83. 83. Chesbrough, H., Open innovation: The new imperative for creating and profiting from technology. 2003, Boston, MA: Harvard Business School Press.
  84. 84. Miller, R., Innovation in complex systems industries: The case of flight simulation. Industrial and Corporate Change, 1995. 4(2).
  85. 85. Tidd, J., Complexity, networks and learning: Integrative themes for research on innovation management. International Journal of Innovation Management, 1997. 1(1), 1–22.
  86. 86. Simonin, B., Ambiguity and the process of knowledge transfer in strategic alliances. Strategic Management Journal, 1999. 20, 595–623; Szulanski, G., Exploring internal stickiness: Impediments to the transfer of best practice within the firm. Strategic Management Journal, 1996. 17, 5–9; Hamel, G., Y. Doz, and C. Prahalad, Collaborate with your competitors – and win. Harvard Business Review, 1989. 67(2), 133–9.
  87. 87. Schmitz, H., Collective efficiency and increasing returns. Cambridge Journal of Economics, 1998. 23(4), 465–83; Nadvi, K. and H. Schmitz, Industrial clusters in less developed countries: Review of Experiences and Research Agenda. 1994, Brighton: Institute of Development Studies; Keeble, D. and F. Williamson, eds., High technology clusters, networking and collective learning in Europe. 2000, Aldershot: Ashgate.
  88. 88. DTI/CBI, Industry in Partnership. 2000, Department of Trade and Industry/Confederation of British Industry, London.
  89. 89. Bessant, J., Networking as a mechanism for technology transfer: The case of continuous improvement. In Kaplinsky, R., F. den Hertog, and B. Coriat, eds., Europe’s next step. 1995, London: Frank Cass.
  90. 90. Semlinger, K., Public support for firm networking in Baden-Wurttemburg. In Kaplinsky, R., F. den Hertog, and B. Coriat, eds., Europe’s next step. 1995, London: Frank Cass; Keeble, D., Institutional thickness in the Cambridge region. Regional Studies, 1994. 33(4), 319–32.
  91. 91. Piore, M. and C. Sabel, The second industrial divide. 1982, New York: Basic Books; Nadvi, K., The cutting edge: Collective efficiency and international competitiveness in Pakistan. 1997, Institute of Development Studies, University of Sussex.
  92. 92. Dodgson, M., Technological collaboration in industry. 1993, London: Routledge; Hobday, M., Complex systems vs mass production industries: A new innovation research agenda. 1996, Brighton: Complex Product Systems Research Centre; Marceau, J., Clusters, chains and complexes: Three approaches to innovation with a public policy perspective. In R. Rothwell and M. Dodgson, eds., The handbook of industrial innovation. 1994, Aldershot: Edward Elgar.
  93. 93. Oliver, N. and M. Blakeborough, Innovation networks: The view from the inside. In Grieve, J., J. Smith, and J. Michie, eds., Innovation, cooperation and growth. 1998, Oxford: Oxford University Press; Tidd, J., Complexity, networks and learning: Integrative themes for research on innovation management. International Journal of Innovation Management, 1997, 1(1), 1–22.
  94. 94. Hines, P., Value stream management: The development of lean supply chains, 1999, London: Financial Times Management. Brem, A. and J. Tidd, Perspectives on supplier innovation. 2012, London: Imperial College Press.
  95. 95. Dyer, J. and K. Nobeoka, Creating and managing a high-performance knowledge-sharing network: The Toyota case. Strategic Management Journal, 2000. 21(3), 345–67.
  96. 96. Dell, M., Direct from Dell. 1999, New York: HarperCollins.
  97. 97. Hines, P., Creating world class suppliers: Unlocking mutual competitive advantage. 1994, London: Pitman; Cusumano, M., The Japanese automobile industry: Technology and Management at Nissan and Toyota. 1985, Boston, MA: Harvard University Press.
  98. 98. Imai, K., Kaizen. 1987, New York: Random House.
  99. 99. AFFA, Chains of Success, Department of Agriculture, Fisheries and Forestry – Australia (AFFA), 1998, Canberra; Marsh, I. and B. Shaw, Australia’s wine industry: Collaboration and learning as causes of competitive success. In Working Paper. 2000, Melbourne: Australian Graduate School of Management.
  100. 100. AFFA, Supply chain learning: Chain reversal and shared learning for global competitiveness, 2000, Department of Agriculture, Fisheries and Forestry – Australia (AFFA), Canberra; Fearne, A. and D. Hughes, Success factors in the fresh produce supply chain: Insights from the UK. Supply Management, 1999. 4(3); Dent, R., Collective knowledge development, 2001, Swindon: Organisational Learning and Learning Networks: An Integrated Framework, Economic and Social Research Council.
  101. 101. Humphrey, J., R. Kaplinsky, and P. Saraph, Corporate restructuring: Crompton Greaves and the challenge of globalization. 1998, New Delhi: Sage Publications.
  102. 102. Bessant, J. and G. Tsekouras, Developing learning networks. AI and Society, 2001. 15(2), 82–98.
  103. 103. Barnes, J. and M. Morris, Improving operational competitiveness through firm-level clustering: A case study of the KwaZulu-Natal Benchmarking Club, School of Development Studies. 1999, Durban, South Africa: University of Natal.
  104. 104. Kaplinsky, R., M. Morris, and J. Readman, The globalization of product markets and immiserising growth: Lessons from the South African furniture industry. World Development, 2003. 30(7), 1159–78; Gereffi, G., The organisation of buyer-driven global commodity chains: How US retailers shape overseas production networks. In Gereffi, G. and P. Korzeniewicz, eds., Commodity Chains and Global Capitalism. 1994, London: Praeger.
  105. 105. Bessant, J., R. Kaplinsky, and R. Lamming, Putting supply chain learning into practice. International Journal of Operations and Production Management, 2003. 23(2), 167–84.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.224.56.216