SPRINT21 PORTFOLIO

DatFade

Reducing booking appointment hassle for a better user experience.

Product Experience

Problem Statement  

How can we make the booking process easier without having to go through the steps of downloading a mobile application on their phone to reduce cycle time?

Problem Background  

The goal of the DatFade booking website application is to reduce shopping cart abandonment and enhance user experience for clients to book appointments with their favourite barbers while avoiding disruptions during the booking process. 87% of users from the age of 18-24 have left a transaction due to a bad transaction process (leaving the application after too many steps required for the client).

However, the problem is the length of mandatory box registrations that is required and annoying ads and not having an option to override the installation step of an application  of the transaction funnel. But rather it would be better to have an “online” booking method. The web application will serve its purpose.

While conducting user research, 66.7% out of 6 people surveyed said that a text message would make them want to come back to the web booking application. An integration of notifying the customer could increase customer retention if a booking app is used. 33.3% of people surveyed mentioned they visit a booking application once a day. 

Research Insights

User Pain Points

We want to understand how people find information/news online about their favorite topics, what works for them, and what their current pain points are so that we can help improve the process and make it easier and faster for them to find the right information.

  • What is the problem?
  • Non-Tech savvy people do not know how to book barber appointments through a app
  • What would we like to know?
  • We want to know why they do not know how to book through a application
  • What are the assumptions?
  • They do not know how to use technology because of their age?
  • They do not use their phone to navigate applications, only phone calls?

Customer Segments

  • Individuals who want quick and easy access to curated information and news about all their favourite topics. From new immigrants who want to stay updated about their own country without any geographical constraints, to social activists or members of social movement groups who want to stay informed about their cause and initiatives happening worldwide.

Supporting Data

87% of users from the age of 18-24 have left a transaction due to a bad transaction process (leaving the application after too many steps required for the client). 

Feedback

While conducting user research, 66.7% out of 6 people surveyed said that a text message would make them want to come back to the web booking application. An integration of notifying the customer could increase customer retention if a booking app is used. 33.3% of people surveyed mentioned they visit a booking application once a day. 

Landing on the Solution 

Based on our target users’ pain points, we knew we wanted to work on the following features:

User Stories 

  1. As a DatFade user, I want to book an appointment without downloading an app, so that I can save the hassle. 
  2. As a DatFade user, I want to fill in no more than 4 boxes to register, so that I can book an appointment without wasting time. 
  3. As a DatFade user, I want to be notified through text message so I can book another appointment in the near future. 
  4. As a DatFade user, I want to receive exclusive discounts to save money.

User Flows/Mockups

Future Steps

This is what we learned from speaking to customers:

  • Time is important for customers
  • Good service inspires clients to book again
  • Incentives are important for client retention

Possible additional problems to address:

  • Customer retention is important for barbers
  • Reduction in registration phase helps clients from the hassle of too many steps

Images

Learnings

Product Manager Learnings:

Cuauhtemoc Dominguez

I have learned how to conduct user surveys/interviews. I have also learned how to write a product requirements document. And I learned a lot about the importance of honing in the problem space first before the solution space.

Designer Learnings:

Designer Learnings:

Jo Sturdivant

  1. Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
  2. Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
  3. Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

&

Developer Learnings:

Maurquise Williams

&

  1. Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
  2. Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
  3. Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning