SPRINT29 - Portfolio

ImmediTask

ImmediTask! Services done right, performed safely, and at your fingertips.

Problem Space 

Many individuals rely on services like Handy or TaskRabbit for immediate task completion, but ensuring safety, especially for vulnerable groups like single women, households with young children, and locations with valuable items, remains a significant challenge. The lack of safety guarantees, taskers being unable to complete tasks, limited immediate availability, and the need to schedule tasks for future days are common pain points experienced by users. How can we enhance the safety measures of such services to provide peace of mind and trust for all users?

Problem Background  

As a remote worker, I often struggle with completing tasks and errands due to time constraints or a lack of expertise. While apps like TaskRabbit or Handy offer convenience, the foremost concern is ensuring safety. Inviting someone into my home to address unfinished tasks, especially with children present and valuable items at risk, raises significant safety apprehensions. It's crucial to find a solution that alleviates these concerns and enables tasks to be completed safely and efficiently.

User Pain Points

  1. Lack of Safety Guarantees
  2. Taskers Unable to Complete Tasks
  3. Limited Immediate Availability
  4. Need to Schedule in Advance
  5. Quality of Service
  6. Communication Issues

Supporting Data

After surveying working professionals who either own or rent a home or condo, it was found that 25% had never used apps like Handy or TaskRabbit. Their reasoning stemmed from a preference for hiring from reputable companies to ensure safety and quality work, or at least having guarantees such as money-back policies or job corrections by alternative service providers.

While all respondents expressed some level of concern for safety, their need for efficient task completion often outweighed these apprehensions. Additionally, users expressed a desire for immediate scheduling convenience paired with assurance of safety and accuracy, with a significant 90% indicating willingness to pay more for such a service.

Feedback

My initial research provided evidence and validation of the problem, reinforcing the need for a solution that prioritizes safety, immediate service, and accuracy.

Landing on the Solution 

The unanimous agreement points towards developing an app that meets the diverse needs of all users. Key priorities include prioritizing safety, ensuring immediate service delivery, and maintaining high accuracy levels. Moreover, a crucial aspect that enhances every app is its ease of navigation and user-friendliness, ensuring a seamless and enjoyable experience for all users.

Future Steps

Next steps for ImmediTask would be developing an interactive prototype to showcase the app's functionality and design. I would need to conduct user testing sessions to gather valuable feedback and prioritize features that align with my core priorities of safety, immediate service, accuracy, and user-friendliness. Following agile methodologies, I will then commence development and thorough testing to ensure high standards of functionality and performance. At some point I would need to do marketing to generate excitement and attract my target audience. Post-launch, I would continue to gather feedback, iterate on the app based on user insights, and explore opportunities for expansion and scaling as ImmediTask gains traction and user adoption.

Learnings

Product Manager Learnings:

Takiyah Anderson

Taking this bootcamp taught me patience. The biggest focus was needing to unlearn my "bad" habits and not jump to solving the problem. Initially I was frustrated with my mentor's feedback because I took it as him telling me to start over. But that wasn't the case; I just needed to redirect my focus and settle on one thing from what I already had.

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