Author: Alessandro Zulberti

  • Agentic AI Reading Instrument

    This experiment helps inspect short ideas about agentic AI through fixed critical lenses. Rather than simulating an assistant, it reads where delegation compresses context, assumes capability, and leaves hidden recovery work behind.

    Editorial experiment

    Agentic AI reading instrument

    Paste a short scenario about an AI agent. The page reads it through fixed lenses so you can see where delegation compresses context, hides repair work, or should stop.

    Not a chatbot. Not a feasibility checker. A compact diagnostic.

    Load an example

    Enter one short scenario only. This version reads one agentic situation at a time, not a list, comparison, or instruction prompt.

  • Creating a Seamless Omnichannel Service

    Reducing Fragmentation Between Channels

    Excess Baggage operated luggage storage, insurance, retail, and travel accessory services across 15 international airports and 18 rail stations.

    As customer numbers and spend increased, the organisation committed to digitising its services to support a more coherent omnichannel experience.

    The challenge was not introducing digital touchpoints, but ensuring that online services reduced friction in high-pressure, time-critical airport contexts while integrating cleanly with physical locations and operational systems.

    Challenge

    Several services relied on fragmented booking and operational flows. The online booking process for left luggage and storage, in particular, required unnecessary steps and fields, increasing interaction cost at moments when travellers were already under stress.

    In parallel, new services such as remote baggage check-in, confiscated item return, and excess baggage handling introduced additional complexity across channels.

    The core challenge was to reduce interaction cost for customers while maintaining operational clarity for staff across locations.

    Excess Baggage store in Dubai
    Image Physical service environments shaped the constraints and expectations behind the digital journeys.
    Excess Baggage store in Gatwick
    Image Omnichannel design had to work across physical locations, operational processes, and digital touchpoints.

    Approach

    Optimising the Booking Journey

    The left luggage and storage booking flow was streamlined to reduce unnecessary steps and form fields, with a clear focus on speed, clarity, and predictability.

    Key improvements included:

    – Clearer progression through booking steps

    – Reduced cognitive load during data entry

    – Early visibility of pricing and storage duration

    – Support for post-booking actions such as charge tracking and retrieval reminders

    The goal was not only to improve usability, but to lower interaction cost at scale across multiple locations.

    Service Blueprinting for Omnichannel Alignment

    To support consistency across digital and physical touchpoints, I created service blueprints mapping frontstage user interactions, backstage staff actions, and supporting systems and dependencies.

    In a security-constrained, time-critical environment like airports, service blueprints were essential to align customer-facing flows with staffing, logistics, and physical space constraints that could not be resolved at interface level alone.

    This work exposed misalignments between customer expectations and operational reality, helping teams coordinate changes across departments rather than solving issues in isolation.

    Solutions were typically piloted in a limited number of locations, validated against real operational constraints, and only then scaled across airports and stations.

    Luggage Weight Check

    Problem to Solve

    Passengers often face stress and inconvenience at the airport due to uncertainty about luggage weight, leading to unexpected fees and delays.

    Benefit

    – Save time and avoid unexpected fees

    – Enhance the user experience through an intuitive, multilingual interface

    – Offer a cost-effective service model for airports and airlines

    Feature Set

    – Precise weight measurement

    – Multilingual support in 15+ languages

    – Flexible payment options including NFC and coin payments

    – Cross-selling opportunities for additional airport services

    Luggage weight check interface one
    Image Concept interface for a fast, self-service luggage weight check experience.
    Luggage weight check interface two
    Image Multilingual, time-efficient interactions designed for airport decision-making under pressure.
    Luggage weight check interface three
    Image Service concepts balanced speed, reassurance, and operational practicality.

    Post & Fly Service

    Problem to Solve

    Travellers rushing through airport security with prohibited or restricted items faced a difficult choice: dispose of the items or find a quick, reliable solution.

    Desired Outcome

    Post & Fly was designed to offer a seamless retrieval service through:

    – A streamlined online portal

    – Timely collection and processing by staff

    – A transparent 30-day retrieval timeframe

    UX Methods

    – Empathy mapping

    – User interviews

    – Mental-model analysis

    Post and Fly service interface one
    Image Service concepts focused on reducing stress after confiscation and restoring a sense of control.
    Post and Fly service interface two
    Image Digital touchpoints designed to support retrieval tracking, options, and reassurance.

    Operational Dashboards

    Problem to Solve

    In a fast-paced airport environment, fragmented dashboard experiences can lead to confusion, frustration, and decreased efficiency for both employees and customers.

    Desired Outcome

    – Unify the user experience across services

    – Enhance employee productivity through clearer workflows

    – Optimise for a fast-paced, time-sensitive environment

    Operational dashboard screen one
    Image Dashboard concepts unified service visibility for operational teams.
    Operational dashboard screen two
    Image Internal tools were designed for clarity, speed, and decision-making under operational pressure.
    Operational dashboard screen three
    Image A more consistent internal system reduced fragmentation across services and locations.

  • Clarity in High-Season Sales

    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.

    Challenge

    The initial goal was direct: understand why a visually refined landing page failed to convert during high-stakes holiday moments.

    Usability testing revealed that users were not lost; they were unconvinced. Under time pressure and emotional load, behaviour changed markedly. Users became more risk-averse, scanned less, and relied on quick heuristics.

    These hesitation points reappeared across successive holiday seasons, particularly around uncertainty about product suitability, shipping timing, and gift appropriateness.

    Quantitative data confirmed limited engagement beyond the first scroll. Qualitative sessions explained why: unmet expectations and delayed reassurance.

    Holiday campaign research slide one
    Image Early campaign analysis focused on where visual polish failed to create decision confidence.

    Surface Clarity

    Primary Methods

    – Remote usability testing, including five-second tests

    – Targeted user interviews

    – Scroll-depth and click data analysis

    – Prototype evaluation of new layout variations

    Diagnosing Misalignment Through Usability Testing

    The same pattern emerged repeatedly: users were not confused enough to stop, but not confident enough to convert.

    One participant captured the tension clearly: after filtering, they felt mostly confident they had found the right product, but still worried there might be a better option they had missed.

    Holiday campaign research slide two
    Image Later design directions focused on decision support rather than visual dominance.

    Designing for Decision

    With baseline issues identified, the focus shifted from diagnosis to intentional redesign.

    One design direction was deliberately deprioritised: a visually dominant, hero-first layout that pushed explanatory content further down the page. Testing showed that users needed clearer value framing and decision aids earlier, not more visual emphasis.

    Using behavioural principles, the journey was reshaped to reduce cognitive load, strengthen salience, and align content order with how decisions are made under pressure.

    The landing page evolved from a static presentation into a sequence of deliberate decision moments, separating inspiration from commerce, elevating the Gift Finder, clarifying support pathways, and rewriting copy for rapid scanning.

    Validating in Motion

    Primary Methods

    – Scenario-based usability testing

    – GA4 behavioural data review

    – ContentSquare heatmaps

    – A/B test planning

    – Device-specific observations

    – Feedback analysis from live prototypes

    Real-Time Research During Campaign Rollout

    Before launch, we conducted pre-live validation to refine nuance rather than uncover major flaws.

    At one point, analytics suggested improved click-through on promotional elements. However, usability sessions revealed that many of these clicks were driven by uncertainty rather than true engagement.

    The tension was resolved by restructuring the hierarchy so promotional elements supported, rather than replaced, decision-critical content.

    Reflection

    A small change produced a disproportionate effect: introducing concise, high-salience value statements such as warranty, gifting suitability, and delivery certainty directly above the product grid. This reduced early-journey hesitation and restored confidence.

    This project was not about redesigning a landing page. It was about learning how people decide when attention is fragmented and stakes are high.

    Clarity, in these moments, is not aesthetic. It is functional.

  • Scaling Research for Strategic Decisions

    Embedding Research into Strategic Planning

    The Company is best known for its iconic Swiss Army Knife, but its digital ecosystem had grown into something far more complex: multiple eCommerce platforms, service portals, and brand-led websites operating across markets and systems.

    As the ecosystem expanded, delivery speed increased faster than shared clarity. Platform and feature decisions were increasingly driven by internal opinion, legacy assumptions, and isolated performance metrics. The risk was not slow delivery, but accelerated launches without validating user impact or accessibility implications.

    As a Senior UX Researcher, I worked across product, marketing, engineering, and service to raise UX maturity, integrate research into decision-making, and restore a shared definition of success across platforms.

    Challenge

    The Company was undergoing a major transformation: a move from a monolithic commerce platform to a composable, headless architecture; the launch of new digital platforms; and an ambition to increase eCommerce performance globally.

    At the same time, accessibility requirements were rising, internal ownership was fragmenting, and teams were under pressure to deliver quickly.

    The core challenge was not change itself, but how to make high-impact decisions during change without relying on assumptions, internal opinion, or partial metrics.

    Video Brand film used as contextual reference for the ecosystem and positioning.

    Strategy

    I led a research-led transformation focused on turning fragmented signals into shared evidence, structured around four pillars.

    Continuous Discovery

    I embedded mixed-method research across web properties to surface behavioural friction early and create a steady flow of decision-ready insight.

    Across platforms and over time, one pattern remained consistent: persistent friction around navigation clarity and content hierarchy. Users repeatedly struggled to understand where they were in the journey and how to progress, particularly in product exploration and service flows.

    These observations reinforced that the issue was not visual design, but semantic precision and hierarchy.

    Cross-functional Enablement

    I worked closely with eCommerce, Development, and Marketing to translate research findings into prioritisation inputs, ensuring insights informed roadmap, content, and feature decisions.

    Operationalising Accessibility

    I acted as a point of escalation for digital accessibility, embedding WCAG requirements into delivery processes so compliance became a design and development concern rather than a late audit.

    Platform-First Thinking

    During the SAP Commerce Cloud migration, I supported the evolution of the design system to meet new development constraints, enabling consistency across Community Online, B2B, and brand platforms while preserving flexibility.

    Video Design-system walkthrough used to support platform migration and consistency across releases.

    Execution Highlights

    Revenue Optimisation via UX Research

    I combined behavioural analytics with usability testing on key product subcategories to understand where personalisation and navigation workflows broke down.

    These signals helped distinguish genuine engagement from uncertainty-driven interaction and guided targeted adjustments to structure and content.

    Service Blueprint for Repairs

    I mapped the end-to-end journey for the Repair Service, connecting frontend interactions with backend processes. The service blueprint exposed misalignments between user expectations and internal workflows, creating a shared reference for operational and experience improvements.

    Platform Migration Support

    During the transition to a headless architecture, I partnered with development and content teams to maintain UX coherence across releases. Documentation and design-system updates helped balance speed, branding, and consistency during parallel launches.

    Accessibility as a Cultural Shift

    Recurring failures in semantic structure, contrast inconsistencies, and keyboard-navigation traps clearly indicated systemic design-system issues rather than isolated defects. This evidence proved decisive in prioritisation discussions and shifted accessibility from reactive fixes to structural improvement.

    Outcome

    This work helped reposition UX research as a stabilising force during transformation.

    Decisions became more evidence-led, accessibility risks were surfaced earlier, and platform changes were supported by a shared understanding of user behaviour.

    We shifted from release-driven decision-making to evidence-informed prioritisation, using research as a standard checkpoint rather than an optional add-on.

    Reflection

    Scaling UX research in this context was less about introducing new methods and more about changing how certainty was earned.

    When research consistently showed where assumptions failed, and when signals were shared across teams, UX moved from being a support function to a source of clarity during change.

  • Accessibility as a Strategic Foundation in the D2C Ecosystem

    From Compliance Checks to Organisational Practice

    The Company was evolving rapidly: new eCommerce platforms, a shift to composable architecture, a global design system rollout, and increasing regulatory pressure across markets.

    Yet accessibility quality remained inconsistent. Issues accumulated across templates, UI components, and content practices, creating friction not only for users with accessibility needs but for anyone navigating the site under real-world constraints.

    Teams were committed to delivering high-quality experiences, but with competing priorities and fragmented ownership, accessibility was often treated as a corrective task: reviewed late, fixed locally, and rarely scaled.

    As Senior UX Researcher and accessibility lead, I established a structured, organisation-wide approach that positioned accessibility as a driver of product quality, risk reduction, and user trust rather than a compliance checkbox.

    Challenge

    The accessibility challenge was structural, not symptomatic.

    Legacy SAP Commerce Cloud pages coexisted with new headless components, creating inconsistent patterns and uneven accessibility quality. The design system lacked WCAG-aligned guidance and governance, and responsibility for accessibility was unclear across design, development, content, and QA.

    Teams shipped quickly. Reviews happened late, accessibility debt accumulated, and fixes became increasingly costly.

    The core challenge was not identifying accessibility issues, but building the structures, processes, and shared understanding required to prevent them.

    Strategy

    The accessibility program was built on four parallel pillars designed to embed accessibility into everyday decisions rather than post-release correction.

    Accessibility Governance and Foundations

    I authored and introduced an accessibility roadmap aligned with WCAG 2.2 AA and tailored to the Company’s platforms and component libraries. It defined responsibility boundaries, acceptance criteria, mandatory checkpoints, and escalation paths.

    Embedding Accessibility in the Design System

    Working with design and engineering leads, I integrated accessibility requirements directly into component specifications, including semantic structure, contrast constraints, keyboard behaviour, error handling, and inclusive copy guidance.

    Continuous Audits and Behavioural Validation

    I established an audit program combining automated scanning, manual WCAG reviews, and user-centred observation using screen reader workflows.

    Cross-Functional Enablement

    I supported teams with training and lightweight tooling, including accessibility office hours, pattern libraries with dos and don’ts, sprint-level checklists, and pre-release smoke tests.

    Execution Highlights

    Transforming the Checkout Experience

    Checkout was prioritised due to its complexity and revenue sensitivity. I supported the redesign by mapping the screen reader journey, standardising form structures, aligning validation logic, and ensuring dynamic steps were announced and focus-managed.

    The most confusing interaction before standardisation was the transition between checkout steps. Users, especially those using screen readers, received no announcement of context change and often did not realise the page had advanced. Resolving this significantly reduced ambiguity and cognitive load for all users.

    Component-Level Accessibility Fixes

    Several components required systemic intervention, including accordions, tabs, filters, product carousels, and heading structures.

    Addressing these issues at the design-system level ensured fixes scaled consistently across global markets rather than being reintroduced through local variations.

    Accessibility Monitoring and Dashboards

    To support prioritisation, I introduced a structured approach to tracking automated scan trends, issue recurrence, component regressions, and accessibility debt over time.

    Recurring regressions in design-system components proved most effective in shifting stakeholder prioritisation. They demonstrated that the cost of inaction multiplied across markets and releases, prompting leadership to prioritise systemic fixes over page-level patches.

    Redefining Content Practices

    Accessibility extended beyond UI components. I worked with content and marketing teams to evolve alt-text practices, heading usage, link naming, and inclusive copywriting standards.

    These changes improved clarity for assistive technologies and reduced cognitive load more broadly, reinforcing that structural clarity, not content reduction, was the primary driver of improved readability.

    Outcome

    The accessibility program reshaped how the organisation approached digital quality.

    Strategic Impact

    Accessibility became part of the standard definition of done. Platform migrations launched with stronger foundations, fewer regressions, and a reduced backlog of accessibility debt.

    User Impact

    Screen reader journeys became more predictable. Form-heavy flows such as checkout, account creation, and repairs showed reduced friction and clearer progression.

    Organisational Impact

    Design system teams adopted accessibility-first component governance. Development teams integrated checks into CI/CD workflows. Content and marketing teams embedded inclusive writing practices as standard.

    The clearest signal of change was the integration of accessibility criteria directly into the design system’s component acceptance process: no new component or update could ship without meeting accessibility requirements.

    Accessibility moved from specialist review to shared expectation.

    Reflection

    Accessibility is not a sprint deliverable. It is an organisational capability.

    This work demonstrated that sustainable improvement depends on shared ownership, clear standards, early intervention, continuous validation, and a unified source of truth.

    It also reinforced a core NN/g principle: accessible design improves usability for everyone.

    The foundation established here supports every future platform, every market rollout, and every digital experience the Company will launch.

  • Designing a Professional Self-Service Platform

    Reducing Support Dependency Through Design

    Talawa Theatre Company launched Talawa Make to address a long-standing structural gap in British theatre: the lack of sustained, professional support and visibility for Black British artists across career stages.

    Talawa Make was conceived not as a single programme, but as a four-stage development ecosystem delivered through workshops, commissions, readings, and mentoring.

    The challenge was to translate this ambition into a digital platform that could support connection, opportunity discovery, and professional credibility at scale, without reproducing the exclusionary dynamics common in creative networks.

    As UX Designer, I led the design and implementation of the Talawa Make online community, shaping it as professional infrastructure, not a social network.

    Challenge

    The challenge was not technical delivery, but participation design.

    Talawa needed a platform that enabled artists to be visible and discoverable without self-promotion fatigue, supported meaningful interaction without being dominated by a small minority of users, reflected professional theatre norms, and balanced openness with moderation, safeguarding, and governance.

    Research and stakeholder discussions made one risk explicit: participation inequality would undermine the platform’s purpose.

    The problem to solve was therefore clear: how do you design a professional community where contribution feels safe, lightweight, and worthwhile, especially for early-career artists?

    Strategy

    The UX strategy focused on lowering the cost of participation while preserving professional standards.

    Designing for Participation, Not Posting

    Rather than encouraging users to create content, the platform was designed so that participation emerged as a side effect of other actions such as applying, attending, bookmarking, editing, tagging, or responding.

    Profiles, events, and opportunities did most of the expressive work. This approach was directly informed by research on online community dynamics and aimed to prevent early drop-off or silent disengagement.

    Audience-Aware Access and Permissions

    Registration defined three distinct user types:

    – Artists

    – Industry

    – Casual visitors

    This distinction ensured that artists retained control over visibility and contact, industry participation supported opportunity flow without dominance, and unregistered users could explore value before committing.

    Taxonomy Before Interface

    A significant portion of the work focused on taxonomy and data structure, not screens.

    Skills, disciplines, interests, career stages, and motivations were defined early, enabling meaningful filtering and discovery, region-aware mapping, and personalised surfacing of opportunities and events.

    Talawa artist profile editing interface
    Image Profile editing designed to support professional visibility without self-promotion fatigue.
    Talawa content creation interface
    Image Participation flows designed to reduce friction and make contribution feel lightweight and worthwhile.

    Prototyping and Validation

    Prototyping was used deliberately at three stages.

    Exploratory Prototypes

    Static visual prototypes tested layout, hierarchy, tone, and brand application. These helped align stakeholders on what professional but welcoming looked like before development began.

    Evaluative Prototypes

    Key journeys including registration, profile creation, messaging, and content posting were tested on the development environment with representative users across artists, industry contacts, and platform administrators.

    This surfaced friction around account setup, messaging expectations, and content visibility.

    Beta Validation

    A controlled beta with approximately 100 users allowed real-world observation of contribution patterns, navigation behaviour, moderation load, and profile completeness.

    This phase was essential for refining interaction rules and reducing unintended friction before wider rollout.

    Talawa artist profile page
    Image Profile experiences designed to communicate credibility, clarity, and professional identity.
    Talawa industry profile setup
    Image Audience-aware setup flows helped balance access, safety, and opportunity discovery.

    Implementation

    The platform was built on Drupal, selected for its flexibility in permissions, content types, and moderation workflows.

    To support parallel development, I recommended a structured deployment pipeline using Jenkins and GitHub, allowing:

    – Features to be tested in isolation

    – UX sign-off before release

    – Reduced regression during iteration

    This was particularly important given offshore development teams and a phased launch plan.

    Talawa map and discovery interface
    Image Taxonomy and structured data enabled filtering, regional discovery, and opportunity visibility.
    Talawa homepage interface
    Image Homepage design positioned the platform as professional infrastructure rather than a generic social feed.

    Outcome

    Talawa Make Online launched as a professional infrastructure, not a social experiment.

    The platform:

    – Enabled artists to present themselves credibly and consistently

    – Supported discovery of opportunities, events, and peers across regions

    – Reduced reliance on informal networks and insider knowledge

    – Gave Talawa visibility into engagement patterns without compromising trust

    By prioritising structure, permissions, and taxonomy, the platform avoided common failure modes of creative communities: noise, inequality, and disengagement.

    Reflection

    This project reinforced a core UX lesson: community platforms do not fail because of missing features. They fail because participation feels risky, performative, or unrewarded.

    Designing Talawa Make required treating UX not as interface optimisation, but as social infrastructure design, where clarity, boundaries, and governance matter as much as interaction.

    The success of the platform lay not in how much content users created, but in how confidently they chose to participate.

  • Designing for a Global Health Charity

    Building Trust in Evidence-Based Health Guidance

    Overcoming MS (OMS) is an international charity promoting an evidence-based, seven-step lifestyle programme for people living with multiple sclerosis.

    Its ambition was to become a globally recognised digital charity, capable of reaching people with MS wherever they were, while maintaining the personalised support and sense of community that defined the organisation.

    The challenge was not simply to publish information online, but to support informed decision-making and sustained behaviour change in a context shaped by uncertainty, fluctuating health, and cognitive and emotional load.

    OMS recognised that achieving this required a research-led UX discovery phase to understand how people with MS seek information, manage energy, and engage with support over time.

    Challenge

    The existing website struggled to support OMS’s mission at scale.

    Key issues included fragmented content structures, a lack of a cohesive design system, low conversion through digital donations, and high dependency on administrators for content updates.

    More fundamentally, the platform did not sufficiently reflect the real-life constraints of people living with MS, including fatigue, variable attention, and the need to revisit information over time.

    The core challenge was to design a platform that balanced clarity, credibility, and compassion, while supporting both educational goals and organisational sustainability.

    OMS donation step interface
    Image Donation-flow redesign focused on clarity, reassurance, and reduced friction.
    OMS user profile layout
    Image User profile concepts supporting saved content, continuity, and return visits over time.

    Discovery Phase

    To move beyond assumptions, the discovery phase centred on a diary study, allowing participants to document aspects of their daily lives over several days.

    This method surfaced:

    – Fluctuating energy levels and attention across the day

    – Non-linear information needs, with frequent revisiting of the same content

    – Emotional sensitivity around health-related decisions

    – Reliance on mobile devices for short, fragmented sessions

    The diary study provided insight into how and when people engaged with information, not just what they sought.

    Supporting methods included internal interviews with OMS staff, reviews of OMS materials, and focus groups validating early findings and testing assumptions about key tasks.

    Focus group feedback highlighted friction in sign-up and account creation, “My account” areas and saved content, and understanding how to progress through OMS resources over time.

    Strategy

    The UX strategy focused on reducing cognitive load while increasing trust and continuity.

    Structuring for Clarity and Return Visits

    Information architecture was redesigned to group content into predictable, clearly labelled templates, support scanning and short sessions without losing context, and allow users to save and return to content over time.

    User profiles enabled favourites and personalised access, reflecting the need to engage gradually rather than all at once.

    Designing for Mobile-First Reality

    Given diary-study insights, mobile experience became a priority. Optimisation work contributed to a reported 30% increase in mobile traffic, reflecting improved accessibility and usability rather than acquisition-driven growth.

    Supporting Behaviour Over Time

    Rather than relying on one-off interactions, the platform introduced lifecycle emails triggered at meaningful moments in the user journey. These were designed to reinforce motivation, encourage return visits, and support sustained engagement without pressure.

    OMS lifecycle email example one
    Image Lifecycle messaging designed to support motivation and return visits without pressure.
    OMS lifecycle email example two
    Image Email touchpoints aligned with gradual engagement and long-term behaviour change.
    OMS lifecycle email example three
    Image A sequence of supportive communications shaped around real user timing and context.

    Design System and Content Enablement

    A core constraint was OMS’s need to update and manage content independently.

    To address this, I:

    – Created a simplified design system to ensure visual and structural consistency

    – Designed modular content templates for articles, recipes, exercises, meditations, podcasts, FAQs, and events

    – Implemented Paragraphs and CK Editor to allow editors to create and update pages without developer intervention

    This reduced reliance on technical support and enabled faster iteration while preserving quality.

    Donations and Trust Signals

    Donation flows were redesigned to reduce friction and increase clarity.

    Key improvements included:

    – Clear, visible donation entry points

    – Support for recurring donations

    – Options to dedicate donations in honour or memory

    – Clear explanations of how funds are used

    – Use of testimonials and third-party endorsements to reinforce credibility

    These changes aligned fundraising with OMS’s educational mission, avoiding pressure while supporting sustainability.

    OMS mission page layout
    Image Trust-building content and organisational context designed to reinforce credibility.
    OMS homepage layout
    Image Homepage structure designed for clarity, orientation, and sustained engagement.

    Outcome

    The redesigned platform strengthened OMS’s ability to deliver on its mission digitally.

    User Impact

    – Clearer access to information and resources

    – Improved mobile usability for fragmented sessions

    – Better support for revisiting and saving content

    Organisational Impact

    – Greater editorial autonomy for OMS staff

    – More consistent experience through design system adoption

    – Improved alignment between content, community, and fundraising goals

    The platform evolved from an information repository into a supportive digital environment shaped around real user behaviour.

    Reflection

    This project reinforced that designing for health-related contexts requires more than clarity and aesthetics.

    Effective UX in this space means respecting fluctuating capacity, designing for return rather than completion, and supporting trust without persuasion.

    By grounding decisions in lived experience through diary studies, the platform shifted from telling users what to do to supporting them as they navigate complex, personal decisions over time.

  • Scalable ROI Framework Matrix for UX Measurement

    Measuring UX Impact at Scale

    As UX work expanded across multiple journeys and markets, the organisation faced a growing disconnect between behavioural insight and business decision-making.

    Teams were improving checkout flows, refining product listings, adjusting navigation, and iterating on templates. Each initiative showed signs of behavioural change, yet there was no shared way to compare their value or prioritise investment across the portfolio.

    The problem was not a lack of data. It was the absence of a common financial language for UX impact.

    This case study documents how a scalable ROI framework was designed to translate UX behaviour into credible, comparable business signals.

    Challenge

    UX initiatives were evaluated in isolation.

    Checkout changes affected a small proportion of users but carried high intent. Product page listing and navigation changes reached more users but produced subtler behavioural shifts. Template updates varied by market and maturity.

    Without a shared framework, UX prioritisation stalled across initiatives and discussions defaulted to subjective judgement rather than evidence.

    The core challenge was comparability and credibility, not measurement volume.

    Strategy

    The strategy was to design a single, reusable ROI framework that could be applied consistently to any UX change, regardless of journey depth or market size.

    The framework needed to:

    Core Requirements

    – Connect behavioural metrics to business impact

    – Normalise performance across different exposure levels

    – Support forecasting before launch and accountability after release

    – Prevent inflated ROI claims in deep-funnel contexts

    – Produce clear, trusted ROI tiers for decision-making

    Scalability was a deliberate design goal, not an afterthought.

    Execution Highlights

    A Consistent Measurement Logic

    The framework translates UX behaviour into business impact using a single principle: impact is a function of behavioural change and exposure.

    Rather than relying on relative uplift or raw analytics, the model:

    – Measures conversion change in percentage points

    – Weights impact by the proportion of users actually exposed

    – Applies consistent time normalisation across initiatives

    – Evaluates performance over multiple post-launch windows

    This ensured that improvements were neither overstated nor dismissed.

    Time-Based Validation

    To avoid premature conclusions:

    – Early post-launch windows captured adoption effects

    – Later checkpoints confirmed behavioural stabilisation

    This approach allowed the team to detect short-term volatility, long-term consistency, and false positives driven by novelty or traffic noise.

    Portfolio-Level Visibility

    Each UX change was documented in a dedicated update view and rolled into an overview layer showing journey step, relative exposure, direction and stability of impact, ROI tier classification, and confidence notes.

    This shifted conversations from “Is this UX change good?” to “Where should we invest next for the strongest return?”

    Discipline Through Rejection

    Several commonly used ROI approaches were explicitly rejected:

    – Relative uplift percentages that exaggerated deep-funnel impact

    – Applying changes to total site traffic regardless of exposure

    – Blind use of industry benchmarks without contextual adjustment

    – Volatile revenue-per-session models

    The final framework prioritised realism over persuasion.

    Outcome

    The framework was first validated through a checkout optimisation initiative, then adopted as the standard evaluation model for UX changes.

    Key outcomes included:

    – A shared, auditable ROI language across teams

    – Increased trust in UX impact reporting

    – Faster, evidence-based prioritisation decisions

    – More disciplined allocation of engineering effort

    Importantly, the framework was also used to deprioritise initiatives with limited exposure and low strategic leverage. It proved capable of constraining investment, not just justifying it.

    UX shifted from a cost discussion to a decision-support function.

    Reflection

    This work changed one foundational assumption: conversion change has no meaning without exposure context.

    Before the framework, impact discussions focused on the size of behavioural shifts. Afterwards, they focused on how many users those shifts actually affected.

    That shift reframed UX ROI from advocacy to accountability.

    The framework does not replace qualitative research, brand thinking, or accessibility judgement. It complements them by providing a clear validation layer where financial decisions require evidence.

    In doing so, it raised the maturity of UX conversations not by inflating impact, but by making it comparable, bounded, and trustworthy.

  • Signal-Driven Discovery

    Teams say they want continuous discovery, but most of the evidence arriving day to day is fragmentary, delayed, and easy to overread. By the time a drop in conversion, a strange search term, or a support pattern gets noticed, the pressure is already to explain it fast and act faster. The real problem is not lack of data. It is deciding which weak signals deserve interpretation, which need probing, and which should not harden into confident stories.

    When to Use This

    • When behaviour shifts and no single release, campaign, or seasonal factor explains it cleanly
    • When interviews are too slow, too expensive, or too operationally heavy to trigger every time something moves
    • When several weak signals are clustering around the same part of the journey but the problem is still blurry
    • When the next step needs to be a concrete probe or decision, not another round of speculative discussion
    • When quieter absences need tracking alongside the loud anomalies that teams already notice

    The Framework

    1. 01

      Signal

      Notice a shift, absence, or recurring trace that refuses to stay incidental. Name the disturbance without pretending it already explains itself.

      What gets misread here A single anomaly gets treated as insight before its shape, context, or persistence has been checked.

    2. 02

      Triage

      Check whether the signal survives basic context: timing, segment, instrumentation, recent releases, and operational noise. The aim is to decide whether this deserves attention now, later, or not at all.

      What gets misread here Triage becomes explanation, so the team smuggles a favourite cause in before the evidence has narrowed.

    3. 03

      Interpretation

      Read across sources until the pattern becomes legible enough to frame a working explanation. Analytics, search, recordings, verbatims, and support should tighten the same question, not perform agreement theatre.

      What gets misread here Cross-source repetition is mistaken for certainty, even when each source is echoing the same blind spot.

    4. 04

      Probe

      Push the interpretation hard enough to expose where it fails. A probe can be a fast analysis cut, a counter-question, a lightweight experiment, or a small piece of qualitative follow-up.

      What gets misread here Any probe that confirms the first hunch is taken as validation, while disconfirming evidence is treated as noise.

    5. 05

      Decision

      Translate the strongest remaining reading into a concrete move: test, content change, design change, escalation, or deliberate non-action. If there is no decision pathway, the framework stops being useful.

      What gets misread here Decision is reduced to shipping something, even when the right move is to escalate, wait, or gather a different kind of evidence.

    6. 06

      Loop

      Carry the result back into the next round by checking what changed, what stayed absent, and what now deserves quieter ongoing listening. The loop keeps anomalies and ambient signals in conversation instead of letting each investigation die as an isolated ticket.

      What gets misread here The loop is treated as closure, so the team records an outcome but never adjusts what it watches next.

    Where This Breaks

    • Weak instrumentation turns noise into false signals or hides the signals that matter.
    • No decision pathway leaves the team able to describe a pattern but unable to act on it.
    • Overinterpretation makes correlation sound like understanding, especially under delivery pressure.
    • Organisational constraints block escalation, so the method keeps surfacing issues it has no permission to move.

  • EU Consumer Law and UX: The Consumer as Ecosystem

    Task-first regulation map

    Scan the obligation first. Open the legal detail only when needed.

    EU consumer law has moved past disclosure. Four regulations — right of withdrawal, legal guarantee, right to repair, age verification — now place active obligations on ecommerce interfaces. Each one lands in a different ecosystem state. Each one is currently met at the lowest possible interface weight. This series maps the gap between legal obligation and interaction design, using the user-ecosystem framework.

    Applying the user-ecosystem framework — Youngblood and Chesluk, Rethinking Users (BIS Publishers, 2020) · NN/g, 2025.

    Let people cancel from the order page The 14-day withdrawal right now needs an active account-area function, not a footer policy. What changed Withdrawal must be executable online through a clearly labelled function. Where in the journey Post-purchase account or order view, then the withdrawal flow. Required UI Clear withdrawal button, live deadline, and purchase-like effort. Failure risk Footer-only policy links make the right hard to exercise and fail the symmetry test.

    Legal detail

    The right to undo a purchase

    ⚖ Dir. 2011/83/EU · amended 2023/2673 · in force 19 June 2026

    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.

    Journey details

    01

    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

    Why it matters

    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.

    Design implication

    Nothing to redesign at this stage. The gap is downstream.

    02

    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

    Why it matters

    The legal archetype is present but weightless. The cognitive archetype is directed at the product. Disclosure is occurring; comprehension is not.

    Design implication

    The right is disclosed at the moment of highest purchase intent, the state least receptive to legal information.

    03

    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

    Why it matters

    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.

    Design implication

    Disclosure does not equal function. Checkout satisfies the information requirement. The withdrawal function belongs in the post-purchase ecosystem.

    04

    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

    Why it matters

    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.

    Design implication

    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.

    05

    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

    Why it matters

    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.

    Design implication

    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.

    What fails today and what must change

    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 interface

    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 interface

    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.

    Required UI pattern

    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.

    Legal source: Directive 2023/2673 · Amendment to Article 11

    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.

    Separate the legal guarantee from the warranty The mandatory 2-year guarantee must not be blurred with a voluntary commercial warranty. What changed ECGT requires clear information on the statutory guarantee and how it differs from any commercial guarantee. Where in the journey Product page, checkout confirmation, and breakdown or support journey. Required UI Two distinct labels: mandatory seller guarantee first, voluntary warranty second. Failure risk Warranty badge dominance can misdirect consumers to paid support or manufacturer paths.

    Legal detail

    Two rights, one confusion

    ⚖ Dir. 2019/771 · ECGT Dir. 2024/825 · in force 27 Sept 2026

    Every product sold in the EU carries a mandatory 2-year legal guarantee. Most interfaces promote the commercial warranty instead, a voluntary manufacturer’s offer. The ECGT directive now requires these to be clearly distinguished. They are not currently.

    Journey details

    01

    Browse

    Acquisition mode — guarantee invisible

    • The intentional browser Building product preference, comparing options
    • The aspirational self Desire-led engagement with products
    • The market participant Responding to pricing and brand signals
    • The guarantee-holder 2-year legal guarantee exists absent

    Why it matters

    No legal archetypes are active at browsing. The legal guarantee exists in law, but has no presence in the browsing ecosystem. The commercial warranty, by contrast, is often promoted actively through badge design and product imagery.

    Design implication

    The asymmetry begins here: the mandatory right is invisible, the voluntary offer is prominent.

    02

    Product page

    Where the law requires clear distinction

    • The evaluating agent Reading specs, reviews, warranty claims
    • The confidence-seeker Warranty information increases purchase confidence
    • The promoted warranty Commercial offer, prominently placed
    • The legal guarantee Mandatory 2-year right, absent or buried absent
    • The breakdown-holder Guarantee becomes relevant only when product fails absent

    Why it matters

    The ECGT directive requires both to be present and distinct on the product page. Currently the commercial warranty dominates because it is a marketing asset. The legal guarantee, which is stronger and mandatory, is either absent or indistinguishable from the commercial offer.

    Design implication

    ECGT 2024/825 creates two separate legal objects: the statutory guarantee label, mandatory and seller-owned, and the commercial durability guarantee label, voluntary and manufacturer-owned. Most product pages currently show one undifferentiated badge.

    03

    Checkout

    Purchase confirmed — two clocks now running

    • The completing agent Finishing the transaction; bandwidth minimal
    • The dual-clock holder Legal guarantee and commercial warranty both activated at purchase
    • The guarantee-holder Legal guarantee begins; consumer is often unaware
    • The warranty-holder Commercial warranty confirmed; consumer may notice this one

    Why it matters

    Two legally distinct timers start at the moment of purchase. The consumer is aware of neither. The checkout confirmation page typically shows order summary and delivery estimate, not the start of their consumer rights.

    Design implication

    A confirmation message that says your 2-year guarantee starts today would activate the temporal archetype at the correct moment. Most interfaces do not do this.

    04

    Breakdown

    The ecosystem the law was written for

    • The problem-solver Trying to get a defective product repaired or replaced
    • The frustrated owner Stress, urgency, and sense of loss
    • The deadline-holder Is the product still within two years? The consumer often does not know
    • The rights-exerciser Legal guarantee entitles free repair or replacement
    • The commercial warranty path Interface redirects to paid support or upsell absent

    Why it matters

    The legal archetype is now maximally relevant. The consumer has a right to free repair or replacement. If the guarantee was never clearly communicated, the interface directs them toward paid support, an upsell, or manufacturer channels that obscure the mandatory right.

    Design implication

    The ecosystem at breakdown is the one the law was designed for. But the information the consumer needs was disclosed at a completely different ecosystem state, high purchase intent, and was not retained. The active artifact that could bridge these states is a guarantee card or account record surfaced at the moment of breakdown.

    What fails today and what must change

    The guarantee label is an active artifact. Currently it amplifies the commercial warranty and renders the legal guarantee invisible. Under ECGT 2024/825 it must do the opposite: make the mandatory right legible and the voluntary offer secondary.

    Current interface

    The commercial warranty dominates the interface. The legal guarantee, the stronger and mandatory right, is absent or indistinguishable. When the product fails, the consumer does not know which protection applies or how to invoke it.

    Required interface

    Two distinct labels, two distinct rights. The mandatory legal guarantee is primary. The commercial warranty is secondary and clearly voluntary. Both can link to a claim process, but the consumer can tell immediately which right is theirs by default.

    Required UI pattern

    The guarantee label on a product page is a legal actor. When it says 2-year warranty without distinguishing legal from commercial, it performs the seller’s interest, not the consumer’s right. The ECGT directive requires it to perform both, separately, clearly, and in that order.

    Legal source: ECGT Directive 2024/825 · Article 6b

    Traders shall provide consumers with clear information on the statutory guarantee of conformity and on the distinction between the statutory guarantee and any commercial guarantee offered.

    Show repair choices before and after purchase The product page becomes a lifecycle surface with repairability, parts, and repair access. What changed Right to Repair requires repair and spare-parts information, reasonable pricing, and no technical blocking. Where in the journey Product page, ownership area, support flow, and repair decision. Required UI Repairability score, parts availability, price cues, and repair pathway. Failure risk Sales-only product pages hide lifecycle costs and steer replacement over repair.

    Legal detail

    The product page after purchase

    ⚖ Dir. 2024/1799 · member states apply from 31 July 2026

    The product page has always been a sales endpoint. The Right to Repair makes it the entry point to a legally mandated post-purchase infrastructure: repairability scores, spare parts availability, and repair pricing. None of these currently exist as active interface nodes.

    Journey details

    01

    Browse

    Acquisition mode — repairability invisible

    • The intentional browser Evaluating products on price, brand, and features
    • The aspirational self Desire-led engagement
    • The market participant Responding to commercial signals
    • The repair-rights holder Right to repair and spare parts access absent

    Why it matters

    The repairability of a product is not a visible attribute in the browsing ecosystem. The consumer has no interface node to evaluate it against. The commercial ecosystem is optimised for replacement, not repair.

    Design implication

    The ecosystem at browsing reflects the commercial incentive: sell new products. The Right to Repair introduces a counter-incentive that currently has no interface home.

    02

    Product page

    The product page must now carry lifecycle information

    • The evaluating agent Reading specs, comparing models
    • The conversion target Interface optimised toward purchase completion
    • The repairability-aware buyer Repairability score required on product page, absent in most interfaces absent
    • The long-term owner Spare parts availability over product lifetime is not shown absent

    Why it matters

    Dir. 2024/1799 requires repairability information on the product page. Currently the product page is a pure sales surface. Repairability scores, spare parts availability, and repair cost indicators have no visual language, no established placement, and no interface precedent.

    Design implication

    This is the most structurally disruptive regulation in the series. It requires the product page to carry information that is actively against the commercial interest: the long-term cost of ownership, at the moment of purchase.

    03

    Ownership

    The post-purchase ecosystem — repair need building

    • The maintaining owner Caring for product, noticing wear or faults
    • The invested owner Attachment to product; preference for repair over replacement
    • The replacement-nudged consumer Interface surfaces new products; repair path is not offered
    • The repair-rights holder Right to spare parts and repair information, no interface home absent

    Why it matters

    The consumer is in ownership mode. A fault develops. The current ecosystem offers no repair pathway. The interface was not designed to support post-purchase repair decisions. The path of least resistance is replacement.

    Design implication

    The Right to Repair creates an obligation during the ownership phase that has no current interface expression. The consumer’s repair rights are invisible to the ecosystem.

    04

    Repair decision

    A choice the interface must now support

    • The repair-or-replace decision-maker Weighing repair cost against replacement cost
    • The cost-conscious owner Financial and environmental consideration
    • The guarantee-extender Repair under guarantee extends legal protection by one year
    • The rights-exerciser Spare parts must be available at reasonable price; repair cannot be blocked
    • The independent repairer Third-party repairers now have legal access, not yet integrated into ecommerce flows absent

    Why it matters

    The directive creates a new decision point the interface must support. The repair-or-replace choice is currently invisible. The commercial incentive is replacement. The legal obligation is to make repair the accessible option.

    Design implication

    A product repaired under warranty gains an additional year of legal guarantee. This changes the repair calculus, but only if the consumer knows it exists. The interface that surfaces this information at the repair decision moment is performing the directive’s intent.

    What fails today and what must change

    The repairability score is a legally mandated active artifact. Currently it does not exist as an interface node. When it does, it changes the nature of the product page, from a sales-only surface to a lifecycle interface that must support both acquisition and long-term ownership.

    Current interface

    The product page is a sales endpoint. No repairability information, no spare parts access, and no repair pathway. The ecosystem is optimised for purchase. The Right to Repair has no active artifact here.

    Required interface

    The product page now carries lifecycle information. Repairability score, spare parts availability, and repair pathway are visible at point of purchase. The consumer can evaluate the long-term cost of ownership before buying.

    Required UI pattern

    The repairability score is a legal actor before purchase and after. It changes the product decision at point of sale, and it anchors the repair infrastructure that must remain accessible for the product’s lifetime. The commercial incentive is replacement. The legal obligation is repair.

    Legal source: Directive 2024/1799 · Article 5

    Manufacturers shall provide information concerning spare parts and repair on their website, make them available at a reasonable price, and shall not use hardware or software techniques that impede repair.

    Verify age without turning checkout into surveillance Age checks need a coherent, privacy-preserving gate despite fragmented EU and national rules. What changed Age assurance is moving toward privacy-preserving, interoperable proof rather than broad identity collection. Where in the journey Cart, checkout, verification step, with earlier restriction cues. Required UI Minimal-data age proof, clear reason, early warning, and a fallback that avoids over-collection. Failure risk Document upload harvests data; date-of-birth fields are weak; both create legal and abandonment risk.

    Legal detail

    The fragmented gate

    ⚖ DSA 2022/2065 · EU Digital Identity Wallet · national law variations

    Age-restricted products online are governed by a patchwork of national laws, platform rules, and product-category regulations. There is no single EU standard. The result is a fragmented legal node that arrives at the moment of highest purchase intent and currently resolves into either a privacy violation or a dark pattern.

    Journey details

    01

    Browse

    Pre-restriction — ecosystem unaware

    • The intentional browser Scanning products, building intent
    • The aspirational self Desire-led engagement
    • The market participant Responding to commercial signals
    • The age-restricted buyer Product category triggers verification requirement absent

    Why it matters

    The consumer is browsing without awareness that an age restriction will interrupt the journey. The legal node does not yet exist in the ecosystem. It will arrive at the worst possible moment.

    Design implication

    The design question begins here: when should the restriction become visible? Surfacing it early reduces checkout friction, but also introduces a gate before the consumer has committed.

    02

    Cart / Checkout

    The legal node arrives at maximum purchase intent

    • The completing agent Focused entirely on transaction completion
    • The completion-seeker Friction is acutely felt; abandonment risk high
    • The converting customer Interface optimised to reach payment confirmation
    • The age-verifier Verification required, but method is undefined by any single EU standard
    • The privacy-holder Consumer wary of data collection during verification absent

    Why it matters

    The legal node arrives at the moment of highest purchase intent. Cognitive archetype: completion-focused. Emotional archetype: friction-averse. Any method that introduces steps, requests documents, or requires account creation will generate abandonment. The commercial and legal archetypes are in direct opposition.

    Design implication

    No single EU standard governs this moment. National laws vary by product category. The interface must resolve a legally fragmented requirement with a coherent user experience.

    03

    Verification

    The verification method determines everything

    • The interrupted agent Task switched from purchase to identity; cognitive cost is high
    • The surveilled self Verification often reads as data collection, not protection
    • The friction interface Document upload, date of birth entry, account creation, all increase abandonment
    • The identity-holder Must prove age; method varies wildly by platform and market
    • The autonomic user EU Digital Identity Wallet: age confirmed without data shared, not yet available everywhere absent

    Why it matters

    The verification method is the design. A document upload harvests data and introduces maximum friction. A date-of-birth field is bypassable and legally inadequate. The EU Digital Identity Wallet offers a third path: cryptographic age confirmation with no data transfer. But this infrastructure is not yet uniformly available.

    Design implication

    The autonomic user archetype is active here. When the Digital Identity Wallet verifies age automatically, the consumer and the verification system become indistinguishable, a single node within the ecosystem.

    04

    Purchase confirmed

    Verification resolved — ecosystem resumes

    • The completing agent Transaction resumes; verification step complete
    • The relieved consumer Friction resolved; purchase intent recovers
    • The converted customer Purchase complete, if abandonment did not occur
    • The verified buyer Age confirmed; legal obligation met for this transaction

    Why it matters

    If verification was smooth and privacy-preserving, the ecosystem recovers. If it required document upload or account creation, a significant share of consumers abandoned at the previous stage and never reach here.

    Design implication

    The design outcome is measured at this stage. The method that minimises the distance between the legal requirement and purchase completion, in effort, time, and privacy cost, is the ecosystem-aware solution.

    What fails today and what must change

    The age verification mechanism is an active artifact with two possible natures. Currently it is either a data-harvesting gate or a bypassable checkbox. The EU Digital Identity Wallet proposes a third state: a privacy-preserving signal that confirms age without revealing it.

    Current interface

    The current dominant pattern is either document upload or a date-of-birth field. The first harvests personal data and introduces maximum friction. The second is trivially bypassable and legally inadequate. Both fail on privacy, friction, or legal certainty.

    Required interface

    EU Digital Identity Wallet: confirm age, share nothing. A cryptographic proof that the consumer is over 18, without revealing date of birth, name, or other personal data. Low friction, low privacy cost, and high legal certainty.

    Required UI pattern

    Youngblood and Chesluk’s concept of the autonomic user, where technology and user become a single whole, is most visible here. When the EU Digital Identity Wallet verifies age automatically and privately, the user does not perform verification. The ecosystem performs it.

    Legal source: European Commission · Age Verification Blueprint, 2025

    The EU age verification initiative aims to allow EU users to prove they are old enough to access age-restricted content without sharing any other personal information, privacy-preserving and interoperable with EU Digital Identity Wallets.

    From observation to method

    This piece shows how legal pressure surfaces as distributed ecosystem strain. Signal-Driven Discovery turns that kind of pressure into a method for deciding what deserves interpretation, probing, and action.

    • Working Framework

      A method page for reading weak signals, testing interpretation, and turning research into decisions.