6.3 Policy Process and Systems Thinking

What Counts as Policy

Policy is a written or unwritten rule that guides decisions, resources, and behavior. It may be a law, ordinance, regulation, school policy, workplace procedure, clinic protocol, funding rule, or organizational practice. Much CHES advocacy happens at organizational and community levels, not only in legislatures — which is why the exam tests procedure and protocol scenarios as often as legislative ones.

The Six Stages of the Policy Process

The policy process is commonly taught as six stages, and the correct advocacy tactic differs at each one:

A frequent exam trap presents a scenario where a policy was adopted but conditions have not changed. The correct answer almost always points to implementation and enforcement, not back to agenda setting.

Systems Thinking

Systems thinking asks how parts interact rather than treating a policy as a single lever. A school physical-activity policy may fail if schedules leave no transition time, teachers lack support, playgrounds are unsafe, and families are uninformed. A clinic screening protocol may fail if the electronic-record prompt is confusing or referrals are unavailable. The visible policy is only one component of the system.

Key systems concepts the exam may test:

• Feedback loops — a walking group that builds social support grows participation (reinforcing); poor lighting that makes early sessions feel unsafe shrinks it (balancing).
• Leverage points — small changes, such as a default healthy option, that shift larger patterns.
• Unintended consequences — a strict snack policy may punish families with limited food budgets; a punitive smoke-free housing policy may raise eviction risk.
• Equity lens — ask how a policy will be experienced by people with the least power.

Adoption Is Not the Endpoint

The single most important exam message in this section: do not treat adoption as the final outcome. The better answer usually includes implementation supports, staff training, communication, monitoring, and evaluation. Ask whether the system changed in ways people can experience — were staff trained, signs posted, forms revised, budgets aligned, and complaint pathways clear? Were barriers reduced for the priority population? These questions connect Area V advocacy directly to Area IV (Evaluation and Research) and keep policy work grounded in measurable practice.

Matching the Level of Change

The level of policy also matters. Some problems require only an internal procedure change; others require funding, regulation, or interagency agreements. Matching the level of change to the barrier keeps advocacy realistic and avoids unnecessary escalation — proposing a new law when a workflow tweak would solve the problem is a wrong answer on the exam.

Health in All Policies and Upstream Thinking

The exam may reference Health in All Policies (HiAP), an approach in which health is considered in decisions made by sectors that are not primarily about health — transportation, housing, education, and zoning. A zoning decision that permits a grocery store in a food desert is a health intervention even though no health agency wrote it. Systems thinking and HiAP push the specialist to look upstream: instead of treating diet-related disease only through education, ask which agricultural subsidies, retail patterns, and built-environment rules shape what food is available.

A useful distinction is downstream, midstream, and upstream action. Downstream addresses individuals already affected (clinical care, behavior change). Midstream addresses risk factors within settings (worksite policies, school environments). Upstream addresses root social and structural determinants (income, housing, policy). Advocacy in Area V concentrates midstream and upstream, where one decision can affect thousands of people at once.

Worked example: a community has high pedestrian-injury rates. A downstream response treats injuries; a midstream response runs a school safety-education program; an upstream response advocates for protected crossings, lower speed limits, and a Complete Streets policy. Systems thinking warns the specialist to anticipate consequences — lowering speed limits without enforcement or design changes rarely works, illustrating why adoption alone does not guarantee impact and why implementation, enforcement, and evaluation must be planned together.

One more concept the exam may probe is the difference between policy, systems, and environmental (PSE) change. Policy change alters rules; systems change alters how an organization or sector operates day to day; environmental change alters physical or social surroundings. A single initiative often combines all three: a school adopts a water-access policy (policy), revises its cafeteria purchasing and scheduling (systems), and installs filling stations (environment).

Recognizing that PSE strategies reinforce one another helps a candidate pick answers that bundle a rule with the operational and physical supports it needs, rather than relying on a rule alone.

Scenario Review Checklist

• Identify the relevant CHES Area of Responsibility.
• Locate the program stage in the scenario.
• Match the answer to evidence, stakeholders, and ethics.
• Reject choices that are premature, unsupported, or outside scope.