pdf analytics-and-witch-doctoring -why-executives-succumb-to-the-black-box-mentality-presentation
TRANSCRIPT
Analytics and Witch Doctoring:A Cure for the Black Box
Mentality
February 1, 2011
O’Reilly Strata Conference
J.C. Herz, Batchtags LLC
Analytics: Occult Phenomenon
Very powerful
Don’t understand it
Practitioners possessarcane knowledge
High Status Helplessness
• If you understood the technology, you’dbe one of those people whose job it isto make technology work.
• You know, underlings
Shiny Pebble Syndrome• Infoviz Porn: Visualization with no
use case– Ex: Social Network visualization. Why?– START with a use case and work
forward
• Demo Envy: just because it looksslick doesn’t mean it’s possible, oreven advisable, to pipe your datainto it.
A Ballad of SpectacularInformation Display
• Time Magazine 1976• Telex text routing:
information off the wiregoes to terminals, properlyfoldered
• Z8 terminal display awesexecutives
• Pneumatic system noteliminated
Half Ass Syndrome
• Halfway into the project, jump off intothe next problem.
• Haven’t refined results or hypothesis
• Failure blamed on technology, but it’sreally loss of interest and desire forinstant gratification
Shelfware Syndrome• The guy who was driving the program left...• Approach-Avoidance conflict --> pilot-itis• A US agency has $30M of software that
hasnʼt been installed…some of it withmaintenance contracts.
• Base Model vs. Fully Loaded– One enterprise bought $12M worth of
Autonomy before figuring out that the add-onsthey needed would be another $22M.
Critical Question: What is theValidation Test?
• Formulating the validation test keepsboth the customer and the developerfocused - and honest
• Suggest pay for performance, and see ifthe developer or vendor freaks out.
• Make sure validation is ongoing - incase the ground is shifting
Critical Question: Data Quality
• How complete is it?– Ex: 600 custom fields, only two have more than 50%
coverage
• How accurate is it? How do you know?
• How consistent is it?
– Good test: make three calls to different partsof the company, to get an answer to a factualquestion that doesn’t require calculation.
Critical Question: Real World Context
• Without real world data, “behavioral” metricsare misleading
• Where is the transactional data that validatesinsights from non-transactional data?
• How would you prove the magic analyticsWRONG?
• Are you prepared to spend painfulamounts of money cleaning up your data?
• Crack heads if people don’t share data?• Make business units accountable for their
data?• Play hardball to make sure data is not
stored in single-application proprietaryformats?
Data: Gut Check
Critical Questions: Workflow• What workflow changes will this
proposed capability require?• People hate changing their workflow,
even if it’s an improvement• Never attribute to stupidity what can be
attributed to laziness• What is your plan for changing
workflow? How do you enforce it?
Critical Question: Consequences
• What actions are you willing to take onthe basis of validated analytic insight?– Change your product?– Change your marketing budget?– Change people’s job descriptions?– Re-allocate R&D budgets?
• What actions are you not willing to take?
Critical Question: Tempo
• How fast will a decision be made on thebasis of analytic insight?
• Quarterly?• Daily?• Within seconds?• Milliseconds?• Never?• Realtime vs. Continuous vs. Batch
Precision vs. Accuracy
When precision exceeds accuracy, you’resetting yourself up for analytic failure
Before You Rip ‘n’ Replace:
What is the exit cost of thistechnology?
Does “turnkey” meanmonoculture?
Business Payoff vs.Intellectual Appeal
Social NetworkAnalysis
OperationsResearch
MarketSegmentation
CompetitiveIntelligence
Pilots to test newanalyst tools withtiny amounts ofgeneric data
360ºLeadScoring
Validate MarketingEffectiveness