Expectation management pivotal to managing your BI program

We want to formalize a business intelligence (BI) program. Where do we start?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the latest BI, analytics, corporate performance management (CPM) trends and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchBusinessAnalytics.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchBusinessAnalytics.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Well, first let me offer a hearty “Congratulations! And God bless…” You’ll have to do a lot of work to establish a sustainable BI environment. But here are some dos and one don’t for starting a BI program:

1. Be sure to mention the initial business problem(s) you’ll be addressing in conjunction with announcing your BI program to the organization. Executives and business users aren’t interested in a BI program per se. They’re interested in how you’re going to help make their jobs easier and save the company money. So be ready with the answer to this question: “What’s the problem you’ll be solving with BI?” Hint: Ideally, there will be multiple answers.

2. Do a little discovery. You probably already have an idea of what the business needs from a formal, sanctioned BI effort. But you might have only heard from the so-called “squeaky wheels.” If you have the luxury of meeting with various parts of the organization and inventorying their analytics and reporting requirements, do it. Engage a consultant for help with structured questions and needs prioritization. But make it clear that you’re not just pandering to finance or marketing and that BI is an enterprise-wide set of efforts.

3. Don’t hang out your shingle too early. We’ve seen a lot of people who are setting up BI programs do big, splashy internal roadshows. One client of mine actually enlisted our help in creating a BI program logo before they’d even identified the first analytics application to be deployed. Avoid the temptation to announce the BI program in advance of being able to deliver value. When you are ready to announce it, don’t talk about vendors or platforms. And for cripes sakes, don’t let the words “BI competency center” leave your lips! (Not yet, anyway.) Instead, position BI as something that will propel the organization forward.

Notice a theme here? It’s all about expectation management. In order to get ongoing support from management and participation from users and/or IT, you’ll need to be realistic about delivery, clear about the value you’re driving and structured in your approach to getting there. Like I said, “God bless…”

This was first published in May 2010

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top