RSA Replay: From Persuasion to Usability - Design Meets the Internet

Main ideas, concepts, and lessons

• Design has drifted from usability to persuasion

  • Ben argues that design in organizations (especially in marketing contexts) has become overly focused on persuading people rather than helping them accomplish tasks.
  • His central theme: design needs to get back to being about usability.

• The internet’s best practices align with design best practices

  • He claims that “design at its best” shares values with “the internet at its best.”
  • Those shared values include:
    • user focus
    • openness
    • iterative delivery
    • reducing bottlenecks

• Government Digital Service (GDS) as proof that design creates real public value

  • GDS’s work is presented as evidence that good design leads to measurable outcomes:
    • Cost savings (reported as £1.7 billion saved in the prior year across government digital work).
    • User improvements (people can complete important tasks more easily, including legal/administrative ones).
  • Awards are mentioned, but framed as secondary to impact.

• Usability-focused examples: icons removal and readable typography

  • Icons on early gov.uk drafts
    • Even visually attractive icons were confusing.
    • The team removed them after user testing showed users didn’t understand them.
  • Road signs and typography
    • gov.uk uses a digital version of a road-sign typeface designed for visibility at speed and in bad conditions.
    • The rationale: typography is chosen because it’s easy to read and tests best with users, not because of branding or storytelling.

• “UX” should not be treated as a silo

  • He challenges how “UX” is used in some companies:
    • UX becomes a late-stage “month of UX” activity.
    • He argues user experience is everyone’s responsibility, including infrastructure, contracts, performance, and content.
  • If websites are “clunky,” it may be due to hosting/server/contract decisions—not something a UX team alone can fix.

• Design should be embedded in delivery and trust-building

  • Trust comes from delivery, not persuasion or creative passion.
  • Design gains influence when it consistently improves real services.

• Adopt an agile, empowered, and open operating model

  • He contrasts:
    • Waterfall: long cycles (requirements → procurement → build → launch), often too late for user needs.
    • Agile: short discovery, build small prototypes (alphas/betas), test continuously with real users, then scale.
  • Why their model works:
    • pushes power down to those doing the work (reducing bottlenecks like sign-offs)
    • enables peer review
    • relies on openness (published patterns/guidelines)

• Openness as leadership

  • Publishing design guidance and patterns publicly is emphasized.
  • Openness is portrayed as essential to leadership and to spreading improvements across organizations and countries.

• Inclusivity and accessibility through “one best site”

  • Accessibility should be built in—not handled via separate “mode toggles” that create multiple versions.
  • The approach includes:
    • strong emphasis on user research
    • an accessibility lead role
    • designing for inclusion as part of “good design”

• Collaboration: everyone contributes to content and design

  • He describes a “zero creative overhead” approach:
    • reducing barriers between roles
    • working directly with content designers and others rather than handing off finished designs for later editing
  • Teams avoid “designing a picture of the thing”; they build the real thing quickly.

• Continual iteration, not one-time testing

  • User research is described as an ongoing loop throughout the project lifecycle (not a one-off step before launch).

• Public-sector design as formative for careers

  • Working in the public sector is described as enriching for designers:
    • different problem types
    • longer time horizons
    • “stuff that matters”
  • He suggests a possible government “design fast stream” for early-career designers.

---

Methodology / instructions presented (detailed bullet format)

A) “Start with needs” (user needs > government process)

• At project kickoff, focus relentlessly on user needs.
• Write principles that explicitly put user needs first, e.g., “the user is trying to do X, not the government process Y.”
• Reinforce seriousness through public accountability (he cites a House of Commons exchange stating this user-centered intent).
• Use user research to validate that the approach matches real user understanding.

B) Use user testing to remove/adjust elements that users misunderstand

• Identify design assets built on assumptions or aesthetics (e.g., early gov.uk icons).
• Test with real users to check comprehension and task success.
• If users don’t understand visual elements:
  • remove or redesign them, even if they are “beautiful” branding artifacts.
• Document changes (e.g., a blog post describing the removal decision).

C) Choose solutions by readability and real performance, not story/branding

• For typography/design system decisions:
  • test multiple options with users
  • pick the typeface/design elements that consistently test best for usability outcomes (e.g., reading speed/legibility)

D) Treat UX as everyone’s responsibility (avoid “UX as a final month”)

• Do not postpone usability improvements until late in the timeline.
• Ensure the entire delivery chain supports usability:
  • design, content, performance, hosting, and procurement all affect user experience.
• Set leadership expectations so UX can’t be “bought” as a bolt-on.

E) Run design with agile delivery and continuous iteration

• Avoid waterfall-style sequencing (requirements → procurement → build → late launch).
• Use an agile cycle:
  • Discovery: a small initial session (days to weeks)
  • Build alphas/betas quickly
  • Test with real users continuously
  • Scale only after evidence shows it works
• Maintain continuous loops rather than a single “launch + stop” mindset.

F) Empower teams and reduce bottlenecks

• Reduce dependence on centralized approval:
  • devolve power to the teams doing the work.
• Implement:
  • team-level publishing decisions for many changes
  • peer review for small changes
  • escalation to leadership for larger changes

G) Design by building code early (not just mockups)

• Start by sketching, but move quickly into real code instead of relying on “wireframes” or “Photoshop mock-ups.”
• The goal is to prototype the real experience early.

H) Publish patterns/guidelines openly and keep them current

• Make design principles and patterns:
  • publicly accessible
  • updated through contributions from across the design community
• Use shared repositories (described as a “hack pad”/wiki-like system).
• Require compliance via service assessment before changes go live.

I) Inclusivity/accessibility approach

• Build accessibility into the single site design:
  • do not create separate versions for accessibility adjustments
• Provide accessibility expertise in the organization (a dedicated accessibility lead).
• Validate inclusivity outcomes using ongoing user research.

J) Collaborative, cross-role design workflow (“break barriers”)

• Sit designers with other key roles:
  • content designers
  • researchers
  • developers
• Avoid “designing then throwing it over the wall” to content.
• Use joint sessions to uncover what the content truly needs and prevent design from masking weak writing.

---

Speakers / sources featured (as named in the subtitles)

• Ben Terrett — RSA student design award alumnus; keynote speaker; Director of Design at the Government Digital Service (GDS) (per talk).
• Severa Davis — Director of Design and Challenges at the RSA; head of the RSA Student Design Awards program; event host/introducer.
• Francis Maude — cited as Minister for the Cabinet Office; asked about user-needs-centered service reform in the House of Commons.
• Martha Lane Fox — mentioned as writing the government digital report (with a structure of four main areas).
• Louise Down — referenced as taking over leadership of design across government next month.
• Henry Ford — quoted: about reputation and trust being earned through actions.
• Tim O’Reilly — referenced with the phrase about “work on stuff that matters.”
• Jock Kinnear — referenced as part of road signs design history.
• Margaret Calvert — referenced as road signs designer; also described as a mentor/fierce critic during early gov.uk work.
• Mark — mentioned indirectly in the Q&A regarding languages (Mark “sat on the front row”).
• Lisa Reichelt — referenced as supporting the establishment of user research practice/profession within GDS/government.

---

Other institutional sources mentioned

• RSA (Royal Society of Arts) — organizer/context for the event.
• Government Digital Service (GDS) — central case study.
• Cabinet Office — government body referenced.
• House of Commons — referenced for the recorded/public exchange.
• Major Projects Authority — referenced in Q&A about agile vs traditional civil service processes.
• DWP (Department for Work and Pensions) — referenced (e.g., Universal Credit).
• University of the Arts London — referenced as a place with students in attendance and Ben’s governance role.
• London Design Festival — referenced as an advisory role and current events.