Product Experience
Designing how products reach users, and what happens once they do

Product Experience
Disciplines
A product is what users do with it. The path from first encounter to recurring use is formed by hundreds of small decisions about onboarding, navigation, feedback, and the moments where the product earns its place in someone's working life.

Most of those decisions get made unconsciously, by whoever happens to be implementing the feature. The product experience that results is the sum of those choices.
1          How it's used
‘‘Eighty percent of features in the average product are rarely or never used. Software companies spend tens of billions building them.’’


How a product gets used in practice usually diverges from what its product team imagined. Where users get stuck. Which features they discover and which they walk past. What they reach for in the first few minutes, and what they grow into months later. The path from a user's first encounter to recurring use, and the moments along that path where the product loses them.

The focus here is on what users actually do, observed in real conditions. Product roadmaps tend to reflect a mix of what the team believes is useful and what the loudest customers request. The data on actual usage often tells a different story. The work surfaces that story before any major design decision gets made.

Around three-quarters of users stop using a new software product within the first week of trying it. Day-one retention for the average product sits around 30 percent, dropping to 7 to 10 percent by day 30. The drop-off curve is steepest at the start and flattens later. These patterns are visible inside the product's data, though they often go unexamined end-to-end.
Our work in practice
‘‘Reducing time to first value by half lifts seven-day retention by 25 to 40 percent. The first session is where most of the leverage sits.’’


What emerges is a product experience built around adoption from the first encounter onward. An onboarding that moves users to first value within the first session. Navigation that surfaces the features people actually need at the moment they need them. Pacing that matches how users build up familiarity with the product over time. Feedback loops that catch the moment a user hesitates, and respond fast enough to matter.

This redesign forces choices about what the product is for. Most feature lists grow over time, accumulating capabilities that were once strategic and have since become noise. The work makes the trade between feature surface area and depth of value explicit. Products with high feature adoption rates also tend to have the lowest churn. The relationship is roughly proportional.

Each interaction either deepens the user's relationship with the product or weakens it, accumulating into expansion or churn over months. For B2B software companies past a certain size, more than 90 percent of new revenue comes from existing customers expanding their use. The product experience that earns that expansion is what most of the business actually runs on.
2          Designing for adoption

Most of our work runs on a five-stage model: growth analysis and planning at the start, then an extended programme across structures, processes, technology, and new ways of working. Product experience runs through every stage, with the densest work happening where strategy meets the actual product surface and where the experience needs to hold up under real-world use.

‘‘Roughly 70 percent of new software users stop using a product within the first three months. The patterns of who stays and who leaves emerge within the first session.’’


A product that worked at one scale usually stops working at the next without active maintenance. Users adapt their patterns while competitors reshape expectations. Sustaining the experience means keeping it under continuous evaluation between major redesigns.

The first months after a major product experience change are about teaching the organisation to read what's actually happening. What a falling activation rate is telling you and when a shift in usage pattern signals a problem to fix, or when it signals evolving user needs. About one in five products has the instrumentation and the operational habit to read these signals consistently. For the rest, product decisions happen without that visibility.
3          Staying useful

More figures on where product experience slows companies as they scale in our growth dashboard.