Integration. This word/concept similar to application, component, data, service and so many other concerns in the software realm: it’s often the case that there are N + M meanings floating around a conversation with N people on the subject.
If you provide a portfolio of products to customers, integration is typically an important aspect of your offering. Do these products play well with each other? Can there inputs and outputs be combined into broader workflow, etc.?
Unfortunately I find that many integrations seems to be merely technical in nature–as if to answer “yes” to “can I technically integrate?” Much like answering “yes” to “do you know the time?” this strikes me as missing the point altogether.
Integrations must be about how should I deliver the right experience to my user. That is, integrations should be experience-driven.
So, what may be some of the signs that indicate a need for focused improvement?
Workflows that span across products involve multiple login experiences (interruptions).
Users are forced to deal with experiences designed for a persona other than their own.
Software concerns are not consistent and therefore are not intuitive (e.g. able to be reused spontaneously in new business contexts).
Integration gaps in product must be addressed via professional services, consulting or directly by customers.
Any of this sound familiar?
When I get involved in an integration-related project, I tend to think about the following layered concerns:
This approach involves:
an experience-driven focus on key business roles/personas and their workflows – user objective over product feature/function (seamless)
data and insight in context for better decisions and actions – mere hand-offs don’t add value (frictionless)
social as glue across users (relational) – provide others’ insights in context to facilitate further insight and action
How do you view and tackle integration in your own products?
Thanks to everyone at Day Ignite Berlin 2010 who came to the technical track session that I presented this afternoon. In order to keep the conversation going, I’ve uploaded this presentation as follows:
During this presentation I recommended that you consume my “Realizing great customer experiences with LiveCycle ES3″ presentation from Adobe MAX 2010, if you’re interested in more details about the architecture and capabilities of LiveCycle ES3. You will find that presentation here.
We’re very excited at Adobe about the opportunity to work with those at Day Software as fellow colleagues. By working together with you, we believe that great things will emerge from the unified delivery of content plus applications.
P.S. If you’re not already watching the #dayignite tweetstream, why not?
Update 10/22/2010: Presentations from Day Ignite Chicago 2010 are appearing here. Presentations that will also be delivered during Day Ignite Berlin 2010 won’t appear on Slideshare until after both events have concluded. (That being said, you can see a thorough write-up of David Nuescheler’s presentation here.) Event photos from Chicago are here.
Update on 10/27/2010: The message first delivered in Chicago around the unified delivery of content and applications was expanded upon in Los Angeles at Adobe MAX 2010, and that presentation is now available here.
My EMC colleague and OASIS CMIS TC chair, Dr. David Choy, will provide an overview of CMIS at 11:30am leading into the panel discussion. As a reminder to my fellow TC’ers, the panel is open to any TC member.
So, if you’re at AIIM info360 and want to learn more about CMIS, please join the discussion. You can also stop by the EMC booth (#825) for the duration of the expo. Cheers!
Yesterday at the AIIM info360 conference in Philadelphia, the iECM committee announced its sponsored demonstration of CMIS. The AIIM press release has more details here.
Today that demo is live: http://aiim-iecm.org/cmisdemoc/. If you’re at AIIM info360, please stop by the EMC booth (#825) for a personal tour of the demo application.
If you want to understand how the demo was made, I encourage you to read Pie’s account, especially since he was a central figure in producing the application above compliant repositories, including EMC.