Organisms
This page documents only organisms that are live in the active runtime or validated as real specimen parts.
Each section keeps one preview and a short constraint note.
Case Study
Long-form project reading with structured facts, ordered narrative flow, optional media, and related links.
Preview
Case Study
Reducing Cognitive Load During Peak Traffic
The Company approached its holiday campaigns with a clear ambition: convert seasonal traffic into meaningful engagement and confident purchasing decisions.
Earlier campaigns assumed that high holiday intent meant users already understood the product value and needed only visual appeal and refreshed layouts to convert. In reality, users required reassurance, guidance, and clearer differentiation, especially under time pressure.
I led UX research and usability testing across successive holiday campaigns, guiding their evolution from surface-level optimisation toward behaviourally informed experiences.
- Constraint: prose is plain text only in this family; lead, media, and related regions are optional.
Tabbed / Indexed Reader
Stepped reading with indexed navigation, panel content, and optional support rail behavior.
Preview
Tabbed Reader
- Constraint: support-rail content only appears when the renderer maps the authored support fields.
Ecosystem
Scenario reading as a network of actors, tensions, opportunities, and supporting context.
Preview
Ecosystem
Ecosystem Nodes
Safety-critical
Navigating, anticipating hazards, reading signs, and making split-second decisions.
This role demands near-full cognitive bandwidth. Youngblood and Chesluk would flag this as a node under extreme load, one whose demands are not being respected by the ecosystem’s other nodes.
Norm-driven
Engaged in a conversation with social stakes: a work call, a family check-in, a negotiation.
This role carries norms of presence and attentiveness. The physical act of holding the phone signals social engagement, even when technically unnecessary. The ecosystem enacts intimacy through posture.
Affordance pull
A device designed for palm-and-ear use. Its form factor trains users toward a particular posture of engagement.
Even when alternatives exist, the phone’s physical affordances reassert themselves as defaults. In ecosystem terms, this node has strong pull. It recruits behaviour through shape and habit.
Underactivated node
Available, capable, and hands-free, yet often unused.
This node represents latent infrastructure that the ecosystem fails to activate. In Youngblood and Chesluk’s model, a node that exists but is not recruited is a design failure: the ecosystem has not built a pathway that makes this the path of least resistance.
Discoverability gap
Buttons for answer, end, and volume, placed precisely to keep eyes on road and hands on wheel.
A thoughtful design intervention, but in the ecosystem this node is often never learned, or is overridden by habitual phone-reaching. Its potential is blocked by onboarding gaps and habitual inertia.
Weak enforcement
In the UK and many jurisdictions, holding a phone while driving is illegal.
Yet enforcement is inconsistent, and social norms around just a quick call persist. This node exerts pressure on the ecosystem but competes with convenience and social expectation. The ecosystem absorbs legal norms as one input among many, not necessarily the dominant one.
- Constraint: the parser requires scenario content and at least one node.
Law
Legal or regulatory reading as navigable regulation blocks with stages, roles, comparisons, artefacts, and quotes.
Preview
Law
- Constraint: at least one regulation is required; supporting blocks remain optional.
Docs
Section-detail or overview-grid reading through the dedicated az_docs path.
Preview
Docs Layout
Shared structural patterns
Across the live runtime, the most common shared pattern is item-plus-fields. The generic visual parser reads az_item blocks, collects az_field name values, normalizes az_list content into point arrays, and turns az_section or az_substep content into titled body sections. That pattern powers the validated tabbed / indexed reader family.
The docs path uses a narrower grammar. az_docs accepts az_field name=”intro” and az_field name=”body”, a top-level az_list name=”points”, nested az_section blocks, and nested az_example blocks. The docs renderer then decides whether the current page is acting as an overview or as a section detail view.
The case-study family is separate and explicit. It uses az_case_hero, az_case_facts, az_case_fact, az_case_section, az_case_figure, az_case_video, az_case_related, and az_case_link rather than the generic az_item grammar.
- Constraint: docs prose is flattened to text by the parser and does not behave as a rich editorial body.
Facilitation specimen parts
Theme-side facilitation building blocks validated on Geometries of Use.
Preview
Facilitation Specimen
Facilitation
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.
- Constraint: this remains a page-owned specimen, not yet a plugin shortcode family.