16.01.2016 Views

Tips for Building a Data Science Capability

WH4vS

WH4vS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

INTRODUCTION<br />

Many organizations believe in the power and potential of data science<br />

but are challenged in establishing a sustainable data science capability.<br />

How do organizations embed data science across their enterprise so<br />

that it can deliver the next level of organizational per<strong>for</strong>mance and return<br />

on investment?<br />

<strong>Building</strong> a data science capability in any organization isn’t easy—there’s<br />

a lot to learn, with roadblocks and pitfalls at every turn. But it can be<br />

done—and done right. This booklet will show you how. We’ve filled it with<br />

the most valuable best practices and lessons we’ve learned—both in our<br />

pioneering work with clients, and in building our own, 500-member data<br />

science team, one of the world’s largest.<br />

In these pages, you’ll discover:<br />

+ + Why your data science investment may not<br />

have delivered on its promise so far. It could<br />

be that you haven’t developed an analyticsdriven<br />

culture.<br />

+ + How to keep from getting bogged down.<br />

Some organizations have difficulty prioritizing<br />

their data science projects. Others face skepticism<br />

from leadership. Here’s how to overcome<br />

the most common roadblocks.<br />

+ + How to get buy-in <strong>for</strong> data science throughout<br />

the entire organization. We show you how to<br />

overcome resistance to everything from using<br />

analytics to sharing in<strong>for</strong>mation.<br />

+ + Where to place your data science teams in your<br />

organization. Should they be centralized?<br />

Dispersed? Permanently embedded in individual<br />

business units? Each option has its advantages<br />

and risks.<br />

+ + How to stand up the position of Chief <strong>Data</strong><br />

Officer (CDO). We tell you why a CDO needs<br />

to be one part “en<strong>for</strong>cer” and two parts<br />

“data evangelist.”<br />

+ + How you can leverage our <strong>Data</strong> <strong>Science</strong> Talent<br />

Management Model. We’ll help you answer three<br />

key questions: Who do you need? Where do you<br />

need them? How do you keep them?<br />

+ + Why design thinking-when applied to data<br />

science-can unlock organizational value.<br />

How the designer’s mindset can ground and<br />

amplify analytic insights.<br />

Introduction | v

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!