August 4, 2016
Feature Story
Data: Innovation’s Gateway
Kellee M. Franklin
Strategic Innovation Executive

Data is reshaping how decisions are being made in business. Consumers have access to data in ways like never before, equipping them with knowledge to make more informed decisions. Harnessed well, data can be a powerful tool for change and innovation within enterprises.

Yet data can also be a tricky business. Consider Gallup, which for decades conducted the gold standard of presidential election polls. In 2012 the polster pulled out of future presidential primaries after their predictions differed significantly from those of their competitors. Rather than predicting presidential preferences, Gallup decided to spend time and money examining its data analytics methods.

What makes the business of data so tricky? Quite simply: people. We often fail to recognize that in most cases data is fundamentally about human behavior. Whether we are talking about Arivale’s app for personalized wellness, Apptio’s software solutions to improve CIO investment decision making, or Fjord’s design for simplifying Ontario’s public transit system, data is collected from multiple channels and used to enhance the customer experience.

As quickly as we are gathering data about our customers, they are simultaneously learning about new technologies, solutions, and cutting-edge ideas and are invariably shifting their behaviors. By the time we develop and roll out products, our customers’ needs and interests may have changed dramatically. After all, they now have access to countless resources for market and competitor data formerly available only to companies through LexisNexis and other subscription-based research engines.

As data and information have become more publicly accessible and available, companies are perpetually challenged with these interrelated questions:

• What business problem are we trying to solve?

• What data do we need to solve the problem?

• What methods should we use to collect that data?

• How do we use the data to design innovation?

Three Dangerous Assumptions

There are three assumptions we tend to make that can doom even our most elegant analyses to failure.

First, we assume that we already know what our customers need and want. In our quest to push products out to consumers, this can cause us to ignore business intelligence, consumer insights, and data analytics. Sadly, we often build expensive and sophisticated technologies without really knowing what business problem we are trying to solve. This is why it is critical to take the time to apply techniques found more commonly in human-centered design, such as learning about and uncovering insights into people’s needs. Taking an open and generative approach will help us more accurately define the problem and expand the number of options for solving that problem.

Second, we may jump to the conclusion that the “hard” data alone will yield all the information we need. There is no question that data is a magnificent way to learn about human behavior and to design more customer-friendly products, experiences, and processes. Nonetheless, hard data needs to be augmented with “soft” data.

Many times I have collected data through traditional data analytics methods and have followed up with participants using more personalized, interactive methods (e.g., face-to-face interviews, focus groups, and field research). In all cases these methods rewarded me with new customer insights. Multiple technology touchpoints may generate an abundance of consumer data and behavior indicators, but this information doesn’t always help us understand the true nuances that make up the human experience. We also need to factor more personalized, human interaction into our analysis of the hard data.

Third, we tend to assume that, once we’ve gone to all the effort to gather and analyze the data about our customers’ needs and wants, we’re done. Human behavior, however, changes often. When we collect data, we are really only viewing a snapshot of a living, breathing, and evolving human system. That snapshot has a short shelf life. Even with repeat engagements with the same customer or client system, we need to recognize that it’s not the same customer or client system we encountered the last time, so we have to factor that into our approach.

We also need to consider how the process of gathering data can affect the information yielded by its analysis. The way we collect information alters the experiences of the people whose ideas and behavior we are studying and subsequently alters the type of information they are willing to give us. Data collection itself is an organizational intervention. With any intervention we inevitably and unavoidably disrupt routine operations, which can cause unintentional stress. Therefore we must plan our data collection strategies carefully so that we can design for the problem we need to solve and accommodate our unique customer or client systems, taking into account how the data collection process itself might affect the results.

Facilitating Real and Meaningful Change with Data

Data is certainly necessary but insufficient on its own. You can’t transform an organization or industry without people—and people require engagement and access to data to make them feel comfortable with change. Over the past few years, more emphasis has been placed on employee, customer, and client engagement for change—and data can play a significant role in this arena.

For instance, the mere act of collecting data from employees, customers, and other populations is inviting engagement. In essence we are asking for participation from those who will both cause and be affected by the change and design process. When we design our collection methods in ways that are safe and welcoming to participants, we have already started to plant the seeds of transformation and have increased the likelihood of buy-in to the new product, tool, technology, or process.

Even so, engagement alone does not make for change. If we want to empower people to make informed choices based on our data and information, we must present it in ways that make it accessible to them, such as data visualizations. Chris Argyris, a renowned Harvard professor and scholar of organization theory, identified three key ingredients necessary for lasting change: (1) valid and useful information, (2) internal commitment, and (3) free and informed choice. Argyris believed valid and useful information is critical to promoting change.*

Apply these concepts to the process of buying a new car. What type of information do you research and from what sources? How do you validate this information? As you collect information about various cars, you probably have more questions and gather additional data until you are satisfied you have all the information to select the best car for your needs.

The same is true with change and innovation. Because humans are a meaning-making species (i.e., attribute meaning to their experiences), they crave data and information. Data can help individuals shift their mindset from an old way of thinking to a new one and change their behavior. For instance, think about the emergence of personalized medicine. As we learn more about what affects our wellness (e.g., data and information), we improve our ability to make better life choices about diet and exercise (e.g., behavior change). Data elevates our sense of security and increases our willingness to learn new things and adopt healthier habits.

* Chris Argyris, Intervention Theory and Method: A Behavioral Science View (Reading, MA: Addison-Wesley, 1970).

Summary

Finally, there’s no “one size fits all” data collection method, which is easy to forget and sometimes hard to accept. No customer or client system is the same; even one that you studied yesterday will not be the same tomorrow. We can certainly learn from our experiences and carry those lessons over to subsequent efforts, but we still have to be rigorous in selecting the right methods for each effort and in tailoring our data collection to each unique case.

Viewed through Argyris’s seminal theory, data really does serve as the gateway to innovation. As you think about ways to benefit from data, keep these core principles in mind:

• Data can be a powerful tool for change and innovation

• Gathering and using data can be tricky because as human behavior changes, so does data

• People require engagement and access to data

• Data collection strategies must be chosen wisely

Kellee M. Franklin is passionate about big ideas and disrupting the status quo. Her consultng practice has helped numerous clients across industries dream more, think differently, drive change, and produce better business outcomes through the integration of business intelligence, data analytics, and visualization. After a battle with breast cancer in 2013, Kellee has become a recognized advocate for health systems innovation, patient-centered engagement, and precision medicine. In May 2016 she joined the advisory panel at the Cambia Grove, Seattle's healthcare innovation hub. A sought-after public speaker, Kellee has served as a member of a TEDx salon speaker selection committee and has been a scholarship recipient to the Wisdom 2.0 conferences for her entrepreneurial work in mindful business. She holds a Ph.D. in human development with an emphasis in organization behavior from Virginia Polytechnic Institute and State University.

TDWI Onsite Education: Let TDWI Onsite Education partner with you on your analytics journey. TDWI Onsite helps you develop the skills to build the right foundation with the essentials that are fundamental to BI success. We bring the training directly to you—our instructors travel to your location and train your team. Explore the listing of TDWI Onsite courses and start building your foundation today.

 
Announcements
NEW Best Practices Report
Improving Data Preparation for Business Analytics
NEW Checklist Report
Seven Best Practices for Streaming Analytics for Real-Time Action
NEW Ten Mistakes to Avoid
In NoSQL
NEW Business Intelligence Journal
Business Intelligence Journal, Vol. 21, No. 2
NEW TDWI E-Book
Why Your Next Data Warehouse Should Be in the Cloud
NEW Checklist Report
Assuring the Quality of Operational Data
contents
Feature
Data: Innovation's Gateway

Lessons Learned as a Tester in an Agile Scrum DW/BI Environment
Feature
Embedding Analytics: Delivery Options

Mistake: Telling a One-Size-Fits-All Story
Education & Events
Seminar in Washington, DC Business Intelligence Fundamentals // Data Quality and Governance
Embassy Suites – Crystal City National Airport
September 19–22
Seminar in Minneapolis
Data Mining and Predictive Analytics

Marriott Minneapolis West
September 26–29
TDWI Conference in
San Diego

Manchester Grand Hyatt
October 2–7
Webinars
TODAY! – 9:00 a.m. PT
Faster BI for the Masses:
How Search Can Make Analytics More Accessible

Thursday, August 4
Data Warehouse Modernization and Analytics for the Digital Enterprise
Thursday, September 1
10 Best Practices for Running Your Business Smarter with Advanced Analytics
Wednesday, September 7
Marketplace
TDWI Solutions Gateway
Informatica – Data Management for Next-Generation Analytics
TDWI White Paper Library
Business Intelligence in the Cloud White Paper
TDWI White Paper Library
3 Steps to Becoming a
Data-Driven Organization

Premium Member Discounts

Ready to take the CBIP Exams or attend our next conference? Take advantage of these exclusive member discounts.

$275

Discount

on TDWI San Diego

$10

Discount

on CBIP Exam Guide

Flashpoint Insight
Lessons Learned as a Tester in an Agile Scrum DW/BI Environment

Many enterprises see data warehouse/business intelligence (DW/BI) solutions as primary strategic assets because they support the data-driven decision-making process.

Failure to properly test a DW/BI solution will certainly result in below optimal decision making and a consequent negative impact on the bottom line. A DW/BI solution will be as valuable as the quality of the data it holds and its value will decrease as the number of critical defects increases.

Agile development methodologies such as scrum are becoming more popular mainly because they bring a completely new mindset to the whole development process, which can certainly be put to good use when testing DW/BI systems.

Agile DW/BI development should also be seen as a process that can improve quality assurance. Even though common testing methodologies also apply to DW/BI solutions, it is important for teams to understand that testing a DW/BI system heavily relies on planning, designing, and executing tests with particular emphasis on data, performance, and volume.

More than ever before, quality must be treated as a topic of high priority in the DW/BI world. Despite this, my own experience indicates that quality assurance and testing are still in their infancy in this context and finding people with the right mindset and skills is turning out to be an increasingly complex task.

Learn more: Read the entire article by downloading the Business Intelligence Journal (Vol. 21, No. 2).

 
TDWI Research SNapshot
Embedding Analytics: Delivery Options

There are multiple ways to deliver on embedded analytics. These run the gamut from dashboards to devices to databases to embedding analytics in real-time systems and applications.

Dashboards rule. By far, dashboards are the most likely place that organizations are planning to embed or operationalize analytics. Fifty-four percent of respondents are using dashboards for strategy and planning (72% among the active group, not shown). Another 38% are expecting to deploy them in the next three years. Forty-five percent are utilizing operational dashboards today and another 42% expect to use them over the next three years (see Figure 1). The results indicate that many of these are traditional, static report-based dashboards that are financial or executive focused (not shown). However, organizations are breaking the mold, too. For instance, some organizations are building interactive dashboards that include information about propensity to buy or cross-sell for sales. Additional organizations are using dashboards for help in field support and for use by other support organizations to understand and interact with their metrics and sound alerts when there are problems. Still others have built simulations into their dashboards for users to do what-if kinds of analyses.

(Click for larger image)
Click to view larger

Organizations are embedding analytics into applications. Of course, analytics are often embedded in applications. This has been a mainstay of embedded analytics. Forty-five percent of respondents are currently embedding analytics such as visualizations or reports in applications today. Another 47% expect to do so in the next three years. Lower on the list are embedding analytics into customer-facing applications; 29% of respondents are doing this today but 33% are planning to do so in the next three years. Embedding analytics into applications can provide value for users of those applications and that is reflected in these numbers.

Operationalizing is happening. When organizations operationalize analytics, they make it part of a business process. They might embed the analytics into an operational system. More frequently, analytic models are operating inside of a database to score new data as it comes into the database. For example, a data scientist might build a retention model. That retention model is then embedded into the database. As new data about a customer comes in, the customer is scored for the probability of defection. That information might be passed to others in the organization. For instance, a call center agent can use this information while on a call with the customer, as mentioned above.

In this survey, 47% of respondents claim to embed analytics into operational systems now. The same percent state that analytics is being embedded into databases. These analytics might not be predictive models; however, the responses seem to suggest, at least with this group of respondents, that organizations are attempting to systematically utilize analytics as part of their business processes. Faculty are notified about student progress; healthcare workers are notified of patients at risk of readmission; marketing produces personalized newsletters based on customer segmentation and behavior; financial institutions use it for credit scoring; and utilities are using it in preventive maintenance. The list goes on.

Embedding analytics into devices is set to grow. Although fewer than 30% of respondents are embedding analytics into devices today, this number is set to almost double in the next three years if users stick to their plans. Tablets and other mobile devices can be useful in providing analytics in a range of use cases, from logistics to the shop floor. They can bring analytics to decision makers when they are not at their desks.

Vendors are also starting to develop with a mobile-first mentality, meaning that they understand that embedding analytics into end-user applications that run on devices is important. Display is important, as are providing native mobile analytics experiences, touch-based interaction, responsive design, and using the right form factor.

Read the full report: Download TDWI Best Practices Report: Operationalizing and Embedding Analytics for Action (Q1 2016).

 
Flashpoint Rx
Mistake: Telling a One-Size-Fits-All Story

Audiences are made up of individuals and every individual is unique. When working with a small audience, try to understand the characteristics, interests, and needs of each audience member.

What is their stake in the story? How are they likely to respond to various story elements? When working with larger groups, identify and understand audience segments—subgroups based on common characteristics. Consider role-related characteristics such as level of responsibility, knowledge, and experience. Look at individual characteristics such as generation, education, and gender; other demographics; and perhaps even psychographics.

With multicultural audiences, consider how people with various cultural perspectives might react to the story. Recognize any variations of domain knowledge and contextual background that will affect how audience members engage with the story.

With geographically dispersed audiences, you’ll also need to consider implications of face-to-face versus remote storytelling, including storytelling media and the ability of the storyteller to receive audience feedback.

Use your understanding of the audience—individuals and/or segments and their similarities and differences—to decide how best to connect with all segments of the audience. Can you craft a single narrative that connects with all members of a diverse audience or will you need to tailor the narrative to specific groups? Do some audience members need more detail or less detail than others? Should the mix of verbal and visual delivery vary among audience segments? Where will presentation style of storytelling work and where will a conversational style be more effective? What is the best way to establish the all-important connection with every audience member?

Read the full issue: Download Ten Mistakes to Avoid in Data Storytelling (Q2 2016).