Medusa first used management reporting

Remember the story of Medusa from Greek mythology, monster with many snakes and eyes instead of hair? Well, this was the first usage of multiple views. Many views over same matter  today, is very common practice in management reporting. CTO looks on company from his angle (costs, projects, services, processes), CFO form his, CIO form his and so on. For example, same generated revenue can be viewed: per sales channels, per business units, per customer segments, per projects, per locations, per products. Same amount of revenue is viewed from different angles, views. Same is with costs which can be reported: per cost categories, per cost centers, per organizational units, per functional units, per projects, per products and services, per activities and so on and so on.

What is the main problem with so many views? Problems are decisions and actions taken upon specific views? Specific view, one or several does not mean to have all views are counted. If CIO cuts one of his projects, how shall taken action be reflected on company service quality, performance or at the end customer experience?  

So many views needed for management, but the real question should be, is there a solution to support frequent changes in views? In other words is there one multiple view consisting of all management views? One homogen view to support all views as one?