ARCH9090 Chap.2 Planning an Engagement Process
Planning an Engagement Process
A defensible engagement process starts with an upcoming decision and a current information need. This chapter follows the taught sequence from objectives and existing research through publics, method design, collection, interpretation, reporting and evaluation. It distinguishes visible outputs from meaningful outcomes and shows how an evaluation question should be planned before delivery, when the design can still change.
What this chapter covers
- 01
Turning a broad topic into a decision-centred engagement aim
- 02
Why the timing of an information need matters to the design
- 03
Existing research and contextual evidence before primary collection
- 04
The sequence from publics and methods through analysis and reporting
- 05
Outputs such as events and response counts versus outcomes such as influence
- 06
Evaluation questions that test reach, evidence quality and decision use
Worked example · free
Plan engagement for a civic-square redesign
- 1Define the decision: choose evening uses and safety changes before the option shortlist is fixed. Marks used in this worked drill are AskSia's practice weighting and are not a published University mark allocation.
- 1State the evidence need: valued activities and conditions that prevent people from staying after dusk.
- 1Map publics and fixed constraints, including safety requirements that participants cannot change.
- 1Choose complementary activities for patterns, spatial barriers and reasons.
- 1Plan reporting and evaluation around reach, access, evidence depth and option influence.
Key terms
- Engagement aim
- A statement connecting the decision, information need, timing and intended public influence.
- Process output
- A delivered activity or product such as a workshop, response set or report.
- Process outcome
- A change in knowledge, options, relationships or decisions produced by engagement.
- Evaluation question
- A planned question used to judge whether the process achieved its stated purpose and promise.
Planning an Engagement Process FAQ
What should be written before choosing a method?
Write the decision, why evidence is needed now, what participants can influence, who may hold relevant knowledge and what constraints are fixed. This short design frame prevents a preferred technique from driving the project without a clear use.
How are outputs different from outcomes?
Outputs are delivered items such as events, responses and graphics. Outcomes concern what was learned, who influenced the options and how the decision changed. A busy engagement can produce many outputs while failing to reach relevant publics or affect the decision.
When should evaluation be planned?
Before delivery. Planning it early clarifies what evidence of success will be needed and allows the process to change. An aim about excluded users requires measures of reach, safety and decision influence, not only an attendance total collected at the end.
What belongs in a process decision log?
Record the decision being supported, why information is needed now, the public promise, method choices, assigned responsibilities, changes made during delivery and reasons for those changes. Add the evidence needed for evaluation and the date when influence closes.
This log is the team’s traceability record, allowing the final reflection to explain how design affected reach, data and interpretation instead of relying on a vague memory that an activity worked well. Include a named owner and review date so the learning record can trigger a decision, rather than remaining an unassigned observation after delivery.
Assessment move
Take one broad prompt and repeatedly narrow it until it contains a real decision, timeframe, information need and influence boundary. Map the seven process moves on one page, leaving room beside each for evidence and responsibility. For every method you consider, draw an arrow back to the information need and forward to the planned analysis.
Practise classifying project measures as outputs or outcomes; response totals, sessions and documents are outputs, while learning, option change and visible influence are outcomes. Draft one evaluation question before each exercise and decide how the team would answer it. In the assessed project, maintain a decision log recording why a stage was designed as it was.
That record becomes evidence for the final report’s reflective discussion rather than relying on memory after collection. Extend the process map with decision dates, owners and dependencies. A method scheduled after the option shortlist closes cannot influence that shortlist, even if the activity is participatory.
For each stage, write the risk created if it fails: weak existing research can produce redundant questions, incomplete public mapping can distort recruitment, and absent analysis planning can leave rich material unused. Test the process by tracing one fictional participant from invitation through feedback.
The path should show what information they receive, what choice they make, how their contribution is handled and when they learn the outcome. Build a small evidence plan for evaluation that covers reach, accessibility, data quality and influence, not just attendance. When the process changes under time pressure, update the aim and promise instead of pretending the original design was delivered.
These habits give the final reflective section specific decisions to analyse and prevent evaluation from becoming a list of feelings about whether the event seemed successful.