Skip to content

Policy Design

The structured activity of crafting an authorised rule for a target population of intentional agents inside an institution, factored into six separable components — frame, goal, target, instrument, implementation, evaluation — so failure can be localized to a slot rather than pronounced globally.

Core Idea

Policy design is the structured activity of crafting an authorised rule or programme, applied to a target population of intentional agents within an institution, to change a social outcome. Its canonical skeleton is six-part: problem framing, goal specification, target population, instrument choice, implementation pathway, and an evaluation-and-feedback loop. The activity is reflective — the designer must anticipate gaming, distributional effects, and the political economy of sustaining the rule, including the implementation gap between rule-as-written and rule-as-enforced.

Scope of Application

Policy design lives wherever its defining triad holds — an institution issuing an authorised rule to intentional agents who can adapt.

  • Public policy and government — the home turf: tax codes, welfare, environmental regulation, public health.
  • Corporate policy — HR rules, compliance regimes, code-of-conduct design, internal incentives.
  • Educational institutions — discipline, grading, and accommodations policy over strategic students and staff.
  • NGO and international development — aid conditionality and programme design at agencies and foundations.
  • Standards bodies and self-regulation — industry codes over member agents who can game or avoid them.

Clarity

Treating policy as a designed artifact with six separable components makes failure diagnosable rather than mysterious. Without the factoring, a policy that does not work invites the undifferentiated verdict "it failed," which points nowhere. Naming the six lets the analyst ask which component broke, and localize the fix there. The distinction it sharpens most is the implementation gap — rule as written versus rule as enforced — which folk reasoning collapses by treating authorisation as accomplishment.

Manages Complexity

A policy is the meeting point of four bodies of reasoning — substantive, instrument, implementation, and political theory — that a working rule must get right at once. Confronted whole, that is an intractable tangle returning one verdict that points nowhere. The six-part skeleton factors it into separately-diagnosable components, converting "did it work?" into "where, in the chain from frame to feedback, did it break?" Each component answers to a different expertise, so the factoring also routes each question to the right judgment.

Abstract Reasoning

Policy design licenses a diagnostic move — localizing a break to a component, with the implementation-gap inference from "authorized but inert" to "the gap is in enforcement." It licenses an interventionist move — instrument choice as a prediction about adaptive response, and target-population construction as a prediction about coalition durability. It draws boundary lines routing each question to its expertise and bounding scope to intentional agents. And it fixes an order-of-events design sequence.

Knowledge Transfer

Policy design's substrate is any authorised rule applied to intentional agents inside an institution, and within it the six-part skeleton transfers as mechanism — the vocabulary and diagnostics carry across public, corporate, educational, NGO, and standards settings because the agents, coalition, and enforcement route are preserved. Beyond that substrate ("ecological policy," an RL "policy") it is metaphor. The genuinely portable structure lives in the component primes it composes — mechanism_design, experimental_design, stakeholder_analysis, institution, institutional_lag — which carry the cross-domain lesson.

Relationships to Other Abstractions

Local relationship map for Policy DesignParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Policy DesignDOMAINPrime abstraction: Experimental Design — is part of, typicalExperimentalDesignPRIMEPrime abstraction: Mechanism Design — is part ofMechanism DesignPRIMEPrime abstraction: Stakeholder Analysis — is part ofStakeholderAnalysisPRIMEPrime abstraction: Institution — presupposesInstitutionPRIME

Current abstraction Policy Design Domain-specific

Parents (4) — more general patterns this builds on

  • Policy Design is part of, typical Experimental Design Prime

    Policy evaluation typically contains an experimental-design discipline for attributing observed effects to the intervention.

  • Policy Design presupposes Institution Prime

    An authorized policy exists only inside an institution whose rules, roles, and enforcement expectations make it binding.

  • Policy Design is part of Mechanism Design Prime

    Rule engineering for adaptive, self-interested agents is the operative instrument-design constituent of policy design.

  • Policy Design is part of Stakeholder Analysis Prime

    Identifying affected, authorizing, implementing, and resisting parties is a constituent of the target-population and political-economy slots.

Hierarchy paths (7) — routes to 6 parentless roots

Neighborhood in Abstraction Space

Policy Design sits in a sparse region of the domain-specific corpus (65th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Public Choice & Policy Failure (5 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12