Member-only story
Benchmarking: how to provide valuable comparisons around UX research
Take snapshots of problematic outcomes to help show the impact of UX

"[Data] gains it's meaning from the comparison." That quote helped me understand what was missing from my re-design recommendations.
When re-designing a product or application, you might have a completely different understanding of what that means compared to other team members. You might imagine it as a complete overhaul, while others think it means "keep mostly everything but touch up a few places."
Change is difficult, especially when it involves significant effort. This is especially true if some team members were on the project's previous iteration: they may prefer something other than scrapping everything they've done.
But this is where that quote led to a breakthrough. You see, I was making the wrong argument. In these cases, you don't need to convince your team that your design solution is "Great."
You must convince them it will be "Better than before." To do that, we can use the power of benchmarking to make our point.