10. Organizational Structure, Design and GovernanceIntroduction and ContextOrganizational structure is the formal pattern through which work is divided, authority is allocated, information flows, and activities are coordinated. Organizational design is the deliberate process of choosing and adapting that pattern in relation to strategy, technology, institutional conditions, and environmental uncertainty. Governance concerns the systems through which organizational purposes are directed, decisions are authorized, performance is monitored, and accountability is maintained. These ideas are central to leadership and organizational behavior because structure is not merely an arrangement shown on an organization chart. It shapes who can speak, who must wait, whose knowledge is recognized, how conflict is resolved, and whether people experience their work as controlled, coordinated, or empowering. A structure may support strategic execution, or it may silently undermine it. For example, a firm that competes through rapid innovation but requires multiple hierarchical approvals has created a strategic contradiction between its competitive intention and its administrative design. At doctoral level, structure should be examined as both an organizational capability and a social system. Formal rules coexist with informal networks, professional identities, political interests, and technological infrastructures. The central managerial question is therefore not whether one structure is universally superior, but whether authority, coordination, control, and accountability are appropriately aligned with the organization's strategy and environment. Learning ObjectivesBy the end of this chapter, the reader should be able to: 1. Explain the concepts of organizational structure, design, governance, bureaucracy, differentiation, integration, centralization, and decentralization. 2. Evaluate classical, contingency, network, ecosystem, and agile perspectives on organizing. 3. Analyze the fit between structure, strategy, environment, technology, and organizational capabilities. 4. Distinguish formal authority from informal influence and recognize the behavioral consequences of each. 5. Design governance and coordination arrangements for complex, digital, multinational, and interorganizational settings. 6. Critically assess the risks, ethical implications, and limitations of alternative structural forms. The Architecture of OrganizingA structure answers several interdependent questions: What work must be performed? How will tasks be grouped? Who has decision rights? How will units coordinate? What information must be visible? How will performance be controlled? A useful analysis therefore goes beyond identifying whether an organization is “tall” or “flat.” It examines at least five dimensions. Division of labor refers to the distribution of tasks among individuals, teams, professions, or units. Specialization can improve efficiency and expertise, but excessive specialization may create narrow identities and fragmented responsibility. Departmentalization is the grouping of work by function, product, customer, geography, process, or project. Hierarchy establishes vertical relationships of authority and reporting. Formalization refers to the extent to which behavior is governed by written rules, procedures, roles, and records. Coordination mechanisms connect differentiated activities so that the organization acts coherently. Structure also has a cognitive dimension. It determines which problems become visible and which are treated as someone else’s responsibility. A sales unit may see customer dissatisfaction, while an operations unit sees capacity constraints and a finance unit sees margin erosion. Without integrative mechanisms, each perspective may be locally rational but collectively damaging. Bureaucracy: Discipline and ConstraintMax Weber’s ideal type of bureaucracy emphasized clearly defined jurisdictions, hierarchical authority, formal rules, impersonal decision-making, technical competence, and written records. Bureaucracy is often criticized as synonymous with rigidity, yet its original logic was to replace arbitrary personal authority with predictable and rule-based administration. In public agencies, hospitals, universities, and large corporations, standardized procedures can protect fairness, continuity, safety, and accountability. The problem is not bureaucracy as such, but bureaucratic dysfunction. Rules may become ends in themselves, employees may protect departmental boundaries, and decision-making may favor procedural compliance over substantive outcomes. “Goal displacement” occurs when conformity to a process is treated as success even when the underlying objective is not achieved. Bureaucracy also tends to privilege information that is formally documented, potentially marginalizing experiential or tacit knowledge. A mature governance approach does not attempt to eliminate all bureaucracy. It distinguishes controls that protect mission, rights, safety, and integrity from controls that merely preserve historical habits. The question is whether rules are proportionate, reviewable, and connected to organizational purpose. Strategy and ContingencyClassical structural thinking often searched for universal principles, such as unity of command or an appropriate span of control. Contingency theory challenged this search by arguing that the effectiveness of a structure depends on its fit with contextual conditions. Relevant contingencies include environmental uncertainty, technological complexity, organizational size, life-cycle stage, regulatory intensity, geographic dispersion, and strategic priorities. A stable environment with repetitive operations may benefit from standardization, specialized departments, and centralized planning. An uncertain environment requiring experimentation may require lateral communication, distributed authority, multifunctional teams, and rapid feedback. Neither condition automatically determines one structure; rather, it changes the costs and benefits of alternative designs. The concept of strategic fit should be treated dynamically. A structure that fits a current strategy can become a source of inertia when the strategy changes. Moreover, organizations frequently require ambidexterity: the ability to pursue efficiency in established operations while exploring uncertain opportunities. This may require differentiated subunits with different controls, connected by senior-level integration and resource-allocation mechanisms. Differentiation and IntegrationLawrence and Lorsch’s differentiation–integration perspective remains useful for understanding complex organizations. Differentiation occurs when units develop distinct goals, time horizons, languages, and orientations. Research and development may emphasize long-term technical possibilities, manufacturing may prioritize reliability and cost, and marketing may focus on customer responsiveness. Differentiation can create expertise, but it also increases the need for integration. Integration refers to the quality of collaboration across differentiated units. It may be achieved through hierarchy, formal planning, liaison roles, integrator positions, cross-functional teams, shared information systems, common objectives, or organizational routines. Integration is not simply more communication. Effective integration requires that relevant parties possess authority, incentives, information, and time to resolve interdependencies. A useful diagnostic asks four questions: - Where are the organization’s critical interdependencies?
- Which decisions require joint knowledge?
- Are coordination mechanisms located close enough to the work?
- Do performance measures reward collective outcomes or only departmental results?
Matrix structures illustrate the trade-off. Employees may report to both a functional manager and a product or project manager. The matrix preserves professional expertise while supporting product or customer integration. However, it can produce role ambiguity, conflict over priorities, and decision delays. Its success depends on clear decision rights, mature conflict-management norms, and leaders who can negotiate rather than rely solely on positional authority. Centralization, Decentralization, and Decision RightsCentralization concentrates decision authority at higher levels; decentralization distributes authority to lower levels, business units, professional groups, or frontline employees. These are not absolute conditions. An organization may centralize capital allocation and risk policy while decentralizing customer-service decisions. It may also decentralize operational choices but centralize data standards and cybersecurity requirements. Centralization can produce consistency, economies of scale, and stronger control over enterprise-wide risks. Its costs include slower responses, reduced ownership, and the loss of local knowledge. Decentralization can improve responsiveness, learning, and motivation, but may produce duplication, inconsistent standards, and fragmented risk exposure. The appropriate question is: Who possesses the information required for a decision, who bears its consequences, and who must be accountable for it? Decision rights should generally be placed where information and consequences are sufficiently connected, while strategic boundaries and escalation rules remain explicit. Decentralization without capability, information, or accountability is not empowerment; it is abandonment. Leaders should distinguish decision authority from decision participation. Employees may contribute information without possessing final authority. Conversely, delegated authority is meaningful only when resources, discretion, and protection from arbitrary reversal accompany it. Governance documents should clarify who recommends, who decides, who executes, who reviews, and who is consulted. Structural Forms Beyond the Functional HierarchyThe functional structure groups activities such as finance, operations, marketing, and human resources. It supports specialization and economies of scale, but can create silo behavior. The divisional structure groups work by product, market, geography, or customer. It increases responsiveness and accountability for results but may duplicate expertise and encourage competition among divisions. The multidivisional form uses relatively autonomous divisions under a corporate center. The center typically governs portfolio strategy, capital allocation, leadership succession, risk, and shared capabilities. Its effectiveness depends on avoiding both excessive intervention and passive oversight. The matrix combines two or more bases of grouping. It is appropriate where multiple dimensions—such as product and geography—are strategically important. Its coordination demands are high, and formal structure cannot substitute for relational competence. Project-based and team-based structures organize work around temporary or continuing missions. They are valuable for innovation, consulting, engineering, and complex service delivery. Their risks include unstable identity, knowledge loss between projects, and uncertainty over career development. Boundaryless and modular organizations retain a relatively small core while relying on external partners, platforms, contractors, or specialized providers. Modularity can increase flexibility, but it makes relational governance, contractual clarity, data protection, and supplier resilience essential. Networks, Ecosystems, and Platform GovernanceA network is a pattern of relatively durable relationships among organizational units or independent organizations. Unlike a hierarchy, a network coordinates through reciprocity, trust, contracts, standards, reputation, and negotiated exchange. Networks are valuable when no single organization possesses all the knowledge or resources required to create value. An ecosystem is broader than a bilateral network. It consists of interdependent actors whose contributions jointly shape a value proposition, often around a platform, standard, technology, or shared market. Participants may include firms, regulators, complementors, users, communities, and civil-society organizations. Ecosystem leadership involves orchestrating rather than simply commanding. The orchestrator must establish participation rules, manage conflicts, protect fairness, and decide how value and data are distributed. Digital platforms intensify governance questions. A platform owner may control access, ranking algorithms, technical standards, identity systems, and dispute processes. These decisions can create significant economic and social power even when the platform does not employ all participants. Platform governance therefore requires transparency, due process, privacy protection, cybersecurity, and safeguards against discriminatory or exploitative practices. Networks are not automatically democratic or efficient. They may conceal power asymmetries, transfer risk to weaker partners, and make accountability ambiguous. A network agreement should specify responsibilities, escalation procedures, information rights, audit access, intellectual-property arrangements, termination conditions, and mechanisms for resolving harm. Agile and Adaptive FormsAgile organizing is commonly associated with iterative work, short feedback cycles, customer or user collaboration, empowered teams, and continuous adjustment. Its deeper significance is structural: authority moves closer to knowledge, work is organized around outcomes rather than narrow functions, and learning is embedded in execution. Agile does not mean the absence of planning, leadership, or governance. Effective agile organizations use lightweight but explicit guardrails. Teams may control methods and sequencing while senior leaders define strategic priorities, ethical boundaries, investment limits, and risk tolerances. Product owners, technical leads, portfolio forums, and communities of practice provide integration without recreating a heavy hierarchy. Agile forms can fail when “empowerment” is rhetorical, when teams lack access to users or data, or when priorities change so frequently that employees experience constant disruption. They can also reproduce hierarchy informally through expertise, charisma, or control of information. Leaders must therefore monitor not only speed, but also quality, inclusion, sustainability, and accountability. Governance as Direction, Control, and AccountabilityCorporate governance concerns the relationships among owners, boards, executives, managers, employees, regulators, and other stakeholders. It addresses how organizational purpose is defined, how executives are supervised, how risks are controlled, and how affected parties can hold decision-makers accountable. Governance is not limited to the boardroom; it operates through policies, committees, delegated authorities, audits, professional codes, information systems, and everyday managerial practices. Agency theory emphasizes the problem that managers may pursue interests different from those of owners or principals. Monitoring, incentives, independent oversight, and disclosure are typical responses. Stewardship theory offers a contrasting possibility: managers may be intrinsically committed to organizational and collective purposes, making trust and autonomy productive. Stakeholder perspectives argue that governance must consider parties affected by organizational activity, not only capital providers. These theories should not be treated as mutually exclusive prescriptions. Different risks and institutional contexts may require combinations of trust, monitoring, participation, and formal accountability. Excessive surveillance can undermine intrinsic motivation, while unexamined trust can permit abuse. Good governance creates transparent expectations, proportionate controls, meaningful challenge, and mechanisms for correction. A governance system should address: - purpose and strategic direction;
- allocation of decision rights;
- risk appetite and internal controls;
- performance measurement and reporting;
- conflicts of interest;
- stakeholder voice and remedy;
- succession and capability;
- ethical conduct and legal compliance.
Designing Structure: A Strategic MethodStructural design should begin with the organization’s value-creation logic rather than with an inherited organization chart. The following sequence is useful for diagnosis and redesign. First, clarify strategic priorities and critical outcomes. A cost-leadership strategy, an innovation strategy, and a reliability-critical public service require different coordination patterns. Second, map the work system: major processes, dependencies, knowledge requirements, customer interfaces, and points of failure. Third, identify environmental demands, including uncertainty, regulation, technological change, stakeholder diversity, and geographic dispersion. Fourth, locate differentiation. Determine where specialized expertise, distinct time horizons, or local adaptation are necessary. Fifth, design integration mechanisms around the most consequential interdependencies. Sixth, allocate decision rights according to information, consequences, capability, and risk. Seventh, align incentives, metrics, technology, and human-resource practices with the intended structure. Finally, establish review mechanisms because structure must evolve as strategy and conditions change. A redesign should be evaluated through multiple lenses. Efficiency asks whether resources are used economically. Effectiveness asks whether strategic outcomes are achieved. Resilience asks whether the organization can absorb disruption. Legitimacy asks whether decisions are regarded as fair and acceptable. Learning asks whether the design generates knowledge and adaptation. A structure that performs well on one dimension may fail on another. Practical and Professional ApplicationsIn healthcare, structure must integrate clinical expertise, patient-flow coordination, professional autonomy, safety protocols, and regulatory accountability. In universities, collegial governance coexists with administrative hierarchy, creating recurring tensions over expertise, resource allocation, and strategic control. In multinational enterprises, global integration must be balanced with local responsiveness and institutional differences. In public administration, formal authority is constrained by law, democratic accountability, and public value. For technology firms, product teams may require autonomy, but architecture, privacy, security, and responsible-use standards must be governed across teams. In supply chains, the focal organization may not control every participant, making contractual, relational, and data-based governance essential. In family enterprises, ownership, management, and family authority can overlap, requiring explicit role separation and succession governance. Useful diagnostic indicators include decision-cycle time, number of approval layers, cross-unit handoff failures, duplicated activity, unresolved escalations, employee perceptions of role clarity, customer response time, audit findings, and the distribution of strategic versus operational decisions. These measures should be interpreted rather than used mechanically. A reduction in approval time may signal empowerment, or it may indicate weakened control. Illustrative Case: Northstar Mobility’s Structural DilemmaBackgroundNorthstar Mobility is a fictional manufacturer and service provider of urban electric-transport systems. It has grown from a specialist engineering firm into a multinational organization offering vehicles, charging infrastructure, software, and maintenance services. Its historical structure is functional: engineering, manufacturing, sales, finance, and service report to global executives. SituationNorthstar’s strategy now depends on integrated solutions rather than vehicle sales alone. Customers want hardware, software, charging access, and maintenance from one provider. However, major proposals require approval from several functions. Engineering optimizes technical performance, sales negotiates customized commitments, manufacturing protects production stability, and software operates on a different development cycle. Projects frequently exceed timelines because no executive owns the complete customer outcome. AnalysisThe organization has substantial differentiation but inadequate integration. Its functional structure remains efficient for professional specialization, yet the competitive offering has become cross-functional and ecosystem-based. Centralized technical and financial controls are valuable because safety, cybersecurity, and capital risk are significant. At the same time, customer-solution decisions require authority closer to market knowledge. The problem is therefore not simply “too much hierarchy.” It is a misalignment between the unit of accountability and the unit of value creation. Northstar measures functions primarily on their own budgets and outputs, while customers evaluate the integrated solution. ApproachNorthstar establishes customer-solution business units responsible for defined market segments. These units receive authority over solution design, prioritization, and customer commitments within risk and investment boundaries. Functional departments remain responsible for professional standards, talent development, technical architecture, and enterprise capabilities. Cross-functional product teams use iterative development methods, while a portfolio governance council allocates major investment and resolves conflicts. The company also creates common data standards, a cybersecurity review process, and an escalation protocol. Performance measures combine functional excellence with solution-level indicators such as delivery reliability, customer adoption, lifecycle profitability, and safety performance. Leaders are trained in integrative negotiation because the new design depends on influence across reporting lines. OutcomeThe redesign reduces duplicated negotiations and clarifies who owns customer outcomes. It does not eliminate conflict; rather, conflict becomes more visible and is addressed through agreed forums and decision rights. Some managers initially resist the loss of unilateral functional control. The transition therefore includes role clarification, revised incentives, and periodic governance reviews. Learning PointsNorthstar illustrates five principles. First, structure should follow the organization’s value-creation logic. Second, differentiation creates a corresponding need for integration. Third, decentralization should operate within explicit enterprise guardrails. Fourth, agile teams require governance rather than managerial absence. Finally, structural change succeeds only when metrics, incentives, information, and leadership behavior reinforce it. Risks, Limitations, and Ethical ConsiderationsStructural redesign often fails because leaders treat it as a chart-drawing exercise. New reporting lines do not resolve conflicting incentives, inadequate capabilities, poor information, or mistrust. Another common mistake is copying fashionable forms—such as agile squads or platform ecosystems—without understanding the work and governance conditions that make them viable. Ambiguity can be productive when it supports experimentation, but excessive ambiguity creates anxiety, duplicated work, and accountability gaps. Informal networks may accelerate problem-solving, yet they can exclude newcomers and reproduce gendered, racial, professional, or status-based inequalities. Decentralization can empower local actors while also shifting risk to employees or contractors who lack resources to manage it. Ethical governance requires attention to who benefits from structural choices and who bears their costs. Algorithmic allocation, automated performance monitoring, and platform ranking may intensify managerial control while appearing neutral. Organizations should assess privacy, explainability, bias, contestability, labor conditions, and the right to challenge consequential decisions. Whistleblowing channels, independent review, documented rationale, and protection from retaliation are important safeguards. Governance must also address structural corruption risks: conflicts of interest, concentrated authority, opaque procurement, weak segregation of duties, and incentive systems that reward harmful outcomes. Compliance is a minimum standard; responsible governance asks whether the organization’s design encourages people to act with integrity when rules do not provide a complete answer. Emerging DevelopmentsSeveral developments are reshaping organizational design. Artificial intelligence can automate coordination, forecasting, scheduling, and monitoring, but it may also centralize decision power in data and model owners. Hybrid and geographically distributed work require organizations to design for asynchronous communication, digital visibility, trust, and equitable access to informal knowledge. Ecosystem competition is increasing the importance of standards, interoperability, data rights, and multi-party accountability. Organizations are also experimenting with more fluid talent arrangements, internal talent marketplaces, product operating models, and mission-oriented teams. These forms may improve adaptability, but they complicate employment relationships, career paths, professional identity, and managerial responsibility. The emerging design challenge is to combine adaptability with institutional memory, human dignity, and dependable accountability. Best Practices for Leaders and DesignersEffective structural leadership rests on disciplined diagnosis. Leaders should: 1. Begin with strategy, work, stakeholders, and risk rather than fashionable labels. 2. Make decision rights explicit and test whether authority matches information and accountability. 3. Design integration around real interdependencies, not around assumptions that communication alone will solve coordination problems. 4. Use centralization for standards, shared capabilities, and enterprise risks where consistency matters. 5. Use decentralization where local knowledge, speed, and ownership create value. 6. Align incentives and measures with collective outcomes. 7. Preserve independent challenge, audit, and ethical escalation. 8. Review structures periodically and treat redesign as an ongoing learning process. Chapter SummaryOrganizational structure distributes work, authority, information, and accountability; organizational design aligns these elements with strategy and context; governance provides direction, control, oversight, and legitimacy. Bureaucracy can provide fairness and reliability but may produce rigidity and goal displacement. Contingency theory emphasizes fit among structure, environment, technology, and strategy. Differentiation creates expertise and specialization, while integration connects units whose work is interdependent. Centralization and decentralization are choices about decision rights rather than absolute organizational categories. Functional, divisional, matrix, project, network, ecosystem, and agile forms each involve distinctive trade-offs. Networks and platforms require governance beyond hierarchy, including rules for participation, data, risk, accountability, and value distribution. Effective structural design begins with value creation, maps interdependencies, allocates authority carefully, aligns incentives and technology, and incorporates review. Ethical design must consider power, inclusion, privacy, surveillance, stakeholder voice, and the possibility of harm. Key TermsOrganizational structure: The formal arrangement of roles, units, authority, and coordination. Organizational design: The deliberate shaping and adaptation of organizational arrangements to achieve purpose. Governance: Systems of direction, oversight, control, accountability, and stakeholder responsibility. Bureaucracy: A rule-based administrative system characterized by hierarchy, specialization, formal procedures, and records. Formalization: The extent to which behavior and decisions are governed by explicit rules and procedures. Centralization: Concentration of decision authority at higher organizational levels. Decentralization: Distribution of decision authority across lower levels, units, or teams. Differentiation: Development of distinct tasks, orientations, expertise, or units within an organization. Integration: Mechanisms that coordinate differentiated activities and reconcile interdependencies. Strategic fit: Alignment among organizational structure, strategy, environment, technology, and capabilities. Contingency theory: The view that organizational effectiveness depends on contextual conditions rather than universal structural principles. Matrix structure: A design combining two or more bases of grouping, usually with multiple reporting relationships. Network organization: An arrangement coordinated through relationships among relatively autonomous actors. Ecosystem: An interdependent collection of organizations and stakeholders jointly shaping value creation. Platform governance: Rules and processes governing participation, access, data, standards, and conduct on a platform. Agile organizing: An adaptive form emphasizing empowered teams, iterative work, feedback, and rapid learning. Decision rights: Explicit authority to recommend, decide, execute, review, or challenge an action. Ambidexterity: The capability to pursue operational efficiency while exploring new opportunities. Formal authority: Legitimate power attached to an organizational role or position. Informal influence: Capacity to shape decisions through expertise, relationships, reputation, or control of information. Review QuestionsShort Answer Questions1. How does organizational design differ from an organization chart? 2. What are two benefits and two dysfunctions associated with bureaucracy? 3. Why does differentiation increase the need for integration? 4. Distinguish centralization from decentralization using the concept of decision rights. 5. What makes governance in an ecosystem different from governance in a hierarchy? Long Answer Questions1. Critically evaluate the relevance of contingency theory for designing organizations in uncertain environments. 2. Compare functional, divisional, matrix, and project-based structures, including their coordination requirements. 3. Explain how governance can combine monitoring, trust, stakeholder participation, and accountability. 4. Analyze the conditions under which agile organizing can improve performance and the conditions under which it may fail. 5. Develop a structural-design method for an organization whose strategy is shifting from product sales to integrated solutions. Analytical / Application Questions1. A regulated financial-services firm wants to decentralize customer decisions while maintaining enterprise-wide risk control. Design an authority and governance arrangement and justify it. 2. A university has strong disciplinary departments but weak collaboration on interdisciplinary programs. Diagnose the differentiation–integration problem and propose mechanisms to address it. 3. An online platform relies on independent providers whose livelihoods depend on algorithmic rankings. Analyze the platform’s governance risks and recommend ethical safeguards. 22. Multiple Choice Questions with AnswersQuestion 1Which structural condition most directly creates a need for integration? A. High differentiation among units with interdependent work B. A complete absence of specialization C. The elimination of formal accountability D. The concentration of all decisions in one manager Correct Answer: A. High differentiation among units with interdependent work Question 2A firm centralizes cybersecurity standards but allows regional units to adapt customer-service processes. This illustrates that: A. Centralization and decentralization can coexist across different decision domains B. Decentralization always eliminates organizational control C. Centralization requires every decision to be made at headquarters D. Regional adaptation is incompatible with enterprise governance Correct Answer: A. Centralization and decentralization can coexist across different decision domains Question 3Which feature is most characteristic of Weber’s ideal-type bureaucracy? A. Personal loyalty as the primary basis of authority B. Undefined responsibilities and informal decision-making C. Formal rules, hierarchical authority, and technical competence D. Complete absence of written records Correct Answer: C. Formal rules, hierarchical authority, and technical competence Question 4Northstar Mobility’s main structural problem in the case is best described as: A. Excessive professional specialization without any market strategy B. A mismatch between functional accountability and integrated customer value creation C. Too much decentralization of cybersecurity decisions D. The absence of any formal departments Correct Answer: B. A mismatch between functional accountability and integrated customer value creation Question 5What is the strongest rationale for locating a decision close to frontline employees? A. Frontline employees should never be monitored B. They may possess relevant local information and face immediate consequences of the decision C. Senior leaders cannot be held accountable for decentralized decisions D. Local decisions automatically reduce all organizational risk Correct Answer: B. They may possess relevant local information and face immediate consequences of the decision Question 6Which statement best distinguishes a network from a traditional hierarchy? A. A network coordinates only through employment contracts B. A network relies substantially on relationships, reciprocity, contracts, and negotiated exchange C. A network eliminates the need for accountability D. A network requires all participants to report to one executive Correct Answer: B. A network relies substantially on relationships, reciprocity, contracts, and negotiated exchange Question 7An agile organization with empowered teams still needs governance primarily to: A. Remove all discretion from teams B. Define strategic priorities, risk boundaries, ethical standards, and escalation rules C. Replace iterative learning with annual approvals D. Ensure that every technical decision is made by the board Correct Answer: B. Define strategic priorities, risk boundaries, ethical standards, and escalation rules Question 8Which governance risk is especially associated with a powerful digital platform? A. The platform has no ability to establish standards B. Access, ranking, data, and dispute decisions may be opaque or unfair C. Participants are always more powerful than the platform owner D. Digital platforms cannot affect labor conditions Correct Answer: B. Access, ranking, data, and dispute decisions may be opaque or unfair Question 9What does organizational ambidexterity refer to? A. Using two unrelated organization charts at the same time B. Pursuing efficiency in existing operations while exploring new opportunities C. Eliminating all formal structures during innovation D. Centralizing exploration and decentralizing every routine task Correct Answer: B. Pursuing efficiency in existing operations while exploring new opportunities Question 10Which redesign practice is most likely to produce only superficial structural change? A. Aligning incentives, information, and metrics with new decision rights B. Mapping interdependencies before assigning authority C. Changing reporting lines without addressing incentives, capabilities, or coordination routines D. Establishing review mechanisms for evolving conditions Correct Answer: C. Changing reporting lines without addressing incentives, capabilities, or coordination routines
|