Thereâs an old joke about a lost tourist in the West of Ireland who asks a local for directions and is told: âI wouldnât start from hereâ. Product managers gearing up for fresh investment and a flurry of new product releases canât escape the same feeling: theyâre starting from the wrong place. Whatâs brought them here? Experience debt. So what is it, and why does it happen? Itâs the accruing of ad hoc changes made over time that lead to deep inefficiencies. Itâs the gas slowly seeping around the house, with the dwellers unaware until itâs too late. There are lots of reasons why it happens: some teams have gone through explosive growth; others might have acquired new companies, or launched a raft of new products in a short timescale. Some telltale signs are: bloated websites product features bolted on or added at random different technical architectures propositions muddied or original customer groups no longer served with clarity. Letâs dig into a couple of scenarios in a little more detail: imagine a SaaS vendor thatâs acquired some other companies over time. Thereâs now the same logo across all the products, and maybe the surface-level look and feel is similar. But dig deeper, and thereâs an inconsistent experience across the different products. They operate differently, the shortcuts donât match up between one product and the other, and the products arenât well matched to actual customer use cases. The user journey has become disjointed. In another scenario, weâve seen where a company launches a good version 1 of a product that was seen as a disruptor, serving a clear market. Customers like it and use it, and the product is cost effective. But over time, through a haphazard user feedback process, the product starts to bloat, with an uncomfortable mix of features. When this happens, some features start to become underused. From the customerâs perspective, onboarding becomes a tough process, which can lead to needing to give users training because the customer starts to sense that this product has a higher degree of complexity. Once thereâs an instinct that the product becomes harder to use, by definition it tends to get more expensive. So is it any wonder that customers get itchy feet and start looking around for lower cost or simpler alternatives? Now weâre getting to why experience debt is such a problem, and why we should be talking about it now. Weâre in a supercharged, rapidly changing landscape. From conversations weâve been having with customers over the past quarter, thereâs a feeling the investment rhythm is ramping up. Everyone wants to scale, adopt AI, or otherwise tune up their product and make it able to withstand the competition. Getting a product suite working effectively so that users want to avail of additional features or buy extra modules in your platform creates the potential to cross-sell and upsell, which makes future growth easier. After all, when we think about where value is derived, itâs always been easier to sell to an existing customer than to acquire a new one. But how much of that precious product development time and money will be wasted because customers arenât availing of the opportunities youâre presenting them with â or worse, theyâre leaving your platform for a competitor? If youâre already seeing customer churn in your business today, it might be a symptom of experience debt. Other warning signs are lower renewal rates, stalling revenue, or reduced upselling and cross-selling opportunities. Before unleashing the investment to create compelling experiences, companies need to refine their product strategy for this competitive moment in the market. Many businesses have ignored it until now because there are often bigger fish to fry in the here and now, like the next product launch or feature rollout. Yet in the changed environment weâre heading into, they need some realignment and revisioning of the platform to focus their features and product suite around user needs while also levelling up their internal processes. To do this effectively, they need to tackle experience debt. Yet itâs harder for internal teams to effect that deeper change outside of a âbusiness as usualâ context. It needs a revision of design systems, processes and capabilities so that continued improvement becomes possible, while avoiding the bloat that characterised the situation until now. The key is to take a step back from the âbusiness as usualâ mindset and start to plot a way forward that applies a consistent look and feel â as the user perceives it â and an internal workflow methodology that can deliver products and features reliably and consistently in a way that delivers value â as the user perceives it. Applying UX principles will refactor products around the userâs priorities and perceptions of the product. But as you might guess, the solution Iâve described above isnât just about applying a magic UX bandage. Itâs about having a unifying future vision along with the tools and components that can deliver it. In other words, itâs about design leadership. And if your organisation is struggling to hire an experienced design leader who can deliver on this brief, thereâs a solution for that too. Iâll talk about that in our next blog.
by Brian Herron