My UX Process

Here you will find the method or ways in which I normally tackle a project. You will see an example of this process with an actual project I have done for fun to see my own improvement over the years.

Overview

Normally, this process consists of steps that allows me to deeply understand the challenge, the client's objectives and the business landscape to ensure the solutions are well-aligned with their goals. These steps consist of:

  • The brief,

  • Understanding the business,

  • Identifying our users,

  • Determine the red route,

  • In-depth data analysis,

  • Analysis of current IA and improvement

  • Wireframing solutions.

The brief

This is the initial challenge or requirements, typically provided in formats like Excel, PDF, or Word, followed or preceded by discussions with stakeholders.

In this case we’ll analyse GoodReads and, since this step hasn’t occured, we’ll just say that they are looking to re-design their current application.

Understanding the requirements

Now this is where our brains have to really do the work. At this moment, we need to clarify, concise, and get a hold of what the client needs, what they asked, and what’s their business model. This includes knowing which users are involved.

GoodReads is a website and app where you can discover new books, share what you’re reading, and see what others think about different books.

Identifying our users

After having a clear understanding of the business, we need to know who’s taking part of our journey through this system. Who are our users, their goals, what they need.

For GoodReads we’ll focus only on our ‘Avid Readers’ archetype. This is because from outsider’s perspective, they are the users we can get to know.

The red routes

The paths that are essential for our user to achieve their goals effectively. For the ‘Avid Reader’ I have identified 4 main tasks:

  1. Discovering new books

  2. Writing and Sharing Reviews

  3. Tracking Reading Progress

  4. Following Authors and Other Readers

The data analysis

To analyze the system, I start by examining the screens, identifying key entities and their properties. Then, I map out how actions and groups interact within these screens. By looking at the entities and screens found, I gain a clear view of the system's architecture, the data flow, management, and required actions.

Study the information architecture

How is information laid out across the system? What’s the relationship between screens and entities? How do I navigate from one place to another?

How can this be simplified?

Finally, wireframing our solution

Now is the time to start wireframing our solutions. This involves sketching out the layout, defining components, and detailing their functionalities. Wireframing helps visualize how the screens will look and interact, ensuring that all elements are logically placed and serve the intended purpose. It’s a crucial step in translating ideas into a practical design blueprint.