Discovery, prioritization, metrics and roadmaps — product thinking for founders, PMs and engineers.
MVP development cost and timeline explained: what moves the price, realistic build weeks by product type, and how to cut scope without cutting the learning.
A clear explanation of the product manager role — responsibilities, a week in the life, skills, how PMs work with engineering and design, PM vs product owner vs project manager, and common anti-patterns.
How to write a product requirements document that's short, clear and useful — problem, goals, non-goals, user stories, requirements, success metrics, open questions — with a template.
How product teams prioritize — RICE, ICE, Kano, MoSCoW, value vs effort, cost of delay and opportunity scoring — with examples, pitfalls and how to combine them with strategy.
A practical guide to building a minimum viable product — defining the riskiest assumption, MVP types, scoping ruthlessly, choosing no-code vs code, measuring learning and what comes after.
Which product metrics to track and why — North Star metric, input metrics, AARRR funnel, activation, retention cohorts, engagement, revenue metrics, guardrails and avoiding vanity metrics.
A practical guide to product discovery — customer interviews that avoid bias, jobs-to-be-done, opportunity solution trees, assumption testing, prototypes and continuous discovery habits.
What product-market fit really means, the signals and metrics that indicate it — retention curves, the 40% survey, organic growth — and a practical process to find it.
How to build product roadmaps that work — outcome-based roadmaps, Now/Next/Later, OKRs, balancing features with tech debt, communicating uncertainty and handling stakeholder requests.
How product management changes for AI and LLM features — defining quality with evals, probabilistic UX, human-in-the-loop, cost and latency trade-offs, data strategy, trust and rollout.
Practical advice for product managers and engineers — sharing context, involving engineers early, estimation, scope trade-offs, technical debt, communication norms and building trust.