Product Management line, station 1 of 11
Product Thinking Foundations
Learn what a product manager really does, and how to turn any request into a clear problem, a map of the people involved and a value case checked against the four risks.
- 4lessons
- 2.5 hto read and do
- Beginnerlevel
- 4podcast episodes
Tools you'll use in this course
The lessons open these with a template ready. They work for your own job too, no course needed.
About this course
This is the first course of Kolom's Product Management track, and the product step in the Product Manager and Career Starter paths. It starts from zero: what a product manager is accountable for, how that differs from a project manager and a product owner, and how the job changes between internal tools, consumer apps, platforms, B2B products and AI.
Then you build the habits every later course relies on. You turn feature requests into problem statements and job stories, and find causes with five whys backed by evidence. You map who uses a product, who pays for it and who can stop it, including staff who can't switch to another tool. And you estimate what a product is worth in money, time and risk, then check the idea against value, usability, feasibility and viability before anyone writes code.
Every example happens at Mangrove Market, a fictional grocery chain with 320 stores, a customer app, a Partner app for 1,800 corner shops and a Store app on handheld scanners. Each lesson ends with a template you can copy into your own work, and the course ends with a one-page problem brief built from a request you will recognise.
What you will be able to do
- Explain what a PM owns compared with a project manager and a product owner, and how the job differs for internal tools, consumer, platform, B2B and AI products
- Turn any feature request into a problem statement and a job to be done, using five whys with evidence
- Map who uses, who pays and who decides, including for internal tools whose users can't switch
- Estimate the value of a product or feature in money, time and risk, and separate cash from capacity
- Check an idea against the four risks (value, usability, feasibility and viability) and pick the cheapest test for each
Syllabus
4 stops, about 2.5 h in total. Each stop fills in when you complete the lesson.
What a product manager actually does
Welcome to the Product Management track. This first lesson explains the job itself: what a product manager owns, how that differs from a project manager and a product owner, how the work changes between internal tools, consumer apps, platforms, B2B and AI products, and where you fit as a product moves through its life.
The PM roleOutcomes over outputsKinds of PMProduct lifecycle
Problems before solutions
Most work arrives as a solution: "add an export button", "make it like that other app". This lesson gives you a repeatable way to find the problem behind any request, describe it so a team can act on it, and decide what to do before anyone writes code.
Problem statementsFive whysJobs to be doneRequest triage
Users, customers and stakeholders
The person who uses a product, the person who pays for it and the person who decides whether it happens are often three different people. This lesson shows you how to tell them apart, how to listen to internal users who can't switch, how to map stakeholders before they surprise you, and how to write personas a team will actually use.
Stakeholder mappingPersonasUsers and buyersInternal users
How products create value
A product succeeds when it is valuable to the people who use it and also works for the business that pays for it. This lesson shows how value flows from users to business results, how common business models capture it, how to put a number on the value of an internal tool, and how to check an idea against the four risks before you build.
Business modelsValue estimationFour product risksInternal tool value
Capstone: From photo button to problem brief
A realistic project with a rubric and a model answer.
Final exam and certificate
10 questions drawn at random, 70% to pass.
Capstone project
From photo button to problem brief
Head office asks Imran to 'add a damaged-stock photo button to the Store app'. Last quarter Mangrove wrote off about $210,000 of stock as damaged across its 320 stores, and suppliers refunded only about a fifth of it, mostly because claims reached them without proof or without the goods received note (GRN) number. Assume about 1,300 damaged-stock write-offs a week, each taking a store about 12 minutes to record and send to the DC returns team, and that suppliers accept a claim only with a photo and the GRN number. Before anyone designs a screen, write the one-page brief Imran would send back to head office: what the real problem is, who is involved, what solving it is worth, and what could make it fail.
You will hand in
- A problem brief: the request split into goal, pain and proposed fix, five whys starting from last quarter's write-offs, a problem statement and a job story
- A who's-who map: users, payers, deciders, blockers and affected people (store staff, Ama as store manager, the DC returns team, finance and the supplier), with an engagement line for each key stakeholder and one persona
- A value estimate in dollars recovered and minutes saved per store per day across 320 stores, given as a range with cash and capacity separated
- A four-risk table naming the biggest value, usability, feasibility and viability risk, the cheapest way to check each, and which one you would check first
Check what you know
Already know some of this? Answer 4 quick questions, one from each lesson, and we will mark the lessons you can skim. It takes about 2 minutes and nothing is graded.
Questions
How long does the course take?
About 2.5 hours for the four lessons, including the checkpoints and practice tasks. The podcast episodes add about 50 minutes if you listen to all of them, and the capstone takes 2 to 4 hours.
Do I need a technical background?
No. The course assumes no product or technical experience. Engineers moving into product will find it covers the parts their background usually skips: finding the real problem, mapping people and estimating value.
I build internal tools for operations teams, not consumer apps. Is this course for me?
Yes. Internal tools are treated as first-class throughout: users who can't switch, workarounds, value measured in minutes and errors, vendors and rollouts. Course 8, Internal Tools, Operations and Platforms, goes deeper later in the track.
Is Mangrove Market a real company?
No. It is a fictional grocery chain used across every Kolom course, so the people, numbers and systems stay consistent. Real companies such as Spotify, Duolingo, M-Pesa, Slack and Square appear where their public facts help.
What should I take next?
Product Discovery, the second course of the track. It teaches the interviews, observation and cheap tests that the problem briefs in this course depend on.
Is it really free?
Yes. Every lesson, podcast episode, exercise, quiz, final exam and certificate is free. The labs and their templates for real work are free too. Plus and Premium add every lab challenge, weekly extras and a mentor on top, and they never lock the tools or the courses.
How does the final exam work?
You get 15 questions drawn at random from a larger bank. You need 70% to pass. If you do not pass, you can try again after 24 hours. The exam is graded on the server and you never see the answer key.