For Teams

Your Product Is Full of Defaults

Every signup flow, settings page, and pricing screen ships with choices already made. Most teams never decide them on purpose, and almost none measure them. I help teams do both.

Audit Instrumentation Experiments Governance

The Blind Spot

The Choice Nobody Logs

Analytics records clicks. The default effect is people not clicking. So the most influential choices in your product leave no trace in your data. Try it: change something, or don't, then sign up.

Create your account

Billing

What most analytics records

    What defaults-aware tracking records

      The Work

      Four Steps, in Order

      You can't improve what you haven't found, and you can't test what you don't measure. Each step makes the next one possible.

      01

      Audit

      An inventory of every default in onboarding, settings, pricing, consent, and notifications. For each one: who chose it, why, and whether anyone measures it. Most teams find dozens they never decided on purpose.

      02

      Instrument

      Events that make defaults visible: what was presented, what was kept, what was changed, and how long it took. Designed for the analytics stack you already have, and implemented alongside your engineers.

      03

      Test

      Default variants tested against your real goals, with guardrail metrics (churn, refunds, complaints, support tickets) that catch a default that wins this quarter and costs you next year.

      04

      Govern

      A lightweight review for new defaults, so the next pre-checked box is a decision, not an accident. Each high-stakes default gets a written rationale, which is also what a regulator will ask to see.

      Why Now

      Defaults Are a Compliance Question

      Regulators have stopped treating defaults as a design detail. In several jurisdictions, the default itself is now the thing being judged.

      EU · GDPR Art. 25

      Privacy by default

      Personal data processing must be limited to what is necessary by default. A pre-checked "share my data" box is not a style choice; it is the wrong default.

      EU · DSA Art. 25

      No manipulative interfaces

      Online platforms may not design interfaces that deceive or manipulate users, including making it harder to cancel a service than to sign up for it.

      US · FTC

      Dark pattern enforcement

      The FTC has brought major cases over subscription traps and consent flows built to be skipped. "Users could have changed it" has not been a winning defense.

      The Approach

      Defaults That Hold Up

      The goal is defaults that serve your business and your users at the same time. Those are also the ones that last: they convert, they renew, and they stand up to scrutiny.

      A useful test: would the default still work if you explained it to the user in plain words? When the answer is yes, we measure it and make it better. When it's no, that's worth knowing early, because the fix is usually a better default rather than better tracking. Design for Good shows what that looks like in practice; Dark Patterns shows the defaults that win a quarter and lose a customer.

      Bolton Consulting

      Who You'd Be Working With

      I'm Jeff Bolton. For more than 20 years I've built products used at national scale, where a single default could change what thousands of people did.

      • Invented and scaled StandOut at CollegeNET, an AI video interview platform, from prototype to national scale
      • Inventor on 10 issued patents in asynchronous video interviewing and adaptive branding
      • Spoke on defaults to a user conference of roughly 500 people, long before regulators took an interest
      • Built this interactive site, which is now cited by other writers as a reference on the subject

      Engagements range from a one-time defaults audit to hands-on instrumentation work alongside your team. Most start with a conversation about one flow that's bothering you.

      Start a conversation →