Tagged : Intuit

Why Regulators Need to Mandate Open Data Protocols in the Cloud

TechCrunch’s arti­cle about Intuit’s deci­sion to shut down Quicken OnLine and not let users migrate their data to the new ser­vice Mint.com is an out­stand­ing exam­ple of the emerg­ing prob­lem of ‘Data Lock-In’ and an issue which reg­u­la­tors need to get ahead of before its too late.

As the mar­ket for ‘Cloud’ ser­vices takes off we’re going to wit­ness an explo­sion of new ser­vices whose value propo­si­tion is based on man­ag­ing some aspects of the con­sumers life on-line. The big buck­ets already are life-centric ser­vices such as health and fit­ness, per­sonal finances and of course man­ag­ing you social graph. The expand­ing ros­ter of new ser­vices will be accom­pa­nied by an equally large num­ber of fail­ures. That is the nat­ural order of things in new mar­kets. Not all new entrants will find a busi­ness model which works or is sus­tain­able over the long term. Reg­u­la­tors need to start think­ing about the con­sumer pro­tec­tion regimes that need to be put in place as this happens.

I was struck by some of the debate sur­round­ing the Intuit issue by the num­ber of folks who think its not a big deal because Quicken On-Line is a ‘Free’ ser­vice. That could not be fur­ther off the mark. One of the chal­lenges for any new entrant in the crowded mar­ket for ‘Cloud’ ser­vices will be fig­ur­ing out how to make their ser­vice as ‘Sticky’ as pos­si­ble. After hav­ing invested a great deal to acquire new cus­tomers you want to make sure its not easy for them to leave or switch to a com­peti­tors ser­vice (Ever won­der why its incred­i­bly dif­fi­cult to dump you mobile provider? It’s called ‘Churn’ and ‘ARPU’)

One way to build ‘Stick­i­ness’ is to ensure that new cus­tomers have to invest a sig­nif­i­cant amount of per­sonal effort to extract the full ben­e­fits of the ser­vice. In Quicken Online’s case that was the time required to upload bank­ing infor­ma­tion and months and months of enter­ing indi­vid­ual finan­cial trans­ac­tions. Mak­ing it easy for cus­tomers to export their data from the ser­vice would under­mine ‘Stick­i­ness’ and there­fore increase the likely hood that cus­tomers might switch to a competitor’s ser­vices. In the highly com­pet­i­tive ‘Cloud’ ser­vice mar­ket it will be very tempt­ing to find ways to bind users to ser­vices by mak­ing it dif­fi­cult for them to take their data and run.

Con­sumers need to be edu­cated about the dan­gers of ‘Data Lock-In’ so that they increas­ingly demand Open Data Access (ODA) from ‘Cloud’ ser­vice providers. I think its also about time that gov­ern­ment reg­u­la­tors started think­ing about man­dat­ing ODA for all ser­vice providers. These reg­u­la­tions would be a nat­ural exten­sion of exist­ing pri­vacy reg­u­la­tions by enshrin­ing the prin­ci­ple that per­sonal infor­ma­tion of any sort belongs to the con­sumer, not the provider, and the con­sumer has the right to take that data with them when they leave a ser­vice. This would be a direct ana­log to ‘Num­ber Porta­bil­ity’ require­ments in the mobile tele­phony sec­tor. Ser­vice providers would be required to ensure that all con­sumer owned data can be exported from their ser­vice using open stan­dard for­mats and protocols.

Such a reg­u­la­tory require­ment would pro­tect con­sumers of the sort of mess now faced by Inuit’s cus­tomers. It would also force ser­vice providers to focus on broader value propo­si­tion of their ser­vice rather than rely­ing on ‘Data Lock-In’ as a com­pet­i­tive lever. This focus on ‘Func­tional’ com­pe­ti­tion would be a great thing for con­sumers and the market.