John Nielsen found that there's an average of 83% increase in key performance indicators from UX. UX improves KPIs. If it's not improving KPIs, then it's not good UX, right? And there are a lot of usability people who don't have an ROI background, who don't have business acumen, who don't get this.
They're busy trying to make the user feel good. That's important. But you also need to connect to key performance indication. Like, you know, write to improving your business metrics. In terms of e-commerce, you can expect to spend 10% and that 83% conversion conversion rates are normally 2%, and that's normal to have a 2% conversion rate. So we're seeing up to 15, 18, 22% and then the jumps up to 80% and 90%,
which which are just, you know, gangbusters returns intention to return. So if a user says I want to come back 60% from Forrester and stat market studies have found that and interesting to compare that to the you know how much would you be willing to spend while intention to return is incremental revenue on the back side right when they're coming back. So typically spending between 10 to 12% of dev budgets in order to get these ROI
returns. So the deal with how much you spend and how much you get back, it's the 110 100 role spend a dollar on research to make the six upfront. That's that early on user research $10 to change it during design or spend $100 to change something in development. So once you start baking and coding, you know, all the interrelationships of JavaScript kind of this and that it's actually easier to
learn about users prototype without much effort and figure out what the requirements are and validate it. Get the outside in validation before you start coding. It just makes sense. It makes financial sense. And that's why UX has become a staple in software development teams.