Every large technology organization I've stepped into has the same gap: a well-funded roadmap, a fully staffed org chart, and no operating model connecting the two. Leadership assumes coordination will happen organically once enough smart people are in the room. It doesn't.
An operating model is the unglamorous plumbing that decides who reviews what, how priorities get reconciled across six teams that all think they're priority one, and what "done" actually means before something gets reported up as done. Nobody puts a line item for it in the budget, and it's the single highest-leverage thing an executive can build.
The tell
You know an organization is missing one when the same status update gets reported four different ways to four different stakeholders, and the exec sponsor finds out about a slipped date in a hallway conversation instead of a review.
Fixing it isn't about more process. It's about fewer, clearer accountabilities — one point of ownership per decision, one cadence for portfolio visibility, and the discipline to kill status theater in favor of an honest read on delivery health. It's boring work. It's also the difference between a portfolio that scales and one that just gets bigger.