As I discussed in my last post, there are many methods of testing that can be used when going about redesigning a website. One of the main goals is to understand early on what can be kept and what needs to be changed. After you and your team have gathered research, it’s time to start analyzing what it means and where to begin making changes. An easy, cost-effective way to do that is using AS IS / TO BE analysis.
AS-IS and TO-BE analysis, according to James Pannafino and Patrick McNeil, is a visual comparison method where the current state of the product or service (AS-IS) is shown next to the future state (TO-BE).
Current state analysis can focus on the user interface as a whole or on one of the specific features within it. The key goals and motivations of implementing this method are user satisfaction, improving existing products or services, and saving money.
This method is usually used after user goals are identified and personas have been created in the user design process.
How to Use This Method
To begin, map out the current state of the product or service. This can be achieved with a map or a flow chart that clearly explains how your interface currently works. Keep notations within the flow chart that point out where possible adjustments can be made or aspects you intend to modify. For example, if you’re trying to pivot into a partnered streaming service, map out the steps the user would currently have to take to stream or rent a movie.
Once you have your current interface mapped out as – is, before you can build a future state design you need to analyze your current process and assess the following:
Bottlenecks: where there might be stalls in your product or service that provide unnecessary confusion or obstacles.
Gaps: areas that hinder the desired outcome or performance of your product or service.
Weaknesses: aspects that need to be added or completely overhauled.
Work with stakeholders and designers to brainstorm improvements to the current interface and why these improvements need to be made. When a number of changes can be agreed upon, create a new visual map that shows the future state of the product or service and showcases all the possible solutions.
The next step is to place both the current and future visual maps next to each other and discuss the effects and outcomes. It’s important to make note of the possible changes that need to be made and the steps needed to get there. Simple before and after analysis can be extremely useful to teams as they consider potential changes. These visuals not only clarify things for your team but also help illustrate unintended consequences of potential changes.
For example, in 2017 IMDb removed the message board function from their site and users have been requesting it back ever since. If designers were to consider bringing it back, they could compare how this affects the site’s current layout and what legal steps they would need to take to make the design successful.
Another added benefit of this method is that sometimes it can be difficult for designers to understand the significance of even what they perceive as a small change to an interface. By visualizing them side by side, these nuances can be more fully recognized. It is also important to bear in mind that this research method may only show you what can be improved, but not necessarily how.
Start Small: Account for all the easy fixes that can be accomplished before tackling the more involved changes. This can be as simple as removing a feature that isn’t contributing to the user experience or rearranging existing components.
Enforce the Existing Process: Sometimes starting from scratch seems like the best option but it’s rarely time- or money-efficient. Pull from existing users and focus on improving rather than rebuilding.
Benchmark Metrics: You and your team should be 100% certain that the changes you plan on making are going to make your product or service better than its current state; otherwise, you are just wasting time. Don’t be afraid to revisit the iterative step during this process. You can always draw up another To Be model.
Taking the time to map out your current system and comparing it to where you would like it to be in the future is a simple, cost-effective research method that can go a long way in solving UX problems and creating a more satisfying experience for your users.
Photo by ThisIsEngineering from Pexels
コメント