Shreyas M.

PM tip: the answer to "what should we build" is almost never a feature. it's usually a clearer definition of who you're building for.

narrow the audience, and the roadmap draws itself.

you don't need a strategy doc. you need a page of prose that a smart new hire could read and immediately know what to say yes to and what to say no to. if your "strategy" doesn't do that, it's a wish list.

when a metric goes up 40% overnight, the correct first question isn't "what did we ship." it's "what did we break."

the best org design is the one that lets your best people say no. the worst is the one that requires them to say yes.