He was referring to cases like the PM being a highly skilled person with clinical trials. The PM already knows a lot about regulations, customers, what problems

He was referring to cases like the PM being a highly skilled person with clinical trials. The PM already knows a lot about regulations, customers, what problems can be "automated" away with software, etc. The PM is likely trained in life science or medicine, and never coded themselves. One might be tempted to ask the PM to decide on the following: What should happen if the user clicks "save" but the network went down? Shall we retry a few times? How many times? With what backoff? Or shall the application be offline-first? How should potential conflicts between the server data and the client data be resolved? As you can imagine, the PM has already enough on their plate, so, in my experience, it's best to not overwhelm the PM with such questions and take a decision based on "best guess" on what would maximize customer success. Another anecdote: A PM had to prioritize "integrate with Lufthansa" and "migrate to Java 8". Clearly the latter issue is at the wrong level of detail for a PM.