UX Part

First, we have to start by understanding the context of ADHD, what it is, what symptoms people with ADHD have, and so on. More importantly, we must understand their goals, pain points and frustrations to offer them the best solution.

Stakeholder Interview

First, we had to meet our clients, get to know them and the foundation, and learn everything we could about the user. The interview was divided into various sections:

1. Introduction, review of the agenda and icebreaker. To get to know and familiarize ourselves with each other.

2. Interview. We asked questions about the foundation and their patients with ADHD.

3. Desired outcomes. We did a small exercise to find out which was the outcome they were expecting from this project.

4. Our working process. We explained all the steps, methodologies and tools we were going to use, and where we wanted feedback from them.

5. Map the existing solution. We talked about the app they had at that moment and how it could be improved.

6. Redefine the problem statement. Lastly, we reviewed the challenge and redefined it, taking into account everything we learned in the session, so it was more realistic.

Secondary Research

After reading some articles and search statistics about ADHD, we learnt some interesting things about the topic:

What is ADHD?

ADHD (attention deficit hyperactivity disorder) is a neurological disorder that impacts the parts of the brain that help us plan, focus on, and execute tasks.

Most common ADHD symptoms:

• Inattention

• Lack of focus

• Poor time management

• Weak impulse control

• Exaggerated emotions

• Hyperfocus

• Hyperactivity

• Executive dysfunction

https://www.additudemag.com/what-is-adhd-symptoms-causes-treatments/

General statistics about ADHD:

• More than 4% of the world’s population has ADHD.

• Males are almost 3 times more likely to be diagnosed with ADHD than females.

• The average age of ADHD diagnosis is 7 years old.

• The causes of this disorder appear to be mainly genetic, although environmental stress and interdisciplinary treatments can modify the appearance and severity of symptoms.

Competitive Analysis

Once we understood the context, before jumping to know the goals, the pain points and the frustrations of the users, we needed to know what was out there on the market to help people with ADHD. In this case, speaking of competition doesn’t make sense as the foundation only wants to help people with ADHD and there are barely any apps for them in Spain. Therefore, we only run a Feature Comparison Analysis to know what features other apps offer, not only those for ADHD but any app which could help them manage time and tasks. These are the apps we analysed: Inflow ADHD, ADHD Lifehacks, Brili Routines — Habit Tracker, Brili Routines — Visual Timer, One Sec, Routine flow — ADHD Organizer, My ADHD, TDAH: Ruido Blanco + marrón, ClickUp, Structured, Daily Planner and Google Calendar.

User Interviews

At this moment, it was time to interview some of the users to learn even more about their goals, their pain points and their frustrations. Not only we interviewed people with ADHD, but also parents of children with ADHD as both user groups will use the app. These are some of the things they told us:

Affinity Diagram & Empathy Map

With all the insights collected from the interviews, we built the Affinity Diagram to group the insights according to the topic and have a first glance at the issue.

Then, gathering together all those insights into an Empathy Map, we were able to be in the shoes of the users to understand better the user's goals, frustrations, pain points and thoughts.

Use Persona

After analysing the insights and empathising with the users, we were ready to create a user persona that could impersonate our main user group. This time as there are two main user groups, people with ADHD and parents of children with ADHD, we decided to create two User Personas, as each of them has different goals, pain points and frustrations.

The first User Persona, the Primary Persona, is Alex the disorganised brainy. Alex is a 23-year-old software engineer student, who lives in A Coruña with her partner. She was diagnosed with ADHD at the beginning of college, and since then she started to go to Ingada, a foundation that helps people of all ages with ADHD.

The other User Persona, the Secondary Persona, is Miriam the caring mum. Miriam is a 42 years old teacher, who lives in A Coruña with her husband and 9 years old child. She also has a 23-year-old daughter who lives with her partner. Both of her children were diagnosed with ADHD.

User Journey Map

With the user personas defined, we created a user journey map to see how each of them could feel in a real situation. For both cases, we defined a one-week-long journey where different day-to-day situations occurred.

From Alex’s User Journey Map, these are some of the opportunities we identified:

• HMW help people to manage their time and to do/check list of the day?

• HMW help people with ADHD focus more on their task?

• HMW reduce the time it takes for a person with ADHD to start a task?

• HMW help a person with ADHD remember important tasks and events?

• HMW register achievements a person with ADHD has, so that they can be used as reminders for bad days?

From Miriam’s User Journey Map, these are some of the opportunities we identified:

• HMW help parents of kids with ADHD to get them to complete their daily tasks without getting distracted?

• HMW help parents to find information or guidance about with they are doing?

• HMW help kids with ADHD to see their progress and realize their advances?

• HMW help children with ADHD build strong self-esteem?

• HMW parents of children with ADHD involve their children more in doing family chores and activities together?

Problem Statement

After gathering all this data and empathising with the users, we were ready to define the Problem Statement for each user group.

Problem Statement for people With ADHD:

People with ADHD need to find a way to cope with ADHD on a day-to-day basis and feel listened to and understood because they struggle with focus, forget important events, have difficulty regulating emotions, and feel uncomprehended.

Ideation

With the problem statement defined, we could start working on the solution. We started by using the crazy 8’s Method to sketch out some ideas that could be included in the app.

MOSCOW Method & MVP

From the crazy 8’s we came up with different features the app could have, so we applied the MOSCOW method to classify them between must-have, should have and could have.

Once we decided the features the app was going to have, we were able to define our Minimum Viable Product:

The MVP for GoTDAH includes a general data section, scales or questionnaires, downloadable and anonymous reports, monitoring of patient’s evolution, awareness of symptoms and improvement potential, access to psychoeducational resources on ADHD, motivational elements for regular assessments, reminders for therapeutic adherence, visual elements for progress monitoring, resources for family members, features to ease clinical appointments, recommendations for improvement, data analysis capabilities for population reports, agenda for organizing appointments and tasks, and personalized reminders for day-to-day activities.

Sitemap & User Flow

With the MPV in mind, we could start building the app, but first, to stay organized, focused, and give structure to the app, we defined the sitemap and the happy path by defining the User Flow. In this case, we defined a user flow for each user group, as they can take different actions.

At this point, as we only had 4 weeks to design the app, we decided to focus on the main user group, people with ADHD, leaving the development of parent profiles for the future.

Low-Fidelity Prototype

At this point, we started creating low-fidelity wireframes in which we defined the basic structure of the app.

Mid-Fidelity Prototype & Testing

After we created the Low-Fidelity Prototype and had a clear idea of the basic structure of the app, we started creating the mid-fidelity prototype. But first, before implementing any changes, we started creating components and component sets to save time and work.

Testing the wireframes, we collected insights to implement in the high-fidelity prototype.

While we were working on the project, we delivered the User Personas, User Journey Maps, Problem Statements, MOSCOW Method & MVP and the User Flows to the client for validation. Then everything was ready and we could start working on the UI part.