#DESIGNSYSTEMS #OPERATIONALISE RESEARCH #SCALE TEAMS
Scaling design quality without being the bottleneck
When C&R moved from a centralised design model to three empowered pods, design ownership stopped running through me — right as AI tools made it faster than ever for anyone to prototype. I replaced design review as the quality gate with principles and systems grounded in real customer evidence.
COMPANY
Compliance & Risks
ROLE
Senior Manager, Product Experience & Market Insights
TIMELINE
2024–2026
THE SITUATION
Three pods, AI-assisted prototyping, and no central checkpoint left to hold the product together
When the three pods were created, design ownership decentralised with them. Each pod now owned its own experience end-to-end — no more routing every decision through a central design function, which had effectively meant routing it through me. At the same time, designers, PMs, and engineers across all three pods were using AI tools to prototype and explore experiences directly, which meant far more design decisions were being made, faster, by far more people.
The risk was obvious: three pods moving independently, using AI to generate options quickly, with no central checkpoint. Without something to hold it together, the product would fragment into three different products that happened to share a logo.
WHAT WE DID
Defined principles from evidence, not from a workshop
I didn't draft principles in a room and circulate them for sign-off. I led a small, deliberately informed group — only people who had actually sat through the underlying research, hundreds of customer interviews — to draft behavioural rules grounded in real friction we'd seen, then validated them with the wider team rather than co-creating from scratch with everyone. The distinction mattered: principles built by people with direct evidence behave like decision tools; principles built by committee behave like values statements.
Five examples, each tied to a specific problem we'd actually seen:
Answer the user's question, not the dataset — built because showing all regulations overwhelmed users. Every screen had to resolve a concrete business question, not display everything available.
Summarise first, prove on demand — built because executives and SMEs needed fundamentally different depth from the same product. Always lead with a conclusion, but make drill-down immediate.
The system must explain itself — built because AI-driven outputs only get adopted when users understand why the system reached them. Visible reasoning, editable inputs, human override.
Never trap the workflow — built because compliance teams had existing processes outside our tool. The product had to support that process, not assume it would replace it.
Progressive commitment — built because first-time and expert users need different amounts of upfront input. Minimal commitment early, more specificity only once value is clear.
Each one is a decision rule, not an aspiration. "The system must explain itself" guided actual interaction patterns — visible reasoning, editable inputs — the same way "build trust" never would have.
"Each one is a decision rule, not an aspiration.."
Systemising research instead of gatekeeping it
Centralising design had also meant centralising who had access to customer insight. I changed that: each pod got direct access to its own customer research rather than insight flowing through one person. That meant pods could apply the principles against their own evidence when making fast calls, instead of waiting on a central decision-maker who'd become a bottleneck by design.
Measuring quality instead of approving it
Rather than holding quality at the review gate, I put measurement on the output itself — tracking customer effort to complete a job step, alongside output quality. That gave pods a live signal on whether their decisions were working, without needing my sign-off to find out.
IMPACT
Three pods shipping independently, faster, with no central design checkpoint
Three pods operating independently with AI-assisted prototyping at higher volume and speed than before, without a central design checkpoint
A shared set of behavioural principles in active use for day-to-day decisions across pods, not published and ignored
Customer insight decentralised to each pod, removing a structural bottleneck I had previously been the centre of
Quality measured continuously (customer effort, output quality) rather than gated at review
WHAT THIS TAUGHT ME
Quality has to be built into principles and systems, not enforced after the fact
Design reviews don't scale when teams move quickly — by the time something reaches review, the decision has already been made ten times over by the AI-assisted prototyping happening upstream.
And principles only work as decision tools if they're behavioural and evidence-based. The job wasn't to write principles — it was to change how decisions got made when I wasn't in the room.