33,99 €
The intensified used of data based on analytical models to control digitalized operational business processes in an intelligent way is a game changer that continuously disrupts more and more markets. This book exemplifies this development and shows the latest tools and advances in this field Business Analytics for Managers offers real-world guidance for organizations looking to leverage their data into a competitive advantage. This new second edition covers the advances that have revolutionized the field since the first edition's release; big data and real-time digitalized decision making have become major components of any analytics strategy, and new technologies are allowing businesses to gain even more insight from the ever-increasing influx of data. New terms, theories, and technologies are explained and discussed in terms of practical benefit, and the emphasis on forward thinking over historical data describes how analytics can drive better business planning. Coverage includes data warehousing, big data, social media, security, cloud technologies, and future trends, with expert insight on the practical aspects of the current state of the field. Analytics helps businesses move forward. Extensive use of statistical and quantitative analysis alongside explanatory and predictive modeling facilitates fact-based decision making, and evolving technologies continue to streamline every step of the process. This book provides an essential update, and describes how today's tools make business analytics more valuable than ever. * Learn how Hadoop can upgrade your data processing and storage * Discover the many uses for social media data in analysis and communication * Get up to speed on the latest in cloud technologies, data security, and more * Prepare for emerging technologies and the future of business analytics Most businesses are caught in a massive, non-stop stream of data. It can become one of your most valuable assets, or a never-ending flood of missed opportunity. Technology moves fast, and keeping up with the cutting edge is crucial for wringing even more value from your data--Business Analytics for Managers brings you up to date, and shows you what analytics can do for you now.
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 441
Veröffentlichungsjahr: 2016
Wiley & SAS Business Series
Title Page
Copyright
Foreword
Introduction
What Is the Scope of Business Analytics? Information Systems— Not Technical Solutions
Purpose and Audience
Organization of Chapters
Why the Term
Business Analytics?
Chapter 1: The Business Analytics Model
Overview of the Business Analytics Model
Deployment of the Business Analytics Model
Summary
Chapter 2: Business Analytics at the Strategic Level
Link between Strategy and the Deployment of Business Analytics
Strategy and Business Analytics: Four Scenarios
Which Information Do We Prioritize?
Summary
Chapter 3: Development and Deployment of Information at the Functional Level
Case Study: A Trip to the Summerhouse
Establishing Business Processes with the Rockart Model
Example: Establishing New Business Processes with the Rockart Model
Optimizing Existing Business Processes
Example: Deploying Performance Management to Optimize Existing Processes
Which Process Should We Start With?
A Catalogue of Ideas with Key Performance Indicators for the Company's Different Functions
Summary
Chapter 4: Business Analytics at the Analytical Level
Data, Information, and Knowledge
Analyst's Role in the Business Analytics Model
Three Requirements the Analyst Must Meet
Required Competencies for the Analyst
Hypothesis-Driven Methods
Data Mining with Target Variables
Explorative Methods
Business Requirements
Summary
Chapter 5: Business Analytics at the Data Warehouse Level
Why a Data Warehouse?
Architecture and Processes in a Data Warehouse
Tips and Techniques in Data Warehousing
Summary
Chapter 6: The Company's Collection of Source Data
What Are Source Systems, and What Can They Be Used For?
Which Information Is Best to Use for Which Task?
When There Is More Than One Way to Get the Job Done
When the Quality of Source Data Fails
Summary
Chapter 7: Structuring of a Business Analytics Competency Center
What Is a Business Analytics Competency Center?
Why Set Up a Business Analytics Competency Center?
Tasks and Competencies
Centralized or Decentralized Organization
When Should a Business Analytics Competency Center Be Established?
Applying the Analytical Factory Approach
Summary
Chapter 8: Assessment and Prioritization of Business Analytics Projects
Is It a Strategic Project or Not?
When Projects Run Over Several Years
When the Uncertainty Is Too Big
Projects as Part of the Bigger Picture
Summary
Chapter 9: Business Analytics in the Future
About the Authors
Index
Wiley End User License Agreement
ii
iii
iv
vi
xi
xii
xiii
xiv
xv
xvi
xvii
xviii
xix
xx
xxi
xxii
xxiii
xxiv
1
2
3
4
5
6
7
8
9
10
11
12
13
15
17
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
35
36
37
38
39
40
41
42
43
44
45
47
49
50
51
53
54
55
56
57
58
59
60
61
62
63
65
66
69
70
71
72
73
74
75
76
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
101
102
103
105
106
107
108
109
110
111
112
113
114
115
116
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
165
166
167
168
169
171
172
173
174
175
176
177
178
179
181
182
183
184
185
186
187
188
189
190
191
192
193
194
196
197
198
199
200
201
202
203
204
205
208
209
211
212
213
214
215
216
218
219
220
221
222
223
224
225
226
227
228
229
230
232
233
234
235
236
237
239
240
241
242
243
244
246
247
248
249
250
251
252
253
254
255
257
258
259
260
261
262
263
264
Table of Contents
Begin Reading
Introduction
Exhibit I.1: The Stairway Chart: Emphasizing the Difference between Lead and Lag Information
Chapter 1: The Business Analytics Model
Exhibit 1.1: The BA Model
Exhibit 1.2: Executive Management Cockpit of Radio Station with KPIs Prior to BA Initiative
Exhibit 1.3: The Radio Station's Dashboard with KPIs after BA Initiative
Exhibit 1.4: Sketching an Information Strategy
Chapter 2: Business Analytics at the Strategic Level
Exhibit 2.1: Link between Strategy and BA
Exhibit 2.2: BA Supports Performance
Exhibit 2.3: The Relationships between Strategic Level and Functional Level
Exhibit 2.4: Feedback Processes and Learning at the Strategic Level
Exhibit 2.5: Information as a Strategic Resource
Exhibit 2.6: The Three Disciplines for Market Leadership
Chapter 3: Development and Deployment of Information at the Functional Level
Exhibit 3.1: From Overall Strategy to Information Requirements at a Functional Level
Exhibit 3.2: Example of a Performance Management Dashboard for the Trip
Exhibit 3.3: Our Base Table
Exhibit 3.4: Analytical Outcome of the Correlation between the End KPI and Start Time of Journey
Exhibit 3.5: From Departmental Objectives to the Development of a New Process
Exhibit 3.6: Level 1: Identification of Objectives
Exhibit 3.7: Level 2: Identifying an Operational Strategy
Exhibit 3.8: Level 3: Identification of Critical Success Factors
Exhibit 3.9: Level 4: Identifying Lead and Lag Information
Exhibit 3.10: Using Lead and Lag Information in Relation to the Development and Management of a Business Process
Exhibit 3.11: Optimization of Existing Processes
Exhibit 3.12: Relationship between Established Measuring Points
Exhibit 3.13: Correlation between Strategy and Operational Processes with Significant Analytical Potential
Exhibit 3.14: The “Whale” That Shows the Interrelationships between the Three Activities: Get, Increase, and Keep
Exhibit 3.15: User Types on Our Web Sites
Exhibit 3.16: Catalogue of Ideas with KPIs for the Company's Different Functions
Chapter 4: Business Analytics at the Analytical Level
Exhibit 4.1: The Analyst's Role in the Business Analysis Model
Exhibit 4.2: The Three Imperatives in Connection with Choice of Methods and Information Mapping
Exhibit 4.3: Demands to the Reporting Are Hierarchically and Internally Aligned
Exhibit 4.4: Illustration of Tests between Two Variables in Our Data Sets
Exhibit 4.5: The Three Steps of a Data Mining Process
Exhibit 4.6: History Is Used to Make Predictions about Illness in the City of Copenhagen Municipality
Exhibit 4.7: Prediction Using the Data Mining Method
Exhibit 4.8: Business Requirements for the Radio Station Case Study (Chapter 1), Visualized with a Mind Map
Chapter 5: Business Analytics at the Data Warehouse Level
Exhibit 5.1: Architecture and Processes in a Data Warehouse
Exhibit 5.2: Example of a Simple ETL Job
Exhibit 5.3: Part of ETL Job with SQL Join
Exhibit 5.4: Fact‐Based Transactions Surrounded by Multidimensional Perspectives
Exhibit 5.5: The Metadata Repository
Exhibit 5.6: A Book Seller's Sales Table
Exhibit 5.7: A Book Shop's Revenue
Exhibit 5.8: OLAP Cube with Sales Figures and Three Dimensions or Perspectives
Exhibit 5.9: Business Performance Dashboard for KPI Monitoring
Exhibit 5.10: An Example of Forecasting with SAS/ETS Software
Exhibit 5.11: Screenshot of SAS Text Miner
Exhibit 5.12: Data Mining Software Identifying Market Basket Profiles
Exhibit 5.13: The BA Analyst's Various Accesses to the Data Warehouse
Chapter 6: The Company's Collection of Source Data
Exhibit 6.1: Model for the Prioritization of Data Sources in Connection with Specific BA Projects
Exhibit 6.2: Loss of Information through Transformations
Exhibit 6.3: Synergy through the Combining of Data
Chapter 7: Structuring of a Business Analytics Competency Center
Exhibit 7.1: The Information Wheel: From Demand to Supply of Business Support
Exhibit 7.2: Interrelationships between Information Strategy, Information Architecture, and Information Technology
Exhibit 7.3: Competency Areas and Types of Tasks in a BACC
Exhibit 7.4: BACC as a Formal Organizational Unit or a Virtual Organizational Unit
Exhibit 7.5: Performance and Strategy
Chapter 8: Assessment and Prioritization of Business Analytics Projects
Exhibit 8.1: BA Project Costs Compared with Benefits
Exhibit 8.2: Return on Investment (ROI)
Exhibit 8.3: SIPOC Diagram Showing the Current Status of the Process
Exhibit 8.4: SIPOC Diagram Showing the Process We Want to Create
Exhibit 8.5: SIPOC Diagram Focusing on Costs and Benefits (years)
Exhibit 8.6: Cash Flows from the BA Initiative in the Radio Station Case Study
Exhibit 8.7: Risk Involved in the Radio Station's Case Study
Exhibit 8.8: Outline of Benefits
Exhibit 8.9: Cost/Benefit Analyses for the Business Case
Exhibit 8.10: Revolutionary and Evolutionary Maturing of Information Systems
Exhibit 8.11: Generic Maturity Model for an Information System
Exhibit 8.12: Chapter 8 Mind Map
Chapter 9: Business Analytics in the Future
Exhibit 9.1 The Information Wheel with the Individual at Its Center
The Wiley & SAS Business Series presents books that help senior‐level managers with their critical management decisions.
Titles in the Wiley & SAS Business Series include:
Agile by Design: An Implementation Guide to Analytic Lifecycle Management
by Rachel Alt‐Simmons
Analytics in a Big Data World: The Essential Guide to Data Science and its Applications
by Bart Baesens
Bank Fraud: Using Technology to Combat Losses
by Revathi Subramanian
Big Data, Big Innovation: Enabling Competitive Differentiation through Business Analytics
by Evan Stubbs
Business Analytics for Managers, Second Edition: Taking Business Intelligence Beyond Reporting
by Gert H. N. Laursen and Jesper Thorlund
Business Forecasting: Practical Problems and Solutions
edited by Michael Gilliland, Len Tashman, and Udo Sglavo
Business Intelligence Applied: Implementing an Effective Information and Communications Technology Infrastructure
by Michael Gendron
Business Intelligence and the Cloud: Strategic Implementation Guide
by Michael S. Gendron
Business Transformation: A Roadmap for Maximizing Organizational Insights
by Aiman Zeid
Data‐Driven Healthcare: How Analytics and BI are Transforming the Industry
by Laura Madsen
Delivering Business Analytics: Practical Guidelines for Best Practice
by Evan Stubbs
Demand‐Driven Forecasting: A Structured Approach to Forecasting, Second Edition
by Charles Chase
Demand‐Driven Inventory Optimization and Replenishment: Creating a More Efficient Supply Chain
by Robert A. Davis
Developing Human Capital: Using Analytics to Plan and Optimize Your Learning and Development Investments
by Gene Pease, Barbara Beresford, and Lew Walker
Economic and Business Forecasting: Analyzing and Interpreting Econometric Results
by John Silvia, Azhar Iqbal, Kaylyn Swankoski, Sarah Watt, and Sam Bullard
Financial Institution Advantage and the Optimization of Information Processing
by Sean C. Keenan
Financial Risk Management: Applications in Market, Credit, Asset, and Liability Management and Firmwide Risk
by Jimmy Skoglund and Wei Chen
Fraud Analytics Using Descriptive, Predictive, and Social Network Techniques: A Guide to Data Science for Fraud Detection
by Bart Baesens, Veronique Van Vlasselaer, and Wouter Verbeke
Harness Oil and Gas Big Data with Analytics: Optimize Exploration and Production with Data Driven Models
by Keith Holdaway
Health Analytics: Gaining the Insights to Transform Health Care
by Jason Burke
Heuristics in Analytics: A Practical Perspective of What Influences Our Analytical World
by Carlos Andre, Reis Pinheiro, and Fiona McNeill
Hotel Pricing in a Social World: Driving Value in the Digital Economy
by Kelly McGuire
Implement, Improve and Expand Your Statewide Longitudinal Data System: Creating a Culture of Data in Education
by Jamie McQuiggan and Armistead Sapp
Killer Analytics: Top 20 Metrics Missing from your Balance Sheet
by Mark Brown
Mobile Learning: A Handbook for Developers, Educators, and Learners
by Scott McQuiggan, Lucy Kosturko, Jamie McQuiggan, and Jennifer Sabourin
The Patient Revolution: How Big Data and Analytics Are Transforming the Healthcare Exp
erience by Krisa Tailor
Predictive Analytics for Human Resources
by Jac Fitz‐enz and John Mattox II
Predictive Business Analytics: Forward‐Looking Capabilities to Improve Business Performance
by Lawrence Maisel and Gary Cokins
Statistical Thinking: Improving Business Performance, Second Edition
by Roger W. Hoerl and Ronald D. Snee
Too Big to Ignore: The Business Case for Big Data
by Phil Simon
Trade‐Based Money Laundering: The Next Frontier in International Money Laundering Enforcement
by John Cassara
The Analytic Hospitality Executive: Implementing Data Analytics in Hotels and Casinos
by Kelly A. McGuire
The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions
by Phil Simon
Understanding the Predictive Analytics Lifecycle
by Al Cordoba
Unleashing Your Inner Leader: An Executive Coach Tells All
by Vickie Bevenour
Using Big Data Analytics: Turning Big Data into Big Money
by Jared Dean
Visual Six Sigma, Second Edition
by Ian Cox, Marie Gaudard, Philip Ramsey, Mia Stephens, and Leo Wright
For more information on any of the above titles, please visit www.wiley.com.
Gert H. N. LaursenJesper Thorlund
Copyright © 2017 by John Wiley & Sons, Inc. All rights reserved.
Published by John Wiley & Sons, Inc., Hoboken, New Jersey.
Published simultaneously in Canada.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the Web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.
For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.
Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material included with standard print versions of this book may not be included in e-books or in print-on-demand. If this book refers to media such as a CD or DVD that is not included in the version you purchased, you may download this material at http://booksupport.wiley.com. For more information about Wiley products, visit www.wiley.com.
Library of Congress Cataloging-in-Publication Data:
Names: Laursen, Gert H. N., author. | Thorlund, Jesper, author.
Title: Business analytics for managers : taking business intelligence beyond reporting / Gert H. N. Laursen, Jesper Thorlund.
Description: Second edition. | Hoboken : Wiley, 2016. | Series: Wiley & SAS business series | Revised edition of the authors's Business analytics for managers, | Includes index.
Identifiers: LCCN 2016028271 (print) | LCCN 2016029032 (ebook) | ISBN 9781119298588 (hardback) | ISBN 9781119302520 (ePDF) | ISBN 9781119302537 (ePub) | ISBN 9781119302520 (pdf) | ISBN 9781119302537 (epub)
Subjects: LCSH: Business intelligence. | BISAC: BUSINESS & ECONOMICS / Decision-Making & Problem Solving.
Classification: LCC HD38.7 .L39 2016 (print) | LCC HD38.7 (ebook) | DDC 658.4/033—dc23
LC record available at https://lccn.loc.gov/2016028271
Cover Design: Wiley
Cover Image: © Michael Mann/Getty Images, Inc
This book provides more fuel for this era of strategic and unified views of business analytics for value creation. In the same vein as Competing on Analytics and Analytics at Work, Business Analytics for Managers: Business Intelligence beyond Reporting adds another interesting and worthwhile perspective on the topic. In times of rapid change and growing complexity, rapid learning becomes more valuable. This book provides the strategic view on what's required to enable rapid learning and ultimately value creation.
Making decisions using huge, noisy, messy data requires business analytics. It is important to have a true appreciation of and advocacy for the analytical perspective on the whole of business analytics—on data (a strategic asset), on methods and processes (including refinement and optimization), and on people (the diverse skills it takes to formulate and execute on a well‐thought‐through strategy).
It starts with an analytical view of data: What is being measured, and is it what matters? Measurement (data generation and collection) is itself a process—the process of manufacturing an asset. When data is viewed this way, the analytical concepts of quality improvement and process optimization can be applied. The authors essentially ask, “What are you doing with your data? How are people in your organization armed to make better decisions using the data, processes, and analytical methods available?”
Business analytics, as portrayed by these analytical thinkers, is about value creation. Value creation can take different forms through greater efficiency or greater effectiveness. Better decisions to reduce costs, reveal opportunity, and improve the allocation of resources can all create value. The authors provide valuable business analytics foundational concepts to help organizations create value in a sustainable and scalable way.
Why business analytics? Even though some have tried to expand the definition of the relatively aged term business intelligence (BI), there is no real consistency, so a new term reflecting a new focus is warranted. Further, through promotion of a process view, we break out of some of the silothink and see the importance of closing the loop—on data (to monitor data quality and measure what matters), on process (to continuously learn and improve), and on performance (to make the best decisions, enable the best actions, and measure impact). How many organizations continue producing text‐heavy, tabular reporting on old and perhaps out‐of‐date metrics that few take the time to consume? How old are some of the processes driving key decisions in organizations? What opportunity costs are you incurring, and how could you be creating more value?
This book provides a synthesized view of analysis, traditional BI, and performance management, all of which are connected and need to be orchestrated strategically for maximum impact. The chapter advocating a shared strategic resource—a competency center or center of excellence—is an excellent way to drive best practices and create more value, making the case for treating data as a strategic asset and investing in the appropriate analytic infrastructure to maximize value.
Wherever you may be on your business analytics journey, you will find worthwhile thinking, shared expertise, and solid practical advice in this book to help you create more value in a sustainable and scalable way. The book is not just about analytics as a step in any given business process, but about the analytical perspective on any process that is key to understanding what it takes to drive continuous learning and improvement.
Anne Milley,Senior Director of Analytic StrategySAS Institute
Imagine a company. It could be an American manufacturer of home computers. Try to imagine, too, all the things such a company must be able to do: purchasing from suppliers, assembling and packaging the parts, preparing manuals and marketing plans, selling the products. The company also has a large number of support functions. Someone must look after the well‐being of its employees, new staff must be hired, people must be paid, the place must be cleaned, and a canteen must work to feed everyone. There is an entire financial function, ensuring that the crediting and debiting of banks, suppliers, owners, and customers runs smoothly. Finally, there are all the planning processes related to product lines and customer groups on which the company has chosen to focus.
Now imagine how much of this the company could outsource. Without too much effort, all production could be moved to East Asia. That could probably bring huge advantages since assembling computers is typically salary‐heavy and standardized production work. Others could handle the logistic side of things. The company could get professionals to write and translate the manuals. In addition, the company wouldn't need its own outlets; its products could be sold through some of the major retail chains. Alternatively, a Web shop could be commissioned to create an Internet site where customers could order the products they want. There is no real need for the company to have its own warehouse for parts and computers, from their arrival to their delivery to the customers. A lot of the support functions could be outsourced, too. Many companies outsource the process of recruiting the right people. Routine tasks such as paying salaries, developing training plans, and executing them in external courses could be outsourced, once the company has put the routines in place. Cleaning, the running of the canteen, refilling vending machines, and mowing grass are functions that are already, as a rule, outsourced by large IT companies.
By now, there is not much left of our company. We have removed all the functions that others can do almost as well or, in some cases, even better. What we have left is what we call the company's core competencies. These competencies are the things that the company is especially good at and that can secure its survival in the future, provided it is capable of developing these so that they continue to meet the requirements in the marketplace.
As shown in our example, core competencies have little to do with the physical world. Machinery, warehouses, and distribution can be outsourced. A company's core competencies lie in knowing how to handle internal processes, and knowing what customers want now and in the future. In other words, the key is to have the right knowledge in the company. More specifically, what the company needs is for the right people to have the right data and information at the right time. When that happens, we have rational decision making that meets strategic, operational, and market conditions. And this is exactly the first half of this book's business analytics (BA) definition:
Definition 1: Delivering the right decision support to the right people at the right time.
In this definition, we have chosen the term decision support, because BA gives you, the business user, data, information, or knowledge, that you can choose to act upon or not. Here's a familiar example: An analysis of check‐out receipts can inform the manager of a 7‐Eleven store which products are often purchased together, thus providing the necessary decision support to guide the placement of goods on the shelves to increase cross‐selling.
There is a saying that “people don't buy drills; they buy holes,” and this definition of BA points out that “people don't buy servers, pivot tables, and algorithms; they buy the ability to execute, monitor and control their business processes, along with insights about how to improve them.”
Regardless of whether predictive models or forecasting is used, it's the historical information that can give companies a status on the situation they are in right now. Maybe the company's analysts and their scenario models can present different alternatives, but ultimately it's the responsibility of the decision makers to choose which business processes they want to alter or initiate based on decision support. BA is about improving the business's basis for decision making and its operational processes, as well as achieving the competitiveness possible when a business is in possession of relevant facts and knows how to use them. In our work as consultants, we have too often experienced BA as purely an IT discipline, primarily driven by the organization's technical environment, which results in BA initiatives floating aimlessly. Successful BA initiatives are always closely interlinked with the organization's strategy (mission, vision, and goals) and are put in place to strengthen the ability of business processes to move in the right direction toward business objectives. Unfortunately, these points are often overlooked, which is one of the reasons for this book.
Over the last ten years, BA has, however, undergone some major developments, which means the definition of BA must be redefined. One big change has been labeled big data. This term is coined to describe the phenomenon of increasing amounts and variability of data—including formats like images, videos, and audio files. But the fact that the volume, variance, and velocity of available data have gone up is still covered by the above definition. Neither do new technologies, such as in‐memory prestored calculations or the increasing use of clouding solutions (where software and data are not hosted at the user location), call for a new definition of BA.
What does call for a new definition of BA is not really the huge volume of data and the new software to store and process it, but the intensified use of analytical models to control operational processes in an intelligent way. We might say that artificial intelligence is beginning to make decisions in the digital area. Here are some examples:
Pure digital processes like omnichannel marketing, where customer communication is send directly to the customers based on what the customer most likely wants from a specific electronic channel. Think of last‐minute‐offers from Booking.com. Also the automated investment programs based on algorithms that day trade shares and currencies automatically. Off course, the most successful investor will be the one using the best algorithm.
Semiphysical digitalized business processes, such as when analytics are used to predict future market demand and automatically reorder new stock for inventories based on, for example, season, campaigns, market growth, or price levels. Again, in this case, the market winner will be the company that runs its digital processes based on the most well‐configured algorithms. The
Internet of Things
is another new term, describing how physical assets can coordinate their actions based on more or less complex algorithms. For example, there are milking cattle farms where the cows are almost entirely served by robots; humans are only called upon when needed to do services such as make decisions about replacing cows, treat detected illness among cows, repair or maintain the machines, or fill and empty inventories.
Fully physical digitalized processes, like robots in the forms of automated cars and vacuum cleaners that respond to external physical input based on algorithms. Soon, these robots must be able to respond based on algorithms that handle voice, face and tone recognition, next to understanding the nonhuman physical environment they are acting in.
Over the last ten years, a huge amount of processes have been automated and digitalized, and the manual decisions that come with these processes have vanished. In many ways, what we see now is what people expected to see during the dot‐com era, which was all about the opportunities of new automated digitalized business process that allowed organizations to compete globally based on extremely scalable business models. Back in these early days, market disrupters like Amazon.com redefined how books were sold on the Internet. Later on, Apple and Kindle started to produce physical devices to increase people's experience of consuming books, music, and movies via the Internet. Now we are at a point where market disrupters can operate across all platforms based solely on apps. Some of the most spoken‐about market disrupters in 2016 are social media providers or the taxi service provider Uber.
Less noticed by the public, it is evident that physical production processes are being increasingly digitalized and intelligent. However, we are still waiting for the robots that can serve us intelligently in our private homes to have their breakthrough.
During the last ten years an increasing amount of business processes have been digitalized to the degree that the next competitor only is an app away. The market‐winning app is often the one that provides the best user experience based on intuitive user‐centric design, customer‐made data feeds, advanced analytics providing relevant suggestions, and the ability to store the relevant user history. Examples could be suggested friends on LinkedIn or Facebook, good offers and purchase tracking in virtual stores, banks, airline companies, or other service providers.
Because BA is increasingly applied and automated in digital processes, BA today is also much more than providing decision supports to humans within an organization, it is also about the provisioning of data to drive digitalized processes in an intelligent way.
This gives us this updated and final definition of BA:
Definition 2: Delivering the right decision support to the right people and digital processes at the right time.
This current intensified digitalization of business processes also means that although ten years ago we had to argue for the relevance of analytics, today we only discuss where analytics can be used efficiently as market challengers are constantly moving forward causing the extinction of “infosauric” companies—organizations that fail to see the direct linkage between analytical ability and competitive position.
It's quite easy to imagine a bank that runs all its customer processes and dialogue programs entirely without using IT—and what really hard work that would be. The point is, of course, that we can have BA without deploying software and IT solutions; at a basic level, that has been done for centuries. However, today it just wouldn't stack up. In this book, we look at BA as information systems consisting of three elements:
The information systems contain a
technological element
, which will typically be IT‐based, but which in principle could be anything from papyrus scrolls and yellow sticky notes to clever heads with good memories. A characteristic of the technological element is that it can be used to collect, store, and deliver information. In the real world, we're almost always talking about electronic data, which can be collected, merged, and stored for analysts or the so‐called front‐end systems that will deliver information to end users. A front end is the visual presentation of information and data to a user. This can be a sales report in HTML format or graphs in a spreadsheet.
A front‐end system
is thus a whole system of visual presentations and data.
Human competencies
form part of the information systems, too. Someone must be able to retrieve data and deliver it as information in, for instance, a front‐end system, and analysts must know how to generate knowledge targeted toward specific decision processes. Even more important is human decision support: those who make these decisions and those who potentially should change their behavior or the configuration of processes based on the decision support are people who must be able to grasp the decision support handed to them.
Finally, the information systems must contain
specific business processes
that make use of the information or the new knowledge. A business process could be the way inventory is optimized or products are priced. After all, if the organization is not going to make use of the created information, there's no reason to invest in a data warehouse, a central storage facility that combines and optimizes the organization's data for business use.
The considerable investment required to establish a data warehouse must render a positive return for the organization through improved organization‐wide decision making and enabling of digital processes. If this doesn't happen, a data warehouse is nothing but a cost that should never have been incurred. An information system is therefore both a facility (for instance a data warehouse, which can store information) as well as a set of competencies that can retrieve and place this information in the right procedural context.
When working with BA, it is therefore not enough to just have an IT technical perspective—that just means seeing the organization as nothing but a system technical landscape, where another layer of costs is added. It is essential to look at the organization as a large number of processes. For instance, the primary process in a manufacturing company will typically consist of purchasing raw materials and semimanufactured products from suppliers, manufacturing the products, storing them, and selling them on. In relation to this primary process there are a large number of secondary processes, such as repairing machinery, cleaning, employing and training staff, and so on.
Therefore, when working with BA, it is essential to be able to identify which business processes to support via the information system, as well as to identify how added value is achieved. Finally, it's important to see the company as an accumulation of competencies and train staff, some of whom undertake the technical solution, and others who bridge the technical and the business‐driven side of the organization focusing on business processes. Added value can be achieved in two ways: by an improved deployment of the input resources of the existing process, which means that efficiency increases, or by giving the users of the process added value, which means that what comes out of the process will have increased user or customer satisfaction. We'll discuss this in more detail in Chapter 3.
In other words, successful deployment of BA requires a certain level of abstraction. This is because it's necessary to be able to see the organization as a system technical landscape, an accumulation of competencies, and a number of processes—and, finally, to be able to integrate these three perspectives into each other. To make it more difficult, the information systems must be implemented into an organization that perceives itself as a number of departments with different tasks and decision competencies, and that occasionally does not even perceive information systems as being members of the same value chain.
We have written this guide to BA in order to provide:
A guide to fuel what we refer to as the
analytical age
, which, as the title of the book indicates, is to take business intelligence (BI) beyond reporting. In this book, we will introduce terms like
lead information
, which is the innovative decision support needed in order to revolutionize the processes landscape—typically done via BA. This should be seen as opposed to traditional BI producing lag information in the form of reports that help users to monitor, maintain, and make evolutionary improvements of their processes. These two types of decision support should be seen as supporting sets of information. However, as shown in
Exhibit I.1
, the value from a business perspective is different. We can compete on lead information, where lag information to a larger extent is maintaining and optimizing already existing processes.
The ability to make an information strategy, which basically is a plan of what the BA department should focus on according to company strategy. After you have read this book, you should have a framework that allows you to make a link between your overall organizational strategy and which specific data you should source in your data warehouse. You need this framework not just for standard reporting, but also to support your company's ability to innovate in the future by using analytics in
Chapter 8
.
An understanding of BA as a holistic information discipline with links to a business's strategy, source data from the operational systems, as well as the entire value chain in between—not just IT. BA is a combination of IT, human competencies, and organizational processes.
An understanding of the ever‐increasing role of BA, a role that today is aimed at optimizing at a business process level but that, we believe, in the near future will be aimed at optimizing individual human behavior, as discussed in
Chapter 9
.
A reference work containing the most frequently used BA concepts, definitions, and terminology. We have developed a BA model that gives a helicopter perspective and that provides the company's employees with one common frame of reference for objectives and means—and that clarifies the individual contributor's role and the interaction in the process. Our BA model constitutes the analytical framework, which is the pivot of the subsequent chapters. The model focuses on BA as an interaction of IT, strategy, business processes, a broad spectrum of human competencies, organizational circumstances, and cooperation across the organization.
Exhibit I.1 The Stairway Chart: Emphasizing the Difference between Lead and Lag Information
The book is relevant for all businesses that want to define information strategies or fine‐tune existing programs with a view to maximizing their effect. It's written for anyone working with the implementation of information systems—that is, project managers, analysts, report developers, strategists or CIOs, CEOs, CFOs, CxOs, IT professionals, social media specialists, and database specialists. But we should add that the book is of relevance to anyone working operationally with these information systems, since it will highlight the role of these systems in terms of the overall strategy of the company. Thus, the book is also for everyone in business‐focused functions in sales, marketing, finance, management, production, and human resources who works at a strategic level.
If, for instance, you are working with customer relationship management (CRM) and wish to focus systematically on customer retention via churn analyses, you need the involvement of product managers, who, based on the customer profiles to be retained, must develop retention products. Customer service functions such as call centers need to be integrated in the information flow, too, when handling campaign response. The communication department that designs the dialog with the target groups about their needs via text—and basically any creative universe—needs to be working systematically with the given customer profiles. In addition, there's a data warehouse that must be able to present and store relevant information about customers over time, as well as customer information that continuously must be adapted based on a mix of customer behavior and company strategy. Even though we often look at our organization through an organization chart, where some people work in marketing and others in procurement and production, it makes more sense to see the organization as a large number of processes that, across the different departments, create value chains to satisfy the organization's customers and their needs.
One example of a traditional value chain could be procurement of raw material, manufacturing, sales, delivery, and follow‐up services. The mere fact that someone is part of this value chain means that he or she is measured at some point. We may not be calling it BA, but instead performance targets, budgets, or key performance indicators (KPIs). Regardless of name, these are measuring instruments established to inform management functions about whether the established processes are achieving the organization's various targets.
BA is relevant in both large and small businesses. As shown in the BA model in Chapter 1, it doesn't say anywhere that a company must be a large financial institution with hundreds of data warehouse tables placed on large and expensive mainframes to deploy BA. Small and medium companies are known to carry out excellent BA, using the most popular BA tool in the world: spreadsheets (as do large companies).
We have endeavored to make this technically complex discipline more easily accessible and digestible to a broader group of readers. Students at business schools with a couple of years' work experience should therefore be able to obtain maximum benefit from the book, too.
The book is structured in a way that shows the role of BA in the individual parts of this process and explains the relationship between these parts. You may read the chapters out of order, depending on the area that is of particular relevance to you. The intention of the book is to describe BA coherently and comprehensively while at the same time offering each chapter as a work of reference.
Compared to other publications on the subject, this book is less about describing the individual small subelements of BA, and more about demonstrating the link between them. Specific examples are also offered showing how to add value in the business by using BA solutions.
In Chapter 1, we examine the BA model. The chapter covers the spectrum from business strategies to sourcing of data from the operational systems (data sources) as well as a case study. The model is the pivot of the subsequent Chapters 2 through 6, and the radio station case study illustrates a BA process that will work as a point of reference throughout the subsequent chapters.
In Chapters 2 through 6, we go through the five layers of the BA model, each of which is allocated a chapter. Chapter 2 addresses the relationship between business strategies and the BA function.
Chapter 3 focuses on the creation and use of information at a functional level. The question is how BA can work to support the improvement and maintenance of the company's various business processes (e.g., in sales, marketing, finance, management, and HR) so that they support the overall strategic goals as discussed in Chapter 2.
In Chapter 4, we look at business analytics through processes and present options as well as analytical methods for the transformation of data into information and knowledge.
In Chapter 5, we explain the functionality of a data warehouse and the processes in connection with the availability of data for business use.
In Chapter 6, we discuss the different operational systems and data sources in the organization's environment.
Chapter 7 shifts gears and focuses on the structuring of BA initiatives in so‐called business analytics competency centers (BACCs).
Chapter 8looks at how businesses can assess and prioritize BA projects, and Chapter 9 focuses on the future of BA. The big question is “Where is BA heading?”
This book could also have been given the title, How to Make an Information Strategy, or How to Use Information as a Strategic Asset. We chose the title Business Analytics for Managers: Taking Business Intelligence Beyond Reporting because we felt that this is the next stepping stone for companies in today's information age. Today most business processes are linked together via electronic systems that allow them to run smoothly and in a coordinated way. The very same information systems generate electronic traces that we systematically collect and store, primarily for simple reporting purposes.
BA allows business to go beyond traditional BI reporting. Had we therefore called our book Business Intelligence, we feared that it would be bundled with all the technical literature on the subject that it attempts to counterbalance. We are entering the analytical age, a window in time where competitive advantages will be gained from companies making increasingly more advanced use of information. It will also be a period when other companies will fail and falter as infosaurs, with only muscles and armor, and not the brainpower needed to survive in changing market conditions.
So to make it clear: Analytics is an advanced discipline within business intelligence. BI today as a term is heavily associated with large software vendors that offer only simple technical reporting solutions for the end users. We will use the term business analytics to put extra focus on these missing elements of the BI equation, and which are by far the most exciting ones; if mastered, they will drive your company into a prosperous future.
The most important thing in a large and complex project with a large number of people and competencies involved is to create an overview of the project from a helicopter perspective as quickly as possible.
This chapter focuses on the business analytics (BA) model, which will help provide that overview. The model provides an outline for understanding—and creating—successful BA in any type of organization. The purpose of the model is to give the organization a single common frame of reference for an overall structure in the creation of successful BA; the model clarifies the roles of the individual contributors and the interaction in the information generation and information consumption process, which is what BA is, too. The model is the pivot of the rest of the book; the five layers of the model are subsequently explained in detail, with each layer allocated a separate chapter.
If your job is to make an information strategy, for example as a CIO, the model comprises all the stakeholders and processes on which you should focus. The model also gives clues about why most BA projects fail, which is simply because it is a large cross‐organizational activity. You can compare it to a chain that is only as strong as its weakest link; if one of the departments involved lacks the skills or resources, or if the knowledge handover between departments fails, your project will fail.
The BA model in Exhibit 1.1 illustrates how BA is a layered and hierarchical discipline. Arrows show the underlying layers that are subject to layers above. Information requirements move from the business‐driven environment down to the technically oriented environment. The subsequent information flow moves upward from the technically oriented environment toward the business‐driven environment.
Exhibit 1.1 The BA Model
As illustrated by the BA model in Exhibit 1.1, there are many competencies, people, and processes involved in the creation of BA. In the top layer of the model, in the business‐driven environment, the management specifies a strategy that includes which overall information elements must be in place to support this strategy. In the second layer, the operational decision makers' need for information and knowledge is determined in a way that supports the company's chosen strategy. In the middle layer of the model, analysts, controllers, and report developers create the information and knowledge to be used by the company's operational decision makers with the purpose of innovating and optimizing their day‐to‐day activities. In the second layer from the bottom, in the technically oriented environment in the data warehouse, the database specialist or the ETL (extract, transform, load) developer merges and enriches data and makes it accessible to the business user. In the bottom layer, in the technically oriented environment, the business's primary data generating source systems are run and developed by IT professionals from IT operations and development. Successful BA processes should have a fixed structure that always begins with the specification of the information strategy, which is derived from the objectives of the business strategy.
All underlying contributions and activities must submit to the chosen information strategy, as specified in the business‐driven environment at the top of the model. This information strategy is decided at this level based on the organization's or the business area's overall business strategy (vision, mission, and objectives). Normally, these strategies will result in a number of key performance indicators (KPIs) with the purpose of measuring the degree of progress and success. The contents of the KPIs will depend on which underlying business process we want to control. The KPIs could, for instance, relate to profitability, return on equity (ROE), or different types of sales targets. The information strategy is often specified by the top management of the organization, by functional managers, or by business process owners. Large organizations may have an actual business development function, which is responsible for the formulation of the strategy for the entire group. How this is undertaken will be explained in detail in Chapter 2.
Once the strategy, along with the overall strategic KPIs, is in place, a framework, focus, and objectives are established for the operational business processes and initiatives. The information and analysis shown in the underlying layers of the model must be directed at changing and managing business processes toward the strategic objectives made visible by the KPIs. The operational decision makers' desired behavior and the subsequent information and knowledge requirements to bring about this behavior are specified and outlined in this layer.
As mentioned, the objective of BA initiatives is to change business processes and actions so that they are targeted toward achieving the organization's strategic objectives. For example, operational decision makers from sales, marketing, production, general management, human resources (HR), and finance can use information and knowledge to optimize their daily activities. In Chapter 3, we'll look at what this means specifically for the various functions of the company.
In the analysis and reporting development environment in the middle of the model, analysts specify which information and data are necessary to achieve the desired behavior of operational managers and digital processes in the business environment. This is where information and knowledge are generated about the deployment of analytical and statistical models, which are typically deployed on data from the data warehouse. The requirements for front‐end applications, reporting, and functionality are also specified in detail here, all with the purpose of meeting the demands from the higher layers and levels of the model. Note that the analysis and reporting development environment is placed in the bordering area between the business‐driven and the technically oriented environment, and that the team in this area usually has competencies in both areas. Chapter 4 covers more about the methodical work in the analytical and reporting environment.
Database specialists and ETL developers receive requirements from the analytical environment about data deliveries. If the required data is already in the warehouse, the process will be to make this data accessible to the front‐end applications of the business. If data is not stored, the data warehouse will need to retrieve data from one or more operational data sources in the organization's environment. Alternatively, data can be purchased from an external supplier, or the IT department may be asked to implement a new infrastructure with a view to create a new operational data source. Chapter 5 focuses on methods and systems for storing, merging, and delivering data.
IT operations and development must meet the requirements from the data warehouse about the delivery of data from the primary operational data sources or the development of new data sources. The different primary data sources in a company's environment and the data created are covered in Chapter 6.
As previously noted, a large number of people, competencies, and processes are involved in the creation of BA. Large organizations sometimes have several hundred people on all levels involved at the same time. In smaller companies, controllers and analysts must have a wider range of competencies to be able to carry out BA initiatives on their own.
