{"id":11961,"date":"2008-12-14T21:00:51","date_gmt":"2008-12-14T20:00:51","guid":{"rendered":"http:\/\/192.220.58.236\/blog\/?p=114"},"modified":"2008-12-14T21:00:51","modified_gmt":"2008-12-14T20:00:51","slug":"what_might_go_wrong_in_busines","status":"publish","type":"post","link":"https:\/\/timoelliott.com\/blog\/2008\/12\/what_might_go_wrong_in_busines.html","title":{"rendered":"What Might Go Wrong in Business Intelligence in 2009?"},"content":{"rendered":"<\/p>\n<p>Faced with the current tough economic conditions, can we predict how organizations might react? <\/p>\n<h4>(1) People will try to do without BI &#8212; and fail<\/h4>\n<p>BI is important, but rarely urgent. In dire economic conditions, some organizations will be too busy trying to survive to think about doing analysis. But action without analysis is called guessing, and is unlikely to help. <\/p>\n<h4>(2) People will revert to hand-coding and excel macros &#8212; and waste a lot of money<\/h4>\n<p>Corporate cutbacks, &quot;thou shalt not buy anything&quot; policies, and new levels of sign-off will encourage some people to attempt to do analysis without extra software investment: hand-coded data extraction in SQL, data manipulation using Excel macros, etc.&#160; <\/p>\n<p>Over time, the work involved in developing and maintaining these solutions will cost much more than purchased packages. The scripts won&#8217;t include any comments. The people responsible will leave the company exactly 4.3 months later. Nobody else will be able to figure out how it works. The project will limp forward for another 7.7 months, and then vendors will be invited in to do prototypes which will reveal that the scripts are faulty and the company has been basing their decisions on incorrect data for the last year. This will be covered up. <\/p>\n<h4>(3) Organizations will implement standards &#8212; but omit to change organizational structures<\/h4>\n<p>Keen to reduce costs, organizations will standardize their BI environments &#8212; but will balk at the perceived cost of implementing a dedicated central BI organization. The result will be lower procurement costs, but without a BI competency center there will still be silo BI projects. This will result in continued needless duplication, BI skill shortages, multiple definitions of&#168;&quot;profit&quot;, &quot;headcount&quot;, etc. Savings will be a fraction of what they might have been, with no improvement in overall view of information across the organization.<\/p>\n<h4>(4) Business units will find it easier than ever to implement their own solutions &#8212; to the detriment of the company as a whole<\/h4>\n<p>Chafing against corporate BI standards that they didn&#8217;t chose, business units will find it easier to ever to implement their own &quot;shadow&quot; BI systems. Lacking any incentive to plan how their system fits in with the others, the result will be more silo BI systems, making it harder than ever to get a &quot;single version of the truth&quot; across the organization. <\/p>\n<h4>The answer? Step one: BI organization<\/h4>\n<p>What can organizations do about this? Now more than ever is the time to implement BI shared services or a BI competency center. Create one by bringing together all the resources that are currently being wasted collecting and analyzing information separately in each department. The first goal of the team should be to prioritize BI projects and consolidate existing projects and solutions, eliminating waste and increasing information flow. Managed correctly, the group will more than pay for itself. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>In 2009, people will be tempted to hand-code scripts for analysis, implement standards without changing organization structures, and implement new business unit silos.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[2],"tags":[160,204,1013],"class_list":["post-11961","post","type-post","status-publish","format-standard","hentry","category-best-practice","tag-bi","tag-business-intelligence","tag-standardization"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3X9RF-36V","_links":{"self":[{"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/posts\/11961","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/comments?post=11961"}],"version-history":[{"count":0,"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/posts\/11961\/revisions"}],"wp:attachment":[{"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/media?parent=11961"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/categories?post=11961"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/timoelliott.com\/blog\/wp-json\/wp\/v2\/tags?post=11961"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}