Peter Loving’s Post

View profile for Peter Loving, graphic

Product design for fast growth SaaS 💸 Added $300K ARR in 90 days | Increased free trial upgrades by 46% 🔥 | Saved $200K on dev costs 🚀

SaaS founders demo their products to me every day. Quotes I hear almost EVERY time are... 'Huh that's weird, usually this loads immediately' 'We're working on getting this to be a bit faster' 'While we wait, I'll just explain what we're aiming to do' I get it... I know what it takes to build lightning fast tech with a great user experience. But how much are you prioritising product experience for users? It's critical to do the work. Because those frustrating moments are when you lose a customer to a competitor with a better product. There's a technical rule at play. It's called the Doherty threshold. Productivity soars when a computer and it's users interact at a fast responsive pace. It means neither has to wait on each other. The optimal speed is <400ms which is a rate at which a computer response feels instant. When things slow down it doesn't only affect productivity, it also becomes frustrating for the user. If this persists, their relationship with a product is associated with frustration and boredom. It stops users actually wanting to use the software. So, if you're planning that back end rebuild and a new tech stack, can you really put it off that much longer without losing more customers?

  • No alternative text description for this image
Mohamed-Younes Rouabehi

Web Developer | Expert in Angular, NestJS, VueJS, TypeScript, and NodeJS

3mo

I didn’t knew the name of this effect. I can only relate. I hate when a product is too slow. Good to know 👍

Like
Reply

To view or add a comment, sign in

Explore topics