Inclusive service design for the real world

I work with founders, product teams, and leaders to design digital services that are usable, accessible, and built around how people actually use them — not how we imagine they will.

I've done this across healthcare, gaming, retail, social impact, and non-profits. What those industries have in common is more interesting than what separates them: real people, real constraints, and services that need to work for everyone.

Where I've worked

I've worked across North America, Europe, Asia-Pacific, and Oceania — across regulation, culture, and distributed delivery. That breadth shapes how I approach problems.

  • 🎮 Games & Digital Media - player experiences, partner platforms, and internal service ecosystems
  • 🏥 Healthcare & Life Sciences - patient services, clinician tools, health platforms, and accessibility‑critical systems
  • 🛍️ Retail & Consumer Products - e‑commerce, loyalty platforms, online journeys, and customer support services
  • 🌍 Social Impact & Non‑profits - public‑interest platforms, education, and community services

FRAME: how I structure the work

FRAME is the model I use to make sure I'm solving the right problem — not just the visible one.

It's a way of looking at services from the inside out: understanding how things actually run before designing how they should. It adapts to what the engagement needs — some projects use one stage, others move through all five.

  1. F: Find the system reality

    Understand how the service actually operates — across users, accessibility, architecture, ownership, and constraints. Start with what's real.

  2. R: Represent the ecosystem

    Map journeys, dependencies, and how teams interact — so everyone is working from the same picture.

  3. A: Architect practical improvements

    Design accessible, feasible improvements that fit how your teams actually deliver — not a blueprint for an ideal world.

  4. M: Mobilize and embed

    Embed changes into how product, engineering, legal, and leadership actually work — so improvements don't rely on one person to maintain.

  5. E: Evaluate and evolve

    Measure impact and keep improving. Good services get stronger over time — that doesn't happen by accident.

Services

Whatever stage your product is at, the work looks similar: understand the system, close the gaps, and build something that holds up as things change.

Service & Experience Design

Aligning your product, teams, and operations across the full journey — because a good experience on screen still falls apart if the organisation behind it isn't aligned.

  • 🗺️ End‑to‑end journey mapping - Identifying friction, drop-off points, and operational gaps across the entire user experience.
  • 🏗️ Service blueprints and operating models - Clarifying how internal teams, systems, and workflows support what customers see.
  • 🔄 Cross‑channel experience design - Ensuring consistency across product, support, marketing, and delivery touchpoints.
  • 🧭 Product and platform strategy alignment - Connecting roadmap decisions to long-term business and technical goals.
  • 🧱 Information architecture, wireframes, and prototypes - Testing structure and flow before investing heavily in build.
  • 🔬 User research and testing programs - Grounding decisions in evidence, not assumptions.

Outcome: Clearer ownership, less friction, and services that hold up as they grow.


Past Projects: Equal Entry, medi.me & Weight Watchers

Accessibility & Inclusive Design

Embedding accessibility into how your organisation builds and evolves products — because it's not a feature, it's how you build things.

  • 📊 Around the world - 1 in 4 adults in the U.S. and Europe have a disability. 16% of people in Asia and the Pacific. 27% of Canadians aged 15 and above. These are already your users, your players, your customers — designing for them makes the experience better for everyone
  • WCAG audits and remediation plans - Prioritizing accessibility improvements based impact, not just compliance.
  • 🧩 Inclusive design systems - Building accessible foundations into product infrastructure so decisions made once multiply across every screen.
  • 🎓 Accessibility governance and enablement - Accountability models and training so accessibility stays embedded over time, not just during a project.
  • 👩‍🦽 User testing with people with disabilities - Validating real-world usability beyond checklists.
  • 🏢 Organizational accessibility assessments - Evaluating maturity and defining a realistic path forward.

Outcome: Accessibility that supports your users, your growth, and your team's confidence — without having to start from scratch every time.


Past Projects: Square Enix & Square Enix Hub

Playtesting Accessibility Review

There's a big difference between checking a game against a guidelines list and watching someone with a disability actually try to play it. This service does the second thing.

  • 🎮 Structured playtesting sessions - Remote, on players' own devices, in their real gaming environments.
  • 👥 Diverse player cohort recruitment, including players with disabilities.
  • ⏺️ Session recordings with voice, screen, and touch interaction captured.
  • ⭐ Accessibility friction report with severity ratings and gameplay context.
  • 📋 Prioritized recommendations mapped to your development stage.
  • 🗒️ Synthesis notes and highlight clips — ready to share with your team.
  • 💭 Optional: follow-up validation round after fixes are implemented.

Outcome: Barriers caught before launch. Player evidence — real clips, real feedback — to make the case for fixes. Games that actually work for the players who are often left out.

Design Systems & Governance

Accessibility decisions made in a design system get multiplied across every screen, every flow, and every update. Getting them right early saves a lot of fixing later.

  • 🧰 Design systems and component libraries - Reducing inconsistency and accelerating delivery with accessible foundations built in from the start.
  • 🖱️ Interface and interaction design - Improving usability while strengthening brand clarity.
  • 🤝 Cross-team collaboration models - Aligning design and development across distributed teams.
  • 🗒️ Accessibility annotation standards for handoff - So engineers know exactly what's expected.
  • ♿ Audit of existing component library against WCAG 2.2 AA.

Outcome: Accessibility decisions made once multiply across the whole product. New components are accessible by default. Faster iteration, stronger coherence, and a shared foundation that scales.

Platform Strategy & Delivery

Strengthening the structural foundation of your digital services so they hold up as complexity increases.

  • 🏗️ Accessible front-end architecture strategy - Ensuring resilience across devices and assistive technologies.
  • Usability optimization tied to KPIs - Improving task completion, engagement, and retention.
  • 📱 Responsive, multi‑device experiences - Ensuring everything works well on phones, tablets, and computers.
  • 🤝 Implementation oversight and developer collaboration - Bridging strategy and build to reduce delivery gaps.

Outcome: Platforms that stay coherent, accessible, and resilient as they grow — without accumulating technical or accessibility debt.


Past Projects: Shoogies NYC

Ongoing Support

Most of the best work happens after the first project ends. I stay involved — at whatever pace makes sense for your team.

  • 👀 Regular check-in sessions - Frequency matched to your team's pace.
  • 👨🏽‍🔬 Retest support as fixes are implemented.
  • 💬 Advice on accessibility questions as your product evolves.
  • 🧠 Training refreshers when teams grow or change.
  • 🤝 A standing relationship, not a series of cold starts.

Outcome: Progress keeps moving after the initial engagement ends. Your team has someone to call when an accessibility question comes up — without having to re-brief a new consultant every time.

My Approach

My work is grounded in collaborative, research-led service design. I adapt methods to fit your goals and constraints — drawing from Agile, Lean, and systems thinking where they're useful, not as a performance.

No theatre. No abstract decks that never ship. Everything is designed to be implemented.

Depending on what you need, I can work in an advisory, embedded, or delivery capacity — with clear milestones and checkpoints so progress is visible throughout.

Time, cost and retainers

Engagements are structured to be transparent, predictable, and aligned with real planning cycles.

Project Timelines

Most projects run between 2–12 weeks, depending on scope and complexity. Larger initiatives can be phased.

Cost Structure

Pricing is based on what the engagement actually involves — scope, duration, and how involved I need to be. Every proposal includes clear milestones and deliverables so there are no surprises.

Retainers

For teams who want ongoing support, retainers work well. They give you consistent access, continuity across strategy and delivery, and someone who knows your product without needing to be briefed from scratch every time.

This works particularly well for enterprise teams, non-profits with continuous delivery, and startups preparing for growth.

If this sounds like the kind of problem you're sitting with, I'd be glad to talk. A 30-minute call is a good place to start.

Book a 30‑minute discovery call
Consistently demonstrated exceptional organization and a self-driven approach. …made a significant impact on our teams. Janus Rau Sørensen Greenlight & User Research Director, Square Enix