Behavioural Economics



Below are a few notes (most are copy pastes) of stuff that I've covered during my time at Dilip Soman's Behavioural Economics online course at edX.

The topic is a recent interest of mine after spending some time earlier this year learning about social graphs and basic graph theory in general. So as a natural extension to that, a question that comes to mind is, how do people make purchasing decision?

The notes have been mostly compiled in Slack - somehow I kinda take a liking in the way the notes there get formatted. It's relatively easy too - perfect for lazy people like myself.

Below are the public links of my notes in Slack with regards to the topic:
  1. Early General Notes
  2. A Theory of Decision Points
  3. Choice Overload 
  4. Glossary of Concepts
  5. Consumption Vocabulary
  6. Recent Nudge Experiments
  7. Decision Aids
  8. Disclosure
One thing that I really like about the course is that it also talks about how to conduct experiments should you have an idea that you'd like to test. Below are some notes:
  1. Basics of Experiments
  2. Analysis of Experimental Data
  3. Two Experiments
  4. Field or Lab?
  5. Intuition and Judgement
I wouldn't say that the notes above are complete in any sense. What I would suggest to others out there who are interested in learning more about the subject: do check the course out at edX. At the time I took the course I was also reading up on Richard Thaler's "Misbehaving" - so that kinda helped me gain additional insights as well.

So how does all of this relate to analytics?

Well, in my field (market analytics) we'd like to understand how consumer make decisions. Maybe it's due to their friends, maybe it's down to the relative quality of the product. And most of the times the assumption is - if the price is lower and the product is superior; it only made sense that consumer will always choose our product over a competitor. In reality however, this needn't be exactly the case. As behavioural economics suggest, humans make irrational economic decisions sometimes. Decisions that does not make any sense (economically that is).

So understanding these quirks and phenomenon will (I hope) ultimately help one

  • Understand the data from a human perspective
  • Build more accurate model 
  • Design better marketing campaign


Comments

Post a Comment

Popular posts from this blog

A Basic Recipe for Machine Learning

Image
Ever since wrapping up the three Deep Learning courses by Andrew Ng I've been meaning to write down some of the gems that he's highlighted throughout the course. One of the nice ones that I felt needed to be written down is his general recipe to approaching a deep learning algorithm/model. I've basically summarized it in a flowchart below (because everybody loves a flowchart right?) Basic deep learning recipe What is bias and variance? The below diagram is the typical explanation that I'm sure most of us are used to.  Graphical illustration of bias and variance How can we know if we have high bias or high variance?  For high bias, we could take a look at the training set performance. A poor performance is an indicator of a poor model fit, and signals that we could try to apply a bigger network to get a better fit of the model. For high variance, we could take a look at the validation set (or dev set - as Andrew calls it) performance. ...
Keep reading

HIVE: Both Left and Right Aliases Encountered in Join

Recently was stuck on this error while trying to do a JOIN in HIVE. Below is my SQL create table ma.internet_v2 as select A.msisdn, A.imsi, A.dt, A.start_time, A.end_time, A.url, A.ttl_connection_dur_ms, A.ttl_upload_bytes, A.ttl_download_bytes, A.ttl_cdr_cnt, coalesce(B.domain_desc,A.domain_desc) domain_desc, coalesce(B.subdomain_desc, A.subdomain_desc) subdomain_desc from db.internet A left outer join hfz_domain_name_mapping B on instr(A.url, B.url_pattern) > 0; HIVE then give me and error message "Both Left and Right Aliases Encountered in Join". After going through some mail threads it seems that HIVE can support certain types of join. Only equality joins, outer joins, and left semi joins are supported in Hive. Hive does not support join conditions that are not equality conditions as it is very difficult to express such conditions as a map/reduce job. A poster from  Stack Overflow  suggested that one should use WHERE instead of ON. Duly following his advice,...
Keep reading

MVNO: Through thick and thin

The below article was taken from Silicon.com. Click here to read the actual article. By Natasha Lomas, 27 October 2008 16:23 MVNO? That'll be an abbreviation - another pointless four letter one no doubt… Right and wrong. MVNO stands for mobile virtual network operator - and it refers to a rather intriguing slice of the mobile pie. I'm listening… Building and operating a mobile network is an expensive business, not least because it requires radio spectrum, so the number of mobile network operators (or MNOs) is limited to, at most, a handful per market. For instance, the UK market has five: 3, O2, Orange, T-Mobile and Vodafone. Spectrum does not come cheap. The auction for 3G licences in the UK - way back in 2000 - ended with five companies shelling out a whopping £22.47bn for the privilege of flogging third-generation services to Brits. So the requirement for large capital expenditure to set up a mobile network goes some way to explaining why actual networks are not 10-a-penny. ...
Keep reading