Defining your UX needs

One of the most common pitfalls novice UX designers fall into is adding or creating features simply because they saw it work somewhere else. I’d like to share some advice that I share with any new designer that works with me or is just starting out. Stop making products that your users won’t use. Just because you can make something pretty doesn’t mean you designed the perfect experience.

Over my many years as a UX Designer I have developed a process that helps me deliver the best results to meet my teams UX goals. The process is called the ABLE process, it is something we use daily at Prattle in almost every operation to help make our product what our users want… That is the key right?

So how do you define your UX needs with a silly acronym? It’s rather simple actually and once you do it a few times you will never want to do it any other way.

Introduction

ABLE stands for Access, Build, Launch and Evaluate.

The key thing to understand here is this process is a continuous cycle that should be repeated over and over again. As you complete each cycle you will slowly start to see the results you are looking for. Now in most cases this process is dictated from evidence and feedback. So it is up to you to record accurately and make the right decisions with the data you collect.

Another thing to always remember is DATA will lead you to victory.

How it works

Here is how simple it is… Follow the ABLE acronym!

ACCESS | Do your research, know your market and competition, collect your data, ask for feedback, principles, mission, do a SWOT analysis and know your who, what, when, where and how.

BUILD | Assemble a team, make a roadrap, create the product, design a prototype, develop a MVP, create tools and routines.

LAUNCH | The beta, product, feature, study group or event.

EVALUATE | Your research, data, info, roadmap, behaviors, habits and choices.

Now I know some of you might say you already do a lot of the above but the important thing in this process is the cycle in which you do them. If you want to solve UX problems you have to be aware what your users need and what your problems are before you can come up with the right experience or solution. Defining your UX needs and goals can be rather simple when you follow this process.

Ask for as much feedback as possible and document everything. Being able to go back and review your data is highly important. The ability to look at metrics and indicators on demand will be a life saver. Use this process and I promise you will learn something new about your product and users. Who knows you might have missed something that can be a game changer for you. It might just help you design that next feature your users have really been waiting for and that all other new designers try to copy.