Aled Pritchard
Ask ClaudeAsk ChatGPTBook a call
  • My name is Aled. I’m a Design Director. I build products, systems and teams that solve multi-million-pound problems.solve multi-million-pound problems.
    My name is Aled. I’m a Design Director. I build products, systems and teams that solve multi-million-pound problems.
    Currently running my own practice, working with fintech, SaaS and AI companies. Previously Head of Product Design at Just Group and Design Lead at Chase. Based in London.
  • About

    Aled Pritchard

    Aled has always made things. For 20+ years he has done it as a designer — brands first, then products, then the systems and teams behind them. He’s done it in-house, at agencies, and by founding his own businesses. He creates things that don’t exist yet. He identifies opportunities that haven’t been named. He explores what is possible — in product, in systems, in how teams are structured and led. When something is broken, stuck, or unable to scale, he diagnoses what’s wrong before anyone starts fixing it. He has led, scaled and restructured design teams for eight years, and stays hands on with the most complex and business-critical parts of the work.

  • I lead design through uncertainty, growth and change, from 0–1 products to scaling teams and platforms. I bring clarity, set direction and build capability to create impact now and momentum that lasts.

    Approach

    Customers don’t experience brand, product and service separately. Using research, user testing and experiments to find what customers need, I work with partners across the business to design a coherent end-to-end experience. I make good design explicit, with principles, standards and measurable design QA.

    Capability

    • Brand identity
    • Product design
    • Service design
    • Design systems
    • Design standards and principles
    • Quality measurement
    • User research and testing
    • Accessibility
    • AI prototyping

    Approach

    I set the vision and explain the why, how, and what that needs to be done. I show the order it needs doing and set the standards. With a clear operating model and agreement on goals, I can trust the team to make their own calls.

    Capability

    • Design operating model
    • Hiring and scaling teams
    • Team structure and role design
    • Onboarding and training
    • Coaching
    • Performance management
    • Design critique and culture

    Approach

    Executives back work they can see moving the business, so I tie design effort to the priorities and numbers they already watch. With product and engineering partners, I agree shared goals at the start and we make trade-offs together.

    Capability

    • Business cases for investment and headcount
    • Executive and board communication
    • Product and engineering partnership
    • Product ownership and roadmaps

    Approach

    Good design keeps a business commercially sustainable, on cost as much as revenue. I connect design work to the measure it should move, whether that is conversion, retention or cost to serve. Every designer on the team knows the KPI their work serves and why it matters.

    Capability

    • Proposition design
    • Conversion optimisation
    • Reducing cost to serve
    • A/B testing and experiments
    • Design KPIs and success measures

    Approach

    Starting from zero, reaching new audiences and changing an established business all come with unknowns. I start with a clear understanding of the need, use proof to build a hypothesis, and use data to refine the idea. I set direction and sequence the work so each step builds momentum.

    Capability

    • 0–1 products
    • Scaling to new markets
    • Raising design maturity
    • Vision and strategy
    • Prioritisation and sequencing

    Approach

    I run my practice on AI agents with written roles and standards, deciding where they support a person and where they act alone. I prototype to accelerate learning and push design to code, so engineers and designers can collaborate on the bigger problems.

    Capability

    • AI assistant design
    • Hyper-personalisation
    • Agentic workflows
    • AI governance
    • Design systems × AI
    • AI prototyping
  • From design system to product platform

    JPMorganChaseDynamo Design System
    Design Lead & product owner2022–2025
    10+ person squad · ~35 designers · 100+ engineersMobile app · Marketing site · UK & Germany

    Rebuilt the architecture, team and review model for the design system, with training, documentation and support, so squads could make design decisions without central review.

    An operating model for agentic AI

    Association of One
    Founder2026
    16 agents · 1,300+ PRs merged
    agents.assoc.one

    Built AI agents that plan, build, review and correct their own work against written standards, so the quality is dependable and repeatable.

    The Chase app home screen before the refresh: a flat list of accounts with their balances under a blue card header, and recent activity below.The same Chase app home screen after the refresh: Spend, Save and Investment tabs above a dark blue debit card header, with the current account and recent activity in rounded panels.

    Adding visual depth without losing clarity

    JPMorganChaseChase app
    Design Lead2022–2025
    Mobile app · Web

    Led the Chase UI refresh, setting systems for colour, depth and motion that keep it minimal with a clearer hierarchy. Released to over a million customers.

    Turning customer data into next best actions

    Just Group
    Head of Product Design2025–2026
    Experience strategy · Data modelling · AI triage · 5 designers

    Defined how customer data is captured and synthesised into a profile, designed for an AI engine that drives hyper-personalised actions and targeted support for pension savers.

    Perceivable

    Information and user interface components must be presentable to users in ways they can perceive. This means users must be able to see or hear the content.


    Visual Clarity
    • Text and essential UI elements must meet WCAG AA contrast ratios:

      • 4.5:1 for normal text
      • 3:1 for large text (18pt or 14pt bold)
      • 3:1 for non-text elements (e.g., icons, focus indicators, graphical controls)
      Read more → WCAG 2.1 SC 1.4.3: Contrast (Minimum)Read more → WCAG 2.1 SC 1.4.11: Non-text Contrast
    • Colour should never be the sole method of conveying information. Use icons, labels, or patterns to support colour-based indicators.

      Read more → WCAG 2.1 SC 1.4.1: Use of Colour
    • Text should remain legible and functional when users increase font size via system settings. Avoid fixed-size text or layouts that break when scaled.

      Read more → WCAG 2.1 SC 1.4.4: Resize Text
    Media Alternatives
    • All meaningful images and icons must have descriptive accessibility labels. Decorative images should be marked as such.

      Read more → WCAG 2.1 SC 1.1.1: Non-text Content
    • Videos must include captions for spoken content. Audio-only content should be accompanied by text transcripts.

      Read more → WCAG 2.1 SC 1.2.2: Captions (Prerecorded)Read more → WCAG Media Accessibility: Transcripts
    • Animations or transitions must not interfere with readability or comprehension. Support reduced motion settings.

      Read more → WCAG 2.1 SC 2.3.3: Animation from Interactions
    Structural Accessibility
    • Use consistent typography, spacing, and layout to guide users through content.

      Read more → WCAG Cognitive Patterns: Page Structure
    • Ensure that important content is not hidden behind gestures, hover states, or animations that may not be accessible to all users.

      Read more → WCAG 2.1 SC 1.3.1: Info and Relationships
    • Designs must adapt to different screen sizes and orientations without losing meaning or functionality.

      Read more → WCAG 2.1 SC 1.4.10: Reflow

    Operable

    User interface components and navigation must be operable. Users must be able to interact with the interface, regardless of their input method.


    Navigation & Focus
    • All interactive elements are reachable via screen reader focus (e.g., VoiceOver, TalkBack).

      Read more → WCAG 2.1 SC 2.1.1: Keyboard
    • Focus should follow a logical, intuitive path that matches the visual layout and reading order.

      Read more → WCAG 2.1 SC 2.4.3: Focus Order
    • All focusable elements must have a visible and consistent focus style to help users track navigation.

      Read more → WCAG 2.1 SC 2.4.7: Focus Visible
    Touch & Interaction
    • Interactive elements must meet minimum touch target size (e.g., 44x44pt) to support users with motor impairments.

      Read more → WCAG 2.2 SC 2.5.8: Target Size (Minimum)
    • Custom gestures (e.g., swipe, pinch) must have accessible alternatives or clear instructions.

      Read more → WCAG 2.1 SC 2.5.1: Pointer Gestures
    • Avoid interactions that rely on device motion (e.g., shake to undo) unless alternatives are provided.

      Read more → WCAG 2.1 SC 2.5.4: Motion Actuation

    Understandable

    Information and the operation of the user interface must be understandable. The content and interface should be clear and predictable.


    Language & Clarity
    • Use plain, concise language appropriate for your audience. Avoid jargon or overly complex terms.

      Read more → WCAG 2.1 SC 3.1.5: Reading Level
    • Use consistent labels and terminology across screens and components to reduce cognitive load.

      Read more → WCAG 2.1 SC 3.2.4: Consistent Identification
    • Ensure the app declares the correct language for screen readers to interpret content accurately.

      Read more → WCAG 2.1 SC 3.1.1: Language of Page
    Feedback & Error Handling
    • Error messages must be clear, specific, and actionable to help users recover.

      Read more → WCAG 2.1 SC 3.3.1: Error Identification
    • Provide hints, labels, and validation to guide users through forms and inputs.

      Read more → WCAG 2.1 SC 3.3.2: Labels or Instructions
    • UI elements should behave consistently and not change unexpectedly (e.g., no auto-navigation on focus)

      Read more → WCAG 2.1 SC 3.2.2: On Input

    Robust

    Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This ensures that the app works well across different devices, platforms, and assistive tech.


    Compatibility & Semantics
    • Use platform-native components that are inherently accessible and support assistive technologies.

      Read more → WCAG 2.1 SC 4.1.2: Name, Role, Value
    • Ensure custom components expose correct roles, states, and properties to screen readers.

      Read more → WCAG 2.1 SC 4.1.2: Name, Role, Value
    • Designs and components should be tested with screen readers, magnifiers, and other assistive tools across platforms.

      Read more → WCAG 2.1 Overview

    Understand

    Users must be able to comprehend what they see and what to do next. Designs should communicate clearly, using familiar language, visual hierarchy, and system feedback.


    Language & Terminology

    Ensure that content is readable, inclusive, and aligned with user expectations.

    • Text is readable, concise, and appropriate for the audience. Avoid jargon and ambiguity.

    • Labels, buttons, and instructions use consistent language across screens and flows.

    • The tone is appropriate for the context—friendly, professional, or instructional—and aligns with the brand’s voice.

    Visual Hierarchy & Layout

    Use layout, typography, and spacing to guide attention and reduce confusion.

    • Headings, body text, and labels follow a clear and consistent structure that reflects the importance and relationship of content.

    • Related elements are visually grouped using spacing, alignment, or containers. Adequate whitespace improves scanability and reduces visual noise.

    • Content aligns to a consistent grid or layout system, helping users predict where to find information and controls.

    • Visual elements support comprehension and usability. Decorative flourishes do not interfere with readability or distract from key tasks.

    System Feedback & Familiarity

    Provide timely feedback and use familiar patterns to reduce uncertainty.

    • Users are informed of what’s happening (loading, success, or error) through clear visual or haptic indicators.

    • Icons, metaphors, and interaction models align with user expectations and real-world conventions (e.g., trash can for delete, star for favourite).

    • Inline guidance, tooltips, and helper text clarify what users need to do, especially in forms or complex flows.

    • Multi-step processes show users where they are, what’s next, and how far they’ve come—reducing anxiety and improving task completion.

    Act

    Users must be able to confidently interact with the interface. Design should support intuitive, responsive, and predictable interaction.


    Navigation & Flow

    Ensure users can move through the product with ease and confidence.

    • Navigation patterns are familiar and consistent. Users can easily find their way through the app without needing to relearn controls on each screen.

    • Flows are structured to minimise unnecessary steps, interruptions, or dead ends. Users can pause and resume tasks without losing progress.

    • Users can return to previous steps or exit a flow without confusion or penalty. Back buttons and close icons are clearly visible and behave predictably.

    Component Behaviour

    Ensure that interactive elements behave consistently and predictably.

    • All components have clearly defined states (default, active, disabled, error). Users can easily tell what is interactive and what is not.

    • Buttons, toggles, and other controls behave the same way across screens. Similar actions yield similar results.

    • User actions trigger instant visual or haptic feedback to confirm interaction (e.g., button press, swipe gesture, form submission).

    Touch & Gesture Support

    Design for responsive, accessible, and forgiving touch interactions.

    • Interactive elements meet minimum size guidelines (e.g., 44x44pt) to support users with different motor abilities and device sizes.

    • Custom gestures (e.g., swipe, pinch) are supplemented with accessible alternatives like buttons or menus.

    • The interface accommodates slight inaccuracies in touch input. Taps near the edge of a button still register, and accidental swipes don’t trigger destructive actions.

    Recover

    Users must be able to recover from mistakes. Interfaces should help prevent errors and support easy correction when things go wrong.


    Error Prevention

    Designs should reduce the likelihood of user mistakes.

    • Forms and fields validate inputs in real time, preventing submission of incomplete or incorrect data.

    • Mandatory fields are clearly marked, and optional fields are visually distinguished to avoid confusion.

    • Only valid options are presented based on the user’s current context (e.g., disabling unavailable dates in a calendar picker).

    Error Handling & Guidance

    When errors do occur, users should be supported with clear, actionable feedback.

    • Messages are specific, human-readable, and explain what went wrong and how to fix it.

    • Errors are shown close to the relevant input or action, not buried in a generic alert.

    • Colour, icons, and text are used together to draw attention to issues without relying on colour alone.

    Undo, Cancel & Confirmation

    Users should be able to reverse or stop actions before they cause harm.

    • Users can easily reverse recent actions (e.g., deleting an item, sending a message).

    • Users can exit or cancel a process at any point without losing unrelated progress.

    • Destructive or irreversible actions (e.g. deleting data) require clear confirmation before proceeding.

    Trust

    Users must feel confident in the product. Interfaces should behave predictably and protect user data, privacy, and expectations.


    User Expectations & Predictability

    Designs should behave consistently and transparently to build user confidence.

    • UI elements behave the same way across screens and contexts. No unexpected changes or hidden actions.

    • Actions lead to predictable results. Users know what will happen before they tap, swipe, or submit.

    • Labels, icons, and microcopy reinforce what an action will do (e.g., “Delete permanently” vs. “Move to trash”).

    Privacy

    Designs should behave consistently and communicate clearly to build user confidence.

    • Only essential data is collected. Users are informed and in control of how their data is used.

    • Sensitive information is displayed thoughtfully based on context — avoid overtly prominent or persistent views unless necessary.

    • Users can toggle visibility of sensitive fields (e.g. show/hide password)

    Transparency & Communication

    Users should be informed about what the system is doing and why.

    • When requesting access to features (e.g. location, camera), the reason is clearly explained.

    • Changes to features, terms, or data handling are communicated clearly and respectfully.

    • Design includes subtle cues that reinforce safety and legitimacy (e.g., padlock icons, verified badges, secure checkout indicators).

    System

    Designs must scale and evolve. Interfaces should remain performant, consistent, and flexible as products grow and user needs change.


    Design System Alignment

    Ensure designs follow shared standards and are easy to maintain.

    • Designs use approved components from the design system where possible, avoiding unnecessary custom elements.

    • Spacing, colour, typography, and motion tokens are applied consistently across screens and states.

    • Designs are annotated or linked to documentation that helps developers implement them accurately.

    Cross-Platform

    Ensure shared experiences feel familiar across mobile and web.

    • Designs respect platform conventions (e.g. navigation, gestures) while maintaining brand consistency.

    • Buttons, forms, and other shared elements behave consistently across platforms unless there’s a clear reason to diverge.

    • Designs adapt to different screen sizes and orientations without breaking structure or usability.

    Performance

    Account for user expectations for speed especially in high-frequency or high-stakes flows.

    • High-frequency or high-impact interactions (e.g. login, checkout, navigation) are designed to load quickly and respond without delay.

    • Designs consider poor network conditions, with fallback UI and retry options.

    • Visual cues (e.g. skeleton screens, loading indicators) are used to reduce perceived wait time.

    • Design choices (e.g. image sizes, animation complexity) consider performance impact on low-end devices.

    Perceivable, 1 of 9

    Making design quality a standard

    Just Group + JPMorganChase
    Head of Product Design / Design Lead2022–2026
    Accessibility & UX checklists · 72 checks · WCAG AA

    Defined and introduced UX, UI and accessibility standards and design system QA, so designers know what to prepare and reviewers know what to check. The same standards now guide the AI agents in my practice.

    • FoundryA public lab for my design-engineering tools.foundry.assoc.one
    • ds.QualityA dashboard measuring design-system quality and AI readiness.Coming soon
    • careerOSMy career as markdown files an AI can read and reason over.Coming soon
    • MB—NA modern Welsh homeware brand I founded, rooted in everyday ritual, natural materials and local craftsmanship.madebyneud.com
  • How design leadership should actually work (according to me).

    I write Mr Pritchard’s Guide to Design on Substack. It draws on real experience of what has worked and what hasn’t.
    Mr Pritchard’s Guide to DesignSubscribe
    • You can't optimise your way out of a bad ideaRead
    • Most projects fail at the diagnosisRead
    • Welcome to the trials and tribulations.Read
  • Aled Pritchard

    Open to new roles

    Start a conversation

    Head of Design and Design Director roles, full-time, contract or interim. Also available for speaking at conferences and on podcasts.

    Topic
    or