> You have been a dev. If you want to be a PM, you should already have opinions
yes yes yes
> on how to build an ideal workflow
no no no. Workflow and process is the least important part by far.
> what your ideal team/org/process structure looks like.
no no no. waste of time.
> PMs who truly understand the creation of software
We're solving customer problems, the creation of software is a side effect for engineering to worry about, this is the 'how', your effort must be focused on the 'why' and the 'what'.
It's pretty shocking you don't mention understanding customers once in this advice.
It is not your job to sweat this stuff. The best PMs are adaptable to the business, and develop a thesis based on customer discovery, about how your business can add value to customers. Then you convince the business to build what your think can give value, aligned with your product vision and product strategy.
Hopefully those opinions you have are about your customers and the problems they have.
The ingredients of good PM are not processes and workflows, but product sense, design taste, and customer empathy.
Product discovery is the single most important activity you can do as a PM (that others do not do or don't want to do).