mixed · product
Product management for engineers
What the other half of the room is doing, why they keep changing their minds, and how to make that go well.
·
By Amit Chakraborty — Kolkata, India · Remote worldwide
What you will be able to do
Write a problem statement, prioritise honestly, and argue for scope with evidence.
Syllabus — 10 chapters
- 1. What a product manager does all day — Replace the caricature with an accurate model of the role.
- 2. Discovery: talking to users without leading them — Run a user conversation that produces evidence instead of agreement.
- 3. Writing a problem statement an engineer can build from — Separate the problem from the proposed solution, in writing.
- 4. Prioritisation, and why your backlog is a lie — Use a scoring method honestly, including its limits.
- 5. Roadmaps that survive contact with reality — Communicate intent and uncertainty at the same time.
- 6. Specs, acceptance criteria and the definition of done — Write down enough that two people build the same thing.
- 7. Metrics: activation, retention and the vanity trap — Choose a metric that moves when the product gets better and not otherwise.
- 8. Experiments and reading a result honestly — Run an A/B test with enough sample to mean something.
- 9. Saying no, and the politics of scope — Refuse work in a way that keeps the relationship.
- 10. Launch, rollback and what happens afterwards — Treat shipping as the middle of the process rather than the end.
0 of 10 published. A new chapter every Wednesday morning. Free to read.
Learn it free, elsewhere too
The documentation, videos, books and practice sites worth your time on this subject. All free. None of it is mine.