Cloudflare's portfolio serves developers, IT administrators, and enterprise buyers, each with distinct workflows, expectations, and decision criteria.
Across 200+ products, the end-to-end experience lacked systemic consistency:
Fragmented patterns and interaction models
Inconsistent terminology
Uneven onboarding and guidance
Complex workflows with limited contextual support
The business impact was tangible:
Elevated support burden
Slower adoption across priority features
Friction in enterprise conversion paths
At scale, UX was sometimes perceived as slowing velocity, not accelerating it. The root issue was not craft quality. It was the operating model.
UX operated like a reactive service. It needed to operate like a product discipline.
I reframed UX as a product function with clear accountability to business outcomes.
To operationalize this shift, I completed Scrum Master training and structured the team around full agile execution, ensuring alignment with product and engineering rhythms.
01
Backlog
Requirement gathering and prioritization of user stories.
02
Planning
Scoping the sprint and defining the iteration goal.
03
Sprint
Development, daily syncs, and execution phase.
04
Review
Stakeholder demonstration and feedback loop.
05
Retro
Analyzing process and workflow improvements.
1. Run UX Like a Product Organization
We implemented disciplined product practices:
Defined UX OKRs tied directly to company-level metrics
Maintained a prioritized backlog of experience initiatives
Ran two-week sprint cycles with planning and retrospectives
Owned an independent UX roadmap aligned to product strategy
That roadmap spanned:
Experience consistency across product surfaces
Friction reduction and workflow optimization
AI-enabled enhancements
Net-new UX-driven initiatives
UX became a proactive strategic partner, not a downstream approver.
2. Design Systems, Not Point Solutions
Because the team operated across the portfolio, we had a cross-product architectural view.
We leveraged that perspective to:
Standardize interaction and language patterns at scale
Align navigation and product structures around Jobs-to-be-Done
Introduce reusable experience frameworks and components
Embed contextual guidance into high-friction workflows
Continuously evolve patterns through backlog grooming and iteration
Instead of optimizing isolated screens, we optimized experience systems.
3. Establish Measurable Feedback Loops
Aligned with my belief that there is no such thing as done, we treated experience design as iterative infrastructure.
We implemented:
Portfolio-wide measurement frameworks (Amplitude)
A/B testing tied to task success and conversion
Support deflection and workflow completion tracking
Ongoing monitoring of customer sentiment and behavioral signals
If improvements drove measurable results, we scaled them. If not, we iterated or retired them.
UX decisions were grounded in product analytics, not opinion.
Listen
Deliver
Measure
Build
Across priority journeys, results were measurable and sustained:
Increased engagement in targeted flows
Reduced time-to-comprehension in complex workflows
Lower support volume tied to UX friction
Improved trial-to-paid conversion
Higher completion rates in critical tasks
Organizational shifts included:
Experience governance enforced at portfolio scale
UX leaders embedded in PRD and architecture reviews
Cross-silo visibility informing enterprise-level decisions
Consistent design patterns applied across product domains
Most importantly:
UX became a measurable driver of product performance, integrated into how the company plans, builds, and ships, not a post-launch refinement layer.