A customer-facing front end, organized by customer or market, is joined to a product or capability back end, with a linking process between them.

What it is

A front-back organization splits the firm into two halves that face different ways. The front end is organized around customers, by segment, industry, or account, and owns the relationship with them. The back end is organized around products or capabilities and makes what the front sells. Linking processes, such as planning, pricing, and team assembly, join the two. On this explorer's reading (a judgment in the profile), each unit keeps one line of authority, and the design effort goes into the link, not dual reporting.

The front-back organization joins a customer front to a product back

Select a unit or a letter to read it; the line between the two halves stands for the linking processes that join them.

Reports toAdjust to each other directlyMMutual adjustmentOStandardization of outputsJimmy and colleagues (2011) found the back grouped by function, which this explorer reads as two bases side by side

Top managementFront and backTopmanagementCustomersegment unitAccount unitProduct unitProduct unitBy customerBy productOM
Top managementFront and backTopSegmentAccountProductProductBy customerBy productOM
Select a unit or a letter to read it. M, mutual adjustment: People coordinate their own work by informal communication with each other. O, standardization of outputs: The results of the work are specified, such as targets or product dimensions, and the method is left to the unit.Top management. Layer: Top management. Reports to no one. Reconciles front and back. Galbraith (2002b) says the design needs a strong, active top management; on this explorer's reading, the disputes the linking processes cannot settle climb to it.Customer segment unit. Layer: Front and back. Reports to Top management. By customer. A front unit organized around one customer segment; it owns the relationship with those customers and sells what the back end makes.Account unit. Layer: Front and back. Reports to Top management. By customer. A front unit too, built around a customer account; the front end may also be cut by industry. Front and back units are run as profit or cost centers under their own heads, on this explorer's reading.Product unit. Layer: Front and back. Reports to Top management. By product. A back unit organized around a product or capability; it makes what the front sells and concentrates the product and technology specialists.Product unit. Layer: Front and back. Reports to Top management. By product. A second back unit. The larger a solution's scale and scope and the more interdependent its parts, the more units and interfaces must be coordinated (Galbraith 2002b).O, standardization of outputs. The results of the work are specified, such as targets or product dimensions, and the method is left to the unit.M, mutual adjustment. People coordinate their own work by informal communication with each other.
The structure in words
  1. Top management
    • Top management, reports to no one. Reconciles front and back. Galbraith (2002b) says the design needs a strong, active top management; on this explorer's reading, the disputes the linking processes cannot settle climb to it.
  2. Front and back
    • Customer segment unit, reports to Top management, grouped by customer. A front unit organized around one customer segment; it owns the relationship with those customers and sells what the back end makes.
    • Account unit, reports to Top management, grouped by customer. A front unit too, built around a customer account; the front end may also be cut by industry. Front and back units are run as profit or cost centers under their own heads, on this explorer's reading.
    • Product unit, reports to Top management, grouped by product. A back unit organized around a product or capability; it makes what the front sells and concentrates the product and technology specialists.
    • Product unit, reports to Top management, grouped by product. A second back unit. The larger a solution's scale and scope and the more interdependent its parts, the more units and interfaces must be coordinated (Galbraith 2002b).
  • Account unit and Product unit: adjust to each other directly, coordinated by standardization of outputs, coordinated by mutual adjustment.
  • Jimmy and colleagues (2011) found the back grouped by function, which this explorer reads as two bases side by side

Front units are grouped by customer and own the relationship, and back units are grouped by product and make what the front sells. Linking processes join the two halves: planning and pricing standardize outputs, and cross-business teams drawn from both adjust to each other directly. On this explorer's reading, each unit keeps one boss.

Source: Galbraith 2002a; Galbraith 2002b, a design essay with illustrative company examples and no systematic data; Jimmy and colleagues 2011, seven interviews in five IT outsourcing vendors, reported as mini-cases in a conference paper.

One profile cell is disputed. On grouping, Galbraith (2002) holds customer and product bases at the same level. Jimmy, Seddon, and Reynolds (2011), seven interviews in five IT outsourcing vendors, reported as mini-cases, found customer grouping at the front and function grouping at the back, which they say conforms to the model of Galbraith, Downey, and Kates (2002); our single-boss test reads it as units on different bases. The lateral mechanisms, as theory, run from teams to integrating roles. In the vendors, cross-business teams joined front and back, and account managers had less formal authority over resources than their owners; matrix reporting in two firms was usually applied only to managers, and in a third, staff on several projects had project bosses besides their unit boss.

As theory, coordination is by standardized outputs through planning and pricing, plus mutual adjustment in cross-business teams. The rest is our judgment: specialization medium to high; formalization medium; centralization mixed; a moderate middle line; decision rights at limited vertical decentralization (Mintzberg's Type C), with front and back run as profit or cost centers; high differentiation with heavy integration; exchange between market and bureaucracy, through internal prices; and a selective boundary, open toward customers at the front.

Where the front-back organization sits on the eleven dimensions

The filled segments are the form's levels, and an outlined segment is the other view's level on a contested row; select a row for its reason and sources.

Select a dimension to read why the form sits there, and on what basis.Basis of grouping: Two or more at once. Basis: Theory. A customer-facing front end and a product or capability back end are held at the same level of the firm, the case the dimension's level 5 names. Sources: Galbraith 2002a; Jimmy and colleagues 2011. View 2: Function or process and client or market segment. In five firms studied, front-end staff were grouped by the types of customer served and back-end staff by the functions the company offers, so different people sit in units on different bases; by the single-boss test the hybrid cell applies, that is levels 1 and 3, not level 5. Sources: Jimmy and colleagues 2011.Specialization: Medium to high. Basis: Judgment. The back end concentrates product and technology specialists and the front end customer specialists; judgment for the band. Sources: Galbraith 2002a.Standardization and formalization: Medium. Basis: Judgment. The linking processes between front and back are designed and written, while much of the work inside each is left to the units; judgment. Sources: Galbraith 2002a.Centralization: Mixed. Basis: Judgment. Kates and Galbraith treat the split of decisions between center and units as a design challenge in its own right; the band is judgment. Sources: Kates and Galbraith 2007.Layers and span of control: Moderate. Basis: Judgment. Front and back units each keep a single line; judgment. Sources: Galbraith 2002a.Decision rights and the locus of authority: Limited vertical decentralization. Basis: Judgment. Front and back units are run as profit or cost centers under their own heads, Type C with the units as market-based; judgment. Sources: Kates and Galbraith 2007; Mintzberg 1980.Prime coordinating mechanism: Mutual adjustment and standardization of outputs. Basis: Theory. Planning and pricing processes between front and back and standardized outputs (level 4, where the dimension note puts planning and control systems), with mutual adjustment in the cross-business teams that link them (level 1). Sources: Galbraith 2002a; Galbraith 2005; Jimmy and colleagues 2011.Lateral mechanisms: Task forces and teams to integrating roles and managerial linking roles. Basis: Theory. Linking processes and integrating roles join front and back. In five IT outsourcing vendors, cross-business account teams drawn from front and back joined them, and account managers held less formal authority over resources than the resource managers who owned them, which the authors distinguish from a matrix; two of the firms also used matrix reporting, applied only to managerial positions. Sources: Galbraith 2002a; Jimmy and colleagues 2011.Differentiation against integration: High differentiation, heavy integration. Basis: Judgment. Customer-facing and product-facing units differ sharply in orientation and need designed linking processes to hold them together; judgment. Sources: Galbraith 2002a; Lawrence and Lorsch 1967a.Mode of exchange and control: Market and bureaucracy. Basis: Judgment. Internal pricing between front and back puts a market-like exchange inside the hierarchy; judgment. Sources: Galbraith 2002a; Williamson 1975.Boundary permeability: Selective. Basis: Judgment. The external boundary with customers is opened by the front, while the back stays inward; judgment. Sources: Galbraith 2005; Ashkenas and colleagues 1995.

Three levels rest on theory: two bases at once, standardized outputs with mutual adjustment, and lateral mechanisms from teams to integrating roles. The other eight are judgment. Grouping is contested: Jimmy and colleagues (2011) found the back end grouped by function, which this explorer's single-boss test reads as units on different bases.

Source: Galbraith 2002a; Jimmy and colleagues 2011, seven interviews in five IT outsourcing vendors, reported as mini-cases in a conference paper; Kates and Galbraith 2007; Mintzberg 1980, a synthesis of earlier research, offering propositions without a new test; Galbraith 2005; Lawrence and Lorsch 1967a, a multi-firm comparative field study; Williamson 1975; Ashkenas and colleagues 1995.

Where it came from

Jay Galbraith set the form out between the 1990s and 2007, in Designing Organizations (2002), "Organizing to deliver solutions" (2002), the customer-centric book (2005), and, with Amy Kates, Designing Your Organization (2007). It answered a firm whose customers wanted integrated solutions bought across several products, while each product still needed scale and depth: add customer-centric units in front of the product units and invest in the processes that join them (Galbraith 2002b).

The schools of organization design and the forms' origins, 1900 to now

Each row is a school's era; each square under them is a form at its first year. Select a row or a square to read it; on a form's page, its own square and span are marked, with the schools that treat it.

1900192019401960198020002020Bureaucracy and its criticsClassical administrationHuman relations and System 4Transaction cost economicsCarnegie schoolSocio-technical systemsLabor-managed firmModularity and mirroringStrategy and structureContingency theoryFrench bureaucratic schoolJapanese-firm literatureScandinavian and DutchConfiguration theoryInformation processingLabor processStrategic choiceGerman codeterminationOrganizational economicsInstitutional theoryPopulation ecologyResource dependenceBusiness groupsScandinavian institutionalSocietal effectNetwork perspectiveComputational designNew-forms debateAlgorithmic managementForms by first yearFront-back organization, 1990s to 2007Now

The forms by first year

1900192019401960198020002020Front-back organization, 1990s to 2007Now

Schools that treat this form: Modularity and the mirroring hypothesis; Information processing.

Select a school's row or a form's square to read it.Select a form's square to read it; open a school below.Bureaucracy and its critics1900s to 1950s, revived from the 1990sWhat it claimsWeber held that rational-legal authority exercised through an office hierarchy, written rules, trained officials, and promotion by qualification is technically superior in precision, speed, and reliability. Critics studied its unintended consequences, Michels's iron law sharpest.What it has shownMerton (1940) argued, with no test, that rules can turn from means into ends; case studies followed. The Aston group concluded that the type's dimensions vary independently, and Wagner's meta-analysis (2021) found that many of their interrelationships have weakened.Who disputes itHuman relations and System 4 sets the costs of impersonal rules to motivation and cooperation against the technical superiority Weber stresses.Bureaucracy and its critics in The Schools of Organization DesignClassical administration1910s to 1940s, and in German to the 1970sWhat it claimsThere are general principles of administration, among them division of work, unity of command, a scalar chain of authority, and a limited span of control, and a structure built to them will be efficient in most settings. Taylor added that planners should set work methods.What it has shownThe school offered reasoning and experience, not tests. Woodward (1965) found that the spans and levels of the more successful firms in her sample differed by production system, and Simon (1946) showed that the principles come in pairs that point in opposite directions.Who disputes itStructural contingency theory found that the structure of successful firms varies with technology and environment, where classical writers treat their principles as general.Classical administration in The Schools of Organization DesignHuman relations and System 41920s to 1960sWhat it claimsOutput depends on the social relations of work, the norms of informal groups, and the style of supervision as much as on formal design. Likert's System 4, overlapping work groups joined by linking-pin managers under participative management, outperforms authoritative systems.What it has shownThe founding evidence is the Hawthorne studies, which later reanalyses dispute (Carey 1967; Levitt and List 2011). Likert's support came largely from his own institute's surveys. Wagner (1994) found participation's effects on performance and satisfaction significant but small.Who disputes itLabor process and critical theory reads human relations as a technique of managerial control rather than a change in the distribution of power.Human relations and System 4 in The Schools of Organization DesignTransaction cost economics and the M-form hypothesis1937, then the 1970s to the presentWhat it claimsFirms exist, and are organized as they are, to economize on transaction costs. Hierarchy replaces the market when assets are specific, uncertainty is high, and exchange is frequent, and the multidivisional form should outperform the functional form in large, diversified firms.What it has shownArmour and Teece (1978) found, in United States petroleum firms from 1955 to 1973, a positive relationship between the multidivisional form and profitability while the form was spreading, but not once an equilibrium in organizational form was reached.Who disputes itThe network perspective on organizations: Granovetter argued that the theory undersocializes economic action, which is embedded in networks of personal relations that also produce trust and order.Transaction cost economics and the M-form hypothesis in The Schools of Organization DesignThe Carnegie school and the attention-based view1940s to the presentWhat it claimsPeople in organizations are boundedly rational, so structure matters because it sets the premises of their decisions and channels their attention: who sees which problems, which goals they pursue, and which routines they follow. Ocasio makes structure distribute attention.What it has shownMarch and Simon (1958) drew propositions from the existing literature, and Cyert and March (1963) added process models and simulations. Two studies show hierarchy shaping what is sent up as well as what is chosen (Reitzig and Maciejovsky 2015; Keum and See 2017).Who disputes itOrganizational economics: decision rights, authority, and complementarities models a principal and agents with defined objectives; the Carnegie school, firms as coalitions with unresolved goal conflict.The Carnegie school and the attention-based view in The Schools of Organization DesignSocio-technical systems1950s to 1980sWhat it claimsAn organization is a social system and a technical system that must be designed together. The same technology admits more than one way of organizing work, and groups that own a whole task and control its variances at the source perform better and are more satisfied.What it has shownTrist and Bamforth (1951) found that longwall mechanization broke up self-regulating work groups. A review of 134 experiments found them extremely successful overall, and Stewart (2006) linked team autonomy to performance; studies of socialist brigades and Volkswagen qualify it.Who disputes itLabor process and critical theory: Kelly argued that labor intensification, not joint optimization, accounts for what socio-technical redesign achieved, and that the part of pay incentives was seriously underestimated.Socio-technical systems in The Schools of Organization DesignThe economics of the labor-managed firm and of enterprise ownership1958 to the presentWhat it claimsA firm run by its workers behaves differently from one run for investors: Ward modeled the Yugoslav-style firm as maximizing income per worker. Hansmann argued that an ownership form's success depends on the balance between the costs of market contracting and of ownership.What it has shownBurdín (2014) found a 29 percent lower hazard of dissolution for Uruguayan worker-managed firms than for conventional ones, and Fakhfakh, Pérotin, and Gago (2012) found French labor-managed firms as productive or more so in every industry studied.Who disputes itOrganizational economics (Jensen and Meckling) contrasts the labor-managed firm, in which tradable residual claims are legally prohibited, with cooperatives and partnerships that arise out of voluntary contracting.The economics of the labor-managed firm and of enterprise ownership in The Schools of Organization DesignModularity and the mirroring hypothesis1960s to the presentWhat it claimsComplex systems are built of nearly decomposable parts, and an organization's structure tends to mirror the architecture of what it makes: modular products allow loosely coupled organizations, and tightly coupled products need tightly coupled teams. Conway's law runs in reverse.What it has shownColfer and Baldwin (2016) review the empirical studies and report both support and principled exceptions. Direct tests point both ways: MacCormack, Baldwin, and Rusnak (2012) found open source products more modular than their commercial pairs; dynamic components break the mirror.Who disputes itNo school in the record disputes it head on; it answers information processing, which meets the coordination load inside the organization; mirroring writers locate it in the product's architecture.Modularity and the mirroring hypothesis in The Schools of Organization DesignStrategy and structure1960s to 1980sWhat it claimsStructure follows strategy: firms that diversify by product or geography outgrow the centralized functional structure and, after a lag and usually a crisis, adopt divisions. Chandler drew this from the histories of DuPont, General Motors, Standard Oil of New Jersey, and Sears.What it has shownChandler (1962) is comparative business history of four firms set against a wider survey. Rumelt (1974) related diversification and structure to performance, and Egelhoff (1988), with 34 multinationals, found some of Stopford and Wells's relationships supported and others not.Who disputes itInstitutional theory: in Fligstein's model divisions spread with a product-related or unrelated strategy, presidents from sales or finance, and other firms in the industry changing; strategy was one of three.Strategy and structure in The Schools of Organization DesignStructural contingency theory1960s to the presentWhat it claimsThere is no one best structure. Performance depends on fit between structure and contingencies such as environment, technology, size, and strategy, on an open-system view of the organization. Drazin and Van de Ven separate fit as selection, interaction, and systems.What it has shownBurns and Stalker, Woodward, and the Aston group related structure to context; Drazin and Van de Ven (1985) supported selection and systems fit only. Pennings (1975) found that fit did not explain effectiveness; Schoonhoven (1981) found traditional hypotheses unsupported.Who disputes itStrategic choice: Child argued that contingency theory explains structure by the constraints of context and leaves out the political process by which power-holders choose strategic action, structural forms included.Structural contingency theory in The Schools of Organization DesignThe French bureaucratic school (strategic analysis)1960s to 1980sWhat it claimsA bureaucracy is a system of power relations organized around zones of uncertainty. Impersonal rules and centralization protect members from depending on one another, those who control uncertainties hold power, and, unable to correct its errors, it changes only through crisis.What it has shownLe phénomène bureaucratique (1963; English 1964) rests on two case studies, a clerical agency and a state industrial monopoly. L'acteur et le système (1977; English 1980) is theoretical.Who disputes itSocietal effect and comparative business systems: D'Iribarne argues that national logics of conduct, such as a French logic of honor, explain differences that Crozier attributed to power games.The French bureaucratic school (strategic analysis) in The Schools of Organization DesignThe Japanese-firm literature1960s to the presentWhat it claimsThe large Japanese firm coordinates operating decisions through horizontal information sharing among semi-autonomous shops and uses its ranking hierarchy mainly as an incentive scheme (Aoki). It creates knowledge through middle-up-down management (Nonaka and Takeuchi).What it has shownAoki (1986) is a formal model. Lincoln, Hanada, and McBride (1986) compared 51 Japanese and 55 United States manufacturing plants, and Nonaka and Takeuchi (1995) rest on case studies, chiefly of Japanese firms. Fruin (1994) found the enterprise system defined at three levels.Who disputes itLabor process and critical theory reads shop-floor delegation as control: Sewell and Wilkinson argue that just-in-time and total quality regimes delegate tactical responsibility while centralizing strategic control.The Japanese-firm literature in The Schools of Organization DesignThe Scandinavian and Dutch socio-technical schools1960s to 2000sWhat it claimsThe Scandinavian program sought democracy at work through field experiments with semi-autonomous groups, then through democratic dialogue. The Dutch school's design theory turns complex organizations with simple jobs into simple organizations with complex jobs.What it has shownEmery and Thorsrud reported field experiments in Norwegian industry; Gustavsen (1992) records that they spread less than hoped, his reason for turning to dialogue. Berggren studied work organization in the Swedish auto industry. The Dutch work rests on design cases and argument.Who disputes itThe Japanese-firm literature: defenders of the Toyota system hold that standardized work with employee participation learns faster; Berggren reports Swedish long-cycle plants matching a line plant on productivity.The Scandinavian and Dutch socio-technical schools in The Schools of Organization DesignConfiguration theory1970s to the presentWhat it claimsStructures cluster into a small number of internally coherent configurations whose elements reinforce one another, so organizations move between a few types in large jumps, not small steps. Mintzberg's five configurations each rest on one coordinating mechanism.What it has shownDoty, Glick, and Huber (1993) found that fit to Miles and Snow's ideal types predicted effectiveness while fit to Mintzberg's did not. A meta-analysis of 40 tests (Ketchen and colleagues 1997) found that configuration partly explains performance, more so with broad definitions.Who disputes itStructural contingency theory: Donaldson counters that most organizations sit at intermediate points on a continuum of fits, not in a few configurations, and that studies over time find mostly incremental change.Configuration theory in The Schools of Organization DesignInformation processing1970s to the presentWhat it claimsThe more uncertain the task, the more information must be processed during its execution. An organization either reduces that need, through slack resources or self-contained tasks, or raises its capacity, through vertical information systems or lateral relations up to the matrix.What it has shownGalbraith (1973, 1974) built the framework from cases and from Simon's theory of bounded rationality, and Tushman and Nadler (1978) set it out as an integrating concept for design. Daft and Lengel (1986) argued that structure must reduce equivocality as well as supply data.Who disputes itThe Carnegie school and the attention-based view: Ocasio holds that firm behavior results from how the firm channels and distributes attention, so structure governs where attention goes, not only how much is processed.Information processing in The Schools of Organization DesignLabor process and critical theory1970s to the presentWhat it claimsStructure is above all a system of control over labor. Braverman argued that management deskills work by separating conception from execution; Edwards traced a sequence from simple control by the boss to technical control through machines to bureaucratic control through rules.What it has shownHistorical and theoretical (Braverman 1974; Edwards 1979). Delbridge (1995), observing a Japanese-owned plant in England, found that just-in-time and total quality regimes combined the control of labor with management's economic goals more completely than piece rates had.Who disputes itBureaucracy and its critics: Adler argues that labor process theory ignores the progressive socialization of the labor process, which drives long-term skill upgrading, and disputes deskilling as the trend.Labor process and critical theory in The Schools of Organization DesignStrategic choice1970s to the presentWhat it claimsStructure is the outcome of choices by those with power in the organization, who decide on strategic action, including the structural form, the manipulation of environmental features, and the performance standards to be met. Context constrains but does not determine structure.What it has shownLargely conceptual: Child (1972) built the argument from gaps in contingency findings, and the empirical case rests mostly on the modest share of structural variance contingencies explain. A 2026 review of 42 studies finds upper echelons theory their main theoretical anchor.Who disputes itStructural contingency theory: Donaldson replies that organizations mostly adopt the structures their contingencies dictate, to avoid the loss of performance misfit brings, so choice over structure is at most limited.Strategic choice in The Schools of Organization DesignThe German codetermination literature1970s to the presentWhat it claimsWorks councils and employee board seats form a structural layer through which coordination can become negotiation between management and employees. Defenders argue that it supports long-term employment, training, and cooperation; critics, that it weakens shareholder control.What it has shownJäger, Schoefer, and Heining (2021) found board-level codetermination left wages unchanged and, if anything, raised capital formation. Jirjahn (2011) reports studies pointing to positive works council effects; a meta-analysis found codetermination laws tied to lower productivity.Who disputes itOrganizational economics (Gorton and Schmid) found that firms with equal employee and shareholder representation did worse for their shareholders than firms with one-third employee representation.The German codetermination literature in The Schools of Organization DesignOrganizational economics: decision rights, authority, and complementarities1976 to the presentWhat it claimsDesign is the joint choice of who holds which decision rights, how performance is measured, and how it is rewarded. Rights should be placed where the specific knowledge lies, formal authority differs from real authority, and practices are complements that pay off in clusters.What it has shownIchniowski, Shaw, and Prennushi (1997) found, on 36 steel finishing lines, that lines using a set of innovative work practices achieved substantially higher productivity, consistent with complementarities. Bloom and colleagues found more decentralization where trust was higher.Who disputes itGhoshal argued that management research has shaped managers' worldview with ideologically inspired amoral theories, built on a scientific model that excludes human intentionality and so denies moral considerations.Organizational economics: decision rights, authority, and complementarities in The Schools of Organization DesignInstitutional theory1977 to the presentWhat it claimsFormal structures are often adopted because they are legitimate in the organization's field, as rationalized myths, and then decoupled from the work done. Organizations in a field grow alike through coercive, mimetic, and normative isomorphism, whether or not it is efficient.What it has shownTolbert and Zucker (1983) found that city characteristics predicted early but not later adoption of civil service reform, which they read as institutionalization. Palmer, Jennings, and Zhou (1993) found support for institutional and economic accounts of late M-form adoption.Who disputes itStructural contingency theory: Kraatz and Zajac found little support for neoinstitutional predictions in 631 liberal arts colleges, which grew less alike; the change they studied was curricular, not structural.Institutional theory in The Schools of Organization DesignPopulation ecology1977 to the presentWhat it claimsOrganizations face strong structural inertia, because selection favors the reliability and accountability of stable structures. Change in a population's forms comes mainly from founding and failure, not adaptation, and changing core features resets the liability of newness.What it has shownAmburgey, Kelly, and Barnett (1993) found that the effects of change on the hazard of failure vary by type of change and over time, and that rates of change depend on how often and how recently an organization has changed. Carroll and Hannan (2000) set out the program's methods.Who disputes itFor structural contingency theory, Donaldson argues that ecology understates managers' capacity to adapt structure.Population ecology in The Schools of Organization DesignResource dependence1978 to the presentWhat it claimsOrganizations depend on outside parties for critical resources, and structure follows the management of that dependence: units that cope with critical dependencies gain power, and boundaries are redrawn through cooptation, joint ventures, and mergers to absorb constraint.What it has shownPfeffer and Salancik (1978) assembled studies of boards, mergers, and joint ventures. A meta-analysis of 157 tests (Drees and Heugens 2013) corroborated the main prediction: organizations meet resource dependencies with interorganizational arrangements that raise their autonomy.Who disputes itTransaction cost economics and the M-form hypothesis explains boundaries by efficiency; resource dependence, by power and constraint.Resource dependence in The Schools of Organization DesignThe business-groups literature1978 to the presentWhat it claimsGroups of legally independent firms bound by ownership and social ties are a durable form of their own, neither one firm nor a market. Where institutions function poorly, groups can benefit member firms and can destroy value; they are sometimes paragons, sometimes parasites.What it has shownKhanna and Palepu (2000) found that affiliates of the most diversified Indian groups outperformed unaffiliated firms. A meta-analysis of 141 studies (Carney and colleagues 2011) found that affiliation lowers performance in general, less so where institutions are underdeveloped.Who disputes itOrganizational economics: agency writers read pyramids and cross-holdings as devices that separate control from ownership; Almeida and Wolfenzon offer a financing rationale for pyramids instead.The business-groups literature in The Schools of Organization DesignScandinavian institutionalism1980s to the presentWhat it claimsIdeas of organizing do not diffuse unchanged; they travel and are translated as they are adopted, so a form taken up in one place is not the same form elsewhere. Organizations can also be built of organizations (meta-organizations), which behave differently.What it has shownA discussion paper by Czarniawska and Joerges (1995) contrasts the diffusion of ideas with their translation, drawing on examples such as Swedish municipal reform; the work on meta-organizations (Ahrne and Brunsson 2008) is conceptual.Who disputes itInstitutional theory can read the same processes, seen from a translocal view, as institutional isomorphism, though translation holds that each adopter modifies an idea, so an institution re-created elsewhere is new.Scandinavian institutionalism in The Schools of Organization DesignSocietal effect and comparative business systems1980s to the presentWhat it claimsFirms matched on size, technology, and industry differ systematically by country, because how a society educates, trains, recruits, and promotes its workforce, and its industrial relations, shape how work is divided and supervised, so structure is partly a national product.What it has shownMaurice, Sorge, and Warner (1980) compared closely matched manufacturing units in France, West Germany, and Great Britain and found more pervasive differences in their organization than usually recognized. Whitley (1999) set out a comparative account of business systems.Who disputes itStructural contingency theory stresses culture-free elements of structure; matched comparisons find nationally different shapes of organization.Societal effect and comparative business systems in The Schools of Organization DesignThe network perspective on organizations1985 to the presentWhat it claimsOrganizations and their members are nodes joined by ties, and the pattern of ties shapes what they can do. Economic action is embedded in networks of personal relations (Granovetter 1985), and network forms are a distinct form, not a hybrid of market and hierarchy (Powell 1990).What it has shownPodolny and Page (1998) review the research and find that network forms foster learning, confer status and legitimacy, bring economic benefits, help manage resource dependencies, and give employees considerable autonomy, and they ask for attention to networks' dysfunctions.Who disputes itTransaction cost economics: Williamson treats the hybrid as a third generic form between market and hierarchy; for Powell, network forms are a distinct form, not a mix of the two.The network perspective on organizations in The Schools of Organization DesignComputational organization design and search1990s to the presentWhat it claimsDesign choices interact, so design space is a rugged landscape with many local peaks, and structure affects how well an organization searches it. Decentralizing interdependent decisions can trap units on poor peaks; temporary decentralization, then reintegration, can help.What it has shownMostly simulation, with one field test: Csaszar (2012), with more than 150,000 stock-picking decisions by 609 mutual funds, found that decision-making structure affects the number of initiatives pursued and the omission and commission errors made.Who disputes itNo school in the record disputes it head on; it disputes structural contingency theory, whose bivariate fit, its simulations show, cannot capture how the best design depends on interactions among choices.Computational organization design and search in The Schools of Organization DesignThe new-forms debate1990s to the presentWhat it claimsOrganizations must solve four universal problems (dividing tasks, allocating them, providing rewards, and providing information), and a form is new when it solves them in new ways. Self-managing organizations radically decentralize authority; skeptics hold hierarchy reappears.What it has shownFoss (2003) traced the rise and partial reversal of Oticon's spaghetti organization to the problem of selective intervention. A meta-analysis of 54 studies of 13,914 teams (Greer and colleagues 2018) found that hierarchy within teams on net slightly lowers team performance.Who disputes itBureaucracy and its critics: removing formal structure leaves informal elites whose power is unaccountable (Freeman), and democratic and network organizations are much less hierarchy-free than their labels suggest.The new-forms debate in The Schools of Organization DesignThe algorithmic-management literature2015 to the presentWhat it claimsSoftware does much of the directing, evaluating, and disciplining that managers and rules once did. Kellogg, Valentine, and Christin (2020) call algorithmic control a new contested terrain; Puranam (2021) treats dividing decisions between people and machines as a design problem.What it has shownMostly qualitative field studies of gig work. Wood and colleagues (2019), with 107 interviews in six countries and 679 survey respondents, found that algorithmic management tends to give remote gig workers flexibility and autonomy, but also low pay, isolation, and overwork.Who disputes itLabor process and critical theory reads control at work as contested terrain; Kellogg, Valentine, and Christin take up that view but argue that algorithmic control is distinct from earlier forms.The algorithmic-management literature in The Schools of Organization DesignFunctional structureOrigin: 1911 to 1937.Family: Classical hierarchies.Line and staffOrigin: 1916 to 1943.Family: Classical hierarchies.Multidivisional (M-form) by productOrigin: 1920s practice; named and analyzed 1962 to 1975.Family: Divisionalized forms.Machine bureaucracyOrigin: 1922 (Weber); 1979 (Mintzberg).Family: Classical hierarchies.Divisional by customer or market segmentOrigin: 1937; 2005.Family: Divisionalized forms.Matrix organizationOrigin: 1950s to 1960s practice; analyzed 1971 to 1977.Family: Lateral and multidimensional forms.Co-determined organizationOrigin: 1951 to 1976 (the laws); 1984 to 2022 (the main studies).Family: Forms from other traditions.Socio-technical autonomous work groupsOrigin: 1951 to 1965.Family: Team-based and self-managing forms.Stratified hierarchy (requisite organization)Origin: 1951 to 1989.Family: Classical hierarchies.Cooperative organizationOrigin: 1958 to 1999.Family: Forms from other traditions.Linking-pin organization (System 4)Origin: 1961 to 1967.Family: Team-based and self-managing forms.Divisional by regionOrigin: 1962 to 1972.Family: Divisionalized forms.Adhocracy (innovative organization)Origin: 1968 to 1979.Family: Professional, project, and knowledge forms.J-form (the Japanese firm)Origin: 1968 to 1990.Family: Forms from other traditions.Professional bureaucracyOrigin: 1968 to 1979.Family: Professional, project, and knowledge forms.Holding company (H-form)Origin: 1972 to 1975; 1987.Family: Divisionalized forms.Ambidextrous organizationOrigin: 1976 to 2004.Family: Professional, project, and knowledge forms.Simple structureOrigin: 1979.Family: Classical hierarchies.Hybrid structureOrigin: 1980 to the present.Family: Lateral and multidimensional forms.Missionary (ideological) organizationOrigin: 1980 to 1989.Family: Ideological forms.Network, modular, and virtual organizationOrigin: 1986 to 1990.Family: Network and market-like forms.Transnational and multidimensional organizationOrigin: 1987 to 1989.Family: Lateral and multidimensional forms.Business group (keiretsu, chaebol, family house)Origin: 1988 to 2007.Family: Forms from other traditions.Shamrock organizationOrigin: 1988 to 1989.Family: Network and market-like forms.Federal organizationOrigin: 1989 to 1992.Family: Network and market-like forms.Self-managing organization (less-hierarchical forms)Origin: 1989 to 2017.Family: Team-based and self-managing forms.Boundaryless organizationOrigin: 1990 to 1995.Family: Network and market-like forms.Front-back organizationOrigin: 1990s to 2007.Family: Lateral and multidimensional forms.Professional partnership (P2 form)Origin: 1990.Family: Professional, project, and knowledge forms.The corporate center and shared servicesOrigin: 1991 to 2000.Family: Divisionalized forms.Internal market organizationOrigin: 1993 to 1994.Family: Network and market-like forms.Process (horizontal) organizationOrigin: 1993 to 1999.Family: Lateral and multidimensional forms.Cellular organizationOrigin: 1994 to 1997.Family: Network and market-like forms.Hypertext organizationOrigin: 1994 to 1995.Family: Forms from other traditions.Team-based organizationOrigin: 1995.Family: Team-based and self-managing forms.Project-based organizationOrigin: 2000 to 2006.Family: Professional, project, and knowledge forms.Agile at scaleOrigin: 2001 to 2016.Family: Contemporary and emerging forms.Distributed (all-remote) organizationOrigin: 2002 to 2021.Family: Contemporary and emerging forms.Open-source and community-based organizationOrigin: 2002 to 2007.Family: Contemporary and emerging forms.Algorithmically managed organizationOrigin: 2015 to 2020.Family: Contemporary and emerging forms.Team of teamsOrigin: 2015.Family: Team-based and self-managing forms.

The schools by first year

  1. Bureaucracy and its critics1900s to 1950s, revived from the 1990sWhat it claimsWeber held that rational-legal authority exercised through an office hierarchy, written rules, trained officials, and promotion by qualification is technically superior in precision, speed, and reliability. Critics studied its unintended consequences, Michels's iron law sharpest.What it has shownMerton (1940) argued, with no test, that rules can turn from means into ends; case studies followed. The Aston group concluded that the type's dimensions vary independently, and Wagner's meta-analysis (2021) found that many of their interrelationships have weakened.Who disputes itHuman relations and System 4 sets the costs of impersonal rules to motivation and cooperation against the technical superiority Weber stresses.
  2. Classical administration1910s to 1940s, and in German to the 1970sWhat it claimsThere are general principles of administration, among them division of work, unity of command, a scalar chain of authority, and a limited span of control, and a structure built to them will be efficient in most settings. Taylor added that planners should set work methods.What it has shownThe school offered reasoning and experience, not tests. Woodward (1965) found that the spans and levels of the more successful firms in her sample differed by production system, and Simon (1946) showed that the principles come in pairs that point in opposite directions.Who disputes itStructural contingency theory found that the structure of successful firms varies with technology and environment, where classical writers treat their principles as general.
  3. Human relations and System 41920s to 1960sWhat it claimsOutput depends on the social relations of work, the norms of informal groups, and the style of supervision as much as on formal design. Likert's System 4, overlapping work groups joined by linking-pin managers under participative management, outperforms authoritative systems.What it has shownThe founding evidence is the Hawthorne studies, which later reanalyses dispute (Carey 1967; Levitt and List 2011). Likert's support came largely from his own institute's surveys. Wagner (1994) found participation's effects on performance and satisfaction significant but small.Who disputes itLabor process and critical theory reads human relations as a technique of managerial control rather than a change in the distribution of power.
  4. Transaction cost economics and the M-form hypothesis1937, then the 1970s to the presentWhat it claimsFirms exist, and are organized as they are, to economize on transaction costs. Hierarchy replaces the market when assets are specific, uncertainty is high, and exchange is frequent, and the multidivisional form should outperform the functional form in large, diversified firms.What it has shownArmour and Teece (1978) found, in United States petroleum firms from 1955 to 1973, a positive relationship between the multidivisional form and profitability while the form was spreading, but not once an equilibrium in organizational form was reached.Who disputes itThe network perspective on organizations: Granovetter argued that the theory undersocializes economic action, which is embedded in networks of personal relations that also produce trust and order.
  5. The Carnegie school and the attention-based view1940s to the presentWhat it claimsPeople in organizations are boundedly rational, so structure matters because it sets the premises of their decisions and channels their attention: who sees which problems, which goals they pursue, and which routines they follow. Ocasio makes structure distribute attention.What it has shownMarch and Simon (1958) drew propositions from the existing literature, and Cyert and March (1963) added process models and simulations. Two studies show hierarchy shaping what is sent up as well as what is chosen (Reitzig and Maciejovsky 2015; Keum and See 2017).Who disputes itOrganizational economics: decision rights, authority, and complementarities models a principal and agents with defined objectives; the Carnegie school, firms as coalitions with unresolved goal conflict.
  6. Socio-technical systems1950s to 1980sWhat it claimsAn organization is a social system and a technical system that must be designed together. The same technology admits more than one way of organizing work, and groups that own a whole task and control its variances at the source perform better and are more satisfied.What it has shownTrist and Bamforth (1951) found that longwall mechanization broke up self-regulating work groups. A review of 134 experiments found them extremely successful overall, and Stewart (2006) linked team autonomy to performance; studies of socialist brigades and Volkswagen qualify it.Who disputes itLabor process and critical theory: Kelly argued that labor intensification, not joint optimization, accounts for what socio-technical redesign achieved, and that the part of pay incentives was seriously underestimated.
  7. The economics of the labor-managed firm and of enterprise ownership1958 to the presentWhat it claimsA firm run by its workers behaves differently from one run for investors: Ward modeled the Yugoslav-style firm as maximizing income per worker. Hansmann argued that an ownership form's success depends on the balance between the costs of market contracting and of ownership.What it has shownBurdín (2014) found a 29 percent lower hazard of dissolution for Uruguayan worker-managed firms than for conventional ones, and Fakhfakh, Pérotin, and Gago (2012) found French labor-managed firms as productive or more so in every industry studied.Who disputes itOrganizational economics (Jensen and Meckling) contrasts the labor-managed firm, in which tradable residual claims are legally prohibited, with cooperatives and partnerships that arise out of voluntary contracting.
  8. Modularity and the mirroring hypothesis1960s to the presentWhat it claimsComplex systems are built of nearly decomposable parts, and an organization's structure tends to mirror the architecture of what it makes: modular products allow loosely coupled organizations, and tightly coupled products need tightly coupled teams. Conway's law runs in reverse.What it has shownColfer and Baldwin (2016) review the empirical studies and report both support and principled exceptions. Direct tests point both ways: MacCormack, Baldwin, and Rusnak (2012) found open source products more modular than their commercial pairs; dynamic components break the mirror.Who disputes itNo school in the record disputes it head on; it answers information processing, which meets the coordination load inside the organization; mirroring writers locate it in the product's architecture.
  9. Strategy and structure1960s to 1980sWhat it claimsStructure follows strategy: firms that diversify by product or geography outgrow the centralized functional structure and, after a lag and usually a crisis, adopt divisions. Chandler drew this from the histories of DuPont, General Motors, Standard Oil of New Jersey, and Sears.What it has shownChandler (1962) is comparative business history of four firms set against a wider survey. Rumelt (1974) related diversification and structure to performance, and Egelhoff (1988), with 34 multinationals, found some of Stopford and Wells's relationships supported and others not.Who disputes itInstitutional theory: in Fligstein's model divisions spread with a product-related or unrelated strategy, presidents from sales or finance, and other firms in the industry changing; strategy was one of three.
  10. Structural contingency theory1960s to the presentWhat it claimsThere is no one best structure. Performance depends on fit between structure and contingencies such as environment, technology, size, and strategy, on an open-system view of the organization. Drazin and Van de Ven separate fit as selection, interaction, and systems.What it has shownBurns and Stalker, Woodward, and the Aston group related structure to context; Drazin and Van de Ven (1985) supported selection and systems fit only. Pennings (1975) found that fit did not explain effectiveness; Schoonhoven (1981) found traditional hypotheses unsupported.Who disputes itStrategic choice: Child argued that contingency theory explains structure by the constraints of context and leaves out the political process by which power-holders choose strategic action, structural forms included.
  11. The French bureaucratic school (strategic analysis)1960s to 1980sWhat it claimsA bureaucracy is a system of power relations organized around zones of uncertainty. Impersonal rules and centralization protect members from depending on one another, those who control uncertainties hold power, and, unable to correct its errors, it changes only through crisis.What it has shownLe phénomène bureaucratique (1963; English 1964) rests on two case studies, a clerical agency and a state industrial monopoly. L'acteur et le système (1977; English 1980) is theoretical.Who disputes itSocietal effect and comparative business systems: D'Iribarne argues that national logics of conduct, such as a French logic of honor, explain differences that Crozier attributed to power games.
  12. The Japanese-firm literature1960s to the presentWhat it claimsThe large Japanese firm coordinates operating decisions through horizontal information sharing among semi-autonomous shops and uses its ranking hierarchy mainly as an incentive scheme (Aoki). It creates knowledge through middle-up-down management (Nonaka and Takeuchi).What it has shownAoki (1986) is a formal model. Lincoln, Hanada, and McBride (1986) compared 51 Japanese and 55 United States manufacturing plants, and Nonaka and Takeuchi (1995) rest on case studies, chiefly of Japanese firms. Fruin (1994) found the enterprise system defined at three levels.Who disputes itLabor process and critical theory reads shop-floor delegation as control: Sewell and Wilkinson argue that just-in-time and total quality regimes delegate tactical responsibility while centralizing strategic control.
  13. The Scandinavian and Dutch socio-technical schools1960s to 2000sWhat it claimsThe Scandinavian program sought democracy at work through field experiments with semi-autonomous groups, then through democratic dialogue. The Dutch school's design theory turns complex organizations with simple jobs into simple organizations with complex jobs.What it has shownEmery and Thorsrud reported field experiments in Norwegian industry; Gustavsen (1992) records that they spread less than hoped, his reason for turning to dialogue. Berggren studied work organization in the Swedish auto industry. The Dutch work rests on design cases and argument.Who disputes itThe Japanese-firm literature: defenders of the Toyota system hold that standardized work with employee participation learns faster; Berggren reports Swedish long-cycle plants matching a line plant on productivity.
  14. Configuration theory1970s to the presentWhat it claimsStructures cluster into a small number of internally coherent configurations whose elements reinforce one another, so organizations move between a few types in large jumps, not small steps. Mintzberg's five configurations each rest on one coordinating mechanism.What it has shownDoty, Glick, and Huber (1993) found that fit to Miles and Snow's ideal types predicted effectiveness while fit to Mintzberg's did not. A meta-analysis of 40 tests (Ketchen and colleagues 1997) found that configuration partly explains performance, more so with broad definitions.Who disputes itStructural contingency theory: Donaldson counters that most organizations sit at intermediate points on a continuum of fits, not in a few configurations, and that studies over time find mostly incremental change.
  15. Information processing1970s to the presentWhat it claimsThe more uncertain the task, the more information must be processed during its execution. An organization either reduces that need, through slack resources or self-contained tasks, or raises its capacity, through vertical information systems or lateral relations up to the matrix.What it has shownGalbraith (1973, 1974) built the framework from cases and from Simon's theory of bounded rationality, and Tushman and Nadler (1978) set it out as an integrating concept for design. Daft and Lengel (1986) argued that structure must reduce equivocality as well as supply data.Who disputes itThe Carnegie school and the attention-based view: Ocasio holds that firm behavior results from how the firm channels and distributes attention, so structure governs where attention goes, not only how much is processed.
  16. Labor process and critical theory1970s to the presentWhat it claimsStructure is above all a system of control over labor. Braverman argued that management deskills work by separating conception from execution; Edwards traced a sequence from simple control by the boss to technical control through machines to bureaucratic control through rules.What it has shownHistorical and theoretical (Braverman 1974; Edwards 1979). Delbridge (1995), observing a Japanese-owned plant in England, found that just-in-time and total quality regimes combined the control of labor with management's economic goals more completely than piece rates had.Who disputes itBureaucracy and its critics: Adler argues that labor process theory ignores the progressive socialization of the labor process, which drives long-term skill upgrading, and disputes deskilling as the trend.
  17. Strategic choice1970s to the presentWhat it claimsStructure is the outcome of choices by those with power in the organization, who decide on strategic action, including the structural form, the manipulation of environmental features, and the performance standards to be met. Context constrains but does not determine structure.What it has shownLargely conceptual: Child (1972) built the argument from gaps in contingency findings, and the empirical case rests mostly on the modest share of structural variance contingencies explain. A 2026 review of 42 studies finds upper echelons theory their main theoretical anchor.Who disputes itStructural contingency theory: Donaldson replies that organizations mostly adopt the structures their contingencies dictate, to avoid the loss of performance misfit brings, so choice over structure is at most limited.
  18. The German codetermination literature1970s to the presentWhat it claimsWorks councils and employee board seats form a structural layer through which coordination can become negotiation between management and employees. Defenders argue that it supports long-term employment, training, and cooperation; critics, that it weakens shareholder control.What it has shownJäger, Schoefer, and Heining (2021) found board-level codetermination left wages unchanged and, if anything, raised capital formation. Jirjahn (2011) reports studies pointing to positive works council effects; a meta-analysis found codetermination laws tied to lower productivity.Who disputes itOrganizational economics (Gorton and Schmid) found that firms with equal employee and shareholder representation did worse for their shareholders than firms with one-third employee representation.
  19. Organizational economics: decision rights, authority, and complementarities1976 to the presentWhat it claimsDesign is the joint choice of who holds which decision rights, how performance is measured, and how it is rewarded. Rights should be placed where the specific knowledge lies, formal authority differs from real authority, and practices are complements that pay off in clusters.What it has shownIchniowski, Shaw, and Prennushi (1997) found, on 36 steel finishing lines, that lines using a set of innovative work practices achieved substantially higher productivity, consistent with complementarities. Bloom and colleagues found more decentralization where trust was higher.Who disputes itGhoshal argued that management research has shaped managers' worldview with ideologically inspired amoral theories, built on a scientific model that excludes human intentionality and so denies moral considerations.
  20. Institutional theory1977 to the presentWhat it claimsFormal structures are often adopted because they are legitimate in the organization's field, as rationalized myths, and then decoupled from the work done. Organizations in a field grow alike through coercive, mimetic, and normative isomorphism, whether or not it is efficient.What it has shownTolbert and Zucker (1983) found that city characteristics predicted early but not later adoption of civil service reform, which they read as institutionalization. Palmer, Jennings, and Zhou (1993) found support for institutional and economic accounts of late M-form adoption.Who disputes itStructural contingency theory: Kraatz and Zajac found little support for neoinstitutional predictions in 631 liberal arts colleges, which grew less alike; the change they studied was curricular, not structural.
  21. Population ecology1977 to the presentWhat it claimsOrganizations face strong structural inertia, because selection favors the reliability and accountability of stable structures. Change in a population's forms comes mainly from founding and failure, not adaptation, and changing core features resets the liability of newness.What it has shownAmburgey, Kelly, and Barnett (1993) found that the effects of change on the hazard of failure vary by type of change and over time, and that rates of change depend on how often and how recently an organization has changed. Carroll and Hannan (2000) set out the program's methods.Who disputes itFor structural contingency theory, Donaldson argues that ecology understates managers' capacity to adapt structure.
  22. Resource dependence1978 to the presentWhat it claimsOrganizations depend on outside parties for critical resources, and structure follows the management of that dependence: units that cope with critical dependencies gain power, and boundaries are redrawn through cooptation, joint ventures, and mergers to absorb constraint.What it has shownPfeffer and Salancik (1978) assembled studies of boards, mergers, and joint ventures. A meta-analysis of 157 tests (Drees and Heugens 2013) corroborated the main prediction: organizations meet resource dependencies with interorganizational arrangements that raise their autonomy.Who disputes itTransaction cost economics and the M-form hypothesis explains boundaries by efficiency; resource dependence, by power and constraint.
  23. The business-groups literature1978 to the presentWhat it claimsGroups of legally independent firms bound by ownership and social ties are a durable form of their own, neither one firm nor a market. Where institutions function poorly, groups can benefit member firms and can destroy value; they are sometimes paragons, sometimes parasites.What it has shownKhanna and Palepu (2000) found that affiliates of the most diversified Indian groups outperformed unaffiliated firms. A meta-analysis of 141 studies (Carney and colleagues 2011) found that affiliation lowers performance in general, less so where institutions are underdeveloped.Who disputes itOrganizational economics: agency writers read pyramids and cross-holdings as devices that separate control from ownership; Almeida and Wolfenzon offer a financing rationale for pyramids instead.
  24. Scandinavian institutionalism1980s to the presentWhat it claimsIdeas of organizing do not diffuse unchanged; they travel and are translated as they are adopted, so a form taken up in one place is not the same form elsewhere. Organizations can also be built of organizations (meta-organizations), which behave differently.What it has shownA discussion paper by Czarniawska and Joerges (1995) contrasts the diffusion of ideas with their translation, drawing on examples such as Swedish municipal reform; the work on meta-organizations (Ahrne and Brunsson 2008) is conceptual.Who disputes itInstitutional theory can read the same processes, seen from a translocal view, as institutional isomorphism, though translation holds that each adopter modifies an idea, so an institution re-created elsewhere is new.
  25. Societal effect and comparative business systems1980s to the presentWhat it claimsFirms matched on size, technology, and industry differ systematically by country, because how a society educates, trains, recruits, and promotes its workforce, and its industrial relations, shape how work is divided and supervised, so structure is partly a national product.What it has shownMaurice, Sorge, and Warner (1980) compared closely matched manufacturing units in France, West Germany, and Great Britain and found more pervasive differences in their organization than usually recognized. Whitley (1999) set out a comparative account of business systems.Who disputes itStructural contingency theory stresses culture-free elements of structure; matched comparisons find nationally different shapes of organization.
  26. The network perspective on organizations1985 to the presentWhat it claimsOrganizations and their members are nodes joined by ties, and the pattern of ties shapes what they can do. Economic action is embedded in networks of personal relations (Granovetter 1985), and network forms are a distinct form, not a hybrid of market and hierarchy (Powell 1990).What it has shownPodolny and Page (1998) review the research and find that network forms foster learning, confer status and legitimacy, bring economic benefits, help manage resource dependencies, and give employees considerable autonomy, and they ask for attention to networks' dysfunctions.Who disputes itTransaction cost economics: Williamson treats the hybrid as a third generic form between market and hierarchy; for Powell, network forms are a distinct form, not a mix of the two.
  27. Computational organization design and search1990s to the presentWhat it claimsDesign choices interact, so design space is a rugged landscape with many local peaks, and structure affects how well an organization searches it. Decentralizing interdependent decisions can trap units on poor peaks; temporary decentralization, then reintegration, can help.What it has shownMostly simulation, with one field test: Csaszar (2012), with more than 150,000 stock-picking decisions by 609 mutual funds, found that decision-making structure affects the number of initiatives pursued and the omission and commission errors made.Who disputes itNo school in the record disputes it head on; it disputes structural contingency theory, whose bivariate fit, its simulations show, cannot capture how the best design depends on interactions among choices.
  28. The new-forms debate1990s to the presentWhat it claimsOrganizations must solve four universal problems (dividing tasks, allocating them, providing rewards, and providing information), and a form is new when it solves them in new ways. Self-managing organizations radically decentralize authority; skeptics hold hierarchy reappears.What it has shownFoss (2003) traced the rise and partial reversal of Oticon's spaghetti organization to the problem of selective intervention. A meta-analysis of 54 studies of 13,914 teams (Greer and colleagues 2018) found that hierarchy within teams on net slightly lowers team performance.Who disputes itBureaucracy and its critics: removing formal structure leaves informal elites whose power is unaccountable (Freeman), and democratic and network organizations are much less hierarchy-free than their labels suggest.
  29. The algorithmic-management literature2015 to the presentWhat it claimsSoftware does much of the directing, evaluating, and disciplining that managers and rules once did. Kellogg, Valentine, and Christin (2020) call algorithmic control a new contested terrain; Puranam (2021) treats dividing decisions between people and machines as a design problem.What it has shownMostly qualitative field studies of gig work. Wood and colleagues (2019), with 107 interviews in six countries and 679 survey respondents, found that algorithmic management tends to give remote gig workers flexibility and autonomy, but also low pay, isolation, and overwork.Who disputes itLabor process and critical theory reads control at work as contested terrain; Kellogg, Valentine, and Christin take up that view but argue that algorithmic control is distinct from earlier forms.

The forms by first year

  1. Functional structure: 1911 to 1937
  2. Line and staff: 1916 to 1943
  3. Multidivisional (M-form) by product: 1920s practice; named and analyzed 1962 to 1975
  4. Machine bureaucracy: 1922 (Weber); 1979 (Mintzberg)
  5. Divisional by customer or market segment: 1937; 2005
  6. Matrix organization: 1950s to 1960s practice; analyzed 1971 to 1977
  7. Co-determined organization: 1951 to 1976 (the laws); 1984 to 2022 (the main studies)
  8. Socio-technical autonomous work groups: 1951 to 1965
  9. Stratified hierarchy (requisite organization): 1951 to 1989
  10. Cooperative organization: 1958 to 1999
  11. Linking-pin organization (System 4): 1961 to 1967
  12. Divisional by region: 1962 to 1972
  13. Adhocracy (innovative organization): 1968 to 1979
  14. J-form (the Japanese firm): 1968 to 1990
  15. Professional bureaucracy: 1968 to 1979
  16. Holding company (H-form): 1972 to 1975; 1987
  17. Ambidextrous organization: 1976 to 2004
  18. Simple structure: 1979
  19. Hybrid structure: 1980 to the present
  20. Missionary (ideological) organization: 1980 to 1989
  21. Network, modular, and virtual organization: 1986 to 1990
  22. Transnational and multidimensional organization: 1987 to 1989
  23. Business group (keiretsu, chaebol, family house): 1988 to 2007
  24. Shamrock organization: 1988 to 1989
  25. Federal organization: 1989 to 1992
  26. Self-managing organization (less-hierarchical forms): 1989 to 2017
  27. Boundaryless organization: 1990 to 1995
  28. Front-back organization: 1990s to 2007
  29. Professional partnership (P2 form): 1990
  30. The corporate center and shared services: 1991 to 2000
  31. Internal market organization: 1993 to 1994
  32. Process (horizontal) organization: 1993 to 1999
  33. Cellular organization: 1994 to 1997
  34. Hypertext organization: 1994 to 1995
  35. Team-based organization: 1995
  36. Project-based organization: 2000 to 2006
  37. Agile at scale: 2001 to 2016
  38. Distributed (all-remote) organization: 2002 to 2021
  39. Open-source and community-based organization: 2002 to 2007
  40. Algorithmically managed organization: 2015 to 2020
  41. Team of teams: 2015

Twenty-three of the 29 schools run to the present, and 16 of those began in the 1970s or later. The forms arrive in waves: 14 of the 41 first appear between 1985 and 1994.

Source: Fayol 1949; Weber 1978; Mayo 1933; Trist and Bamforth 1951, an interview-based field study in one industry; Burns and Stalker 1961, a field study of twenty firms; Mintzberg 1979; Child 1972a; Coase 1937; Meyer and Rowan 1977; Hannan and Freeman 1977; Galbraith 1973; Jensen and Meckling 1976; Crozier 1963; Emery and Thorsrud 1969; Yoshino 1968; Streeck 1984a; Kellogg and colleagues 2020, a review of earlier research through one theoretical lens, with no new data; Puranam and colleagues 2014, a conceptual argument; Chandler 1962, several independent case histories by a historian; Pfeffer and Salancik 1978; Simon 1946; Maurice and colleagues 1980, a comparison of matched factories in three countries; Levinthal 1997; Simon 1962; Braverman 1974; Hamilton and Biggart 1988, a comparison of three economies by scholars; Ward 1958; Czarniawska and Joerges 1995; Granovetter 1985.

It grew out of the information processing school, whose framework Galbraith built (1973, 1974): lateral relations, from direct contact through teams and integrating roles to the matrix, raise an organization's capacity to process information.

Where it fits

No study behind these ratings varied the factor. Theory ratings rest on Galbraith's writing, untested on this form.

The front-back organization against the twelve contingency factors

Each factor at its three levels, Fits, Partial, or Strain, or Contested where a contested cell's views disagree; select a row for its reason, sources, and grade.

Select a factor to read its reason, sources, basis, and grade.Size. Separate customer-facing and product units joined by linking processes need enough scale on both sides; Galbraith's guide names large organizations with multiple product lines and market segments as the form's ground, and his examples are large multiproduct firms. Basis: Theory. Grade: conceptual only, no empirical test. Sources: Galbraith 2002b; Galbraith 2010; Strikwerda and Stoelhorst 2009; Jimmy and colleagues 2011; Galbraith and colleagues 2002.Age. The form is usually built by an established product company adding a customer-facing front end. Basis: Judgment. Sources: Galbraith 2002b; Gebauer and Kowalkowski 2012; Hannan and Freeman 1984; Amburgey and colleagues 1993. View 1: Young partial, Established fits, Old fits. The form is usually built by an established product company adding a customer-facing front end. Sources: Galbraith 2002b; Gebauer and Kowalkowski 2012. View 2: Young partial, Established fits, Old partial. Inertia rises with age, and attempts at reorganization raise death rates, so reorganizing an old organization into this form is itself a hazard at the old level. Sources: Hannan and Freeman 1984.Environmental uncertainty (unpredictability, dynamism). The front end can regroup around shifting customer demands while the back end keeps product scale; in a stable market the linking processes are overhead. Basis: Theory. Grade: conceptual only, no empirical test. Sources: Galbraith 2010; Galbraith 1973; Raja and colleagues 2018; Pennings 1975.Environmental complexity. When customers need complex solutions drawn from many products, a front end that owns the customer and a back end that owns the products pays its linking cost. Basis: Theory. Grade: conceptual only, no empirical test. Sources: Galbraith 2002b; Pennings 1975.Munificence and hostility. The linking processes between front and back are heavy overhead when resources are scarce and the firm must react fast. Basis: Judgment. Sources: Burton and Obel 2004; Galbraith 2002b; Pennings 1975.Diversity of products and markets. The front end bundles several product units' offerings into solutions for the same customers, which needs related products; unrelated ones give it little to bundle. Basis: Judgment. Sources: Galbraith 2002b.Strategy type. The front-back form keeps a product back end run for scale while the front assembles solutions for customers, close to an analyzer's stable core plus selected new domains; the fit rests on a customer-centric axis this scale does not hold. Basis: Judgment. Sources: Galbraith 2005; Galbraith 2002a; Burton and Obel 2004.Technology and routineness. A standardized product back end joined to a front that tailors offerings suits work with many exceptions that known methods can handle; wholly routine work needs no front, and wholly novel work has no stable back end to draw on. Basis: Judgment. Sources: Galbraith 2002a; Perrow 1967; Hickson and colleagues 1969; Mohr 1971.Interdependence. The back end supplies what the front sells, a sequential link the form manages through planning and pricing processes; for reasonably complex solutions those processes also carry some back-and-forth work. Basis: Theory. Grade: conceptual only, no empirical test. Sources: Galbraith 2002b; Galbraith 2002a; Thompson 1967.Knowledge intensity and professionalization. The front-back design divides customers from products, and no work read ties it to how trained the workforce is, so this factor gives no reason for or against. Basis: Judgment. Sources: Galbraith 2002a.Global integration pressure. Galbraith's guide lists serving global customers with the need for cross-border coordination among the conditions for which the front-back hybrid is best; where there is little or some integration pressure, it gives no reason for or against. Basis: Theory. Grade: conceptual only, no empirical test. Sources: Galbraith 2010; Jimmy and colleagues 2011; Galbraith and colleagues 2002.Local responsiveness pressure. The front-back design divides customers from products, not countries; a customer-facing front can be cut by country, but no work read ties the form to local responsiveness. Basis: Judgment. Sources: Galbraith 2010; Galbraith 2002a.

Counting the contested age cell by its first view, the 36 settings read Fits at 11, Partial at 22, and Strain at 3, the strains at a small size, a hostile environment, and unrelated diversification. Only age is contested, and seven of the twelve cells rest on judgment.

Source: Galbraith 2002b, a design essay with illustrative company examples and no systematic data; Galbraith 2010; Strikwerda and Stoelhorst 2009, interviews at 36 Dutch organizations and five case studies; Jimmy and colleagues 2011, seven interviews in five IT outsourcing vendors, reported as mini-cases in a conference paper; Galbraith and colleagues 2002; Gebauer and Kowalkowski 2012, case studies of 36 manufacturers; Hannan and Freeman 1984; Amburgey and colleagues 1993, a quantitative study of organizational change and failure rates; Galbraith 1973; Raja and colleagues 2018, one case study of three divisions inside one manufacturer; Pennings 1975, a quantitative field test of the structural-contingency model; Burton and Obel 2004; Galbraith 2005; Galbraith 2002a; Perrow 1967; Hickson and colleagues 1969, a multi-organization comparative survey; Mohr 1971, a quantitative field study of technology and structure; Thompson 1967.

Your own situation against the front-back organization

Set any factor to outline its cell in the strip above; the lines under the switches give the counts, the form's place among the 41, and the misfit rules that fire.

Size
Age
Environmental uncertainty (unpredictability, dynamism)
Environmental complexity
Munificence and hostility
Diversity of products and markets
Strategy type
Technology and routineness
Interdependence
Knowledge intensity and professionalization
Global integration pressure
Local responsiveness pressure

Set: 0 of 12 factors. Fits on 0, Partial on 0, Strain on 0, Contested on 0.

Its place in the explorer's rankingEvery factor is on Any: all 41 forms tie, and the explorer lists them alphabetically.1st of 411st of 41, tied with one other1st of 41, tied with 0 othersSunk by a misfit rule: 1st of 41Sunk by a misfit rule: 1st of 41, tied with one otherSunk by a misfit rule: 1st of 41, tied with 0 others

No misfit rule can fire for this form at any setting.

Ranking rule: by count of Fits on the factors the reader has set, then fewest Strains, then alphabetical; a fired misfit rule that no source disputes sinks the form to the bottom when every level of the form's profile meets it, a disputed one, or one that meets the form only through one end of a spanned level, one view of a contested profile cell, or one part of a two-part form, is flagged on the row (with both views where it is disputed), and a misfit between two of the reader's own settings is shown once above the list; a contested cell counts only where its views agree at the reader's level, and otherwise shows as Contested; factors on "Any" count for nothing; with every factor on "Any" the list is alphabetical and says so.

Open these settings in the explorer

No misfit rule can fire for this form at any setting.

None of the 39 contingency misfit rules can fire for this form: its profile meets no rule's conditions, and no rule names it.

Source: Burton and Obel 2004; Burton and colleagues 2020a.

  • Size. Strain small, partial medium, fits large, as theory: Galbraith, Downey, and Kates (2002), a practitioner's guide, call the form best for large organizations with multiple product lines and market segments; every work the cell cites concerns large firms, so size was not varied.
  • Age. Contested, our judgment. Galbraith (2002b) and Gebauer and Kowalkowski (2012): partial young, fits established and old, since an established product company usually adds a front. Hannan and Freeman (1984): partial at old too (inertia rises with age, and attempts at reorganization raise death rates); Amburgey, Kelly, and Barnett (1993), a quantitative study of organizational change and failure rates, found the effects of change on failure vary by type of change and over time.
  • Environmental uncertainty. Partial stable, fits shifting and unpredictable, as theory: the front regroups around shifting demand while the back keeps scale (Galbraith 2010, 1973). The stable level is our judgment.
  • Environmental complexity. Partial simple and moderate, fits complex, as theory: Galbraith (2002b) recommends the form for reasonably complex solutions; reading the offering's complexity as environmental complexity is the cell's mapping, not his.
  • Munificence and hostility. Strain hostile, partial neutral and munificent, our judgment. Burton and Obel (2004), authors of the most developed scholarly fit model, say hostility calls for lower organizational complexity so the firm can react fast; counting the linking processes as that complexity is ours.
  • Diversity. Partial single business, fits related, strain unrelated, our judgment: the front bundles several product units' offerings for the same customers, which needs related products (premise, Galbraith 2002b).
  • Strategy. Partial defender, fits analyzer, partial prospector, our judgment: a back end run for scale beside a front assembling solutions resembles an analyzer's stable core plus new domains. The fit really rests on customer-centricity (Galbraith 2005, not peer reviewed), which this scale lacks.
  • Technology. Partial routine, fits mixed, partial nonroutine, our judgment on Perrow's (1967) levels: routine work needs no front to tailor it, and novel work has no stable back end.
  • Interdependence. Partial pooled, fits sequential, partial reciprocal, as theory: the back supplies what the front sells, a sequential link managed by planning and pricing; for reasonably complex solutions those processes also carry some back-and-forth work, which the essay counts a cost, not a reason against the form (Galbraith 2002b; Thompson 1967 pairs sequential interdependence with coordination by plan).
  • Global integration. Partial low and moderate, our judgment; fits high, as theory: the same guide names serving global customers that need cross-border coordination among its conditions, as advice, not a test; Jimmy and colleagues did not vary it.
  • Knowledge intensity and local responsiveness. Partial throughout, our judgment: no work read ties the form to these.

What it does well

It lets a firm sell across its products without breaking up its product units, which become the back end once customer-centric units are added in front of them (Galbraith 2002b, a design essay with illustrative company examples and no systematic data). Jimmy and colleagues add the client's view: one interface, one point of accountability. Askim and colleagues (2011), a three-country comparative case study, report the public version: with information technology, specialization can to some extent stay behind the frontline.

The symptom view offers it for five complaints: on theory, divisions competing for the same customers (Burton, Obel, and Håkonsson's 2015 book, with Galbraith 2002b) and no one owning the customer's experience end to end (Galbraith 2002b); as our judgment, turf wars (after Goold and Campbell 2002) and two-boss gridlock; and, also our judgment, units hitting their own numbers, which it relieves only with its linking processes and rewards, since front and back both run as profit centers.

What it costs

The link is the cost. Galbraith (2002b) names five linking processes: customer strategy, product portfolio planning, solutions development, solutions ordering and pricing, and the assembly and disassembly of teams. Pricing needs its own process because a won solution's price often differs from plan, reopening each product unit's revenue. Talent must be built for new roles and managers equipped for conflict, and since solution pricing blurs each unit's performance, rewards shift toward company performance and customer measures.

A multi-firm comparative field study by Lawrence and Lorsch (1967) found high performers matched their integrating devices to their differentiation; reading front and back as that differentiated is our judgment. Askim and colleagues (2011) conclude the trade-off between specialization and coordination persists.

How far units differ, and the integration that holds them together

Compare the units on the four orientations, judge how far apart they are, and choose a level to see the integrating device the high performers used at it.

What to compare between the units

  • Goal orientation
  • Time orientation
  • Interpersonal orientation
  • Formality of structure
Low differentiation, light integration. Units resemble each other in goals, time horizons, interpersonal style, and formality, and the hierarchy and its procedures integrate them.What the high performers usedThe managerial hierarchy.Where the study found itContainers.Moderate differentiation, some integrating roles. Units differ in some orientations, and individual integrators or committees join them alongside the hierarchy.What the high performers usedIndividual integrators.Where the study found itFood.High differentiation, heavy integration. Units differ sharply, and an integrating department, cross-unit teams, and open confrontation of conflict are needed to hold them together.What the high performers usedAn integrating department and cross-functional teams.Where the study found itPlastics.

The figure has no formula: Lawrence and Lorsch scored differentiation from managers' perceptions, on measures of their own that this figure does not reproduce, so the level is the reader's judgment.

LevelWhat it meansWhat the high performers usedWhere
Low differentiation, light integrationUnits resemble each other in goals, time horizons, interpersonal style, and formality, and the hierarchy and its procedures integrate them.the managerial hierarchycontainers
Moderate differentiation, some integrating rolesUnits differ in some orientations, and individual integrators or committees join them alongside the hierarchy.individual integratorsfood
High differentiation, heavy integrationUnits differ sharply, and an integrating department, cross-unit teams, and open confrontation of conflict are needed to hold them together.an integrating department and cross-functional teamsplastics

In Lawrence and Lorsch's ten firms, the high performers matched their integrating devices to how far their functional departments differed: the managerial hierarchy in containers, individual integrators in food, and an integrating department and cross-functional teams in plastics.

Source: Lawrence and Lorsch 1967a, a multi-firm comparative field study.

How it fails

Galbraith, Downey, and Kates (2002), as Jimmy and colleagues report, list the form's disadvantages, among them contention over resources, disagreement over prices and customer needs, and conflicting metrics.

How the front-back organization fails, and the coordination failures behind it

The entry's failure modes at the left, each tied to the Coordination Failures patterns it names at the right; a pattern links its entry there.

Regulator overloadJurisdictional gap or overlapDiffused responsibilityLocal optimization against the global constraintGoal displacement and metric gamingCoordination overhead overrun
Regulator overloadJurisdictional gap or overlapDiffused responsibilityLocal optimization against the global constraintGoal displacement and metric gamingCoordination overhead overrun

How many ties the failure has. Highest: Disputes between front and back climb to the topFront and back both claim the decisionNo one owns the solutionEach half hits its own numbers while the offer failsThe link costs more than it joinsRegulator overloadJurisdictional gap or overlapDiffused responsibilityLocal optimization against the global constraintGoal displacement and metric gamingCoordination overhead overrun

Select a failure to read its place in the network.Disputes between front and back climb to the top. Degree 1Front and back both claim the decision. Degree 1No one owns the solution. Degree 1Each half hits its own numbers while the offer fails. Degree 2The link costs more than it joins. Degree 1Regulator overload. Degree 1Jurisdictional gap or overlap. Degree 1Diffused responsibility. Degree 1Local optimization against the global constraint. Degree 1Goal displacement and metric gaming. Degree 1Coordination overhead overrun. Degree 1
FailureDegree
Disputes between front and back climb to the top1
Front and back both claim the decision1
No one owns the solution1
Each half hits its own numbers while the offer fails2
The link costs more than it joins1
Regulator overload1
Jurisdictional gap or overlap1
Diffused responsibility1
Local optimization against the global constraint1
Goal displacement and metric gaming1
Coordination overhead overrun1

Five failure modes name six patterns, and only the two halves hitting their own numbers names two: local optimization against the global constraint, and goal displacement and metric gaming.

Source: Galbraith 2002b, a design essay with illustrative company examples and no systematic data; Jimmy and colleagues 2011, seven interviews in five IT outsourcing vendors, reported as mini-cases in a conference paper; Galbraith and colleagues 2002.

Disputes between front and back climb to the top. Galbraith (2002b) puts the top in the design: reconciliation needs a strong, active top management, and conflict not legitimized and resolved can turn the firm inward and cost it competitiveness. The failure, on our reading, comes when the processes cannot settle offer, price, and customer, so the executive referees every deal (regulator overload).

Front and back both claim the decision. Galbraith (2002b) gives the contested decisions owners: pricing committees or centers for a solution's price and the product units' revenue. Jimmy and colleagues' vendors used a price matrix and escalation. Where such owners are missing, on our reading, a decision is owned twice or by no one (jurisdictional gap or overlap).

No one owns the solution. Galbraith (2002b) designs an owner in: strong customer-centric profit centers, the solutions units, pull the products together. On our reading a firm that adds account teams without one leaves a bundle drawn from several back-end units with no owner (diffused responsibility).

Each half hits its own numbers while the offer fails. In Galbraith's (2002b) Nokia example both sides were profit centers. Two profit centers trading at internal prices can, on our reading, each gain at the offer's expense (local optimization against the global constraint) or play the transfer price (goal displacement and metric gaming). Galbraith's remedy is one-company and customer-centric rewards.

The link costs more than it joins. Galbraith (2002b) ties the load to the solution: the larger its scale and scope and the more interdependent its components, the more units and interfaces must be coordinated; he answers with top-down administration of the linking processes. Our reading is that the cost can outrun what the link joins (coordination overhead overrun).

The symptom view offers this form as relief for three of these patterns (diffused responsibility, jurisdictional overlap, and units hitting their own numbers); both readings stand, and no study recorded here says which a firm will get.

Its profile meets no profile rule's conditions, and no misfit rule names the form either.

What the research found

The literature is mostly description. No study recorded since Galbraith's (2002b) design essay measures whether the form outperforms another, and Raja and colleagues (2018) say the standard advice rests mostly on anecdote.

In a conference paper, Jimmy, Seddon, and Reynolds (2011) reported seven interviews with client-facing managers in five vendors as mini-cases and found all five global IT outsourcing vendors using a front-back hybrid structure, consistent, the authors say, with the theory of Galbraith and his co-authors. A near relative: Strikwerda and Stoelhorst (2009), interviews at 36 Dutch organizations and five case studies, found seven organized on several dimensions with the customer as the main profit center.

Davies, Brady, and Hobday (2007), case studies of five firms, found a mixed set of forms, not a simple transition from systems selling to systems integration. Raddats and Burton (2011), interviews in 25 firms, found strategy the main parameter deciding where services sit. Raja and colleagues (2018), the most recent study, is one case study of three divisions inside one manufacturer, where several front-back configurations sat side by side, shaped by the offering's complexity and temporality and the customer's power.

The later studies support the existence of front-end and back-end designs but find more variety than Galbraith's one model; no replication failure is recorded.

Several schools dissent from the information processing account the form comes from. Classical administration makes the hierarchy the backbone of coordination, where information processing makes it one channel that overloads under uncertainty (Galbraith 1974); the essay's reconciling top team fits either reading (ours). The network perspective reads structure as informal ties, not formal channels carrying an information load (Hunter 2015, a review), which questions coordination designed into formal processes (ours). Ocasio's (1997) attention-based view, from the Carnegie behavioral tradition, holds that structure governs where decision makers' attention goes, not only how much information is processed. The modularity and mirroring school, which also lists this form, replies by locating the coordination load in the product's architecture: standardized interfaces embed coordination, so a modular product holds together a loosely coupled organization (Sanchez and Mahoney 1996; Colfer and Baldwin 2016, a review of 142 empirical studies, finding mirroring prevalent but not universal).

The evidence ledger holds 9 studies filed under this form.

In practice: one published case

Nokia Networks is one case study, an illustrative company example in Galbraith's design essay "Organizing to deliver solutions" (2002), not a research case study.

Nokia first sold stand-alone products to state-owned telecom monopolies. When wireless was deregulated, new operators with small engineering staffs asked how fast Nokia could design and build them a network, and Nokia responded quickly while equipment rivals with long-standing monopoly ties were slow.

Nokia built a Professional Services organization whose units could be mobilized quickly into teams led by global account teams. As large operators acquired subsidiaries across countries, a Global Accounts unit was added.

The Customer Operations unit became a customer-centric front end: structured around customers, measured on customer satisfaction and customer share, and willing to install other suppliers' equipment. It sat beside the product units that formed the back end, and both were run as profit centers.

Galbraith calls this a front-back hybrid. He argues that a solutions provider needs five linking processes between front and back (in the executive summary the five of What it costs; in the essay's sections strategy and reconciliation, product portfolio, solutions development, solutions fulfillment, and assembly and disassembly of teams), rewards with a customer-centric and a one-company orientation, and conflict management skills, and he advises leaders who cannot manage these tension-filled processes to stay with solutions of small scale and scope.

Source: Galbraith 2002b. Organizing to deliver solutions, Organizational Dynamics 31(2), 194 to 207; a design essay with illustrative company examples and no systematic data.

Variants and near relatives

Solutions organization. A front end that packages products from several back-end units into customer solutions, with a solutions unit owning the bundle (Galbraith 2002b).

One-stop shop (a single public front office over specialized agencies). The public sector's version, from welfare administration, built by merging agencies (Askim and colleagues 2011), so it stays inside one organization; a front desk shared by independent agencies is inter-organizational.

The Matrix organization, the nearest neighbor, gives the same people two bosses, while this form puts the coordination into designed processes between a customer front and a product back along one value chain. Our judgment that each unit keeps one boss is not a settled finding: the grouping cell is contested, and Jimmy and colleagues report some managers and project staff with more than one boss.

Divisional by customer or market segment gives each customer division its whole value chain; this form shares one product back end among several fronts. The Process (horizontal) organization gives an end-to-end process an accountable owner, where this form keeps a customer front beside a product back, joined by linking processes, with the balance of power between them a design choice (Galbraith 2002). The Internal market organization settles units' dealings by price; its variant Multidimensional organization (Ackoff) comes closest: market units act as profit centers and advocates toward output units supplied by input units (Ackoff 1994, a design proposal argued from practice, not tested). Here prices sit beside designed linking processes and a reconciling top team (our judgment). The Hybrid structure sets units on different bases side by side, each serving its own market. The Transnational and multidimensional organization gives national units different roles in one network (this form splits by customer and product), and its multidimensional and reconfigurable variant uses front-back designs as one layer.

The front-back organization beside its nearest neighbor, the matrix

Select a number to fill what it marks in both drawings; the list under them gives the dimensions on which the two profiles differ.

Customer-facing front units own the customer and sell what product back units make, and designed linking processes join the two halves along one value chain, so the coordination is built into those processes; the matrix puts it in a second boss.

Front-back organization

Top managementFront and backTopmanagementCustomersegment unitAccount unitProduct unitProduct unitBy customerBy productOM1111223
Top managementFront and backTopSegmentAccountProductProductBy customerBy productOM1111223

Reports toAdjust to each other directlyMMutual adjustmentOStandardization of outputsJimmy and colleagues (2011) found the back grouped by function, which this explorer reads as two bases side by side

Matrix organization

Adjust between the linesStrategic apexThe two linesTwo bossesSharedsuperiorFunctionalheadProjectmanagerSpecialist inboth lines2By functionBy projectM1223
Adjust between the linesStrategic apexThe two linesTwo bossesSuperiorFunctionProjectSpecialist2By functionBy projectM1223

Reports toAdjust to each other directlyMMutual adjustment2Two superiors

  1. Each front and back unit keeps one line of authority on this explorer's reading, though two of Jimmy and colleagues' (2011) five firms used matrix reporting for managers; the matrix's specialist has two bosses.
  2. The front is grouped by customer, the back by product (by function in Jimmy and colleagues' vendors); the matrix usually crosses function with project or product, and in multinationals often product with area.
  3. Planning and pricing along the link standardize outputs between front and back, beside the teams' mutual adjustment; the matrix's two lines coordinate by mutual adjustment alone.

Differs on 4 of 11 dimensions

  • Decision rights and the locus of authority Limited vertical decentralization; Matrix organization: Limited vertical decentralization to selective vertical and horizontal decentralization
  • Prime coordinating mechanism Mutual adjustment and standardization of outputs; Matrix organization: Mutual adjustment
  • Lateral mechanisms Task forces and teams to integrating roles and managerial linking roles; Matrix organization: Matrix
  • Mode of exchange and control Market and bureaucracy; Matrix organization: Bureaucracy

Each holds two bases of grouping at one level of the firm. The front-back form joins a customer front to a product back by designed linking processes, and each unit keeps one boss on this explorer's reading; the matrix puts the coordination in a second boss.

Source: Galbraith 2002a; Galbraith 2002b, a design essay with illustrative company examples and no systematic data; Jimmy and colleagues 2011, seven interviews in five IT outsourcing vendors, reported as mini-cases in a conference paper; Davis and Lawrence 1977; Galbraith 1971.

Moving into or out of it

On our reading (the age cell's judgment), firms usually come in from a product structure by adding a front. Galbraith (2002b) gives the sequence: create customer-centric units, integrate them with the product units through the linking processes, and redesign rewards, talent, and conflict management to match. Gebauer and Kowalkowski (2012), case studies of 36 manufacturers whose external validity could not be assessed accurately, describe four patterns of moving from product-focused or geographically focused structures toward service-focused or customer-focused ones; they do not call the customer-focused end front-back.

For older firms Hannan and Freeman (1984) argue that attempts at reorganization raise death rates; Amburgey and colleagues (1993) found the effect of change varies by type of change and over time, and Donaldson (1995), for the contingency school, argues that ecology understates managers' capacity to adapt structure, though his critique of rival paradigms is itself disputed.

No study recorded here measures this move's cost. The nearest evidence is from the M-form: Hoskisson and Craig Galbraith (1985), a time-series study of six firms, found quantum reorganizations did better than incremental ones; in Girod and Whittington (2016), a multi-firm panel study, sweeping restructuring was associated with better performance in general, a result that reversed in dynamic environments. How to run a reorganization belongs to Change & Transformation.

The thinking behind it

Jay Galbraith, "Organizing to deliver solutions" (2002): the form itself, a design prescription, not a test. Designing the Customer-Centric Organization (2005): four degrees of customer-centricity chosen by strategy, the strategy line's real basis; from a fifteen-company study with McKinsey, not peer reviewed. Amy Kates, with Galbraith (2007): the Star Model applied to design challenges, a practitioner guide that sets the form out.

With colleagues: Hans Strikwerda (2009), the multidimensional organization, a near relative of this form; Andrew Davies (2007), solutions firms combining vertical integration into services with systems integration, not one ideal type; Jawwad Raja (2018), several front-back configurations in one firm; Chris Raddats (2011), strategy shaping where services sit; Heiko Gebauer (2012), paths toward customer-focused structure; and Jostein Askim (2011), the one-stop shop, this form's public version.

James Thompson (1967): sequential interdependence coordinated by plan, the reason planning carries the link. Paul Lawrence and Jay Lorsch (1967): differentiation and integration, which explains the heavy integration two unlike halves need. Michael Hannan and John Freeman (1984): structural inertia: selection favors inert structures, inertia rises with age, and attempts at reorganization raise death rates, which bears on moving an older firm into this form; tests show effects vary by type of change. Richard Burton and Børge Obel (2004): multi-contingency fit and misfit rules, the basis of the hostility line. William Ocasio (1997): the attention-based view, a dissent from the information processing account behind this form. Ron Sanchez (1996) and Carliss Baldwin (2016), with colleagues: modularity and mirroring, which put part of the coordination load in the product's architecture.

Also called

Front-end/back-end structure and customer-product hybrid. Galbraith (2002b) calls it the front-back hybrid; Strikwerda and Stoelhorst (2009) write of the wider multidimensional organization; public administration has the one-stop shop.

Hybrid here means customer fronts and product backs, not the hybrid structure entry.

Works cited

On this page, “read” means read by this series: where a line says a work, or part of one, was not read, the series did not read it.

Back to the explorer