Here's how to successfully implement an analytics methodology.
Decisions made based solely on intuition, gut feelings, and years of experience, while valuable, tend to be less effective than scientific methods. Analytics provides a methodology that incorporates crucial variables and provides simulations that show the impact of our choices before we implement them.
Analytics--the application of mathematics and statistical methods to organizational decision making--has been the focus of a great deal of marketing hype. But to use it successfully requires more than products. Here's a seven-step process for applying analytics.
1. Define the problem. Assumptions must be challenged and terms defined to come up with what in Six Sigma parlance is referred to as the "operational definition." We also must define objectives. What criteria will be used to select the appropriate decision? What conditional states exist relative to the problem, and how are they affected by the solution alternatives? What is the scope of the problem definition, and how do we know when we've succeeded?
2. Identify relevant factors. Relevant factors include controllable and uncontrollable variables. Examine whether these variables are related to each other directly, or there's a range of possibilities. Be on the lookout for latent variables, hidden factors that aren't observed directly but are inferred from the behavior of other variables. Finally, factor in risk and uncertainty.
3. Focus on data collection and preparation. This step can become complicated, particularly when mining vast amounts of data. Data mining algorithms often identify features including data affinity and patterns that aren't readily apparent with a cursory examination. This is also the time to establish baselines--measurements of the current "as is" process, against which you'll compare future "to be," post-implementation results.
4. Model the solution. Here, mathematical models of a process and its variables simulate the behavior of the actual process. A working model may be largely composed of strings or chains of mathematical formulas.
5. Report the results. The analyst must be able to walk through the analysis step-by-step. It is upon this report that "go/no-go" decisions are made. In some cases, this is a one-time decision to modify the process or organization; in other cases, it will be a decision to initiate a new process.
6. Implement the decision. This is where models and simulations migrate from a conceptual state to practice. It requires detailed planning and project management. In too many instances, implementations fail due to a lack of qualified project management skills.
7. Follow up. Post-implementation follow-up is the time to compare as-is baseline measures with to-be, post-implementation results. Measurement periods should cover meaningful reporting cycles, such as monthly, quarterly, or annual assessment, and you'll need sufficient granularity to make needed adjustments to your models over time.
Gary Smith is a principal at Doyen, a consulting firm that specializes in project management and process analytics.
How Enterprises Are Attacking the IT Security EnterpriseTo learn more about what organizations are doing to tackle attacks and threats we surveyed a group of 300 IT and infosec professionals to find out what their biggest IT security challenges are and what they're doing to defend against today's threats. Download the report to see what they're saying.
Digital Transformation Myths & TruthsTransformation is on every IT organization's to-do list, but effectively transforming IT means a major shift in technology as well as business models and culture. In this IT Trend Report, we examine some of the misconceptions of digital transformation and look at steps you can take to succeed technically and culturally.