Question 4 of 7: The Normative Process and the Technical Process in Community Planning

Question 4: The Normative Process and the Technical Process in Community Planning (20 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

Community planning weaves together two different kinds of activity: deciding what the community should become and value (the normative process) and working out how to get there in a rigorous, factual way (the technical process). A sound plan needs both, and the planner’s craft lies in relating them.

The normative process. The normative process is concerned with values, ends and goals — with what ought to be. It asks what kind of community the residents want: what quality of life, what vision, what goals and objectives, what is desirable and in the public interest. It is inherently political and value-laden: because reasonable people disagree about ends, the normative process is worked out through public participation, debate, consultation and political decision — visioning exercises, community goals workshops, public hearings, and ultimately adoption by an elected council. Its outputs are the vision, goals, objectives and policies that give the plan its direction. The planner facilitates and informs this process but does not own its conclusions; the community and its elected representatives do.

The technical process. The technical process is concerned with facts, means and methods — with what is and what can be done. It is the rational, professional, analytical side of planning: gathering and analysing data (population and economic projections, land-supply and land-use inventories, environmental and infrastructure studies), forecasting, generating and evaluating alternative plans against the community’s goals, and designing the means of implementation. It rests on the planner’s professional expertise and on objective, replicable methods, and it supplies the factual and analytical foundation on which good value-choices can be made. Its outputs are surveys, analyses, projections, alternatives and evaluations — the evidence base and the technically-worked options.

The differences between the two. The contrast is essentially ends versus means, values versus facts:

• Question asked: normative — “what should we do / what do we want?”; technical — “what is the situation and how can we achieve it?”
• Nature: normative is value-based, subjective and political; technical is fact-based, objective and professional.
• Who decides / who leads: normative is led by the community and elected council (planner facilitates); technical is led by the professional planner and technical staff (council receives and directs).
• Basis of legitimacy: normative rests on democratic consent and the public interest; technical rests on expertise, evidence and method.
• Outputs: normative → vision, goals, objectives, policies; technical → data, projections, analysis, alternatives, evaluations, design.

The two are interdependent and iterative, not separate stages: the normative process sets the goals against which the technical process evaluates alternatives, and the technical process supplies the facts and options that make the community’s value-choices realistic and informed. Planning goes wrong when they are confused — when technicians impose value-choices under the guise of “objective” analysis (technocracy), or when goals are set with no factual grounding. The rational planning cycle (goals → survey/analysis → alternatives → evaluation → adoption → implementation → monitoring) deliberately interleaves the normative steps (goal-setting, adoption) with the technical steps (survey, analysis, evaluation).