Creating a Business Intelligence Competency Center

Establishing a

Business Intelligence

Competency Center

Data Analytics SymposiumAugust 7 – 8, 2013 • Baltimore, Maryland

Data Analytics SymposiumAugust 7-8, 2013

What is a BICC

• Sits in the middle of IT, analysis, and business users

• Collects all the functions of a business intelligence

program into a single team

• Creates an environment for analysts and technology

managers to learn from each other

• Designs the blueprint for BI infrastructure

• Controls the methodology and standards

© 2013 Tommy Tavenner


What is a BICC?



Primary functions a BICC

• Defines the vision for BI

• Designs the blueprint for BI infrastructure

• Controls the methodology and standards

• Manages training and professional development of BI

staff.



What does a BICC look like?

COO

Team 1 Team 2 Team 3

BICC

CIO

Department BICC Department

BICC

Fundraising Web/E-mail Direct Mail/Annual Giving

Fundraising Web/E-mail Direct Mail/Annual Giving



Why choose the BICC model?

• Puts control over the infrastructure in the hands of the

analysts

• Creates a learning environment for different types

analysis

• Leads to a more holistic picture of the organization

• Makes the organization more nimble



Where we started

• Different analysts on each major team

> Development – one part-time analyst for all activities

> Membership – budget and campaign analysts

> Advocacy – primarily e-mail analyst

> Web/E-mail – a different e-mail and web analyst

> Catalog – one part time analyst

> Publications – borrowed analytical support from catalog and

membership

• None really communicated with the others or

understood the other departments



Where we started

• The team who managed our databases was separate

from the analysts, each department controlled their own

system.

> Development, membership, catalog, and publications each had

their own systems with limited or no integration

> Our e-mail and advocacy system only talked to our

membership database

• Basically no one communicated



What we wanted to accomplish

• To know who our constituents were

• To compare demographic profiles and trends across

different constituent types

• To understand how different mediums and programs

interacted



How we got there – Laying the ground work

• No immediate changes

• Put together a plan and make the case

• Convince the executive team

• Buy-in and feedback from key stakeholders



How we got there – Forming the team

• Initially everyone stayed in their location

• Held a simple getting-to-know-you retreat

• Started a team meeting



How we got there – Shifting mindsets

• Began talking with clients as a team

• Shifted the request process to a centralized system

• Created more team, cross-function projects



How we got there – Shifting priorities

• Started looking at the broader data eco-system

• Set business intelligence priorities for the organization

as a whole

• Plan for long-term infrastructure needs



How we got there – Shifting roles

• Assign projects based on functional abilities rather than

department

• Departments no longer think of employees as ‘their’

analyst.

• Build relationships across departments and teams.



Team Structure

Constituent Systems

Development Web/E-mailDirect Mail/Annual Giving

Advocacy



Team Structure

BICC


Advocacy



Team Structure

BICC


Advocacy

Catalog Publications


Creating a Business Intelligence Competency Center

Data & Analytics

Transcript of Creating a Business Intelligence Competency Center