XML and software
XML, web and software in general, with notes on Radio Userland resources

Ken Novak's Weblog


daily link  Thursday, February 22, 2007


The endowment effect, the 9X problem and collaboration:  Nice summary from HBS.  "the "endowment effect" [is when] we value items in our possession more than prospective items that could be in our possession, especially if the prospective item is a proposed substitute.  We mentally compare having the prospective item to giving up what we already have (our 'endowment'), but because we're loss averse giving up what we already have (our reference point) looms large. 

And Gourville points out three factors that make the situation worse for product developers who want their offerings to succeed.  First is timing:  adopters have to give up their endowment immediately, and only get benefits sometime in the future.  Second, these benefits are not certain; the new product might not work as promised.  Third, benefits are usually qualitative, making them difficult to enumerate and compare. ..

Because of all of the above, Gourville talks about the '9X problem' --  "a mismatch of 9 to 1 between what innovators think consumers want and what consumers actually want."1  The 9X problem goes a long way to explaining the tech industry folk wisdom that to spread like wildfire a new product has to offer a tenfold improvement over  what's currently out there...

Email is a channel technology.  It creates a private conduit between the sender and receiver.  Other parties don't know that the email was sent, and can't consult its contents.   Wikis, del.icio.us, Flickr, Myspace, Facebook, and YouTube, on the other hand, are all platform technologies.  They accumulate content over time and make it visible and accessible to all community members.  [They also foster emergence, where structure emerges rather than being imposed by "groupware" products.] ..  So the new tools are not direct substitutes for email; instead, they're intended to provide capabilities that email can't.  Will they succeed?  It depends  heavily, I believe, on whether companies and their managers want technology platforms for collaboration.  This desire will be an important factor in solving email's 9X problem. "
  1:44:26 PM  permalink  

How To Tell The Open Source Winners From The Losers: A 9-point checklist for evaluating open source solutions:
  1. "A thriving community: A handful of lead developers, a large body of contributors, and a substantial--or at least motivated--user group offering ideas.
  2. Disruptive goals:Does something notably better than commercial code. Free isn't enough.
  3. A benevolent dictator: Leader who can inspire and guide developers, asking the right questions and letting only the right code in.
  4. Transparency: Decisions are made openly, with threads of discussion, active mailing list, and negative and positive comments aired.
  5. Civility: Strong forums police against personal attacks or niggling issues, focus on big goals.
  6. Documentation: What good's a project that can't be implemented by those outside its development?
  7. Employed developers: The key developers need to work on it full time.
  8. A clear license: Some are very business friendly, others clear as mud.
  9. Commercial support: Companies need more than e-mail support from volunteers. Is there a solid company employing people you can call? "
  1:05:13 PM  permalink  


daily link  Monday, February 12, 2007


Eleven Emerging Ideas for SOA Architects in 2007:  Good listing of how web services are actually succeeding today.  "This is where the World Wide Web continues to teach us effective techniques for service consumption and adoption. .. This is using the basic Web formats and protocols such as HTTP, XML, REST, and JSON as the "Unix Pipe of the Web" -- to quote a colorful phrase of Ray Ozzie's -- as the fundamental glue between systems. This allows widgets, Ajax applications, and mashups to be wired together so quickly it can almost be done in real-time with the latest tools."
  8:36:07 AM  permalink  

Copyright 2007 © Ken Novak.
Last update: 2/22/2007; 1:46:56 PM.
0 page reads.