Decision-Process Analysis

When Consensus Is Not the Problem

The governance pattern is familiar to anyone who has followed space rule-making for more than a few years. A problem is widely acknowledged. A rough consensus on the needed response takes shape among technical experts and in the better-prepared delegations. Years pass. Working groups meet. Language is drafted and redrafted. Decisions are referred and reviewed. And still the binding outcome does not arrive, or arrives so long after the problem has evolved that the binding text governs conditions that no longer exist.

The instinctive diagnosis is substantive disagreement. Someone must be blocking; some interest must be misaligned. Sometimes that is true. Often it is not. A significant share of the time, the technical consensus really is broad and the interests really are not deeply opposed, and yet the outcome does not form. The explanation lies not in the content of the decision but in its process — in the architecture through which issues become outcomes. Decision-process analysis is the method that takes this architecture seriously. It asks who decides, at what stage, with what mandate, through which veto points, and whether the formal process matches the informal one. Applied well, it can reveal that the binding constraint on a stalled decision is not who disagrees but how the procedure is structured.

Three Frameworks, One Analytical Impulse

The method’s intellectual inheritance is ecumenical. It draws on three distinct traditions that converged, through the last decades of the twentieth century, into a shared analytical discipline about decision architecture.

The first is John Kingdon’s multiple streams framework, developed in Agendas, Alternatives, and Public Policies (1984). Kingdon argued that policy change occurs when three independent streams — problems, policies, and politics — couple at a policy window, and that analyzing the streams separately is essential for understanding why policy does not change despite apparent consensus in any single stream. A problem can be widely recognized, a solution can be widely available, and the political stream can still be misaligned. Kingdon’s tradition taught analysts to disaggregate what the casual observer fuses.

The second is George Tsebelis’ veto player theory, developed through the 1990s and formalized in Veto Players: How Political Institutions Work (2002). Tsebelis showed that the structure of a political system — the number of institutional actors whose agreement is required for change, and the distance between their preferences — directly determines how much policy stability the system exhibits. Systems with many veto players produce stable policies; systems with few produce volatile ones. For international bodies that operate by consensus, every member is effectively a veto player, and the number of veto players alone explains much of the tempo of multilateral decision-making without requiring reference to any substantive disagreement.

The third is Graham Allison’s models of decision-making, canonized in Essence of Decision (1971), which analyzed the Cuban missile crisis through three lenses: the rational actor model, the organizational process model, and the bureaucratic politics model. Allison’s contribution was to insist that foreign policy decisions cannot be understood by assuming states reason as unitary rational actors. Standard operating procedures, organizational interests, and intra-governmental bargaining shape outcomes independently of any coherent national interest, and an analyst who sees only the rational-actor model will misread the process systematically.

Decision-process analysis as a method consolidates these inheritances. From Kingdon it takes the discipline of separating problem, policy, and political streams. From Tsebelis it takes the veto-player inventory and the analytical weight placed on decision rules. From Allison it takes the insistence that formal process is an incomplete account and that organizational and bureaucratic layers must be traced. Institutionalist process tracing — the detailed reconstruction of how a decision actually unfolded — is the evidentiary method that binds the three together.

Inheritance Core contribution Analytical move it supplies
Kingdon (multiple streams) Problems, policies, politics as independent streams Disaggregate what casual observation fuses
Tsebelis (veto players) Decision rules and actor-preference distance Inventory veto points and weight them
Allison (three models) Rational actor, organizational process, bureaucratic politics Trace organizational and intra-government layers
Process tracing Detailed reconstruction of enacted decisions Evidence the informal layer against the formal

Where the Method’s Value Concentrates

The characteristic move of decision-process analysis is to separate the formal from the actual. The formal process is what the treaty, charter, or statute says happens: committees meet, drafts circulate, votes are taken, instruments are adopted. The actual process is what produces the outcome: the pre-negotiations that set the draft before the formal session, the bilateral bargaining that pre-commits key delegations, the organizational routines that determine which text the committee chair places on the table, and the budget gates whose procedural innocence conceals their substantive force.

The gap between the formal and the actual is where the method’s analytical value sits. An analysis that describes only the formal process and stops has produced a flowchart. An analysis that describes only the informal dynamics, without the formal scaffolding, has produced gossip. The method requires both, and the comparison between them is the source of the findings.

The operation begins with defining the decision itself: what is being decided, what instrument produces the outcome (regulation, treaty, standard, allocation, license), and where the process currently sits (pending, in progress, concluded). Without this scoping, the analysis diffuses into a general description of institutional behavior.

The formal architecture is then mapped: which body has authority, what decision rule applies, what stages exist, and who participates with what standing at each stage. This is the flowchart. It is a necessary artifact but not a sufficient one.

Veto points are located next. At each stage, the analyst identifies who can block progress: unanimity requirements, ratification gates, budget approvals, technical review hurdles. The inventory is only half complete at this point. The other half asks whether each formal veto holder has the will and capacity to exercise the block, not only the formal right. An unanimity rule makes every member a veto player formally; in practice some members would never block, while others would block on specific issues, and a few sit in positions where the threat to block is as strategically useful as the actual blocking.

The informal layer is then traced. The analyst compares the formal process with how decisions actually unfold: pre-negotiations, backchannels, issue-linkage across domains, agenda control, side payments. In international space governance, much of the substantive work occurs in intersessional working groups where a handful of delegations effectively control drafting, and in bilateral conversations that pre-commit major parties before formal sessions open. An analyst who reads only the formal minutes misses the layer where the decision is actually formed.

Allison’s bureaucratic politics lens is applied next: organizational interests, standard operating procedures, and bargaining positions that drive outcomes independently of the formal process. Space policy in particular is marked by organizational routines — budget cycles, procurement calendars, industrial partnerships — that impose schedules on decisions the substantive timetable does not call for.

Constraints and enabling conditions are then surfaced: legal precedents, treaty obligations, technical feasibility, budget limitations, political windows, crisis pressures. These are the boundary conditions that expand or contract the space of possible decisions, often without being visible in the formal procedure.

Finally, the analyst diagnoses process pathologies. The method identifies a short list of characteristic failure modes, and the diagnosis is consequential because different pathologies suggest different interventions. A fragmentation pathology is not solved by pushing harder on any one track; a speed-mismatch pathology is not solved by more consensus-building. Naming the pathology precisely is how the analyst makes the output policy-usable.

Gridlock
Decisions that cannot form because veto players are stable and their preferences do not converge. No amount of further substantive work breaks the stall.
Capture
Processes dominated by narrow interests, producing outcomes tilted toward a small set of participants even where the formal procedure is open.
Opacity
Processes whose closure prevents informed external pressure, shielding the decision from the scrutiny that would surface flaws.
Fragmentation
Decisions distributed across bodies with no coordinated precedence, producing overlapping or contradictory outputs rather than a coherent instrument.
Speed mismatch
Processes whose tempo cannot track the phenomenon they regulate. Guidance arrives governing conditions that no longer exist.

Debris Mitigation, Read Through the Process

Consider the multi-decade evolution of international space debris mitigation guidelines. The formal architecture is well-known. The UN Committee on the Peaceful Uses of Outer Space (COPUOS) has a Scientific and Technical Subcommittee that drafts technical text by consensus; the full Committee adopts; the UN General Assembly’s Fourth Committee endorses through resolution. The decision rule throughout is consensus, which gives every member implicit veto power.

A formal reading ends here. A decision-process reading continues. Pre-negotiation occurs in intersessional working groups, where a small number of delegations with dedicated staff and technical depth carry most of the drafting load. Bilateral coordination among major launching states happens before formal sessions. When draft language reaches the Subcommittee, it has already been substantially shaped by actors whose influence is invisible in the formal attendance list.

The diagnosis at the pathology level is revealing. The process is not failing primarily because of substantive disagreement; on core mitigation principles, the technical consensus has held for decades. It is not failing primarily from capture; a reasonably wide set of delegations participate, and the technical community is well-represented. It is not primarily fragmentation, since COPUOS has held its position as the primary multilateral forum for technical guidelines. The dominant pathology is speed mismatch. The consensus cycle moves on annual timescales. Commercial space activity — especially constellation deployment, on-orbit servicing, and the rapid evolution of operator populations — moves on monthly or even shorter timescales. A process that can update its guidelines every few years cannot track a phenomenon whose governance needs evolve within a year.

The process map produces a non-obvious policy finding. The binding constraint on more effective debris governance is not, primarily, the need for deeper consensus or more technical work. It is the tempo of the process itself. Interventions aimed at the substantive layer — more working group meetings, more technical papers, more harmonized national positions — do not address the binding constraint. Interventions aimed at the procedural layer — parallel fast-track instruments for emergent issues, intersessional decision-making authority for narrow updates, recognized industry-body standards that can move faster than the Committee — do. The analyst who produces this reading has given the practitioner a specific handle on a problem that substantive analysis alone would have described only as “governance is slow.”

The Method’s Usefulness, and Its Blind Spots

Decision-process analysis is strongest when it surfaces procedural constraints that substantive analysis misses. It is essential for diagnosing why a decision has stalled, distorted, or produced unexpected outcomes, and for identifying windows of opportunity in ongoing processes. In multi-body environments like space governance — where COPUOS, ITU, national regulators, and industry consortia hold overlapping jurisdictions — mapping the process architecture is often the prerequisite for any serious strategy.

Its limits are real. Actual decision processes are often opaque, particularly internationally. Reconstructing them requires triangulation among public records, expert accounts, and whatever post-hoc reflections are available; the reconstruction carries uncertainty that the analyst should flag explicitly. Multi-body, multi-track processes common in space governance are extremely complex to map, and the honest response is to scope the analysis to the most consequential track while acknowledging the tracks excluded.

The method can miss the role of raw power and external shocks. A procedural analysis can produce a careful pathology diagnosis and still be overridden by a major power’s unilateral move or by a crisis that collapses the normal procedure. Pairing with realist power analysis guards against overreading the process when raw power is doing the work.

The analysis is specific to the decision cycle in question. A process map accurate for one instrument does not necessarily generalize to the next, even in the same body, because committee chairs, key delegations, and agenda conditions change. The temporal boundary of the analysis should be explicit.

For emerging space issues — certain space resources questions, some on-orbit services governance — the formal decision process is itself incomplete or nonexistent. The method’s response is not to abandon the analysis but to note the absence of structure as itself a finding. A governance problem lacking any established decision process has a characteristic pathology all its own, and the analyst should name it directly.

Within the library, decision-process analysis feeds stakeholder mapping by grounding influence assessments in procedural standing, specifies the internal mechanics of whatever policy cycle stage the issue occupies, defines the interaction space that game-theoretic modeling can then formalize, and supplies red-team analysis with the vulnerabilities in the decision architecture available for adversarial stress-testing.

A Note for the Practitioner