And now for the exciting part: how did it go?
I'm delighted to share that in one of our five chosen areas of the product, we saw a 78% improvement in speed! And in another of the five, we saw gains of 26% improvement in speed. I would usually think that the 26% was super impressive if not for that 78% improvement.
And then the part about the delightful experience, likewise, had some incredible results as well. In two areas where we improved the perception of speed, we saw bounce rates drop by 50%.
What’s more, we saw an unexpected result that teams were able to communicate better because we were using an OKR with language that spoke to everybody, no matter their discipline.
Our engineers might have previously said something like, "We need to do a refactor on this code base." Now we're hearing language more like, "Hey, we think that if we improve this, we should see some gains in performance, and that should help with conversion rates."
It's such a different frame of mind where we're always thinking about the end-user, their experience, and the impact on them and on our business.
It sounds so simple, right? It sounds like, "Oh, of course you should know that," but in practice, I really haven't seen this in many places. I really haven't seen product teams using language that puts the user as that shared common denominator and then rallies everybody to make their contributions toward that goal.”