Turning Customer Data into Profits with a Spreadsheet The Guide to Maximizing Customer Marketing ROI | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Note: In the next table "Lycos" excludes Hotbot
Hmmm. Sure are different, aren't they? There's frequently a difference of double or triple in the same metric across the engines. But traffic also matters. FAST delivers great overall stats but hardly any traffic, so I should probably look into what is going on there. And I will. Fortunately, you will be spared the results,
as this is the promised end of the series on analyzing web
logs. What did we learn? Questions from Fellow Drillers A: Aw, shucks. Thanks for the kind words. Q: I would like to know your opinion as to how this approach could be modified suitably for implementation in a Software Development and IT outsourcing firm like mine. A: Generally, any transactional activity can be profiled using the RF scoring method. It is used for everything from predicting the likelihood of someone to commit another crime to predicting the likelihood of someone to make a bank deposit. RF is based on human psychology and is therefore applicable in any culture. Any part of your business where transactions are generated - medical transcription, attendance records, project tracking, and so on. All you have to do is think of situations where the prediction of repeat behavior likelihood is desirable. In some cases, frequently in service businesses, the desired outcome is inverted - that is, it is positive if people become less likely to do something. For example, in regards to attendance tracking, if you want to predict the likelihood of a person to skip or call off work, look at the Recency and Frequency of this past behavior. If you were using RF scoring, a falling score for the person would be positive, since they are becoming less likely to call off again. In transcription, for monitoring coding errors, the higher the Recency and Frequency of past errors, the more likely they are to be committed again. A falling RF score for a transcriber would be positive, since they are becoming less likely to commit another error. A rising score, they are becoming more likely to commit an error. I don't know if likelihood prediction is useful for the transcribed records themselves, but it could be. For example, predicting the likelihood of a doctor to prescribe a certain medicine or order a certain procedure. The tracking of these things might be useful to a client and you could offer this as an added service to them. As far as software development for clients, there are any number of situations where a simple predictive model may be useful, especially where there is transactional activity related to purchases in B2C and B2B - reordering / replenishment for trading hubs, for example. And of course, in CRM, there are many, many uses for simple predictive behavior models. Generally, one should try using the RF scheme for prediction
before any more complex modeling operations are carried out. Often, after a long and torturous data mining project is
completed, one finds Recency and Frequency to be the primary
variables predicting the behavioral outcome; much time and
effort could have been saved by using the simple RF
scoring process detailed in my book in the first place!
If you would like me to teach you these concepts using your
own business model and customer data, check out my
workshops and project-oriented service: Customer
Consulting. Any comments on the newsletter (it's too long, too short, topic
suggestions, etc.) please send them right along to me, along with
any other questions on customer Valuation, Retention, Loyalty,
and Defection to me.
Copyright 2001, The Drilling Down Project by Jim Novo. All
rights reserved. You are free to use material from this
newsletter in whole or in part as long as you include complete |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
/ |
|