User-engagement techniques in programming: gaming, simulation, and squatters

One-line orientation

Gaming uses role-playing or scenarios to uncover user needs. Simulation uses a mathematical or computer model to test consequences. Squatters are intensive work sessions usually held at the project site.

Key points

• Gaming technique: engages end users in role-playing or an imagined scenario to reveal how they expect to use the space. Physical pieces may support the exercise, but they are not required. The value is the discussion and the user needs it uncovers, not a finished layout.
• Simulation: uses a mathematical or computer model to test a process, such as emergency evacuation in high-rise buildings. Used to validate the adequacy of design elements and to develop emergency plans.
• Squatters technique: the programming team holds intensive, preplanned work sessions, usually at the project site, to gather information and get immediate feedback. A remote site may make the technique especially useful, but remoteness is not its definition. It is a charrette format originated by CRS / Peña, the same lineage as the five-step Problem Seeking method.
• Baseline gathering still applies: these techniques supplement, not replace, the standard Information Request work — client data collection, site analysis, site visits, and user interviews.

Confusions / comparison

	Gaming	Simulation	Squatters
Who is involved	End users (role-playing)	Computer program (+ programmer)	The programming team, on-site with the client
Medium	Role-playing or imagined scenarios; pieces are optional	Mathematical or computer model of a function	Intensive work sessions, usually on site
Purpose	Visualize intended use; build discussion and consensus	Validate design-element adequacy; develop emergency plans	Concentrated information gathering + immediate client feedback when the site is far from the office
Typical exam cue	”Role-playing,” “scenario,” “user needs"	"Model,” “variables,” “test consequences"	"Intensive project-site work sessions”

Related

→ prog-programming-activities (this module): where these techniques sit in the Information Request activity · prog-adjacency-diagrams (this module): the analytic diagrams that document what engagement uncovers · prog-documentation-tools (this module): how gathered input becomes program deliverables.