BUS 6513 Module 3 Systems Thinking and Ambidexterity Analysis Example

Feedback Loops That Starve the New: Systems Thinking, Ambidexterity and IBM's Emerging Business Opportunities

Student Name

American College of Education

BUS6513: Innovation Theory and Organizational Practice

Module 3 Assignment

Instructor Name

February 12, 2029

Introduction

The Polaroid analysis in the previous module showed a capable firm whose beliefs and allocation process stalled a promising innovation. Explanations at the level of individual decisions, however, leave a question open: why do the same patterns recur across firms, industries and decades? Systems thinking answers by looking at the structure of feedback that produces behavior over time. This paper applies systems thinking and organizational ambidexterity to innovation. It maps the feedback loops that tend to starve new ventures inside established firms, draws on research on capability traps and examines how IBM designed its Emerging Business Opportunities program to interrupt those loops.

Why a Systems View

Sterman (2000) argued that managers routinely misjudge dynamic systems because cause and effect are separated in time and space, feedback is often hidden and short-term responses can worsen long-term results. Senge (1990) made a similar case for managers, describing recurring structures such as fixes that fail and shifting the burden, in which a quick solution relieves a symptom while weakening the capacity for a fundamental one. Innovation inside established firms has these properties. The returns to a new venture come years after the costs, while the returns to the existing business arrive every quarter, so a decision rule that looks sensible each quarter can starve the future.

The Exploitation Loop

The first structure is a reinforcing loop around the core business. Investment in existing products produces predictable returns, those returns build confidence and budget for further investment in the same products and the organization's skills and routines deepen around them. March (1991) described this self-reinforcing tendency as a source of competence traps, in which improving performance in current activities makes exploration look less attractive. The loop is healthy in a stable market and dangerous in a changing one, because each turn makes the firm better at what it already does and less able to do something different.

The Starvation Loop

A second, balancing loop acts on new ventures. A new business begins small, with low revenue and uncertain margins. When it competes for resources against established units on the same financial criteria, it receives less funding than it needs, which slows its growth, which keeps its numbers small and confirms the judgment that it deserves little support. Christensen and Bower (1996) documented this dynamic in the disk drive industry. The loop does not require anyone to oppose the venture; it emerges from applying reasonable rules uniformly to businesses at different stages.

Capability Traps

Repenning and Sterman (2002) uncovered a related structure in plants trying to improve their processes. When performance fell short, managers pushed people to work harder, which raised output quickly but left less time for improvement, so capability eroded and the gap returned. Supervisors then blamed the recurring gap on lax employees instead of on the way the work was organized, and that reading appeared to justify still more pressure. The same trap applies to innovation: when the core business is under pressure, leaders pull people and money from exploratory work to meet near-term targets, and the firm's capacity to renew itself declines just when it is most needed.

Ambidexterity as a System Intervention

Seen through this lens, ambidexterity is not only an organizational design but an intervention in the feedback structure. O'Reilly and Tushman (2013) described structural ambidexterity as separating exploratory units with their own processes and culture while integrating them at the senior level. Separation weakens the starvation loop by removing the new venture from direct competition on the core business's metrics. Integration at the top prevents the opposite failure, in which the separated unit loses access to the parent's assets and knowledge. The test of any ambidextrous design is whether it changes the loops or merely moves the venture to a different box on the chart.

IBM's Emerging Business Opportunities

O'Reilly et al. (2009) describe how IBM responded to an internal review around 1999 that found it had repeatedly missed new businesses, despite strong research, because its management system emphasized short-term results and the needs of existing customers. In 2000, IBM created the Emerging Business Opportunities process. Selected ventures, in areas such as life sciences, Linux and pervasive computing, received dedicated funding outside the business units' budgets, an experienced senior leader as champion and oversight by a corporate team. Ventures were reviewed monthly against milestones suited to their stage, such as customer pilots and partnerships, rather than revenue and margin targets.

How the Program Changed the Loops

Each feature of the program acted on a loop. Separate funding broke the link between a venture's small current revenue and its next budget, weakening the starvation loop. Stage-appropriate milestones replaced the core business's financial measures, so ventures were judged on learning and market validation rather than early profit. Experienced champions, often moved from running large businesses, brought credibility and access to the parent's assets, supplying the integration that ambidexterity requires. Regular corporate review made it harder to raid exploratory budgets during short-term pressure, guarding against the capability trap. O'Reilly et al. (2009) report that several ventures grew into substantial businesses and were moved into the mainstream units once established.

A Test Against Polaroid

Applying the same model to Polaroid clarifies what IBM did differently. Polaroid separated its electronic imaging group, but proposals were still judged against the razor and blade logic, so the starvation loop continued inside a new box. It had no protected budget rule, so when instant film revenue fell in the 1990s, pressure on the core business competed directly with digital investment, the pattern of a capability trap. IBM's program changed the evaluation criteria, the funding source and the review process together, which is why it altered behavior where Polaroid's separation did not.

Limits of the IBM Approach

The program also shows limits. It depended on sustained attention from senior executives, which is scarce and can shift with leadership changes. It was designed for a very large firm with the resources to fund many ventures at once; smaller firms cannot easily create a separate pool. And moving successful ventures back into business units reintroduces the exploitation loop, since the venture is then judged by the unit's metrics. A systems view suggests these limits are structural: any intervention that relies on executive attention will weaken as that attention moves, unless the new rules become embedded in budgeting and review processes.

Implications for Leaders

Four implications follow for leaders seeking innovation in established organizations. First, map the feedback loops that govern funding and attention before designing structures, because structures that leave the loops intact will not hold. Second, protect exploratory budgets with explicit rules, such as a fixed share of investment, so that short-term pressure cannot drain them quietly. Third, judge new ventures by stage-appropriate milestones and change the measures as they mature. Fourth, provide integration through senior sponsors who can share the parent's assets without imposing its logic, the failure observed at Polaroid.

Conclusion

Systems thinking explains why established firms repeatedly starve innovation: a reinforcing loop deepens commitment to the core business, a balancing loop keeps new ventures small and capability traps drain exploration under pressure. Ambidexterity works when it changes these loops, not merely the organization chart. IBM's Emerging Business Opportunities program did so through separate funding, stage-appropriate milestones, senior champions and corporate review, though its dependence on executive attention and the return of ventures to business units reveal limits. The next module turns to the ethical and societal dimensions of innovation decisions.

References

Christensen, C. M., & Bower, J. L. (1996). Customer power, strategic investment, and the failure of leading firms. Strategic Management Journal, 17(3), 197-218. https://doi.org/10.1002/(sici)1097-0266(199603)17:3<197::aid-smj804>3.0.co;2-u

March, J. G. (1991). Exploration and exploitation in organizational learning. Organization Science, 2(1), 71-87. https://doi.org/10.1287/orsc.2.1.71

O'Reilly, C. A., III, & Tushman, M. L. (2013). Organizational ambidexterity: Past, present, and future. Academy of Management Perspectives, 27(4), 324-338. https://doi.org/10.5465/amp.2013.0025

O'Reilly, C. A., III, Harreld, J. B., & Tushman, M. L. (2009). Organizational ambidexterity: IBM and emerging business opportunities. California Management Review, 51(4), 75-99. https://doi.org/10.2307/41166506

Repenning, N. P., & Sterman, J. D. (2002). Capability traps and self-confirming attribution errors in the dynamics of process improvement. Administrative Science Quarterly, 47(2), 265-295. https://doi.org/10.2307/3094806

Senge, P. M. (1990). The fifth discipline: The art and practice of the learning organization. Doubleday.

Sterman, J. D. (2000). Business dynamics: Systems thinking and modeling for a complex world. Irwin/McGraw-Hill.