Product Requirement Document (PRD)

As a product manager, my initial endeavor was to thoroughly define the project's scope. This foundational process led to the meticulous drafting of the PRD. Throughout its development, iterative feedback from stakeholders refined the document, ensuring it met technical, user, and business requirements.

Roadmap

I drafted the roadmap and kept updating it based on the team's progress and the situation.

User Persona

Based on our user research and the information provided by our client, we came up with one primary user persona (persona 1) and three secondary user personas (persona 2-4) to better understand their needs and pain points.

Want to learn more details about the project?

Redesign: Landing Page

Redesign: 'How It Works' Page

Redesign: 'Contact Us' Page

1. Navigating Time Zones and Connectivity

Our design team was dispersed across the United States, Asia, and Europe, which complicated the scheduling of internal meetings. The additional hurdle of synchronizing these sessions with our client in Kenya amplified the complexity due to the expansive time differences. Moreover, our client faced inconsistent internet connectivity, which further impeded our ability to conduct smooth and productive Zoom meetings.

To cope with this challenge, I learned to...

• Optimizing Internal Meetings: I encouraged all team members to share their availability as comprehensively as possible and aimed to create a more flexible meeting schedule that accommodated different time zones
• Asynchronous Client Updates: When Zoom meetings with the client were not feasible, I resorted to using email and pre-recorded presentations of deliverables to keep our client abreast of our project's progress

2. Embracing Adaptability Over Perfectionism in Voluntary Projects

Undertaking a volunteer project taught me the vital lesson of adaptability in the face of fluctuating commitments and communication barriers. Our team members, juggling varying schedules with academic and personal responsibilities, experienced shifts in availability that impacted our workflow. Remote work and timezone differences introduced communication challenges that occasionally slowed our progress. Recognizing that aiming for perfectionism could hinder our momentum, I learned to be nimble, adjusting our roadmap multiple times to manage delays in deliverables pragmatically. This project underscored the importance of resilience and the ability to recalibrate expectations to maintain forward motion in a collaborative, volunteer-based environment.

To cope with this challenge, I learned to...

• Be Flexible: I adjusted our roadmap multiple times to manage delays in deliverables pragmatically. This project allowed me to learn the importance of resilience and the ability to recalibrate expectations to maintain forward motion in a collaborative, volunteer-based environment.
• A Strategic Approach to Delays: Due to delays in our deliverables, I took initiative to prioritize tasks and communicated promptly with our client. For example, I determined that the design of the chat feature could be deferred to a future iteration. Instead, we concentrated our efforts on the redesign of the user experience and user interfaces of existing pages.

Shout out to my amazing teammates & the client!

Team: Veronica T., Umika Mathur, Rachel Tan, Vivian Le, Caroline David, Julius Nguyen, Laura Wu, Shraavasti Bhat
Client: Kennedy Odoyo

Win24 Demo Day student and mentor participants
Source: Develop for Good Newsletter