Fourth parties

From Project VRM
Revision as of 08:31, 10 May 2010 by Dsearls (talk | contribs) (New page: Fourth parties are to customers what third parties are to vendors. They are companies that work primarily for customers, and make most of their money by helping customers buy, rather than ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Fourth parties are to customers what third parties are to vendors. They are companies that work primarily for customers, and make most of their money by helping customers buy, rather than helping vendors sell. As customers acquire more native ability through VRM tools, it is only natural that fourth parties will arrive to help customers use those tools, and to add services that amplify the power of those tools and their users.

The idea of fourth parties came up during conversations within the VRM community. It is unpacked several places, but at this writing the best example is this post on the ProjectVRM blog.

Fourth parties are by definition what Joe Andrieu calls user driven services, which he explains in ten additional posts:

  1. Impulse from the User
  2. Control
  3. Transparency
  4. Data Portability
  5. Service Endpoint Portability
  6. Self Hosting
  7. User Generativity
  8. http://blog.joeandrieu.com/2009/05/12/user-driven-services-8-improvability/[ Improvability]
  9. Self-managed Identity
  10. Duty of Care