DEERE: FORCED ADOPTION, WITHOUT THE FORCE

Driving platform-wide data adoption across 500K+ users without breaking trust — on the flow that gates Deere's $3.8B connected-services business

RoleSenior Lead UX — Digital Customer Experience
ScopeAccount Systems · Identity · Dealer Workflows · Multi-channel Onboarding
Timeline2020 – 2024
What I DidEmbedded lead designer across product teams — sole UX owner for licensing and account flows, partnering with 40+ product teams on the design system.

The Real Problem

The problem was never licensing.

A single physical machine could, at one moment, carry multiple owners and multiple operators, sit mid-transfer between dealers, and run a paid license alongside a free trial and an already-expired service — with features metered by consumption, licensed by the acre or the gallon sprayed. Each was a different data-consent condition. Every exception multiplied against every other.

So the real problem wasn't a screen. It was a state space that exploded faster than any single flow could keep up with — and the connected-services business Deere was betting its future on couldn't switch on until that state space was legible enough to design around.

The challenge wasn't designing another form. It was making an exploding state space simple enough that 500,000 people would opt in without being forced — on a brand nearly two centuries old, where forcing the door is a one-way trust hit.

Why This Was Hard

This problem sat at the intersection of business risk, user trust, and organizational complexity:

  • User diversity: Customers ranged from highly technical operators to users without email access—and accessibility couldn't be an afterthought across that range
  • Data sensitivity: Sharing triggered deep concerns around surveillance, ownership, and value exchange
  • System fragmentation: Decades of acquisitions left inconsistent data models, legacy systems, and accumulated tech debt
  • Sales-model variance: The same equipment was sold a dozen ways—per acre, per hour of use, outright, dealer-financed—so there was no single "customer" or "transaction" to design the flow around
  • Relationship complexity: Dealers—not Deere—owned many customer relationships
  • Hardware on a waterfall: Connected services ride on machines shipped on multi-year manufacturing cycles—you can't sprint embedded-equipment UX when the tractor it lives on is on a manufacturing waterfall
  • Global scale: 12 languages across diverse regulatory environments

A purely coercive approach would have increased churn and damaged long-term brand trust.

The System Underneath

Designing the adoption flow meant first modeling the system it lived in — every state, every transition, every edge case — so we built for reality, not the happy path.

THE COLLAPSE — every cell is a different consent question, multiplied by 12 languages and per-region rules. You can't ship a screen per cell — so we reduced the matrix to one lifecycle with one unlock: the owner accepting terms. Every prompt, dealer tool, and trust message hangs off the states below.

UNCLAIMED
CLAIMED
ACTIVEgoal state
EXPIRED

↻ renewed each cycle

CLAIMED → ACTIVE — the unlock: the equipment owner accepts the data terms, not the dealer.

TRANSFERRED new owner re-accepts terms DEALER-MANAGED dealer sets up, owner still signs 12 LANGUAGES per-region terms & states
The matrix is why "just build the screen" didn't work; the lifecycle is how we tamed it. The contextual prompts, dealer tooling, and trust messaging all hung off these states.

The Calls

Three faster paths were on the table—and each was a trap:

  • Hard-gate the account—lock features until the profile's complete. The fastest line to the number, but it spikes churn, floods dealers with angry calls, and on a brand this old, forcing the door is a one-way trust hit.
  • Dark-pattern nudges—pre-checked consent, buried opt-outs, manufactured urgency. Converts short-term and poisons the exact relationship you're building: the moment a customer feels tricked about their own machine data, connected services is dead on arrival.
  • One universal flow—clean in Figma, impossible in reality given the sales-model variance, dealer-owned relationships, and 12 languages.

The bet. Progressive value exchange traded a fast, forced curve for a slower, durable one—and it cost real work: contextual prompts at every value moment, dealer tooling, and per-region trust messaging instead of one blocking form. The wager was that adoption that survives the relationship beats a number that burns it.

What we bet on instead was progressive value exchange, built on four rules:

  • Value Before Friction: Users should experience tangible benefits before being asked to share more data
  • Transparency Builds Trust: Make it clear what data is requested, why, and how it's used—no dark patterns
  • Multiple Paths, One Outcome: Support adoption through digital flows, dealer-assisted onboarding, and in-field support
  • Graceful Degradation: Users who didn't complete profiles immediately still retained access—urgency was created through value, not lockout

What We Got Wrong First

The hardest part wasn't the flow. It was the dealer.

Dealer-Up Didn't Hold

Our first instinct was dealer-up: arm the dealers, let adoption grassroots from the people who own the customer relationship. It didn't hold. Dealers sell too many ways—per acre, per usage, outright, concierge—to build coherent happy paths from the bottom up. We pivoted to top-down and user-centric: design the canonical flow around the end user and the value they get, then make the dealer a multiplier on top of it, not the foundation under it.

The B2B2C Twist

Deere reaches most customers through the dealer, and for the biggest accounts dealers run white-glove concierge—they do everything for the customer, including the digital setup. But the account that unlocks connected services carries Terms of Use and a data-sharing agreement that, legally, the equipment owner has to accept—not the dealer on their behalf. The thing standing between us and the data wasn't a form; it was agency. So we flipped the incentive: reward dealers for bringing customers into the digital relationship—their own account, their own data, their own sovereignty—instead of proxying it. That shift, more than any single flow, is what turned completion from a wall into a climb.

Execution

Progressive Profile Completion

Instead of a single blocking form, we designed contextual prompts tied to moments of value: predictive maintenance, equipment insights, automation features. Each step answered one question: "What do I get if I do this right now?"

Dealer-Enabled Adoption

Dealers became UX multipliers, not just support. Clear dealer workflows for assisting customers, shared visibility into completion state, and consistent language across touchpoints reduced friction while preserving trust in local relationships.

Trust-First Messaging

We replaced abstract legal language with plain-language explanations, explicit benefit statements, and clear reassurance around data use and control. This dramatically reduced resistance during onboarding.

Results

34%→87%

Profile Completion

$3.8B

Business line this flow gates

-16%

Setup Support Tickets

500K+

Users · 12 Languages

Turned a forced-adoption mandate into voluntary completion.

  • Profile completion increased from 34% to 87%
  • Reduced support tickets related to account setup by 16%
  • Established a reusable adoption framework used across multiple Deere platforms

The account/consent flow is the gate every connected-services dollar passes through — I owned that gate.

What This Unlocked

This work didn't just solve onboarding. It created:

  • A scalable foundation for AI-driven services
  • A repeatable model for introducing "forced" change without backlash
  • A trust-based approach now reused across Deere's digital ecosystem

By the time I left, that adoption framework was the default other Deere platform teams reached for when they needed to move a number without breaking trust.

Gallery

John Deere Operations Center UI across desktop monitors and an in-cab tablet

LET'S TALK

Interested in discussing enterprise design challenges or exploring opportunities?