Search results

In a relationship both sides are important for the development. This is one reason why purchasing has always been as central as marketing in the empirical studies in IMP. The manner in which the features of business networks affect the role of purchasing and the roles of the suppliers and supply management is here in focus. The existence and importance of business relationships have normative consequences for purchasing that are very distinct and break clearly with some of the traditional normative recommendations for purchasing. The authors believe that ‘buying organisations increasingly need to develop interactive interfaces with their suppliers. One reason is that collaborative innovation and therefore the development role of PSM (purchasing and supply management) is becoming more important’. The conclusion is clear: If the buying organisations want to get more out of the suppliers than the supply of a standard product at a certain price, they have to engage in a more extensive interaction and develop a broader and closer business relationship that must be properly managed. That implies giving up some autonomy and accepting dependence on suppliers as developmental partners.

This chapter describes the change efforts and action research projects at a Dutch multinational which, over a period of 25 years, produced in one of its businesses a zigzag path toward collaborative leadership dynamics at the horizontal and vertical interfaces. The chapter also identifies the learning mechanisms that helped achieve this transformation. Changing the patterns at the vertical interfaces proved to be a most tricky, complex, and confusing operation. The data show that organizations need hierarchical interfaces between levels, but are hindered by the hierarchical leadership dynamics at these interfaces. The data furthermore show that competitive performance requires more than redesigning horizontal interfaces. A business can only respond with speed and flexibility to threats and opportunities in the external environment when the leadership dynamics at agility-critical vertical interfaces are also changed.

This paper deals with the organizing of interactive product development. Developing products in interaction between firms may provide benefits in terms of specialization, increased innovation, and possibilities to perform development activities in parallel. However, the differentiation of product development among a number of firms also implies that various dependencies need to be dealt with across firm boundaries. How dependencies may be dealt with across firms is related to how product development is organized. The purpose of the paper is to explore dependencies and how interactive product development may be organized with regard to these dependencies.

The analytical framework is based on the industrial network approach, and deals with the development of products in terms of adaptation and combination of heterogeneous resources. There are dependencies between resources, that is, they are embedded, implying that no resource can be developed in isolation. The characteristics of and dependencies related to four main categories of resources (products, production facilities, business units and business relationships) provide a basis for analyzing the organizing of interactive product development.

Three in-depth case studies are used to explore the organizing of interactive product development with regard to dependencies. The first two cases are based on the development of the electrical system and the seats for Volvo’s large car platform (P2), performed in interaction with Delphi and Lear respectively. The third case is based on the interaction between Scania and Dayco/DFC Tech for the development of various pipes and hoses for a new truck model.

The analysis is focused on what different dependencies the firms considered and dealt with, and how product development was organized with regard to these dependencies. It is concluded that there is a complex and dynamic pattern of dependencies that reaches far beyond the developed product as well as beyond individual business units. To deal with these dependencies, development may be organized in teams where several business units are represented. This enables interaction between different business units’ resource collections, which is important for resource adaptation as well as for innovation. The delimiting and relating functions of the team boundary are elaborated upon and it is argued that also teams may be regarded as actors. It is also concluded that a modular product structure may entail a modular organization with regard to the teams, though, interaction between business units and teams is needed. A strong connection between the technical structure and the organizational structure is identified and it is concluded that policies regarding the technical structure (e.g. concerning “carry-over”) cannot be separated from the management of the organizational structure (e.g. the supplier structure). The organizing of product development is in itself a complex and dynamic task that needs to be subject to interaction between business units.

In every industry there are resources. Some are moving, others more fixed; some are technical, others social. People working with the resources, for example, as buyers or sellers, or users or producers, may not make much notice of them. A product sells. A facility functions. The business relationship in which we make our money has “always” been there. However, some times this picture of order is disturbed. A user having purchased a product for decades may “suddenly” say to the producer that s/he does not appreciate the product. And a producer having received an order of a product that s/he thought was well known, may find it impossible to sell it. Such disturbances may be ignored. Or they can be used as a platform for development. In this study we investigate the latter option, theoretically and through real world data. Concerning theory we draw on the industrial network approach. We see industrial actors as part of (industrial) networks. In their activities actors use and produce resources. Moreover, the actors interact − bilaterally and multilaterally. This leads to development of resources and networks. Through “thick” descriptions of two cases we illustrate and try to understand the interactive character of resource development and how actors do business on features of resources. The cases are about a certain type of resource, a product − goat milk. The main message to industrial actors is that they should pay attention to that products can be co-created. Successful co-creation of products, moreover, may require development also of business relationships and their connections (“networking”).

This paper presents the safety case for the consideration of cross-cultural factors in aviation by focusing on cultural interfaces, those situations where members of one culture encounter people or artifacts from other cultures. Global aviation is strongly influenced by the USA and Western Europe as the largest manufacturers and largest customers; hence almost all cultural interfaces are weighted in favor of the dominant users. The challenge for safety is not to ignore or eliminate these interfaces but to manage the potential threats they pose. To move forward, there is a role for those inside and outside the dominant model.

The role of management control has not received sufficient attention in the literature on value creation so far. Therefore, this paper aims to investigate the role of control in value creation in industrial networks. More specifically, the aim is to examine the management and control of interfaces between key resources within and between firms, in the networks surrounding firms, when they attempt to create value. All the firms that take part in a value-creation process have both formal and informal control systems: these firms have budgets, specific routines, reward systems, and sanctioned “ways to behave.” The paper relates the Industrial Marketing and Purchasing (IMP) group's research on interaction, relationships, and networks with control literature, and presents a framework for controlling resource interfaces in a network setting. Two in-depth cases illustrate the role of control in value creation. The first case covers the development of a low-weight newspaper grade that Holmen and its paper mill Hallsta initiated. The second case examines the attempt to develop and commercialize a new, energy efficient pulping technology.

The chapter pays specific attention to the organizing and reorganizing process of the embedding of new technology. The aim is to increase the understanding of how a focal technology is incrementally aligned into a customer’s different business settings. Embedding becomes subject to intense organizing efforts. It becomes a struggle with activating different features of the focal technology by forging and modifying the resource interfaces between the focal technology and customer resources.

The organizing efforts are about seeking, in an explorative mood, for resource interfaces between the focal technology and the customer resources. This organizing process enables the identification of new adaptation opportunities for technology embedding processes, whereby the focal technology obtains certain feature and values.

A systematically developed knowledge of resource interfaces is a key for activating different features of the focal technology and thereby facilitating its embedding into the customer’s various business settings. This is described in a single case study in the chapter. This case and the analysis show how a supplier and a customer struggle with developing resource interface knowledge to activate the different features of the focal technology, thereby facilitating its embedding process. The first part of the chapter establishes a theoretical framework, followed in the second part by the case study and analysis. The concluding discussion emphasizes the importance of understanding and managing various interfaces as part of the organizing processes.

A fundamental issue driving much of the current research is the design of the interface between humans and ROVs. Autonomous robots are sufficiently different from most computer systems as to require new research and design principles (Adams & Skubic, 2005; Kiesler & Hinds, 2004). Previous work on coordination between humans and automated agents has revealed both benefits and costs of automation for system performance (Parasuraman & Riley, 1997). Automation is clearly essential for the operation of many complex human–machine systems. But in some circumstances automation can also lead to novel problems for operators. Automation can increase workload and training requirements, impair situation awareness and, when particular events co-occur in combination with poorly designed interfaces, lead to accidents (e.g., Degani, 2004; Parasuraman & Riley, 1997).

In this paper we extend established concepts of product and process architectures to propose a concept of organization architecture that defines the essential features of the system design of an organization needed to achieve an effective strategic alignment of an organization with its competitive and/or cooperative environment. Adopting a work process view of organization, we draw on concepts of product and process architectures to elaborate fundamental elements in the design of an organization architecture. We suggest that organization architectures may be designed to support four basic types of change in organization resources, capabilities, and coordination, which we characterize as convergence, reconfiguration, absorptive integration, and architectural transformation. We also suggest the kinds of strategic flexibilities that an organization must have to create and implement each type of organization architecture. We identify four basic types of strategic environments and consider the kinds of changes in resources, capabilities, and coordination that need to be designed into an organization's architecture to maintain effective strategic alignment with its type of environment. We then propose a typology that identifies four basic ways in which organizational architectures may be effectively aligned with strategic environments. Extending the reasoning underlying the proposed alignments of organization architectures with strategic environments, we propose a strategic principle of architectural isomorphism, which holds that maintaining effective strategic alignment of an organization with its environment requires achieving isomorphism across a firm's product, process, and organization architectures. We conclude by considering some implications of the analyses undertaken here for competence theory, general and mid-range strategy theory, and organization theory.

B2B business is very much about relationships, and solution-oriented business may further underline this. But relations could look very different and the interface between buyer and seller could also vary a lot and be more or less fit for purpose.

In this chapter, we point at possibilities to be more methodical about the ways in which the interfaces are organized. In longer-term business, this seems to be a core factor in order for the two or more parties involved how to get the best value of their relation. We discuss interaction patterns and what seem to be the most important factors influencing the success or failure.