The Expectation Effect (Part 3/3)
The 9x Barrier
In Part 1, we recognized that "Expectation" is the invisible parameter defining the user's experience. In Part 2, we navigated the Sea of Miss-Expectations, aligning the maps of stakeholders, users, and ourselves. We accepted the role of the Navigator, responsible for steering through the fog of data and intuition.
And now, with a perfect map and a seasoned crew, the ship eventually meets the shore. This is the moment of truth: when the product hits the reality of the user’s everyday life.
And this is where we encounter the tallest wall in design - a wall built not of code or requirements, but of biology.
The Mathematical Wall: The 9x Barrier
We often talk about "resistance to change" as if it’s a minor friction - a bit of rust on the gears. It isn't. It is a fundamental asymmetry in how the human brain weighs value.
According to Harvard's John Gourville, for a new product to be adopted, it shouldn't just be better than the status quo. It has to be nine times better.
This isn't an arbitrary number. It’s the result of two opposing cognitive biases colliding:
- The Builder's Curse (3x Overvaluation): As creators, we are biased. We see the potential, the edge cases we solved, and the elegance of our solution. We overvalue our innovation by roughly a factor of three. We forget the learning curve because we built the curve.
- The User's Comfort (3x Overvaluation): The user is running on System 1 efficiency. Their old way - no matter how clunky - is "metabolically free". They overvalue their existing habit by a factor of three because it requires zero energy to execute.
3 (Your bias) x 3 (Their habit) = 9.
When you ask a user to switch, you aren't offering a gain. You are demanding a Loss. And as we established in Part 1, the Prediction Engine hates errors, and the amygdala hates loss. The pain of losing $100 is twice as sharp as the joy of gaining it. The pain of losing a familiar workflow is no different.
The Intuitivity Trap
I bet you have heard something like: "It needs to be innovative and intuitive". The issue with this phrase is that it assumes that "intuitive" is a universal constant. It isn't. Intuitiveness is a relative concept, anchored in the user's prior experience and tied to low energy spending - which makes sense for "don't make me think".
When you introduce an innovation, you are essentially asking the user to "unlearn" their existing mental model and "relearn" a new one. This is not just a cognitive load; it's a metabolic cost. The user has to invest energy to break the old habit and form the new one.
While working on a complete new dishwasher interface, I had to keep reminding the team that the goal wasn't to make it intuitive, but inviting for change and quick to learn. Otherwise, we could just do a facelift and call it a day. No innovation and still trapped in the "buttons wars" of the 90s where more buttons equals more values even if you have no idea what half of them do.
One way to verify how fast the user can learn is to setup your test with similar tasks in the beginning and at the end. Pair it with an eye tracking and you can see how the user's gaze shifts from the high cognitive load to a fluid flow. You can analise the the path of the gaze and the time spent on each element to understand where the friction points are and how quickly they are adapting to the new mental model.
Breaking the Barrier
To break the 9x Barrier you need to consider how much the user is willing to be open to change. It is much easier to find a solution for a user who is actively looking for a new product because they are already trying to solve a painpoint. So doing your homework to find users who are in a state of "System 2" investment is crucial. They are already in the mindset of "I need to change something, but I don't know what." This is a much more fertile ground for innovation.
But the real secret is how frictionless you can make the transition. The more you can reduce the perceived loss and increase the perceived gain, the easier it is to break through the barrier. This is where the Expectation Effect comes into play. By engineering the user's expectations and managing the prediction engine, you can lower the metabolic cost of change and make the 9x barrier feel more like a 2x or even a 1x.
From all my years designing products, the most effective ways to break the barrier have been:
- Gradual Onboarding: Instead of asking users to switch all at once, introduce the new features gradually, allowing them to adapt step by step.
- Familiar Patterns: Use smaller and familiar patterns and metaphors to anchor the new experience in the user's existing mental models, reducing the learning curve.
- True Value Achievement: Make the benefits of switching besides explicit and tangible, achievable so users can see and feel the gain outweighing the loss.
- Align with their values: If the innovation aligns with the user's core values or identity, they are more likely to be motivated to switch despite the friction.
- No Dark Patterns: Avoid tricks or manipulative tactics to force users to switch. This can backfire and create resentment, losing them forever.
Conclusion: The Invisible Parameter
Over these three parts, we’ve looked at the Expectation Effect from the level of neural wiring, through the lens of the Designer's internal duality, and finally against the mathematical reality of adoption.
User Experience is not the pixels on the screen, nor the flow of the journey. It is the delta between what the user predicts will happen and what actually unfolds.
As designers, we are not just architects of interfaces. We are Expectation Engineers. We manage the neurochemical loops that define whether a product feels like a tool or a chore.
The next time you sit down to design, look beyond the "demographics" and the "user needs." Look for the ghosts in their memory. Look for the metabolic cost of your innovation. Instead of asking "Is this intuitive?", ask "What does the user expect to happen here, and how much energy am I asking them to spend to change that expectation?".
Because the most important parameter in your design isn't in your product - it's in the user's head.
Thank you for sticking with me through this series. I hope it helps you see your next journey through a different lens.