Talbot West doctrine

Systemicity

Systemicity is the profile of complexity that makes the realization of purpose non-obvious.

Systemicity describes the interacting forms of complexity that make it non-obvious what an enterprise can achieve, what a particular movement will require, and how its consequences will unfold. Fitness concerns how well enterprises fit that reality through discovery, decision, action, learning, and revision.

Enterprise possibility

Enterprises operate inside a changing field of possibilities.

Every enterprise pursues purposes within a reality it does not fully control. Its present state contains capabilities, constraints, relationships, knowledge, architecture, commitments, and operating conditions that shape what it can do next.

Some possibilities are readily visible. Others become apparent only when the enterprise understands how multiple conditions interact, how a constraint might change, or how existing capabilities could be combined differently.

Systemicity concerns the forms of complexity that make those possibilities—and the requirements for realizing them—more or less obvious to a finite enterprise.

The concept

Systemicity is the profile of complexity that makes purpose non-obvious.

Systemicity describes the interacting complexity in and around a system that stands between a purpose and a clear account of how to realize it.

Interdependence is one part. So are configuration, emergence, thresholds, feedback, history, path dependence, distributed knowledge, adaptation, and change through time. Which forms matter depends on the purpose being pursued and the state of the enterprise.

Systemicity already exists in an operating enterprise before a new initiative begins. A particular move activates portions of that inherited condition, adds new relationships and consequences, and can change the systemicity faced by later moves.

See Addendum A for systemicity’s manifestations, and Addendum C for the distinction from complexity and difficulty.

Representation

Reality modeling concerns what becomes visible to the enterprise.

Before an enterprise can compare alternatives, it must form an account of what is happening and what could happen. That representation shapes the option set.

Under systemic conditions, an apparent constraint may be alterable, a local improvement may depend on another capability, or a valuable option may exist only in a different configuration. A rigorous comparison of the visible options cannot account for a possibility that never became visible.

Reality modeling develops a representation sufficient to discover, construct, and compare possibilities without attempting to reproduce the whole of reality.

Explore reality modeling↗

Rationality and fit

Systemicity can separate rationality from fit.

An enterprise can reason impeccably from the reality available inside its operative model and still fit actual reality poorly. A missing dependency, state change, propagation path, threshold, or possibility can change what the appropriate response would have been without making the response look irrational from inside the existing frame.

Incoherent rationality is reasoning or action that makes sense within the operative model but is materially misfitted to purpose-relevant reality.

As systemicity rises, more consequential reality can remain distributed, hidden, or difficult to compose, increasing the room for rationality and coherence to diverge without the divergence being obvious. Sophistication does not remove this problem. Better analysis improves the reasoning applied to a model; it does not guarantee that the model contains the reality that would change the answer.

Through realization

Systemicity remains present through realization.

A decision does not end systemicity. Implementation changes enterprise state, distributes work across specialized actors, and creates new interactions among systems, people, incentives, and constraints.

Results can also be difficult to interpret. Effects arrive at different times and in different places, other conditions change concurrently, and the intervention itself can alter the system that later evidence is meant to explain.

Incoherence is misfit between enterprise aims and reality. Avoidable incoherence is the portion of that misfit for which materially better fit was reasonably attainable. Value leakage concerns the reasonably attainable value lost through consequential avoidable incoherence. Both occur throughout discovery, decision, implementation, and learning—including within initiatives that meet their stated targets.

Explore incoherence↗Explore value leakage↗

See Addendum B for systemicity across the full realization cycle.

Related discipline

Coherence concerns fit between purpose and reality.

Coherence is fit between enterprise aims and actual purpose-relevant reality. Systemicity describes why that fit can be difficult to establish and preserve.

What was reasonably knowable or attainable governs whether incoherence was avoidable; it does not redefine the reality the enterprise actually fit or failed to fit.

Enterprises already produce substantial coherence through leadership, expertise, analysis, coordination, architecture, and operating discipline. But the presence of those components does not establish that they compose into the required function, and successful composition does not establish fit to the purpose at hand. A pile of parts does not make a 747; a perfectly assembled 747 is still the wrong vehicle for a fishing expedition.

A coherence discipline makes explicit the work of preserving what materially matters as the enterprise forms possibilities, compares paths, commits, implements, observes, and revises.

Different forms of systemicity call for different responses. Some can be reduced through modularity, dependable interfaces, clearer authority, or better representations. Others must be carried through the movement by preserving material relationships and updating the enterprise’s understanding as conditions change.

Coherence does not mean maximum integration, coordination, or centralization. It means fit with reality for the purpose at hand, maintained as the enterprise acts and learns.

Explore fitness↗Explore AI, systemicity, and coherence↗

Addenda

Further development of the concept.

The addenda develop systemicity’s manifestations, how it appears through realization, its distinction from complexity and difficulty, and related scholarship.

Addendum A

How systemicity makes value difficult to discern

Systemicity is not a single mechanism. It can arise through interdependence, configuration, thresholds, feedback, adaptation, history, sequence, distributed knowledge, and change through time. Different forms matter in different situations, and they often interact.

The operating enterprise already contains these conditions before any new initiative begins. A move can activate some of them, create additional relationships, and alter the state faced by later moves. External change can alter the same landscape independently.

The following sections examine several recurring manifestations and how they affect enterprise possibility and realization.

A01

Discovering which reality matters

An enterprise investigating production delays must determine how far beyond the production line its inquiry needs to extend. Scheduling may reflect commitments made during sales, while those commitments reflect assumptions about product design and supplier performance. Improving the production line alone leaves the causes of delay intact.

Investigators must follow consequential evidence beyond the initial scope. Evidence from one function may establish that improving performance requires intervention elsewhere or across several functions.

An organizational chart establishes responsibility. A project charter establishes scope. Neither establishes which portions of reality determine the result.

A02

Configuration determines what resources produce

The value of a capability depends partly on the conditions surrounding its use. Its interfaces and supporting capabilities determine how effectively the enterprise employs it. Authority and operating practices determine whether that technical potential becomes an actual result.

Consider inventory. The value of holding an additional unit depends on replenishment reliability, demand variation, production flexibility, service commitments, and the cost of a shortage. Changes in those conditions make the same inventory level prudent, wasteful, or inadequate.

Evaluating inventory policy while treating every surrounding condition as fixed excludes opportunities to improve the surrounding system. More reliable replenishment, for example, may allow the company to reduce inventory and improve service simultaneously. The value lies in an arrangement that isolated inventory optimization would never propose.

A03

Capabilities emerge from combinations

A functioning enterprise accomplishes things none of its constituent parts accomplishes independently. How it combines those parts determines the capabilities it possesses and the results it produces.

An enterprise may already possess the ingredients for a valuable capability without having assembled them. Recognizing it requires understanding how those resources would function together and identifying what else the combination needs.

Portfolio economics follow the same logic. An investment with a modest direct return may enable several valuable applications. Appraisals that omit this enabling value understate its return and risk rejecting the investment that makes the applications feasible.

A04

Thresholds defeat simple extrapolation

System behavior need not vary smoothly. In a process with variable arrivals or processing times, queues and delays grow disproportionately as utilization approaches capacity. Growth that once required modest adjustments now demands a different operating response.

Historical averages describe the conditions that produced them. Extrapolating across a threshold conceals the consequences of entering a different operating state.

The same problem affects new capabilities whose performance depends on sufficient supporting infrastructure or participation. Early results provide an incomplete basis for judgment when the enterprise has not yet established the conditions required for productive operation.

A05

Effects propagate beyond their point of origin

A local improvement changes demands on connected operations. When intake limits throughput, automating it releases more cases to downstream teams. Whether the enterprise benefits depends partly on their ability to absorb that volume and resolve exceptions.

Costs and benefits therefore appear in places other than the function making the investment. An assessment confined to that function omits consequences that may dominate the enterprise result.

The pattern of connections also matters. A common platform distributes improvements widely while concentrating exposure to failure. Understanding each application separately leaves that shared exposure poorly represented.

A06

Feedback changes the conditions of action

Enterprises act on systems that respond. A pricing change affects customer behavior, which alters demand and operating conditions. Those conditions then influence later pricing decisions.

Feedback reinforces or counteracts effects over time. Delays complicate judgment because the consequences of earlier actions are still developing when new actions are taken. Repeated adjustments made without accounting for those delays risk producing instability.

The enterprise must understand how its own conduct helps produce the conditions it observes. Otherwise it risks strengthening the mechanism causing a problem or abandoning a useful intervention before its effects become visible.

A07

Other actors pursue purposes of their own

Employees, customers, suppliers, and competitors interpret enterprise action through their own interests. Their responses depend on what they want, what they know, and what they expect others to do.

A supplier’s willingness to invest in capacity depends partly on its confidence in the commercial relationship. A procurement change that improves immediate purchasing terms may weaken that confidence and reduce the supplier’s willingness to support future expansion.

Those responses belong inside the enterprise’s understanding of the decision. Formal terms describe only part of the relationship; expectations and incentives influence what the parties actually do.

A08

History shapes present possibilities

Enterprises inherit architecture, skills, contracts, relationships, and operating routines. These accumulated conditions make some improvements readily attainable and others expensive or impractical.

History also conceals the sources of current performance. An experienced scheduler may use informal supplier relationships to resolve exceptions before they interrupt production. A formal process description records the schedule but omits the interventions that make it dependable.

A redesign that removes those interventions without replacing their function undermines the reliability it sought to improve. Investigation must explain how the enterprise succeeds as well as why it fails.

A09

Sequence determines which futures remain attainable

Commitments change the starting conditions for later commitments. An investment that establishes shared infrastructure or expertise improves the feasibility and economics of subsequent applications. A commitment that creates restrictive dependencies narrows the enterprise’s later choices.

The same nominal investments made in different orders therefore produce different intermediate states and potentially different outcomes. Comparing their standalone returns does not establish the most valuable sequence.

Migration demands and temporary operating arrangements consume resources before the intended benefits arrive. A strategy must account for those costs and establish a viable route through the intermediate states.

A10

The environment changes during the pursuit

Markets and technologies evolve while enterprises investigate and implement. A previously unattractive opportunity becomes feasible, or an approved investment loses its advantage. Different parts of the enterprise and its environment change at different rates.

New capabilities can expand the range of actions worth considering, while changes in markets, suppliers, technologies, regulation, and supporting infrastructure can alter the merits of existing approaches.

The enterprise must keep evaluating both its progress and the changing conditions that determine its value. A plan approved under earlier conditions needs a mechanism for incorporating consequential new evidence.

A11

The manifestations compound

These properties rarely operate independently. A commitment creates dependencies that shape how the enterprise responds to technological change. The response alters employee behavior, which affects performance and the evidence available for later decisions.

Understanding those effects separately is insufficient when their interaction determines the result. The enterprise needs an account of how they operate together, at enough depth to recognize valuable possibilities and pursue them effectively.

Addendum B

Systemicity throughout realization

B01

Directing attention

Current reports and targets direct attention toward what the enterprise already measures. Opportunities outside that representation struggle to enter consideration, even when they bear directly on the company’s performance.

Coherence begins by relating attention back to enterprise aims. Investigation must expose consequential conditions omitted from the current understanding, including opportunities that lack an established owner or familiar category.

B02

Forming possibilities

Developing a possibility into a credible option requires explaining how the enterprise could realize it from its actual position.

Systemicity complicates that process. Relevant knowledge resides in different specialties, and combining it requires resolving incompatible assumptions or descriptions. A proposal may look infeasible until operating knowledge reveals a way around a constraint that the financial or technical assessment treated as fixed.

Reality modeling develops these possibilities far enough for meaningful comparison. A stronger option set improves the basis for every subsequent commitment.

B03

Comparing and committing

An enterprise must assess alternatives under their actual requirements and consequences. Standalone returns often exclude enabling value or effects on future capabilities, especially when those benefits belong to other functions or later investments.

Coherent judgment connects a proposed commitment to the enterprise’s aims and the conditions required for its value. It compares the commitment with credible alternatives and investigates consequential assumptions before resources become difficult to redirect.

B04

Configuring and implementing

A decision becomes real through changes in how the enterprise operates. Responsibility passes among people and functions, creating repeated opportunities to lose the reasoning behind the commitment.

A team optimizing implementation cost may remove a capability that justified the investment. If the team knows only the specification, it has little basis for recognizing that consequence.

Coherence gives implementers enough understanding to preserve the requirements of value and to recognize when practical discoveries warrant revising the approach.

B05

Observing and interpreting

An outcome rarely explains its own causes. Reported improvement may depend on temporary conditions or additional effort elsewhere. Benefits and costs often appear at different times, complicating early assessments.

Observation must test whether the expected mechanisms are operating. Understanding what produced a favorable metric helps the enterprise judge whether the improvement will persist and whether the approach will work elsewhere.

B06

Learning and revising

Implementation produces evidence about the enterprise’s original understanding. That evidence should inform both the current undertaking and later decisions.

When teams lose the connection between decision reasoning and operating evidence, they struggle to identify which assumptions held and which failed. Later teams repeat the investigation or inherit conclusions without understanding their limits.

Coherence practice preserves that connection and assigns responsibility for acting on the findings. Learning then changes both the enterprise’s understanding and its conduct.

Read the fuller treatment of reality modeling↗

Addendum C

Systemicity, complexity, and difficulty

Imagine assembling a 747.

The aircraft is extraordinarily complex. Construction requires many parts, precise tolerances, specialist skills, and extensive coordination. It is also difficult, expensive, and time-consuming.

Now suppose you have complete, correct schematics, verified assembly procedures, exact interface specifications, and clear tests at each stage. You also have the equipment and expertise needed to follow them.

Engineers have already resolved much of the systemic structure and encoded that understanding in the instructions. You still face an enormous task, but you have a dependable account of what to do and how the parts must function together.

Now remove the warehouse indexing system. The instructions identify the parts needed for the next operation, but finding them takes hours. The task becomes much more difficult without a corresponding increase in uncertainty about how to assemble the aircraft.

Finally, remove the schematics and verified procedures. You have the same parts and the same objective, but must discover which arrangements work, which interfaces are compatible, which sequences are viable, and how to determine whether the assembled system will perform safely.

You must now reconstruct the systemic understanding the instructions supplied.

The distinction matters.

Complexity concerns the structure, variation, and intricacy of what is involved. Difficulty concerns the demands of accomplishing it. Systemicity concerns the profile of complexity that makes the realization of purpose non-obvious.

A system can be highly complex yet well understood for a particular purpose; another can be simpler yet systemically demanding because the relevant configuration, dependencies, or path are unclear.

The aircraft’s interdependence remains present even with perfect instructions. The instructions relieve the assembler of having to discover and resolve much of that interdependence. Good representations, tools, interfaces, and accumulated expertise make the undertaking tractable.

The aircraft illustrates only a narrow slice

Even without the manual, this example holds much of reality conveniently still. You know which aircraft you intend to build. Its parts conform to a known design, and assembling them correctly fulfills the objective.

The systemic challenge centers on reconstructing that arrangement and its assembly sequence. An enterprise encounters a much broader problem.

It must determine which capabilities are worth building before it has a design to reconstruct. During development, employees and customers respond to its choices, influencing both what works and what remains worth pursuing. Competitors and technologies evolve independently, changing the value of the intended destination.

A closer enterprise analogy would require deciding what kind of aircraft to build while the available components, prospective passengers, and competing forms of transportation were changing. Building experience would reveal new possibilities, and each commitment would affect which of them remained practical.

The missing manual demonstrates one form of opacity. Enterprise systemicity combines that opacity with emergence, adaptation, changing possibilities, and consequences that feed back into later action.

Return to the fuller account of systemicity’s manifestations.

Addendum D

Related scholarship

Talbot West developed this doctrine through independent inquiry into enterprise value creation. Many of its constituent phenomena have substantial intellectual histories. The works below offer useful treatments of particular mechanisms and neighboring concepts.

Systems, feedback, and regulation

W. Ross Ashby, An Introduction to Cybernetics (1956)

Examines regulation, variety, and the relationship between a system’s possible disturbances and its capacity to respond. It provides useful foundations for considering whether an enterprise has sufficient response capability for the reality it faces.

Read the book

Donella Meadows, Thinking in Systems (2008)

Explains stocks, flows, feedback, delays, and intervention in systems. These mechanisms help explain counterintuitive results and the disproportionate effects of particular interventions.

Publisher’s page

Complexity and decomposition

Herbert A. Simon, “The Architecture of Complexity” (1962)

Examines hierarchy and near-decomposability in complex systems. This is relevant to how enterprises divide responsibility and analysis, and to the conditions under which separately understood parts provide an adequate understanding of the whole.

Read the paper

Rationality, outcome, and correction

Herbert A. Simon, “From Substantive to Procedural Rationality” (1976)

Distinguishes evaluation of behavior relative to goals and conditions from evaluation of the process used to reach it. This is an important neighboring distinction to rationality versus coherence, though Talbot West uses the terms differently.

Source

Carl Spetzler, Hannah Winter, and Jennifer Meyer, Decision Quality (2016)

Separates decision quality from realized outcome under uncertainty: a well-formed decision can still produce a poor outcome, and a poor decision can get lucky. This supports the distinction between quality of treatment and the particular state reality ultimately produces.

Source

Chris Argyris, “Reinforcing Organizational Defensive Routines” (1986)

Describes defensive routines that can become self-reinforcing and make organizational diagnosis and correction harder. This offers a concrete neighboring mechanism for the way an internally sensible organizational treatment can protect itself from disconfirming reality.

Source

Complementarity and configuration

Paul Milgrom and John Roberts, “The Economics of Modern Manufacturing” (1990)

Examines complementarities among manufacturing technologies and organizational choices. It explains why the value of a change depends on coordinated changes elsewhere, with direct implications for investment appraisal.

Read the paper

Modularity and the economics of change

Carliss Y. Baldwin and Kim B. Clark, Design Rules, Volume 1: The Power of Modularity (2000)

Explores how modular architectures alter design, innovation, and economic possibilities. It is relevant to changing the systemic conditions an enterprise faces through dependable interfaces and contained dependencies.

Publisher’s page

Capability and adaptation

David J. Teece, Gary Pisano, and Amy Shuen, “Dynamic Capabilities and Strategic Management” (1997)

Examines how firms integrate, build, and reconfigure competencies in changing environments. It connects to the enterprise’s continuing ability to discover and realize valuable configurations as its circumstances evolve.

Read the paper

The Talbot West synthesis

The Talbot West synthesis treats systemicity as a property of the reality through which enterprise purpose is pursued, not as a synonym for complexity, organizational boundaries, or poor management. Reality modeling concerns how an enterprise develops a sufficiently useful account of that reality. Coherence concerns actual fit with purpose-relevant reality as the enterprise forms possibilities, commits, acts, learns, and revises. Rationality within an operative model can therefore diverge from coherence when systemicity keeps consequential reality outside that model.