Learning Hub Product Management Week 3
Week 3 of 7 Completed

Building an MVP

In this assignment, you will work as a team to develop a comprehensive case study and solve a problem for a product using everything you have learned so far.

Week 2 Week 4
Day 1 — Monday

Company Background and Scenario

Done

Start by reading the full assignment. Understand the company, the problem, and what is being asked before anything else.

Assignment Overview

From the Notes — Verbatim
Status
Completed
Week
Week 3
Description

In this assignment, you will work as a team to develop a comprehensive case study and solve a problem for a product using everything you have learned so far.

Company Background

From the Notes — Verbatim

Farmako (farmako.in) is an Indian startup working in the health-tech space known for its rapid medicine delivery service, promising to deliver medications within 20 minutes.

Scenario

From the Notes — Verbatim

Farmako has noticed a problem: many of its customers, especially those who need to take medicine regularly for long-term health issues, often forget to take their pills on time.

When people don't take their medicine as they should, it can make their treatments less effective and might lead to health problems. Farmako thinks it can help solve this problem.

As a Product Manager, your job is to create a new feature for Farmako's app that will help customers remember to take their medicine on time.

What You Need to Produce

1
Case Study Deck or Document

Develop a case study presenting your MVP solution for a medication reminder and adherence tracking feature within Farmako's existing app.

2
7 Focus Areas

Business model, value proposition, user segment, user research, feature ideation, MVP definition, and product design — all covered in the case study.

Day 2 — Tuesday

Study: Ideation Techniques and Decision Making

Done
Self-Study Topic

Ideation, Decision Making and Product Design

What is Ideation in Product Management?

Ideation is the creative process of generating, developing, and communicating new ideas. For a PM, ideation is not about random brainstorming — it is a structured process that begins with a deeply understood problem and ends with a set of concrete, prioritised solution candidates.

Good ideation is always anchored to a specific user problem and a specific context. For the Farmako assignment, the context is: a health-tech app used by patients with chronic conditions who forget to take medication.

Common Ideation Techniques

How Might We (HMW)

Reframe the problem as an opportunity. "How might we help Farmako users remember to take medication?" Each HMW question opens a different solution direction. Generate many, then filter.

Crazy 8s

Sketch 8 rough ideas in 8 minutes. Forces quantity over quality in the first round. Used in design sprints to avoid anchoring on the first idea. Works well for feature design.

SCAMPER

Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse. Apply each lens to an existing product or feature to generate variations and improvements.

Analogous Inspiration

Look at how other products solve a similar problem in a different domain. How do fitness apps track habits? How do banking apps send payment reminders? Borrow and adapt.

Decision Making for PMs

After generating ideas, you need to narrow down to the best option. PMs use structured frameworks to make this decision transparent and defensible.

Impact vs Effort Matrix

Plot each idea on a 2x2 grid with Impact on the Y axis and Effort on the X axis. Ideas in the top-left quadrant (high impact, low effort) are your quick wins. Ideas in the top-right (high impact, high effort) go into your roadmap. The bottom half is generally deprioritised.

RICE Scoring

RICE = (Reach × Impact × Confidence) ÷ Effort
Reach
How many users will this affect per time period?
Impact
How much will this move the needle? (0.25 = minimal, 3 = massive)
Confidence
How confident are you in your estimates? (expressed as %)
Effort
How many person-months of work will this take?

Today: Study ideation techniques and practice applying HMW questions to the Farmako medication reminder problem. Tomorrow you will study Product Design and wireframing before starting the assignment on Day 4.

Day 3 — Wednesday

Study: MVP Definition and Product Design

Done
Self-Study Topic (continued)

Ideation, Decision Making and Product Design — MVP and Wireframing

What is an MVP?

A Minimum Viable Product is the simplest version of a product that delivers enough value to early users and generates enough feedback to validate (or invalidate) your key assumptions. The goal is not to build something small — it is to learn as quickly as possible whether you are solving the right problem in the right way.

What does NOT belong in an MVP
  • Nice-to-have features that do not test core assumptions
  • Advanced personalisation before the basics work
  • Anything that takes months to build before you can learn
What SHOULD be in an MVP
  • Core feature that solves the primary user pain
  • Just enough for users to complete the key flow
  • Measurement hooks to know if it is working

For Farmako — Thinking About the MVP

Core assumption to test:
Will Farmako users set up medication reminders if offered, and will this reduce missed doses?
MVP features to consider:
1.Simple push notification reminder at a user-set time
2.Medication schedule setup in the existing Farmako app
3.Simple "I took it" confirmation to track adherence

Product Design and Wireframing

Wireframes are low-fidelity sketches of a product interface. They communicate structure and flow without visual design. For this assignment, wireframes should show:

  1. Where the reminder feature lives inside the existing Farmako app
  2. The flow for setting up a medication schedule
  3. The reminder notification UI
  4. The adherence tracking view

You can use Figma, Google Slides, or even hand-drawn sketches photographed and inserted into your document. The purpose is to communicate — not to produce pixel-perfect designs.

Today: Study MVP definition and wireframing. By end of day you should have rough wireframe sketches ready, and a clear list of what features are in vs out of your MVP. Day 4 is full assignment work.

Day 4 — Thursday

Assignment Work — Build the Case Study

Done

Assignment work day. Start building your case study today with your team. Cover as many of the 7 focus areas as possible. Day 5 is for final polish and submission.

Your Task — From the Notes

From the Notes — Verbatim

Develop a case study presenting your MVP solution for a medication reminder and adherence tracking feature within Farmako's existing app. You can submit the case study as a deck or a document.

While working on this problem, focus on the following aspects:

  1. Business Model Integration: Explain how this feature fits into Farmako's existing business model and quick-delivery value proposition.
  2. Business Value Proposition: Outline the potential benefits for Farmako in addressing medication adherence.
  3. Target User Segment: Identify the specific user group who would benefit most from this feature.
  4. User Research: Propose methods to validate the need for this feature and gather insights on user preferences for medication reminders.
  5. Feature Ideation: Present your ideation process for the reminder system, considering factors like notification types, tracking methods, and integration with the delivery service.
  6. MVP Definition: Clearly define what features would be included in the Minimum Viable Product version of this medication adherence tool.
  7. Product Design: Create basic wireframes or mockups showing how the reminder feature would be integrated into Farmako's existing app interface.

Working Through Each Section

Section 1 — Business Model Integration

Farmako's core business model is rapid medicine delivery (20-minute delivery). Think about how a medication reminder feature reinforces this: reminders drive timely reorder behaviour, which increases delivery frequency. The feature creates a habit loop that ties users more closely to the Farmako platform.

Section 2 — Business Value Proposition

Frame the value in terms Farmako's leadership cares about: increased repeat orders, higher customer lifetime value, reduced churn, and differentiation from other pharmacy apps that do not offer adherence tracking.

Section 3 — Target User Segment

The most direct target is chronic disease patients — diabetes, hypertension, thyroid conditions — who take the same medications daily or weekly. These are high-frequency, high-LTV customers for Farmako. Secondary segments could include caregivers managing medications for elderly family members.

Sections 4–7

User research (surveys, interviews, app session data), ideation (notification types, voice reminders, caregiver alerts), MVP definition (what is in vs out), and wireframes (3–4 key screens). Work through each with your team.

Day 5 — Friday

Finalise Case Study and Submit

Submitted

Full Task — From the Notes

From the Notes — Verbatim

Develop a case study presenting your MVP solution for a medication reminder and adherence tracking feature within Farmako's existing app. You can submit the case study as a deck or a document.

While working on this problem, focus on the following aspects:

  1. Business Model Integration: Explain how this feature fits into Farmako's existing business model and quick-delivery value proposition.
  2. Business Value Proposition: Outline the potential benefits for Farmako in addressing medication adherence.
  3. Target User Segment: Identify the specific user group who would benefit most from this feature.
  4. User Research: Propose methods to validate the need for this feature and gather insights on user preferences for medication reminders.
  5. Feature Ideation: Present your ideation process for the reminder system, considering factors like notification types, tracking methods, and integration with the delivery service.
  6. MVP Definition: Clearly define what features would be included in the Minimum Viable Product version of this medication adherence tool.
  7. Product Design: Create basic wireframes or mockups showing how the reminder feature would be integrated into Farmako's existing app interface.

Submission Guidelines — From the Notes

From the Notes — Verbatim
  • Use any platform like Notion, Google Doc, Canva, Figma or Google Slides. Share a public link to the doc as your submission.
  • Utilize space efficiently with appropriate font sizes and layout optimization.
  • Cite any external data sources with hyperlinks.
  • Focus on conciseness and clarity.

Remember, attempting the assignment and receiving feedback is more valuable than striving for perfection.

Final Checklist Before Submitting

Business Model Integration section is complete
Business Value Proposition clearly outlined
Target User Segment identified with rationale
User Research methods proposed
Feature Ideation process documented
MVP Definition clearly states what is in and what is out
Wireframes or mockups included for the reminder feature
All external data sources cited with hyperlinks
Public link to document shared as submission
Next: Week 4