Will integrating “generative” attributes help EA adoption?

by | June 25, 2009

JP Rangaswami wrote an interesting post titled Mother of Invention. In it he discusses, Frank Zappa and piracy and as usual, he expands my understanding on this contentious topic. Thank you JP!

What really caught my eye was JP’s reference to Kevin Kelly’s article Better than Free. Kevin talks about the Internet being a super-distribution system where once a copy is introduced it flows freely forever.  So when everything is free or as close to free as possible, how do we make money? Kevin’s solution is pretty simple …

“When copies are super abundant, they become worthless.
When copies are super abundant, stuff which can’t be copied becomes scarce and valuable.

When copies are free, you need to sell things which can not be copied.”

Next Kevin talks about “generatives”.  Here is his definition:

“A generative value is a quality or attribute that must be generated, grown, cultivated, nurtured. A generative thing can not be copied, cloned, faked, replicated, counterfeited, or reproduced. It is generated uniquely, in place, over time.”

Kevin proposes 8 “generatives” listed below (please read Kevin’s article for the details on each):

  • Immediacy
  • Personalization
  • Interpretation
  • Authenticity
  • Accessibility
  • Embodiment
  • Patronage
  • Findability

This really got me thinking about how we approach introducing and maturing enterprise architecture in our organizations. How many of you made attempts to introduce EA practices and struggled in your organizations?  What do you do to attract clients to your EA service? Do you use a carrot or a stick? Why would people in your organization come to you for services?

Can we take Kevin’s “generatives” and apply them as principles of our EA practice? In a future post, I will comment on how I think applying Kevin’s “generatives” as guiding principles to delivering Enterprise Architecture.

If applications, services and technology are freely available in the cloud, why would our clients come to us? What can we create in an Enterprise Architecture service that is immediate, personalized, interpreted, authentic, accessible, aligned, appreciative and attributable?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.