One of the more troubling DW/BI maladies is the business acceptance disorder. In layperson's terms, the business community isn't using the DW/BI environment — it's just not a critical component of the business decision-making process. Frankly, this is a frightening diagnosis for project teams. It's impossible to declare DW/BI success if no one in the business has embraced the results of your hard work and best intentions.The article focuses on alignment between business requirements and technical solution, and gives a lot of very basic advice about getting feedback from users: find out what they think.
Nothing wrong with his advice of course; I guess most IT professionals know this stuff (although they may not always practise it consistently).
But feedback of this kind suggests a first order learning process: the business community has some decision-making practices, and the target for DW/BI solutions is to support these practices more effectively. The feedback recommended by Bob enables the IT requirements to be refined and extended, but don't directly address the decision-making practices and their organizational context.
Decision-making is an important aspect of management activity. It is has an economic value that depends on several variables, including significance, scope, complexity, uncertainty and time-horizon (higher paid managers typically engaging with higher-value decisions.) Many decisions are taken collaboratively, involving complex social interaction between decision-makers.
If you want a business organization to accept and assimilate meaningful changes in the DW/BI platform, you have to think about meaningful changes in the organization itself. Roles and responsibilities may have to be realigned. Managers need to learn new capabilities – not just learning to operate the DW/BI systems, but learning to ask more complex questions, interpreting the answers, and integrating this into how they run the business. In general, IT systems may be used to produce a range of effects on the business organization (for example, affecting the visibility of some business processes, or altering the communication/delegation between different locations). But of course these effects are produced not by IT systems alone, but by the socio-technical systems into which IT is embedded. It's the people.
IT practitioners often see people first as a source of requirements, then as a source of resistance. "We gave them what they asked for, dammit, now let's force them to use it."
Business acceptance is all about making effective and appropriate changes to these socio-technical systems. (This means users experimenting, adopting and learning, not being coerced.) Designing the technical pieces may be important, but what is more important is giving the users good opportunities to discover better ways of doing their jobs. Thereby enabling the organization to deploy the intelligence of the people together with the intelligence of the tools, to achieve measurable improvements in organizational intelligence. This is a change management challenge that goes way beyond simple feedback.