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

3 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.

The initiative addressed a broken enterprise flow that was costing Lowe’s on three dimensions simultaneously:

  • Verification spend on user who never converted
  • Loyalty enrollment delay for a high-valued customer segment
  • Digital experience out of step with modern standards.

The existing flow had a structural flaw: It required ID.me verification before account creation. That sequencing decision had downstream consequences across cost, conversion, and customer loyalty. This was not a design problem. It was a business architecture problem with a design symptom. 

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 Decision

The structural insight came out of Discovery: the flow charged Lowe’s for verification before confirming anyone intended to become a customer.

Before: Verify Identity → Create Account → Access Discount. Cost incurred before account creation, including for users who abandoned.

After: Create Account → Verify Identity → Discount + Loyalty. Verification cost gated to confirmed account holders. Loyalty captured up front.

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.

Decisions

Three decisions shaped the outcome

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.

cs4-02-branded-mobile-design

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

cs4-05-registration-flow.webp

Three fronts, one reordered step.

Retention

A discount transaction became a loyalty acquisition event, ie 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.