Let's talk about UX Design

First thing first, if you have no idea of what UX Design is, let me kindly suggest you to watch this video, made by the talented folks at Fiverr :

Are we good now?

Ok!

I've spent a lot of time around customers, in various markets and fields.

I created ad campaigns for them. I created print and digital tools for them. I listened to them, trying to provide the best services I could.

And I learned. A lot!

Now, more often than not, you will hear CEOs and Managers say something that goes like:'I know my customers. I know what they want.' Here is the thing: you probably have a good idea of who they are and what they think they need (If not, you REALLY need to schedule a meeting with your marketing team...).

But do you know how to tailor an app to that audience, only based on that knowledge, right out of the blue? An app so compeling it will drive your users to check it over and over again with excitement?

My bet is that you likely do not know how to achieve such a magic trick... and neither do I. (if you do, then what are you here for anyway?)

That's what interviews, mock-ups, usability tests and UX Design tools are made for.

Investigate, Ideate, Prototype, Test, Repeat

How do I detect users habits?

That is one thing to assume you know who your audience is. It is an other to actually spend time with real people to learn what they're used to, and where their comfort zone is.

I usually spend as much time as I can chatting with and observing end-users, in their own environment. Through this process, I usually detect what drives them, as well as their fears and 'no-goes'. This lays a pretty good foundation to extrapolate on what the app I'm working on might need or surely does not. This is also a good time to find out who are the targets the initial brief didn't even recognize. It is indeed very important to no close my mind on all the surrounding aspects that might show up in this phase.

To help visualize and schematize every informations gathered, I'm using tools like storyboards, experience maps, and personas.

How do WE create the best solutions?

Once all these informations well represented, the whole team invested in the project (ideally) shoud meet. It is then time to ideate and brainstorm on the best solutions to solve theses users problematics, together.

There are many ways to do so, but never lose sight on the objective. To do so, I'm always asking the team this simple question:'does this solution answer their problematics in the most efficient and pleasing way?'

How do I create a solid UI?

Chances are we have gathered enough datas to start prototyping UI mock-ups. That is when Adobe Experience Design comes into play. Notice that I could as well use Balsamiq, or inVision for the matter.

I am using most of the best practice applied in the ergonomy and visual design fields, and constantly read, listen and watch pieces on these subjects.

Note that, if I've got enough time, I may also consider creating a functional prototype using React or Vue.

How do I validate these prototypes?

Once the prototypes are ready to use comes the testing phase.

Usually, I return to the users previously interviewed and see if the product is getting close to what they would be satisfied to use/work with everyday. If it does, then everything is fine! But usually, it takes some adjustments to really come close to a good version of the product. One that they would feel they always 'have been dreaming about.'

If you do not have a pool of beta-testers ready to give a hand, fear not. It may be unconventionnal, but guerilla-testing have also been a pretty effective way to test my previous works. I usually hang around cafés and bars and ask people close to the target-users profile if they are willing to help me on the project I'm working on. Of course, free coffees/beers help a lot!

What if your project is already online?

There are tons of tools to help an app or a website past the production state.

One might start with the infos that Google Analytics is providing to detect where said app/website is lacking in good UX.

I have already worked with tools like Hotjar, and deployed A/B testing (you're currently being A/B tested by the way). These are excellent tools to test how your users are using what you presented to them. However, it does not replace face-to-face interviews and observations phase.

Convinced? Want to know more? Contact me!