Professional/Case Studies/Case Study 04

Professional · Case Study 04

Military Customer Verification Redesign

Consumer Product Craft · Lowe's

A verification flow that made loyal customers give up partway through. The fix wasn't a new interface — it was one reordered step that protected revenue, lifted conversion, and turned a discount into a loyalty event.

57%

Faster task completion

91%

Verified completion rate

19pt

Drop-off reduction

4.7/5

User satisfaction

Organization

Lowe's Companies, Inc.

Fortune 50 Retail

Role

Senior UX Manager

Product UX & delivery

Team

1 designer · 1 researcher

1 content designer

Timeline

2 sprints

Discovery → launch

The Business Problem

A design symptom on top of a business-architecture flaw.

Lowe's military discount program serves one of the company's most loyal, high-value customer segments. To claim the discount, military members had to verify eligibility through a third-party identity provider before a Lowe's account was ever created.

That one sequencing decision cost the company on three fronts at once: verification spend on people who never converted, loyalty enrollment delayed for a premium segment, and an experience out of step with modern standards.

This was not a design problem. It was a business-architecture problem with a design symptom.

No Intake

No defined problem statement, segment, or objective

No Framework

No phased process from discovery to validation

No Metrics

No defined criteria for what success looked like

The Diagnosis

The business case was formed without UX in the room.

The ask that reached the design team was scoped as a UI modernization. That framing missed the actual problem. Without intervention, this would have shipped as a surface-level refresh — faster to execute, and far less valuable.

The Intervention

2 structural moves.

Framework

A seven-phase delivery framework, introduced before design began

I established the operating structure first. Each phase had defined entry criteria, artifact outputs, and a handoff condition. No work entered development until it passed validation — and the framework became the team's repeatable standard going forward.

  • 01 · Strategy & Intake
  • 02 · Pre-Discovery
  • 03 · Discovery
  • 04 · IA & Wireframing
  • 05 · Visual + Content
  • 06 · User Testing
  • 07 · Ready for Dev
Decisions

Three decisions shaped the outcome

Discovery produced personas, journey maps, and requirements. User testing validated with real military-affiliated participants before anything reached engineering. Every phase produced evidence; every handoff was earned.

  • 01 · Reframe the problem — moved the work from “UI refresh” to business architecture; the sequencing was the issue, not the styling.
  • 02 · Find the retention opportunity — members who abandoned before account creation were never enrolled. I connected the redesign to loyalty acquisition, expanding the business case beyond cost.
  • 03 · Structure delivery before execution — research methodology and success metrics were defined before a single screen was designed.

The Result

Every metric traces to a decision made before design began.

Completion rate

72%

91%

Average completion time

6m 45s

3m 10s

Drop-off rate

28%

9%

User satisfaction (1–5)

3.2

4.7

Source: user validation with military-affiliated participants · old flow vs. new flow

Three fronts, one reordered step.

Retention

A discount transaction became a loyalty acquisition event — members enroll earlier, before verification completes.

Conversion

Completion up 19 points; drop-off cut from 28% to 9% by removing the primary abandonment point.

Cost

Unqualified verification spend eliminated — Lowe's stopped paying for users who would never onboard.

Leadership in Action

Craft and strategic influence, in the same project.

Upstream business influence.

UX entered at the strategic layer before the business case was finalized. The loyalty opportunity was surfaced before a single screen existed.

Delivery structure as a business decision.

The seven-phase framework was introduced, applied, and institutionalized — governance was the mechanism that converted a tactical request into a measurable outcome.

Consumer craft at scale.

The redesigned flow was validated with real users and landed a 4.7/5 satisfaction score. The outcome took both structural governance and screen-level product judgment.

The lesson I reuse everywhere: treat compliance as a design partner, not a constraint to fight. The wall was never the requirement. It was the order we asked for it in.