Facilitation
Geometries of Use
Geometries of Use is a facilitation page built from service blueprint logic. It does not replace the blueprint. It adds a compact visual language for reading what kind of condition is taking shape in a service moment: access, threshold, interruption, dependency, shelter, exchange, return.
The page is meant to sit between editorial explanation and workshop material. It translates observations from research, case studies, and reflective writing into artefacts that teams can compare, move around, and discuss while a problem is still open enough to be reframed.
Jump to the paired comparison cardsStarter set
Four starting signals for reading entry, continuity, and backstage support before the discussion becomes too abstract.
Framing
From editorial reading to facilitation artefact
The rest of the site already works through close reading: paying attention to how a service moment feels, where a failure mode becomes visible, and what a system quietly asks of a person before anyone names it. This page keeps that tone, but turns it into something teams can use together.
The visual discipline still comes from reduction and seriality rather than from decorative diagramming. The point is not to build an icon library detached from practice, but to give facilitation a stable, discussable set of marks that can sit beside blueprint work, editorial explanation, and applied design thinking.
Facilitation uses
What this page helps a team do
Read the condition, not only the step
A blueprint usually shows where the process goes. These artefacts help a team describe what the moment feels like to move through: blocked, ambiguous, dependent, recoverable, or quietly withheld.
Compare two forces at once
Many problems are not caused by one sign alone. They come from the overlap between access and threshold, or between route and interruption, or between exchange and hidden dependency.
Carry insight into decision-making
The artefacts are meant to support workshops, not decorate them. They give a smaller language for discussing what must change before the team disappears back into generic statements about improvement.
Core artefacts
A working alphabet for facilitation
These are the single artefacts that underpin the page. They are deliberately compact so they can be used in workshops, applied pages, and later design-system documentation without changing their meaning each time they appear.
The set is most useful when teams are mapping a live problem and need shared language quickly. Each artefact names a condition that can then be combined with another one.
Action node
Use when a moment gathers activity, attention, or decision-making and needs to be treated as a focal point.
Indirect access
Use when access exists formally but only becomes real through another actor, space, or condition.
Directed effort
Use when progress is technically possible, but demands disproportionate force, work, or persistence.
Route
Use when the service depends on sequence, ordered movement, or a path that should remain legible over time.
Ambiguity
Use when the person can act, but the meaning of the situation or the right next move remains unclear.
Repeated effort
Use when burden accumulates through small acts that repeat until they become structural friction.
Threshold
Use when the important question is crossing: into a place, into a state, or into the next service condition.
Interruption
Use when continuity breaks and the team needs to locate where recovery becomes difficult or invisible.
Dependency
Use when the visible service relies on backstage support, prior approval, or hidden coordination.
Exchange
Use when value, knowledge, trust, or responsibility passes between actors in a shared service moment.
Shelter
Use when the service must provide pause, reassurance, or a protected space before forward movement resumes.
Return
Use when re-entry, retry, or cyclical movement is not a failure but part of how the service actually works.
Combination cards
Pairs that make service conditions easier to discuss
The paired cards are the most useful facilitation move on the page. They let a group hold two conditions next to each other without collapsing them into one simplified diagnosis.
Each card keeps two SVG artefacts side by side so the comparison stays visual, legible, and stable across desktop and mobile layouts.
Indirect access + Threshold
Use this pair when entry is said to be available, but the real crossing is hidden, delayed, or socially marked. It is the clearest pair for arrival, permission, onboarding, and access questions.
Route + Interruption
Use this pair when a service looks organised on paper but breaks in the lived sequence. It is useful for pressure points, handoffs, and moments where continuity fails under load.
Dependency + Exchange
Use this pair when the visible interaction depends on backstage conditions or another actor carrying the transfer. It helps teams talk about coordination rather than only interface.
Shelter + Return
Use this pair when recovery matters as much as first-pass completion. It helps frame retry, reassurance, and safe re-entry as designed conditions rather than edge cases.
Action node + Repeated effort
Use this pair when a key service moment keeps absorbing small burdens. It is useful for diagnosing where friction collects until a team starts treating it as normal.
Ambiguity + Directed effort
Use this pair when unclear meaning forces the person to work harder simply to keep moving. It is a good facilitation lens for confusion, hesitation, and compensatory effort.
Applied reading
How the artefacts help read a problem or decision
The page is not a detached glossary. Its value comes from being used against real material already present on the site: stories about access, case studies under commercial constraint, and a homepage position that treats facilitation as part of design work rather than an afterthought.
The Shape of Access
This page translates threshold conditions into story. The facilitation value is that a group can move from a vivid narrative of entry to a sharper discussion about who was imagined, who was diverted, and what the environment declared before anyone arrived.
Case-study diagnosis
The case studies show why paired signs matter in practice. Commercial pressure rarely presents as one isolated issue. More often, a route breaks, an exchange becomes overloaded, or dependency stays hidden until the service starts failing in public.
Homepage position
The homepage frames the practice as research, design, and facilitation under real conditions. This specimen page gives that stance a concrete form: artefacts that can be read editorially and then used operationally in a room.
Workshop rhythm
A simple way to use the page in a session
Start with the live moment
Bring one concrete service situation into view first. Ask what the person is trying to do before naming the system around them.
Compare one sign with another
Use a single sign when the condition is clear. Use a pair when the problem depends on tension, overlap, or contradiction between conditions.
Turn the reading into a decision
End the exercise by asking what must change: the threshold, the dependency, the recovery path, the communication, or the visible support around the moment.