Why this site exists
Search for "product roadmap template" and you will find a hundred pages that say the same six things, all of them written to rank rather than to teach. Search for "what do I do when my stakeholder keeps overriding the roadmap" and you will find almost nothing. Product with Ashish exists to write the second kind of article.
What I cover
Three tracks that follow the actual loop of the job — discovery and research, strategy and roadmapping, and execution and delivery. They are separated for navigation, not because the work is separable. A roadmap built without discovery is guesswork, and discovery that never reaches delivery is a research hobby.
How articles are written
Every guide names its failure modes. A technique described only in its ideal form is not much use — what you need to know is how it breaks, what the warning sign looks like two weeks beforehand, and what to do instead. Most product writing skips this because it requires having actually run the thing badly at least once.
Where a framework has a real weakness, I say so, including for the ones I recommend. RICE has a systematic bias toward broad and shallow work. Jobs to be done is weak for incremental improvement. Opportunity trees become wallpaper if nobody updates them. None of that makes them useless; pretending otherwise makes them harder to use well.
No framework on this site will tell you what to build. They exist to make your reasoning visible so a group can argue about the right thing. Any model treated as an oracle will produce confident nonsense — usually with a decimal point attached.
What I don't do
- Gate content behind an email address. Everything here is readable without signing up. The newsletter is there if you want it.
- Recycle other people's posts. If an article does not contain something you would only know from doing the work, it does not go up.
- Pretend the job is tidy. Most product management happens with incomplete information, a stakeholder who says yes in the meeting and no in the corridor, and less authority than the org chart implies. Advice that assumes otherwise is entertainment.
Who writes this
I'm Ashish. I write everything here.
Two or three sentences: your current role, how long you have worked in product, the kind of products you have shipped, and one specific thing you learned the hard way. Add a photo too. Search engines weigh demonstrated expertise heavily now, and this paragraph is where a reader decides whether to trust the rest of the site.
Get in touch
Corrections, article requests and disagreements are all welcome — the disagreements especially. If something here is wrong, or true only in a context I did not name, that is worth an email.