Garage
Garage is a platform connecting car owners and mechanics, making it easier, more efficient and more transparent in dealing with fixing their cars.
Problem Statement
How might we make it a smoother and easier experience for car owners when dealing with mechanics?
Problem Background
For most younger car owners, when dealing with mechanics the probability of having a bad experience with mechanics is extremely high.
User Pain Points
From phone interviews with younger car owners, it was discovered the two main pain points when dealing with mechanics was
- Finding quality car mechanics
- Verifying quotes given transparently
- Thoroughly concluding a job given
Feedback
Research showed that car owners mostly found mechanics through referrals gotten from friends and connections through personal friend circles or social media circles eg. Instagram. Furthermore, when dealing with some mechanics there was little transparency with the quotes given. Car owners were unable to verify what seemed to be a fair price for the work being done, allowing for room to be cheated. Also, some problems were encountered and quoted long into the job or weren’t given attention at all. This often left the car owners paying for half work done on their vehicles.
Landing on the Solution
Based on our target user pain points, it was clear that a platform that enabled car owners to find and book quality mechanics with verified competency in the type of vehicle the car owner utilised was the preferred solution. Also, enabling car owners to easily verify or compare quotes from the general market of qualified mechanics to see if they are being billed the effective range for the type of work being done on the car.
Explanation of Solution
After explaining the solution to potential users we found out that most young people have little knowledge of the full work down on their cars, especially any work being done on the engines. This further helped assert the need for a qualified third party able to verify the work the cars are doing as they should prevent owners from being billed for work neglected and to ensure that the work on the vehicle are thoroughly done as agreed upon before returning to car owner.
Future Steps
Whilst finding and booking mechanics is only the beginning, it would further benefit car owners if Garage was a top-down platform that allowed car owners to completely manage all aspects of their vehicles. This includes being able to register and track work being done on each vehicle they possess, being able to register documentation and perform or get reminders of regular documentation renewals required, and being able to even find and get insurance through the platform based on the data provided.
Learnings
Product Manager Learnings:
Eni Chidumebi Amogu
Co.Lab was a very interesting experience for me as it allowed me to think of business as simply finding solutions for an existing problem. Being able to do this, no matter how little the problem is, gives the potential for a unique selling point/ value-add to be created. This gives a significant competitive edge over other businesses/solutions in the marketplace.
Designer Learnings:
Designer Learnings:
Jo Sturdivant
- 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.
- 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.
- 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
&
- 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.
- 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.
- 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.