CX Studio
A service design tool for UX teams, now in beta.
The brief · My own product, in beta
A service design tool for design teams: understand experiences in layers, turn issues into solutions, and follow each change through handover and adoption by the teams who own it.
- Started
- 2026
- Built by
- Solowith AI agents
- Capabilities
- 6in the beta
- Checkpoints
- 4from handover to monitoring
My roleEverything, solo
I designed and built it myself: research into existing tools, product definition, the service model behind it, interface design, the build with AI agents, and the verification and review standards.
Tools, not a teamSolo build
No team: a solo build with Claude Code and ChatGPT, and an independent review before each increment is accepted.
- Claude Code
- ChatGPT
- Independent review
Outcome
Designed and built solo, in beta.
Why I built it
Before building anything, I reviewed what already exists: journey management tools, whiteboards, CX platforms, research repositories and ecosystem mapping. Each covers one part of the work well. None of the ones I reviewed connects understanding an experience, designing the change and following it through to adoption.
So I built one from the ground up, modular by design, so it can change as the team learns.
- Journey management tools
- Whiteboards
- CX platforms
- Research repositories
- Ecosystem mapping
One connected flow, in CX Studio
- Understanding an experience
- Designing the change
- Following it through to adoption
People, journeys, blueprints and evidence, connected to what follows
Three equal workflows connect the same people, journeys, blueprints and evidence. Pick a way in to follow it.
Everything connectsIllustrative
Three equal ways in
Every layer of the experience, and the service behind it
Open the whole journey, step into a moment, then into a single interaction. Turn any of them over to see the service that makes it work.
Every layer, and the service behind itIllustrative
From decision to adoption
Every change is followed through four checkpoints: handover, delivery support, delivery review and experience monitoring. The design team recommends, and the delivery owner decides what ships.
Design standards and principle checks
What is in the beta
Available to explore now, with synthetic data.
- 01Journeys in layers
Current and future journeys, from the whole experience down to a single interaction.
- 02Service blueprints
The service behind each interaction, with handovers recorded as agreements.
- 03Touchpoints, evidence and issues
Evidence and changes stay linked to their context, with issues and opportunities beside them.
- 04Decisions and adoption
Decisions, handover and adoption tracked at four checkpoints, with owners.
- 05Metrics and standards
Metrics, standards and principle checks, built into the underlying model.
- 06Templates and a library
Start from a template, reuse shared touchpoints, and keep an inspiration wall.
The outcome
A beta running in a protected review environment, with synthetic demonstration data. Usability testing with people is still to come.
Planned nextWorkshop mode
A collaborative canvas where a team builds a journey together in the room.
Under consideration, not builtMore help from AI and data
AI drafts for a designer to review, connections to surveys, NPS and analytics, and roles that help people find what needs their attention.
The decisions
Seven decisions, across five chapters.
Select a decision to read what I chose and why.
Chapter 01Why I built it
Chapter 03Layers
Chapter 04Decision to adoption
Chapter 05Standards
Chapter 06The beta
Decision 1 of 7 · Chapter 01 · Why I built it
Build the tool around the work
Instead of fitting the work to an existing tool
WhyA design team needs a connected way to understand experiences, build solutions and follow their adoption, not only individual features.
I built the tool around how a service design team works.
Contact
Open to design leadership roles.
I’m based in Singapore and can work in Singapore and the EU without sponsorship. Available now.