The Law Of Diminishing Intent

When Users Stop Caring Before They Finish

I spent most of 2023 watching a checkout redesign tank conversion rates by twelve percent, and the problem wasn't anything we tested. It was the space between what the user wanted and what they had to do to get it. I call it The Law Of Diminishing Intent, though I didn't coin the term originally. People in product and growth circles use it informally the way they use "friction" or "cognitive load." It describes a single observable thing: the further a user's stated goal drifts from the action required to achieve it, the more likely they are to walk away. It is not a formal law the way Ohm's law is a law. There is no equation everyone agrees on. What there is, is a pattern that shows up repeatedly in onboarding flows, feature adoption, subscription renewals, and the million small decisions people make before they actually press a button.

The Law Of Diminishing Intent In Practice

Intent is not a constant. It behaves more like a battery that leaks over time and distance. Every extra step, every ambiguous label, every time the interface asks for something the user did not expect, the battery drains a little more. When it hits empty, the user leaves. They do not always do it angrily. Sometimes they just close the tab and think about dinner. The most useful application of this principle is not adding more steps to preserve revenue, it is subtracting until the intent stops leaking. Here is the method I use when a funnel looks fine on paper and terrible in practice. Start by writing down what the user says they want. Put it on a sticky note. Then write down everything they must do to get it, in exact order, with no skipping. If the second note is longer than four items, you already know where the leak is. Length alone is not the enemy, but length correlates with opportunity for doubt, and doubt kills intent faster than any broken button.

Intent has a half life. In my work, I track the median time between a user arriving at a decision point and taking the next step. When that median crosses two minutes for a low value action, conversion drops sharply. When it crosses five minutes for anything involving payment, you are watching intent evaporate in real time. Hotjar session recordings and simple funnel analytics will tell you this without any fancy tooling. People love to A/B test button colors while keeping a form that asks for ten fields. That is backwards. Reduce the number of required inputs first. Then reduce the cognitive category of each remaining input. Then, and only then, test micro copy or color. This order matters because intent loss happens at the structural level, not the cosmetic level. Last year I worked on an internal tool for a payments company. The goal was simple: let support agents verify a customer transaction in under thirty seconds. We built a flow with three panels, dropdowns, and a search field. Everyone agreed it was clear. Real users disagreed. Completion rate hovered around forty one percent, and the drop off was concentrated at step two, where the agent had to switch from a search view to a detail view.

The workaround was not to make step two faster. It was to eliminate it entirely. We changed the architecture so the search results rendered inline with the detail they needed. Agents could verify transactions from a single screen. Completion jumped to sixty eight percent within two weeks. The intent gap had been the view switch, not the number of clicks. You can miss that if you only count clicks.

Counter Intuitive Things Beginners Miss

Adding constraints can sometimes increase intent instead of decreasing it. When a product signals exclusivity, or when it forces a decision rather than leaving the user hovering, the perceived value rises and the willingness to complete the action rises with it. Limited invite queues, tiered access, and mandatory setup wizards all exploit this. The trick is that it only works when the constraint feels earned, not arbitrary. Users can tell the difference, and they punish arbitrariness by leaving. Another thing people get wrong is confusing friction with commitment. Friction is resistance that does not serve the goal. Commitment is a deliberate pause that reinforces the goal. Asking a user to confirm their intent before a high value action is commitment, not friction. Asking a user to re enter information they already provided is friction. The distinction is not always obvious in analytics, so you need qualitative context, not just drop off numbers.

Where The Law Breaks Down

The Law Of Diminishing Intent does not explain everything. There are contexts where more steps correlate with higher completion, usually in high stakes situations where users want reassurance. Mortgage applications, medical forms, and enterprise procurement workflows all intentionally add steps. In those domains, the user's primary intent is risk reduction, not speed. If you apply a lean product mentality there, you will create anxiety, not conversion. Another failure mode is when the product itself is unfamiliar. New categories force users to spend cognitive budget learning the domain before they can even evaluate whether the flow is efficient. In those cases, reducing steps too aggressively can feel confusing rather than fast. The workaround is to front load explanation, not to pad the flow with unnecessary actions. A short explainer video or an interactive tour that takes under forty five seconds usually restores intent without reintroducing structural leakage.

A Quick Implementation Checklist

I run this list on any flow that touches user money, identity, or irreversible actions. Write the user goal in one sentence and keep it visible during design reviews. List every required action and mark each as structural, explanatory, or defensive.

Remove structural items that duplicate existing data. Replace defensive items with progressive disclosure whenever possible. Measure median decision to action time and flag anything above two minutes.

Test the simplified flow against the old one before rolling it out, because regression testing is where most teams forget to look.

The Hard Truth About Intent

You cannot manufacture intent that the product does not justify. No amount of micro copy editing or button animation will compensate for a flow that asks the user to do something they did not agree to do. The Law Of Diminishing Intent is useful because it reminds you to measure the distance between promise and requirement, not just the distance between screen one and screen two. When that distance is small, users finish things. When it is large, they leave, and they rarely come back to tell you why.