Member-only story
To persuade your team to look past quick wins, you need to understand the funnel
How RICE prioritization and Funnel Analysis can help you re-prioritize design problems
Stop me if you’ve experienced this before: you present your team with several design recommendations that you’ve found through user feedback.
Everyone’s entirely on board with minor quick Design fixes that’ll have some impact. But you hear crickets when you present an underlying user issue that will require significant effort to fix.
Whether it’s “out of scope,” “not part of MVP,” or any other reason, your team isn’t convinced to make more significant changes. Even if it eventually results in users stopping using your product, you can’t seem to persuade your team to take action.
If this has happened to you, it’s essential to understand how problems get prioritized.
Understand that not all UX problems are equal
“The decision about whether to fix a design flaw should certainly consider how much use it’ll get: it might not be worth the effort to improve a feature that has few users” — Jakob Nielsen, N/Ng
Many designers fail to realize one fundamental concept: not all UX problems are equal.
