1.4 Place of Data Analysis in Problem Solving - ARTICLE
1.4 Place of Data Analysis in Problem Solving - ARTICLE
A data analyst often doesn’t come into the picture until mid-way through
the data step of PPDAC. To do a good job, an analyst needs to develop a
good understanding of what has gone on before, particularly how the
data was actually obtained. (Involving statisticians from the very start of
the PPDAC process is much better as it leads to better-quality data that
is better suited to answering an investigator’s questions).
The Data step is about obtaining the data, storing it and “whipping it into
shape” (data cleaning). Data analysts are always involved with data
cleaning, if only because we almost always discover problems with data
during analysis.
The Analysis step and the Conclusions steps are about making sense of it
all and then communicating what has been learned. There is always a
back and forth involving doing analysis, tentatively forming conclusions
and doing more analysis. The formation of conclusions typically involves
the analyst and a subject-matter expert (e.g. someone who understands
the business) who will “own” the conclusions.
Often, looking at a set of data will raise more questions than it answers.
For this reason we may need to go around this cycle several times before
we feel that we’ve learned what we needed to learn. But with real-world
problems, there are always limits to the time and money that can be
spent on data collection and analysis.
This article has been about purpose-collected data. We also analyse data
that was collected for reasons unrelated to our problem. Such data is
much less reliable (for reasons discussed in Week 5) but a whole lot
cheaper!
(The PPDAC model was developed by R.J. Mackay and W. Oldford in the
early 1990s. Our diagram is an elaboration of PPDAC.)
How does PPDAC relate to PDCA, DMAIC and similar models used in
management?
The PDCA (Plan, Do, Check, Act) cycle often used in management and its
descendent DMAIC (Define, Measure, Analyze, Improve and Control) used
to drive six-sigma projects are helpful for structured ways of thinking
about addressing a need to act to solve a practical problem such as
improving a manufacturing process or an administrative system.