Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
Memberships
JUSTANOTHERPM
Public • 387 • Free
15 contributions to JUSTANOTHERPM
Oct 23 in
FOP 2.0 [Week 5] Q&A Thread
Please add your questions and learnings from the week here. We will be sure to discuss in detail in our upcoming live session
0
1
New comment 4h ago
0 likes • 4h
My question is more around how do we tie each of the stages in the different cycles that we have learned so far together. Starting from Product Discovery, then Design Thinking, The Product Lifecycle, and now the Software Development Lifecycle. There seems to be a lot of overlap in between them, so I am unable to understand which cycle to apply where or what stage am I in while working as a Product Manager.
Oct 23 in
FOP2.0 Week 5 Learning
Please share everything that you've learned in Module 5. Also review learnings from other students to make sure you are aware, and share your thoughts if you agree/disagree.
0
1
New comment 5h ago
0 likes • 5h
To ensure we know how to work with engineers, this module was extremely helpful in establishing your ways of working with them. 1. Knowing more about the Software Development Lifecycle - Waterfall and Agile (Scrum or Kanban) works helps you as a Product Manager into adjusting to different engineering, design, analytics team's working style. 2. Make sure that the requirements are translated very well into user stories and acceptance criteria so as to help engineer focus on the end goal of that project. It is highly possible that engineer might interpret your user story separately and therefore Acceptance Criteria helps in that regards 3. Make sure testing is carried out thoroughly despite delays before it launched into Production for user access. There are many examples (including mine ;-D) of feature release without testing caused more issues that feature not being releases at the right time. 4. Learn to keep your engineers close; a.k.a build great relationships with your engineers - as they will help you a lot when resolving critical issues for the product and technical understanding.
Oct 23 in
FOP2.0 Week 4 Learning
Please share everything that you've learned in Module 4. Also review learnings from other students to make sure you are aware, and share your thoughts if you agree/disagree.
0
5
New comment 2d ago
0 likes • 2d
Wow, Comprehensive and great learning overall. I really enjoyed this module: 1. You as a Product Manager are responsible for everything related to the Product Lifecycle irrespective of the level or the org that you are working at. 2. Always begin with high-end vision, then create a plan of action of how we achieve that vision. The vision is really helpful in bringing alignment with your stakeholders to ensure everyone is on the right track. 3. Communication is really important in relaying your message to keep the engagement high and resolve conflicts if they occur in the process. 4. Ensure you keep a buffer of usually 2 weeks plus whenever Legal is involved so as to communicate potential delays during the Execution (speaking from experience) 5. Think about the most important metrics that you are aiming to create or improve. This will help in bringing moire information about the next strategies, roadmaps and other decisions.
21d ago in
FOP 2.0 [Week 2 Module 3] Task 2 Submission
Task: Select one of the problems defined in task 1 which can be solved by improving the product. - deate and write down 5-6 potential solutions for the selected problem statement. - Select one idea from the solutions and share your rationale for selection. - Share your output on the post below
0
2
New comment 19d ago
0 likes • 20d
Selected Problem Statement: Users: All Users Needs: Reliable and accurate delivery status updates Insights: Users experience anxiety and uncertainty due to inconsistent or inaccurate delivery updates, leading to a lack of trust in the app’s communication and reliability. Solutions to solve the above problem: 1. Real-time GPS tracking of delivery driver 2. Predictive ETA updates based on restaurant's earlier time history of preparing food and handing to delivery driver 3. Notifications based updates for the order like a Visual Progress Indicator 4. In-App Chat Support for concerns regarding delivery time 5. Contact delivery driver to check on times or customizations Solution selected: Predictive ETA updates based on restaurant's earlier time history of preparing food and handing to delivery driver Rationale: Dynamic time updates based on restaurant's history gives a range of how much the delivery usually takes when ordering from a restaurant. For example if the location of the order is not far from the customer but the restaurant is a busier one, the time range will give user a ressaurance that their order is going to be delivered in certain time frame.
21d ago in
FOP 2.0 [Week 2 Module 3] Task 1 Submission
Task: Create Problem Statements from Empathy Stage Findings The designer has completed the Empathy Stage of the design thinking process for the food delivery app. Below, you will find the key user insights, user personas, and emotional map that summarize the findings. Your task as the Product Manager is to identify the pain points and create clear problem statements for each. These problem statements will help guide our ideation and prototyping phases, ensuring we address the most pressing user needs. The findings are shared below: 1. Key User Insights: Through interviews, surveys, and observation, we have gathered the following insights about our users: "I want my food to arrive on time and still be warm." (4 out of 5 users mentioned this) Insight: Users feel frustrated when their food arrives cold or late, which diminishes their overall satisfaction. "It’s hard to find the food I want quickly—there are too many steps." (3 out of 5 users mentioned this) Insight: Users find the app’s navigation complex and time-consuming, leading to frustration when they can’t easily find what they want. "I wish I could filter restaurants based on dietary needs like vegan or gluten-free." (2 out of 5 users mentioned this) Insight: Users feel limited by the current filtering options, which don’t accommodate specific dietary preferences. "I don’t trust the app’s delivery status updates; they aren’t reliable." (3 out of 5 users mentioned this) Insight: Users feel anxious and uncertain because they don’t receive accurate or timely updates on the status of their delivery. 2. User Personas: Persona 1: The Busy Professional Needs: Quick access to meals during work breaks, reliable delivery times. Frustration: Delays in delivery and difficulty navigating the app. Persona 2: The Health-Conscious User Needs: Easy access to healthy food options, the ability to filter restaurants by dietary needs. Frustration: Lack of dietary-specific filters and confusing app navigation.
1
5
New comment 19d ago
0 likes • 20d
Solving the above with a Point of View Problem Statement:
1-10 of 15
Active 1h ago
Joined Sep 25, 2024
Seattle, Washington, USA
powered by