Building An Effective Analytics Organization PDF
Building An Effective Analytics Organization PDF
Special Edition on
Advanced Analytics in Banking
4 13 20
28 36 44
Using data to unlock the Hidden figures: The quiet Using analytics to increase
potential of an SME and discipline of managing satisfaction, efficiency, and
mid-corporate franchise people using data revenue in customer service
52 60 68
80 86
Gloria Macias-Lizaso In working with a wide range of organiza- pertise, beyond specific sector expertise, will
tions, McKinsey has seen many companies become more and more relevant.
start their analytics journey eagerly, but
With this in mind, McKinsey conducted an
without a clear strategy. As a result, their
extensive, primary research survey of over
efforts often end up as small pilots that fail
1,000 organizations across industries and
to scale or have significant impact. Some
geographies to understand how organizations
of these pilots have been mere exercises in
convert AA insights into impact, and how
“intellectual curiosity” rather than a serious
companies have been able to scale analytics
effort to change the business. Consequently,
across their enterprise (see sidebar on page
they are not designed with an end-to-end
61). In this article, we will discuss how to
approach that incorporates the necessary
design, implement, and develop the right or-
conditions for implementation. Instead, the
ganization and talent for an AA transforma-
pilots are carried out in small labs with lim-
tion. An AA transformation usually requires
ited connection to the business, and fail to
new skills, new roles, and new organizational
provide the answers the business needs to
structures.
move forward. Even if a pilot does answer the
right questions, it may not address the cul- Building an AA-driven organization
tural aspects that would, for example, make a Top-performing organizations in AA are en-
sales representative trust a model more than abled by deep functional expertise, strategic
her own experience. partnerships, and a clear center of gravity for
organizing analytics talent. These companies’
These companies quickly become frustrated
organizations usually include an ecosystem
when they see their efforts falling short while
of partners that enables access to data and
more analytically driven companies are le-
technology and fosters the co-development of
veraging their data. Democratization of data
analytics capabilities, as well as the breadth
is blurring sector boundaries; businesses will
and depth of talent required for a robust pro-
increasingly find themselves disrupted not
gram of AA.
by the company they have been monitoring
for the last several years, but by a newcomer For a company aspiring to an AA transforma-
from another industry. Being the best in an tion, these elements can be incorporated into
industry is no longer enough; now companies any of several organizational models, each of
must aspire to be at least at par across indus- which is effective as long as there is clear gov-
tries to compete effectively. Functional ex- ernance, and the company encourages an an-
alytical culture across business units to learn work effectively, as long as governance is
and develop together. Answering a few key established to prevent the various units
questions can help to identify the best model. from becoming islands. The proposed or-
ganization depends somewhat on how ad-
1. Centralized, decentralized, or a hybrid:
vanced the company and the business units
First, the company should decide whether
are in their use of analytics.
to create one centralized AA organization,
in which AA stands alone in a center of ex- It is important to note that any organiza-
cellence (COE) that supports the various tion will change over time as the AA trans-
business units; a decentralized organiza- formation evolves. Some companies start
tion, in which analytics is embedded in out decentralized and eventually move AA
individual businesses; or a hybrid, which into a centralized function, while others
combines a centralized analytics unit with that are centralized later move into a hy-
embedded analytics areas in some units. brid model of hubs and spokes. Top-per-
forming companies prepare for these
Our benchmark of several organizations
eventual changes.
indicates that any of these models can
The choice between centralization and tegic partnership with an external vendor
decentralization is not an all-or-noth- be the best approach? AA will effectively
ing decision but should be decided per become the “brain” of the organization,
sub-function. Data governance, how- so companies should be careful not to
ever, should be centralized, even if data outsource too much. Top-performing com-
ownership is not. For data architecture, panies often keep analytics that provide a
top-performing companies often have competitive advantage—such as pricing an-
data centralized within business units. alytics—within the organization. A central,
This data typically includes data from internal unit can oversee all AA outsourc-
marketing, sales, operations, and so on. ing, and partnerships can be established
Most top-performing companies centralize for specific AA solutions or to bring in
partnership management; otherwise, com- particular assets, such as unique sources of
peting or redundant partnerships could data or advanced solutions.
inadvertently be set up in various parts of
3. Locating the AA unit: Yet another import-
the organization, and intellectual property
ant decision is where to locate the AA unit.
could be at risk.
AA is most effective when it is cross-func-
2. To outsource or not to outsource: An- tional, accessible enterprise-wide, and inte-
other decision is whether AA talent should grated with the business. Various levels and
be partially outsourced, and if so, how. functions can host it, but the final location
Should outsourcing be limited to low-level should have enough visibility and access to
data analytics activities? Or should the the C-suite to break through inertia and en-
company establish several tactical partner- able transformation. It is helpful if the unit
ships for selected tasks? Or would a stra- has an enterprise-wide view, given its trans-
Exhibit 1
Developers
Data
acquisition
managers
2. Over- and under-thinking technology. Some companies attempt to replicate an entire data history when building
their AA COE, resulting in data “scope creep.” It is vital to sufficiently think through data integrity/architecture; failing
to do so may result in missing data and missing data connections. Some companies try to do too much at once by
replacing their hardware, software, and analytics stack simultaneously rather than tackling one at a time. These com-
panies may buy the “best of breed” in each category but then find that none of them “talks” to each other. Instead,
companies should build systems and functionality as needed—especially since technologies tend to become obso-
lete within just a couple of years. New innovations can be integrated later if the system is built gradually.
3. Taking more than 18 months to deliver value. The COE’s benefits should begin to come online well before the
entire roll-out is complete. If the COE does not deliver benefits sooner, it is often because it depends too heavily on
insights-delivery FTEs instead of automation. The delivery of insights should be staged to capture value sooner.
4. Insufficient skill-building and change management. Top management and the internal team must be 100 percent
committed to the COE if it is to succeed. Internal stakeholders must be engaged in development or accountable for
delivery. The effort cannot focus exclusively on technology instead of the process and people; in particular, the or-
ganization must build the requisite front-line skills needed for an effective AA COE. Companies should hew closely to
the business case and avoid the functional scope creep that can occur when mid-flight changes not included in the
business case suddenly become priorities.
5. Operating analytics as an island. One large US insurance company interviewed by McKinsey hired a sizeable num-
ber of data scientists and launched more than 50 pilot projects to test its new capabilities. Despite a real commitment
and considerable investment, the analytics team was isolated from the rest of the company, with no connection to
the overall business strategy—a critical mistake. Not surprisingly, this company’s ad hoc analytics projects had no
real impact.
At the other end of the spectrum, successful AA-driven companies are building centralized AA capabilities and then
creating end-to-end agile teams (“use case factories”) that integrate profiles from IT, sales, marketing, finance, and
other functions. This approach ensures that use cases are immediately integrated into business processes and thus
create value.
and capabilities within the COE (Exhibit 1), the COE and business units. The translators
including data scientists (“quants”), data usually have a combination of business, an-
engineers, workflow integrators, data archi- alytics, and technology skills and are found
tects, delivery managers, visualization ana- in the business partner role in data analytics
lysts, and, most critically, translators from leadership.
the business who act as a bridge between
Exhibit 2
Board
Top team
Analytics COE BU 1 BU 2
Data Data
Design
science engineering
• The data scientist works with the translator to develop an analytics use case, including an algorithm and analyses to test.
• A data engineer from the COE works with the relevant business division to understand the data requirements of the
use case and to identify data sources.
• The data engineer works with IT/the business to ensure data availability, identify gaps, and develop ETL (extract, trans-
form, load) to load data into analytics sandbox.
• A data scientist programs the algorithm and analyzes the data in the sandbox to generate insights.
• A COE workflow integrator works with the business owner to develop a prototype for models and tools.
• The COE ensures that key business and IT stakeholders test the prototype tools and solutions.
• A delivery manager pilots the prototype and dashboard and works to obtain a go/no-go decision.
• The delivery manager and COE workflow integrator work with IT to scale the prototype to the enterprise level.
• The COE delivery team and translator work with the business and IT to ensure adoption and ongoing model maintenance.
In this process, feedback would be gathered between steps nine and ten.
While the COE and some of its roles may In McKinsey’s survey, 58 percent of respon-
emerge gradually, it is best to have the data, dents at top-performing companies say that
platform, and career paths needed for an AA their organization has deep functional ex-
transformation in place from the beginning. pertise across data science, data engineering,
If the platform is still under development, data architecture, and analytics transforma-
adding more people may only make that de- tion. Top-performing organizations have four
velopment more complicated. And without times as many analytics professionals and
a clear career path, attracting this scarce one and a half times more functional experts
talent will be difficult. As much as possible, than other companies.
roles should be clearly delineated to prevent
These companies also retain three times
squandering valuable talent on functions for
more talent—primarily by creating strong ca-
which they are over-qualified, which can un-
reer development opportunities. People with
dermine retention.
superior analytics talent usually have many
Career development and strategic potential opportunities and thus need to
partnerships see a clear career path and opportunities for
Gaining an edge in analytics requires attract- growth within a company if they are to join or
ing, retaining, and sourcing the right talent. stay with it. Several career tracks should be