OCT 18, 2011 7:48am ET

Related Links

Business Analytics Services Spending to Reach $89.6 billion in 2018
September 15, 2014
Artificial Intelligence Meets the C-suite
September 15, 2014
Mayo Clinic to Use Watson to Bolster Trial Enrollments
September 11, 2014

Web Seminars

Essential Guide to Using Data Virtualization for Big Data Analytics
September 24, 2014
Integrating Relational Database Data with NoSQL Database Data
October 23, 2014

The Secrets to Managing Business Analytics Projects

Print
Reprints
Email

Last week I reported on the first of two analytics-intriguing articles from the Fall 2011 Issue of the MIT Sloan Management Review. “Creating Business Value with Analytics” presents survey research findings that articulate factors distinguishing companies transforming the way they do business with analytics.

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to information-management.com including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?

Advertisement

Comments (1)
An excellent article. I think it is important to say one of the issues skirted here is the oft-overlooked bias frequently encountered of both I/T and business teams being uncomfortable with the required iterative (experimental) approach. To succeed, both project planning/management and stakeholders have to understand, be comfortable with, and support the notion of iterative cycles. Often I have seen the lack of stated support along this avenue be one of the largest threats to success in analytic projects. I'm inclined to believe there must be specific discussion around this topic to ensure all stakeholders understand the iterative cycle is a standard part of the process - much like a Deming quality cycle - not an admission of failure in the prior iteration.
Posted by Gary B | Saturday, October 29 2011 at 10:59AM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.