[LukaAl]

As a PM I almost totally agree with you. There's a caveat, though. I know what I want, and in general, I want everything well done and polished.

But the right question is not "What do I want?" but "What need to be done?". That means having different priorities than my wishes and understanding the work on some non-sexy features that will make the product stronger in the long run.

One thing I noticed, though, is that what needs to be done could change, in a startup environment pretty quickly, and having been on the other side, it is pretty difficult to understand. So you need to communicate clearly why priorities are shifting, and you need to be able to take the blame if they are shifting due to a mistake you have done.

Anyway, my suggestion to any wannabe PM: Thinks of what is important for the product, not what you (or the stakeholders) want in the product. Second, be clear in your communication.