Website
Use case
Highlights
Standardized persona structure across teams
Introduced gaps tracking and validation model
Connected personas to real workflows and product decisions
Enabled consistent decision-making across UX, product, and engineering
Overview
Personas existed — but they were not usable.
Different teams had different formats. Content varied in quality. There was no shared structure, no validation model, and no connection to how the product was built.
They drifted over time.
The goal was to make personas something the product could rely on.
Understanding the Problem
The issue was not lack of research. It was lack of system.
Personas inconsistent across teams
No standard structure or completeness criteria
Gaps in key fields and validation
Limited connection to real workflows
No ongoing maintenance or ownership
Without structure, personas became static documents.
Strategic approach
The approach was to treat personas as infrastructure — not deliverables.
Building a performance model for UX
I defined a standardized template with consistent sections, layout rules, and completeness criteria.
Each persona captured responsibilities, workflows, constraints, tools, and decision behavior in a comparable format.
I introduced a gaps tracking system to measure completeness and confidence. Missing fields, evidence coverage, and validation status were tracked and resolved over time.
The system was grounded in real inputs: support tickets, customer calls, shadowing, onboarding notes, and SME validation. Where available, usage data and workflow timing were layered in.
Personas were then operationalized as a shared system, not a one-time output.
Principle: Personas create value when they are structured, validated, and maintained.
Key Initiatives
Standardized persona template
Personas varied widely in structure and quality.
What I did
Defined a consistent template across all personas
Standardized sections such as workflows, goals, constraints, and behaviors
Established layout rules for clarity and comparison
What changed
Personas became comparable across teams
Consistency improved across the system
Teams could scan and use them quickly
Gaps tracking and validation
Persona quality and completeness were inconsistent.
What I did
Introduced a gaps tracker to measure missing fields and confidence levels
Defined validation loops using SMEs, tickets, and observation
Tracked status and ownership for ongoing refinement
What changed
Persona quality became measurable
Gaps were visible and actionable
The system improved over time instead of drifting
Workflow alignment and research synthesis
Personas were not grounded in real usage.
What I did
Synthesized inputs from tickets, interviews, shadowing, and onboarding data
Mapped workflows, constraints, and collaboration patterns
Connected personas directly to how work actually happened
What changed
Personas reflected real behavior
Design decisions aligned with actual workflows
Less reliance on assumptions
Additional improvements
Centralized persona hub with consistent naming and structure
Linked personas to workflows, evidence, and gaps
Established maintenance cadence aligned with product changes
Created shared language across UX, product, and engineering
Cross-Functional Collaboration
Worked across UX, product, engineering, and SMEs. Aligned teams on a shared model of users and workflows. Used personas as a reference point for decisions, not documentation.
Financial Impact & Business Enablement
Personas became usable.
They shifted from static documents to a system that supported decisions.
Teams aligned faster. Workflows were clearer. Product direction became more grounded.
Reduced misalignment in product decisions
Faster alignment across teams
More efficient research reuse
Improved product direction through better user understanding
Takeaway
Research scales when it is structured. Without a system, it drifts. With one, it drives decisions.
Role
Director of UX
Designed and implemented the persona system. Defined structure, validation, and maintenance processes, and connected personas to real workflows to support consistent product decisions across teams.
Related Case Studies
Reducing onboarding friction by restructuring how users reach first value.
Making dependency behavior predictable in a visual planning system.
Scaling a product with limited design resources by building systems, not screens.
Lowering early drop off by restructuring how users reach first value.
Keep the product focused on the planning model, not expanding features.
Making product decisions that preserve control and predictability.
Designing scheduling behavior that feels powerful without becoming unpredictable.
Using direct observation to guide product decisions when analytics are incomplete.
Turning design from a service into a system tied to delivery outcomes.
Driving adoption and executive buy-in through phased, measurable impact.
Turning design into a decision driver by making its impact visible.
Turning fragmented research into a system that guides product decisions.