I find it frustrating the the US Govt spends > $800B/yr on our "defense" while we run out of basic supplies like ammunition and all of our tanks and ships are falling apart.
Meanwhile, that same Govt spends < $1B on fusion, which could change the course of humanity.
I'm usually the last person to suggest that the govt should spend money on things, but for goodness sake I wish we could at least get our priorities straight as far as what to spend the money on.
If I didn't know better I'd think that the whole point of the defense department was to funnel money to well-connected corporations and execs.
I imagine it has a lot to do with oil company lobbying.
1. Map the product or idea being built to those who will use it. Present it, get users feelings on it, if it is viable and needed. Throughout development, gather continuous feedback by demoing, shadowing, and adapting to new feedback. Plan and execute a launch, watch for snags, provide support and solutions to users.
2. Communicate gathered feedback to engineering, and do so with an understanding of where the project is engineering-wise, where it is going, what needs to change. Give engineering the "why. Convey the priority of everything the project needs vs what it has and what is being worked on.
Repeat this feedback loop.
But most of them seem to think they can operate entirely in document-land and just crank out roadmap docs and keep stakeholder alignment via endless check-ins and nagging. They are doing a "project manager" job instead.