Establishing a Business Intelligence Competency Center (BICC)

Below is the continuation of the transcript of a Webinar hosted by InetSoft on the topic of Business Analytics and Competitive Advantage. The presenter is Mark Flaherty, Chief Marketing Officer at InetSoft.

BICC as an IT Department

So, one, we can see that there is the BICC as an IT department. It is its own group. It’s staffed with its own people, and it reports up to the CIO. There are advantages and disadvantages depending on your organization to that. A Business Intelligence Competency Center (BICC) within an IT department can offer numerous advantages to an organization. Firstly, having a dedicated BICC can enhance data governance and management. By centralizing the responsibility for gathering, analyzing, and disseminating business intelligence (BI) insights, the BICC ensures consistency and accuracy in data usage across the organization. This helps in making informed decisions based on reliable data, thereby improving overall business performance. Additionally, the BICC fosters collaboration between IT professionals, data analysts, and business stakeholders, facilitating a holistic approach to BI initiatives.

A BICC can promote innovation and agility within the organization. By staying abreast of emerging technologies and industry trends, the BICC can recommend and implement advanced BI tools and methodologies to drive competitive advantage. This proactive approach enables the organization to adapt quickly to changing market dynamics and customer preferences, thereby staying ahead of the curve. Furthermore, the BICC serves as a knowledge hub where best practices and lessons learned from BI projects are documented and shared, fostering a culture of continuous improvement and innovation.

There are also some disadvantages associated with having a BICC as part of the IT department. One potential drawback is the risk of siloed thinking and departmental conflicts. If the BICC becomes too entrenched within the IT department, there may be a tendency to prioritize technical considerations over business needs. This can lead to a disconnect between BI initiatives and strategic objectives, hindering the organization's ability to derive meaningful insights from its data. Additionally, the IT-centric focus of the BICC may alienate business users who feel marginalized in the decision-making process, resulting in resistance to BI initiatives.

Another challenge is the potential for resource constraints and scalability issues. As BI projects become more complex and data volumes grow, the demands on the BICC's resources may exceed its capacity. This can lead to delays in project delivery, increased costs, and decreased ROI. Moreover, if the BICC lacks sufficient expertise in specialized areas such as data science or predictive analytics, the organization may struggle to fully leverage its data assets for strategic advantage. Therefore, it's essential for the BICC to strike a balance between technical proficiency and business acumen to effectively meet the organization's BI needs.

The Virtual BICC

Another one is a virtual BICC. This is where you have a representative within each business unit or in each line of business that is responsible for some business intelligence function that makes up a virtual team within an organization. Or we could have BICC as its own operations group because it tends to go across business operations as well as IT, so sometimes it makes more sense to have it there.

Or the last model is a distributed model with the BICC established within corporate, and then they have distribution throughout each of the divisions. And again, each of these models have their pluses and minuses or positives and negatives. One thing I will say is if you are fairly mature and have a need across the enterprise to establish your BI visibility and sharing of information, the virtual BICCs are sometimes a challenge because you have someone, a resource that is devoting some percentage of their time to this, and it’s difficult to get the focus that you need to really get that push across the enterprise. But again, if you are at a lower maturity level, this might be a perfect thing for you if you don’t have the funding to establish a separate BICC.

When organizations begin evaluating these different BICC models, it is important to anchor the discussion in their current analytics maturity and political realities. A company with fragmented reporting, multiple overlapping tools, and no clear data ownership will often benefit from a more centralized BICC at the outset, simply to create order and standards. In contrast, an organization that already has strong analytics capabilities embedded in several business units may find a hybrid or distributed BICC more effective, because it can formalize what is already working while adding governance and shared services. The key is to avoid copying a model from another company without first mapping it to your own culture, decision-making style, and strategic priorities.

Another critical success factor for any BICC model is the definition of roles and responsibilities. Beyond the executive sponsor, you need clear ownership for data governance, BI platform administration, solution architecture, and business-facing analytics enablement. If these responsibilities are vague or scattered, the BICC will quickly become a bottleneck or a political battleground. By documenting a RACI (Responsible, Accountable, Consulted, Informed) matrix for major BI activities—such as data model changes, dashboard publication, or access approvals—you create transparency and reduce friction. This clarity also helps business users understand where to go for support and what they can safely do on a self-service basis.

Training and change management are often underestimated components of a successful BICC. Even the most elegant data models and visualization tools will fail to deliver value if users are not confident in how to use them or skeptical of the data. A mature BICC invests in ongoing education programs: introductory workshops for new users, advanced sessions for power users, and role-based training for managers who need to interpret metrics for decision-making. In addition, the BICC should communicate frequently about new capabilities, retired reports, and changes to key performance indicators, so that the organization does not revert to spreadsheets and shadow systems when something changes.

Measuring BICC Performance

It is also helpful to think of the BICC as a service provider with a portfolio of offerings rather than a purely internal committee. Typical services might include rapid prototyping of dashboards, data quality remediation, advisory support for business-unit analytics projects, and stewardship of enterprise KPIs. By defining these services and associated service levels, the BICC can set expectations and measure its own performance. For example, you might track average turnaround time for new dashboard requests, the percentage of issues resolved within a defined window, or user satisfaction scores from periodic surveys. These metrics give the BICC tangible evidence of its impact and help justify continued investment.

Finally, a high-performing BICC does not remain static; it evolves as the organization’s strategy and technology landscape change. Early on, the focus may be on consolidating reports and standardizing definitions. Over time, the emphasis might shift toward advanced analytics, embedded BI within operational applications, or external data sources such as market benchmarks and IoT streams. Regularly revisiting the BICC charter, governance model, and technology roadmap ensures that the competency center remains aligned with business goals rather than becoming an isolated technical function. In this way, the BICC becomes a catalyst for continuous improvement in how the organization uses data to compete, innovate, and serve its customers.