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
Portfolio
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
01 · Right of withdrawal
The right to undo a purchase
The consumer has 14 days to cancel any online purchase without giving a reason. The amended directive now requires an active withdrawal function, not just a policy link, in the post-purchase interface. Most interfaces do not provide it.
Browse
Acquisition mode — legal node absent
- The intentional browser Scanning options, building preference
- The aspirational self Projecting desire onto the product
- The market participant Responding to price, promotion, scarcity
- The rights-holder Withdrawal right exists absent
No legal archetypes are active here, and this is appropriate. The ecosystem is correctly configured for browsing. The absence of the legal node at this stage reveals where and how it eventually surfaces.
Nothing to redesign at this stage. The gap is downstream.
Product page
High intent — disclosed but not received
- The evaluating agent Processing product info, reviews, fit
- The committed self Investment building toward purchase
- The conversion target Responding to interface optimised for sale
- The informed consumer 14-day right in footer link or small print
- The deadline-holder 14-day window not yet relevant absent
The legal archetype is present but weightless. The cognitive archetype is directed at the product. Disclosure is occurring; comprehension is not.
The right is disclosed at the moment of highest purchase intent, the state least receptive to legal information.
Checkout
Completion mode — disclosure met, function absent
- The overloaded agent Managing payment, address, delivery
- The completion-seeker Strong drive to finish the transaction
- The converting customer Interface minimises friction toward payment
- The acknowledged rights-holder Right referenced; disclosure legally met
- The future returner 14-day window does not yet exist absent
Disclosure is met. The cognitive archetype is at maximum load. The legal information lands in a hostile ecosystem state and is processed by no active archetype.
Disclosure does not equal function. Checkout satisfies the information requirement. The withdrawal function belongs in the post-purchase ecosystem.
Post-purchase
Where the law places its obligation
- The evaluating owner Assessing product against expectation
- The uncertain or disappointed self Post-purchase dissonance; desire to correct
- The deadline-holder 14-day clock running; deadline not shown
- The active rights-holder Withdrawal function required here, absent in most interfaces absent
The ecosystem has completely changed. The clock is running. The consumer is evaluating a product they own. The withdrawal function the directive requires to be here is absent.
Dir. 2023/2673 is explicit: the withdrawal function must be in the account area or on relevant pages, not a footer link. The temporal archetype must also be activated: the consumer needs to see not just that they can withdraw, but when that right expires.
Withdrawal
The symmetry test
- The problem-solver under pressure Navigating an unfamiliar flow under deadline
- The frustrated consumer Friction is experienced as injustice here
- The deadline-holder Urgency is high; hours or days remaining
- The rights-exerciser Attempting to exercise a right the interface resists
- The asymmetric interface Withdrawal harder than purchase by design absent
The ecosystem is now the inverse of purchase. The law requires withdrawal to be as easy as purchase. The footer link fails this test on every dimension.
The symmetry principle: if purchase took two clicks and a primary button, withdrawal must take the same. The interface structurally opposed to this is not merely poor UX. It is non-compliant.
Active artifact — footer link vs. withdrawal function
In ecosystem terms the withdrawal button is an active artifact, a designed object that performs the consumer’s right. Its absence from the order view is not a UX omission. It is the ecosystem refusing to activate a node the law requires to be present.
Current state — fails the standard
The node is present, but its weight is near zero. A footer link signals administrative content. The user who wants to withdraw must know to look there, navigate past unrelated links, and work through a policy page. The symmetry test is not met.
Required state — directive standard
The active artifact is doing its work. The withdrawal function is contextual, in the order view, with a live deadline. The button carries the same action register as the purchase button. Symmetry of effort.
Active artifact
The withdrawal button is a legal actor. When absent, the right cannot be exercised. When present with a deadline counter, it performs the law’s symmetry requirement on behalf of the consumer, making the safe action the natural one.
The trader shall ensure that the consumer can exercise the right of withdrawal by means of a clearly labelled withdrawal function placed in the consumer’s account area or on any other relevant page.
- 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.