Hey Jason Imani, thanks for the nice words!!

It does require a lot of buy-in from PMs for this process, as does rest of the design 😃. It depends also on how open your team is to rational ideas (that are not their own).

In this particular case, we had established design components early-on following a mix of both Google material guidelines and Apple HDI. At the same time we had also established patterns for combining multiple actions into a single menu. We took wireframes and used the method of elimination to determine priorities — starting with identifying the core feature for a section without which the whole section would be meaningless (ranked 5 — almost always the content). From there on, we asked a lot of what next to rank other actions (filters, changing views of tables/charts in our case).

Next, when we started designing interface for different flows, we had space for only so many elements to fit without overwhelming the users. In an existing design, data from GA or any other analytical tool should play part in forming those opinions, like you mentioned.

Selling your ideas to the team varies from one place to another and depends a lot on the culture of your organization. If a team is not willing to accept data-backed opinions, it’s a tough nut to crack.

Hope this is helpful. Feel free to respond with any questions you may have, or you could send me an email. I think I have idea about what I can write next at length 👍🏾 .