Design Paradigms Design and technology analysis for UK product teams.

Design Paradigms

Design and technology analysis for UK product teams.

Latest Articles

Spent on Yes: A Consent Budget for UK Privacy Design
E-commerce

Spent on Yes: A Consent Budget for UK Privacy Design

Privacy design usually treats consent as a single decision on a single screen. In practice UK users are asked to agree to something dozens of times a week, across shop checkouts, apps and preference centres. This opinion piece proposes a consent budget model and argues that withdrawal should be designed as carefully as sign-up.

The Doormat Is the First Screen: Designing Notification Parity for UK Services
Accessibility

The Doormat Is the First Screen: Designing Notification Parity for UK Services

For a great many UK households, the first contact with a digital service is still a letter on the mat. This article argues that post, SMS, email and in-app messaging should be designed as a single notification surface, with consistent next actions and deadlines that survive the channel, and sets out practical envelope-to-screen tests for product teams.

Documentation as Interface: Designing UK APIs for the Partner in the Room
Product Design

Documentation as Interface: Designing UK APIs for the Partner in the Room

UK product teams refine the consumer screen while partners meet the same service through documentation, sandboxes, error codes and deprecation notices. This deep dive argues that API ergonomics is a design discipline in its own right, with practical tests for onboarding non-engineer partner staff and signalling change without breaking trust.

Sixty Minutes of Doubt: Auditing UK Product Assumptions at the Clock Change
Product Design

Sixty Minutes of Doubt: Auditing UK Product Assumptions at the Clock Change

The twice-yearly switch between BST and GMT is more than a calendar event; it is a controlled failure test for any UK service that stores, displays, or acts on local time. This article sets out where hidden time assumptions surface, and offers a practical audit for product teams ahead of the next transition.

Product Design

Where the Account Outlives the Owner: Designing a Verifiable Handover for UK Estates

UK executors now inherit not only property and paperwork but inboxes, subscriptions, cloud libraries, and domain names. Yet most services still treat bereavement as a contact form and a death certificate upload. This article argues for a verifiable, narrow, auditable handover protocol as a core service surface.

Last Orders: Designing the Final Mile of a UK Digital Service
Product Design

Last Orders: Designing the Final Mile of a UK Digital Service

UK product teams are fluent in launch and growth, but retirement is rarely treated as a designed experience. This article argues that end-of-life UX should be planned as a core service surface, with clear notice, usable data exit, assisted support and honest communication.

Degrees of Maybe: Interface Language for Systems That Cannot Be Certain
Product Design

Degrees of Maybe: Interface Language for Systems That Cannot Be Certain

Statistical models now sit behind ordinary UK service decisions, yet our interfaces still speak in the flat tone of a filing cabinet. A deliberate language of confidence bands, plain-English error margins and rehearsed fallbacks would let people calibrate trust rather than guess at it.

Outside the Confident Yes: Designing Identity Journeys for People the System Cannot Match
Accessibility

Outside the Confident Yes: Designing Identity Journeys for People the System Cannot Match

Biometric matching, document scanning and risk scoring increasingly decide who gets through UK services. For disabled users, older faces, people without passports and households with shared addresses, the confident yes never arrives. The fallback path now deserves the same design rigour as the happy path.

The Second Visitor: Designing UK Services for Software That Acts
Product Design

The Second Visitor: Designing UK Services for Software That Acts

AI agents are beginning to compare, book and transact on behalf of UK users, yet most interfaces still assume a human at the screen. A machine-readable service layer — structured offers, explicit consent, auditable actions and legible failure states — would let teams serve these secondary users without surrendering human oversight.

Holding Patterns: Designing Dignified Waiting for Services at Capacity
Product Design

Holding Patterns: Designing Dignified Waiting for Services at Capacity

Virtual waiting rooms have become a default response when UK services cannot meet demand. This article argues that the waiting state is now a primary product surface, and sets out practical patterns for honest capacity signalling, fair progression and dignified waiting.

Designing the Declined Path: Refusal as a Service Surface
Product Design

Designing the Declined Path: Refusal as a Service Surface

UK product teams tend to instrument the successful journey and leave refusal to a red banner or a generic letter. This article treats refusal as a designed service surface, with practical tests for intelligibility, agency, continuity and contestability.

The Handover Gap: Designing UK Products for the Owner After the First
Product Design

The Handover Gap: Designing UK Products for the Owner After the First

UK households increasingly pass on, resell and inherit digital devices, but most products still assume a single, original owner. This article examines the handover gap — account decoupling, licence transfer, warranty provenance and the awkward language of 'someone else's' — and sets out a practical audit for UK product teams.

The Silent Cohort: Designing for People Who Never Reach the Service
Product Design

The Silent Cohort: Designing for People Who Never Reach the Service

Research and analytics tend to describe the people who arrive. This article sets out an absent-user practice for UK product teams, drawing on frontline insight, dropout evidence and adversarial personas to treat non-participation as design data rather than an inconvenient gap.

Nobody at the Keyboard: Designing UK Services for Delegated Authority
Product Design

Nobody at the Keyboard: Designing UK Services for Delegated Authority

As AI agents book, switch, file and buy on behalf of UK users, the person operating a service is no longer the person looking at it. Product teams now need mandates with edges, revocation that can be proven, receipts written for humans, and a paper trail that survives a dispute.

Download Not Required: Designing UK Services That Assume No Install
Accessibility

Download Not Required: Designing UK Services That Assume No Install

App-only onboarding has become a quiet default in UK service design, but the customer without storage, confidence or consent is not an edge case. This article sets out a web-first blueprint that treats the non-downloader as a mainstream user.

The Conversational Reflex: When UK Product Teams Reach for Chat Too Soon
Product Design

The Conversational Reflex: When UK Product Teams Reach for Chat Too Soon

Conversational AI has become the default answer to almost every product problem, even when a form or filter would finish the job faster. This analysis offers a decision framework for UK teams weighing chat against clearer, more accessible interfaces.

Written Before the Wireframe: How UK Buying Decisions Become the Real Design System
Accessibility

Written Before the Wireframe: How UK Buying Decisions Become the Real Design System

By the time a UK product team opens a design tool, frameworks, contract clauses and evaluation weightings have already decided much of what can be built. This opinion piece argues that procurement is an invisible design system, and that designers need to be in the room when requirements are drafted rather than when screens are drawn.

Agency on Loan: Designing UK Products That Can Be Handed Back
Product Design

Agency on Loan: Designing UK Products That Can Be Handed Back

Delegation is quietly becoming a default mode of interaction, and most interface conventions were never built for it. This analysis sets out what changes when the person in front of the screen stops being the operator and becomes the principal, and offers a working checklist for consent, auditability and graceful handback in UK services.

The Long Service: Making Maintenance a Design Discipline
Product Design

The Long Service: Making Maintenance a Design Discipline

UK product teams are still rewarded for launch dates, while many services spend a decade or more in maintenance. This article argues that maintenance deserves its own design practice: documented intent, reversible choices, planned component lifecycles and a considered UX for gradual change.

Accessibility

Who Wrote This Screen? Provenance That Works Beyond the Badge

Generative AI is moving into UK dashboards, writing tools and service flows. If users cannot tell what was generated, edited or uncertain, trust becomes guesswork. This article sets out accessible provenance patterns that make accountability visible without turning every screen into a disclaimer.