Case Study 01
Architecting Clarity in a High Complexity Delivery System
Enterprise UX Operating Model Transformation · Lowe's
A 30+ person UX organization was absorbing a structural failure the company kept reading as a design problem. I rebuilt how work entered the system and turned volatile delivery into a measurable, durable operation.
Organization
Lowe's Companies, Inc.
Role
Senior UX Manager
Scope
30+ practitioners · 12 Direct reports
Window
Q3- Q4 2024
The Problem
Delivery volatility was systemic, not individual.
UX was being pulled in after product decisions were already locked.
Requirements arrived incomplete. There was no unified process across designers, content, and research (no sprint schedule, no pointing system, no shared definition of “ready.”) Rework was constant and untracked, and Product had lost trust in UX delivery.
~50%
Jira ticket carryover
<50%
Sprint commitment accuracy
35–40%
Mid-sprint requirement changes
Weekly
Stakeholder escalations
Untracked
Rework absorbing capacity
Zero
Unified process across disciplines
The Diagnosis
Before fixing anything, I looked inward.
I audited how UX was actually delivering, not how we assumed we were. I looked at Jira reopen and carryover data, clarification meeting tracking, and a map of how work moved from intake to handoff. No RACI. No consistent tracking. Ad hoc alignment with Product on no defined cadence.
The Decision
Two competing explanations surfaced early. One team believed it was design capability; another believed it was insufficient Product engagement. The data showed symptoms of both but neither explained the pattern.
The Operating Model
Five structural levers, one system.
Every intervention targeted the operating model, not individual behavior and was designed to be maintained without the person who built it.
01
Sprint Stability
Defined schedules, agile pointing, and structured touchpoints that make commitments visible and reliable.
02
Intake Discipline
03
Research Activation
04
Accountability
05
AI Governance
Prompt frameworks, mandatory human review gates, and cross-discipline guardrails, adopted in under 60 days.
The Intervention
4 structural moves.
Move 01
Unified Internal Process + RACI
I aligned designers, content, and research to a single delivery model and defined who owns what at every stage. Ambiguity inside the team was eliminated before I addressed anything external — you can’t ask Product to trust a process you don’t have yourself.
Move 02
Sprint Infrastructure
Intake
Problem definition & success criteria validated
Discovery
Research activation & requirement refinement
Design
Structured iteration within sprint guardrails
Validation
Stakeholder & feasibility alignment
Delivery
Engineering handoff with stable scope
Measurement
Sprint performance tracking
Move 03
Transparent Delivery
Two structured Product touchpoints per sprint: one to show progress and gather feedback, one for final review and sign-off. Transparency replaced assumption, reinforced by a defined rhythm every discipline operated from.
Mon · D1
Stand-up
Sprint Planning
UX/PM Sync
TUES · D2
Stand-up
Design Review
WED · D3
Stand-up
Lead Review
thurs· D4
Stand-up
Lead Review
Fri · D5
Stand-up
Lead Review
mon · D6
Stand-up
Backlog Refinement
Tues · D7
Stand-up
Backlog Refinement
Wed · D8
Stand-up
Backlog Refinement
Thu · D9
Stand-up
Backlog Refinement
Fri · D10
Stand-up;
Sprint Review
Move 05
The UX Ready Intake Gate
The keystone. Requirements were validated before design started and if a level of effort couldn’t be determined, work didn’t begin. That was the signal requirements were missing. Scope creep was stopped at the entry point. All five must be present at intake before work is committed.
- 01 · Business Goals & Success Metrics: What problem are we solving, and how will success be measured?
- 02 · User Needs & Research Insights: Who are the users, and what are their needs and behaviors?
- 03 · Technical & Business Constraints: Are there dependencies or limitations to be aware of?
- 04 · Scope, Effort & Prioritization: Must-haves versus nice-to-haves, and a design level of effort we can actually size. If we can't size it, requirements are missing.
- 05 · Cross-functional Alignment & Ownership: Product, Engineering, and stakeholders agreed, with a named decision owner
The Result
Delivery became predictable. Trust was restored.
35–45% → <15%
baseline → −50–65%
<50% → ~80%
Weekly → Occasional
Source: Jira sprint analytics & ticket tracking; sprint retro analysis · Lowe’s, 2024
How UX moved upstream. The governance created its own leverage.
Influence wasn’t a single moment. It accumulated across sprints. As the UX Ready gate surfaced the real cost of incomplete requirements through carryover and escalation data, I took that evidence to product leadership. The argument was never about design quality. It was about delivery risk.
Governance
The gate produced hard data
Evidence
Carryover & escalation rates
Credibility
Risk framed in Product's terms
The Seat
UX invited before features locked
Leadership in Action
Enforcing structure before it was comfortable.
Reframed the problem with data.
When pushback came, I returned to the Jira audit, the carryover rates, and the escalation logs. The data removed opinion from the conversation.
Held the gate under resistance.
Product initially pushed back on UX Ready. I held the standard. Within two sprints, incomplete requirements dropped sharply and the gate became expected.
Built trust through transparency, not persuasion.
I didn't ask Product to trust UX. I gave them visibility into the work and let the results speak.
Leadership also meant building capability inside the system. An associate designer carried real fear about presenting to stakeholders. Rather than waiting for readiness, I created it, an internal presentation assignment, pairing with a content designer, and five coaching sessions. She presented confidently and engaged stakeholders directly from that point forward.