Very good summation. Though for the title I’d change it to “Minimum Viable Product-Manger” (note the hyphen). I initially read it as “Minimum-Viable-Product Manager” which I think is how most people would read it since MVP means Minimum-Viable-Product. Perhaps you meant it as MVP Manager, but these skills are the minimal needed for a good product manager, not just those needed for those who just do Product Management for MVPs.

You’re right that this stuff doesn’t come overnight, and there is no program that teaches all this, or even enough of any of it without cramming a ton of other useless stuff in there that gets in the way (and still misses a ton). In general you need to know enough to know what each part of your team is talking about when speaking in broad terms of their status at any given time and this is a pretty good sample of what those domains will be. Just as important as what to know is “where you shouldn’t focus”. This is where you separate the “Managers who help” from the “Managers that make people want to quit”.