Product teardown
Pick an app you use, explain who it is for, what job it does and one change you would make.
Decide what to build and why, then guide a team to ship products that people value.
You have reached the end of the beginner stages. Prove what you learned with a project.
You have reached the end of the intermediate stages. Prove what you learned with a project.
You have reached the end of the advanced stages. Prove what you learned with a project.
Pick an app you use, explain who it is for, what job it does and one change you would make.
Write a brief for a small feature: the problem, who has it, how you will measure success.
Interview five people about a real problem and summarise what you learned and what surprised you.
Score ten feature ideas with RICE and turn the top ones into an outcome-based roadmap.
Define a north star metric and dashboard for a product, with the SQL behind each number.
Plan a feature launch end to end: users, messaging, support, risks and success criteria.
The same roadmap as a reading list: every stage, what each topic covers, and which ones are optional.
Own the problem, align people and make trade-offs. PMs lead through influence, not authority.
How most product teams plan, build and review work in short cycles.
Enough about front ends, back ends, APIs and releases to talk with engineers.
Short, precise documents that help a team decide and act.
Ask about real past behaviour, not opinions about the future.
Understand the progress people are trying to make, not just what they say they want.
Connect a goal to user problems and to the ideas that might solve them.
Recognise when a product truly meets a market need, and when it does not yet.
Where the product is going, and the few bets that will get it there.
Compare ideas by reach, impact, confidence and effort instead of by who shouts loudest.
Communicate direction and outcomes without promising exact dates too early.
Set measurable objectives that connect daily work to company goals.
Describe who needs what and why, with acceptance criteria the team can test.
Decide together early, so ideas are valuable, usable and feasible.
Plan who needs to know, what changes for them and how you will measure success.
Trackers and docs such as Jira, Linear and Notion. Learn whichever your team uses.
Pick a north star and a few supporting metrics that reflect real user value.
Answer your own questions from the data instead of waiting in a queue.
Run A/B tests and read results without fooling yourself.
How the product makes money and how price shapes who buys it.
Keep leaders, sales, support and partners informed and aligned.
Know where AI genuinely helps users and how to manage its risks.
Build products that are fair, private and usable by everyone.
Free talks on building products and companies from founders and investors.
They work out which problems are worth solving, decide with design and engineering what to build, and make sure it reaches users and delivers value.
No, but understanding how software is built and being able to read data with SQL makes you far more effective with your team.
Many PMs move from engineering, design, support, sales or analysis inside a company. Show product thinking through teardowns, briefs and small projects.
© 2026 KamerLink. All rights reserved.