Home > User Experience > How to bucket product design battles? | by Dhananjay Garg | Nov, 2020

How to bucket product design battles? | by Dhananjay Garg | Nov, 2020

How to bucket product design battles? | by Dhananjay Garg | Nov, 2020


In the above example, it is clear that an outlined button (medium emphasis) next to a contained button (high emphasis) is a good UI practice when using multiple buttons. For these smaller issues, file a small JIRA bug and directly notify the developers to get it fixed for the next production release.

If things are a bit tight and you get caught in these no brainer discussions often, then start leveraging frameworks like Jakob Nielsen’s 10 general principles for interaction design.

When dealing with UX tickets, product team members can often put you on the spot to derive a solution out of thin air. Please don’t take the bait and try to prove your design expertise by giving them a solution. Sometimes the final solution can be more complex than what it looks like on the surface. You may have to scratch the surface more to learn about the skeleton hidden within 💀.

During these instances, take note of the topic and let the team know that it will take a few more research/inspection days. This way, you get some buffer time to talk to developers and stakeholders in/outside the team. Once you are sure what to do, create a short UX-discovery document using a tool like Atlassian Confluence 🗒 to document all that you uncovered to get to the solution and the exact solution.

Following this small trick will help you come off as a professional who doesn’t make decisions in haste, and you will continue to nail down targets for your organization.

Bonus Point: You will also end up with a huge list of design case studies to show your peers.

And finally, the third UX bucket is all the big bets. You have been assigned this project because of the skills and expertise you have displayed in the past, and you are ready to show how design can drive clarity for big-budget projects.

These projects are worth battling for, and you can make it clear to your stakeholders by conducting a before-after impact study. If your design suggestions can save 10 days or 240 hrs of manual work month-on-month or similar high gains for the company, then it is a project worth fighting for.

To make a big UX bets project a success, start with strong 💪 documentation. Put together things like competitor study, current scenarios, what can be done next, technical feasibility (interviews with engineering teams), wireframes, and an interactive prototype in the end.

No matter where you are in your UX career journey, it is always important to access the project at hand and approach it from a research angle that covers both businesses and user pain points/gains.

Being a designer can mean that you have to be the one making tough design/product decisions. Classifying your UX battles in the right manner can be the key to displaying your design and technical expertise to your direct peers and C-Suite stakeholders.

Now conquer those design battles ⚔️.



Source link