It's strange organizations want to push users off of a minor $100/yr/user cost when there are many other ways to save money that don't involve making a power user useless for years.
I’ve realized that companies like McKinsey also provide a scapegoat for a manager’s decision gone wrong. They can just blame McKinsey for advising them to do it. But they can’t as easily blame an AI. And McKinsey is happy to be the bad guy.
I think this is an area where we will still keep humans. To blame someone when something goes wrong.
Unfortunately for McKinsey, that’s not going to be enough to prop up their revenues.
People develop relationships with coworkers, you care if someone has issues, you're happy if a solution makes customers/coworkers happy but none of that matters to the lawnmower, it just mows lawns.
In some cases I have seen, people use RFCs to steamroll decisions when they are the only stakeholders. Here the waste comes from the fact that the proposal becomes just a bureaucratic step or a way to diffuse responsibility.
In the case you mention (which I have seen many times) I would say the general issue is that the goals and the constraints are not qualified sufficiently. If that's the case, then there are only 2 cases: there is an objective way to measure if an objection or comment makes sense or not, or it is subjective. If it's objective, then consensus is easy to reach, if it's subjective, it needs to be acknowledged and usually the decisions falls on those who are responsible for the outcome (e.g., the team who needs to maintain or build the thing).
Of course, the debate can move to constraints, goals or even ways to measure, but these are generally more straightforward.
Really though it's the organization (and people) that makes or breaks anything.