Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
JUSTANOTHERPM
1k members • Free
12 contributions to JUSTANOTHERPM
Oct '24 •
FOP2.0 Week 6 Learning
Please share everything that you've learned in Module 6. Also review learnings from other students to make sure you are aware, and share your thoughts if you agree/disagree.
0 likes • Dec '24
- Approach career growth like a product with a long-term vision. Create a (career) vision for around 5 years – make it ambitious and aspirational. - Develop a (career) strategy on how you plan to get to the vision from your current position. - Break the plan down into 12, 24 and 60 months – this is your (career) roadmap. - Implement the plan, track progress, get feedback and iterate continuously to give yourself the best opportunity to reach your goals. The achievement tracker to document progress and achievements is a very useful resource and something I will look to implement going forward for myself. Finally, it was very insightful to hear both Sid and Shirin’s career learnings from their respective careers in product management. Some of the learnings were very relatable to my current role and will be useful to take onboard – Thank you!
Oct '24 •
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 likes • Nov '24
The software development lifecycle (SDLC) is a series of steps that are taken to develop high quality software, with the product manager contributing throughout but to various levels of detail. There are different types of methodologies and the two main types; Agile and Waterfall were focused on to explore the differences between them. It is important that you look to build a strong relationship with your engineering team where possible. This can be done by continuously collaborating and seeking feedback for continuous improvements. Clearly communicating requirements and providing as much detail as possible to avoid them being interpreted incorrectly. Listening to the team, they can also have some great ideas for features for the product, sharing credit where possible and being decisive in finding the best balance between business vs technical value all contribute to strengthen these relationships.
Oct '24 •
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.
1 like • Nov '24
The Product lifecycle consists of four phases: 1. Planning 2. Alignment 3. Execution 4. Measuring and Improving Planning: - Where do we want to go? – This is the vision statement and should be broad, ambitious and inspiring - How do we get there? - This is the product strategy, which outlines how we reach the destination. We were shown what we could include in a product strategy document. - What do we do to get there? This is the roadmap and outlines what we do today, tomorrow and later to meet the goals set out in the product strategy. Essentially, a list of problems and the sequence to solve these. Alignment: The purpose is to ensure a cohesive understanding between all parties with an interest in the product so that everyone is moving in the right direction. - Identify- the correct people/teams that you need to align - Communicate- to effectively relay and translate the correct messages. Try to be transparent. - Engage – Build and leverage relationships to get support when needed. - Conflict Resolution – How to still make progress even when there is a disagreement. Execution: This is where we start “doing” by executing tactical and tangible tasks translated from the strategy. It is where features are developed and launched. The success criteria for successful execution are to meet the strategic goals, meet timelines and maintain quality. Measuring and Improving: Measuring – validate you have the right plan and what you have executed is meeting the plan and the goals. - If you are doing well, then ask yourself, how can you repeat - If you are not doing well, then ask yourself how can you fix this This can be done through metrics, where we learned what is considered good metrics and what to always keep in mind when doing so. Improving – What you can do and ways to continuously improve your product. The aim is to ensure that every product management cycle should be better. Look at the wins and lessons learned to assess whether you are making progress.
Nov '24 •
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 likes • Nov '24
Problem Statement - How might we simplify the app navigation for our users to make it easier for them to place an order Solutions: 1. Introduce a search option to allow the user to search if they have specific food in mind and it can filter the results 2. Group food options into logical categories 3. Guided Navigation – Tutorial on how to use the app or in app tooltips for the user 4. Personalized homepage – shortcut to “reorder” option to purchase previously bought items or recommendations to similar items from previous purchases 5. Allow for payment details to be saved so these can be re-used when required Solution selected: Group food options into logical categories By categorizing the food options available, each category can be clearly labelled with a relevant image associated to this label. It will then be clear to the user what categories are available for selection. This can allow the user to seamlessly switch between categories to filter the results based on this action. By reducing the options available it can allow for the user to complete their transaction in less steps as they don’t have to keep going through various steps of menu choices.
Nov '24 •
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.
0 likes • Nov '24
1. How might we improve our delivery process to our users to ensure their food arrives at an edible temperature within the specified time slot 2. How might we simplify the app navigation for our users to make it easier for them to place an order 3. How might we make it easier for our users with specific dietary requirements to find food choices that are suitable for them 4. How might we make the delivery status updates for our users more realistic
1-10 of 12
Active 4d ago
Joined Oct 10, 2024
Powered by