Patients Aren’t Ready for Treatment?
In my job of being “a guy who finds money-making opportunities using data,” I get to meet all kinds of businesspeople in various industries. Thanks to the business trend around analytics (and to that infamous “Big Data” fad), I don’t have to spend a long time explaining what I do any more; I just say I am in the field of analytics, or to sound a bit fancier, I say data science. Then most marketers seem to understand where the conversation will go from there. Things are never that simple in real life, though, as there are many types of analytics — business intelligence, descriptive analytics, predictive analytics, optimization, forecasting, etc., even at a high level — but figuring what type of solutions should be prescribed is THE job for a consultant, anyway (refer to “Prescriptive Analytics at All Stages”).
The key is to an effective prescription is to listen to the client first. Why do they lose sleep at night? What are their key success metrics? What are the immediate pain points? What are their long-term goals? And how would we reach there within the limits of provided resources and put out the fire at the same time? Building a sound data and analytics roadmap is critical, as no one wants to have an “Oh dang, we should have done that a year ago!” moment after a complex data project is well on its way. Reconstruction in any line of business is costly, and unfortunately, it happens all of the time, as many marketers and decision-makers often jump into the data pool out of desperation under organizational pressure (or under false promises by toolset providers, as in “all your dreams will come true with this piece of technology”). It is a sad sight when users realize that they don’t know how to swim in it “after” they jumped into it.
Why does that happen all of the time? At the risk of sounding like a pompous doctor, I must say that it is quite often the patient’s fault, too; there are lots of bad patients. When it comes to the data and analytics business, not all marketers are experts in it, though some are. Most do have a mid-level understanding, and they actually know when to call in for help. And there are complete novices, too. Now, regardless of their understanding level, bad patients are the ones who show up with self-prescribed solutions, and wouldn’t hear about any other options or precautions. Once, I’ve even met a client who demanded a neural-net model right after we exchanged pleasantries. My response? “Whoa, hold your horses for a minute here, why do you think that you need one?” (Though I didn’t quite say it like that.) Maybe you just came back from some expensive analytics conference, but can we talk about your business case first? After that conversation, I could understand why doctors wouldn’t appreciate patients who would trust WebMD over living, breathing doctors who are in front of them.
Then there are opposite types of cases, too. Some marketers are so insecure about the state of their data assets (or their level of understanding) that they wouldn’t even want to hear about any solutions that sound even remotely complex or difficult, although they may be in desperate need of them. A typical response is something like “Our datasets are so messy that we can’t possibly entertain anything statistical.” You know what that sounds like? It sounds like a patient refusing any surgical treatment in an ER because “he” is not ready for it. No, doctors should be ready to perform the surgery, not the patient.
Messy datasets are surely no excuse for not taking the right path. If we had to wait for a perfect set of data all of the time, there wouldn't be any need for statisticians or data scientists. In fact, we need such specialists precisely because most data sets are messy and incomplete, and they need to be enhanced by statistical techniques.
Analytics is about making the best of what we have. Cleaning dirty and messy data is part of the job, and should never be an excuse for not doing the right thing. If anyone assumes that simple reports don’t require data cleansing steps because the results look simple, nothing could be further from the truth. Most reporting errors stem from dirty data, and most datasets — big or small, new or old — are not ready to be just plugged into analytical engines.
Besides, different types of analytics are needed because there are so many variations of business challenges, and no analytics is supposed to happen in some preset order. In other words, we get into predictive modeling because the business calls for it, not because a marketer finished some basic Reporting 101 class and now wants to move onto an Analytics 202 course. I often argue that deriving insights out of a series of simple reports could be a lot more difficult than building models or complex data management. Conversely, regardless of the sophistication level, marketers are not supposed to get into advanced analytics just for intellectual curiosity. Every data and analytics activity must be justified with business purposes, carefully following the strategic data roadmap, not difficulty level of the task.
Stephen H. Yu is a world-class database marketer. He has a proven track record in comprehensive strategic planning and tactical execution, effectively bridging the gap between the marketing and technology world with a balanced view obtained from more than 30 years of experience in best practices of database marketing. Currently, Yu is president and chief consultant at Willow Data Strategy. Previously, he was the head of analytics and insights at eClerx, and VP, Data Strategy & Analytics at Infogroup. Prior to that, Yu was the founding CTO of I-Behavior Inc., which pioneered the use of SKU-level behavioral data. “As a long-time data player with plenty of battle experiences, I would like to share my thoughts and knowledge that I obtained from being a bridge person between the marketing world and the technology world. In the end, data and analytics are just tools for decision-makers; let’s think about what we should be (or shouldn’t be) doing with them first. And the tools must be wielded properly to meet the goals, so let me share some useful tricks in database design, data refinement process and analytics.” Reach him at firstname.lastname@example.org.