I liked this article until it got into the charts and didn't really outline what the governance points actually entail in terms of work. I'm also missing how th

I liked this article until it got into the charts and didn't really outline what the governance points actually entail in terms of work. I'm also missing how the bottom part actually gets you closer to the goal at the end unless you explicitly make setting that goal part of your governance / planning / project start which wasn't really mentioned. I gather from the article's initial paragraphs that these "Governance" point is really the team getting input from all the normal stakeholders and creating the backlog of work themselves? This makes all the sense in the world - getting technical folks involved in discussions is key. What I would like to see added are concrete steps / workflows that these technical teams have found that help make these governance points effective without eating up a lot of time, and what practices they used to ensure that the project goal / direction / outcomes were decided upon up front. I personally think Agile Roadmapping / Storymapping with the whole group can go a long way toward ensuring whatever you build is going in the right direction. From there, you'll want the team to work with the product owner folks and keep a tighter grip on the backlog toward that direction and good things can happen.