Users hate change, doesn’t matter how bad was the original design, they got used to it, and now they need to learn something new. Monitoring analytics post-release and keep in mind users will need to go through some initial adjustments. Give them some time to recover attitudes and fall in love with a new design. Support easy feature adoption with some contextual help and guidance.

Users hate change

As a designer, your role is to bring everyone on the same page and unite over one common goal. <ul><li>First, interview stakeholders to understand what and why we are trying to achieve for the business and on what timeframe. Check their expectations regarding look and feel, functionality, and target audience. </li><li>Interviewing dev and support teams it’s also a good idea to get more insight into what are problem areas.</li><li>But your primary target is users. </li></ul>

Start with building shared understanding

There are many activities you can do to understand users better, build empathy. <ul><li>User journeys and value propositions are beneficial, but there is not always time to do them when we are talking about something small. </li><li>Personas, on the other hand, are fluffy and fake and have very little practical application. </li></ul>An essential thing that you can do is to list Jobs to be done. This will help you understand the user’s motivations and expectations.

Define Jobs to Be Done

Having a list of problems and ideas on how to solve them is a good thing, but it needs prioritization. We need to understand what are the low-hanging fruits. For each opportunity, we need to understand what it will take to deliver it and how much value we will add for the end-user.

Understand the value versus the effort

Fresh ideas and innovation are never coming from competitor analysis. As everyone keeps a close eye on each other, you can only learn what is considered to be a standard. For inspiration, look beyond your domain. There are hundreds of amazing products that deal with similar problems that you are trying to solve in a different context.

Explore beyond your domain

Once you found out the issues, the next step is to find solutions for each identified problem. Competitive research and exploration should give you enough inspiration.

And find improvement opportunities

There are no perfect designs, and there is always space for improvement. But excellent user experience comes at a great cost. Creating a marginal improvement in already great design will require exponentially more resources invested than taking something bad and turning it into an average design. Sometimes to substantially improve the experience, you need to reinvent it completely.

Great design is hard to get

Hand sketches are great ways to start offloading some of the ideas from your head into the physical world.

Sketch on paper first

Like in a fancy restaurant, presentation is as important as the dish itself. If you spend months crafting a design, spend some time on presentation. And remember you are not selling new styles, clean fonts. Create a new story, a story about newly empowered users, because humans are fascinated by stories and visions.

Sell your design

Your goal is to listen and capture everyone’s thoughts and propositions, but don’t take it as absolute truth. In the end, you are the expert who needs to filter through the noise and find where to focus.

Don’t take anything for granted

It is as simple as that. Everyone can confidently say that they know better than the users, and “users don’t know they need it till they get it.” That statement is true only in a very rare case. Don’t forget that everything you are doing is for users.

If you are not testing with users, you’re wasting time

The number one mistake that designers do during the redesign process is that they completely ignore and disregard the current design. The worst thing you can do is to take the current design and create a new one based on your personal preferences. There was probably a ton of thinking and research that went into the creation of the original solution. Your goal is to carefully inspect the current design, try to understand how it works, and the intention behind each decision.

Deconstruct existing design

Each hour spent on low fidelity will save 10 hrs from being spent on high fidelity work later. Try to sketch a very rough idea of flow, have a quick validation, and add a layer of fidelity. Starting feedback sessions with presentation of high fidelity work may show your stakeholders that there is no space for changes, and their opinion was not taken in the account.

Get feedback fast, with low-fi storyboarding

Once you have understood everything clearly with the help of data from analytics, you can start identifying key problem areas with the existing design. Those problems can range from usability issues to visual flows, bugs, inconsistencies, wrong patterns applied, or exotic solutions without any reason.

Identify key problem areas

Once you narrowed down your focus to some key areas, you need to know the performance of the design. <ul><li>Pageview and traffic analysis. Tracks your visitors’ entry and exit from different pages, what browser and screen size they are using, and where they are coming from.</li><li>Behavioral flowchart. It helps you to understand how users behave and common journeys.</li><li>Timing and conversion. Funnel creation and analysis. Analyzes conversion and creates baseline metrics to compare the new design.</li></ul>

Review analytics

It’s one of the first natural questions that should come to mind. “Well, what are others doing?” As your customers will have to choose between your product and its alternatives, you need to analyze the experience they provide to customers. When reviewing both direct and indirect competition, look for commonalities, similar flows. Define what is considered a standard experience for your case. You can collect all of your findings in the InVision board or any similar tool.

Review competition

The design process never stops. New patterns emerge, more tools become accessible by users. Smooth user experience comes when you truly understand the problem you are solving and help users solve it effortlessly.

There is always space for improvement

The process described in this article will work for various scopes of redesign — from a feature or view level to full application redesigns. These recommendations will help you avoid pitfalls and…

Define Jobs to Be Done

Similar ideas to Define Jobs to Be Done

What Is Jobs To Be Done Theory

Making sure your service works well

Four dimensions of service consistency