How to explain that choice of UI library and framework should be made after the design of user experience

Pretext

Most UI frameworks or libraries (that I know of) provide components and layouts in a declarative manner with the underlying implementation as a grid with hooks for extending the functionality. This means that once you have defined a blueprint of your layout (which is a grid internally) what you can do on it later will be limited by the structure of the grid.

Question

How to explain to the architects and managers that the choice of a library or a framework should be made or evaluated after deciding what is to be done rather than first choosing the framework and then choking the UX designer with limitations of that framework (some of which may be identified in due course of engineering itself)?

Is there a study or research done on pitfalls of such approach?