<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Architectural Principles for Enterprise Social Software</title>
	<atom:link href="http://binaryplex.com/2008/06/05/architectural-principles-for-enterprise-social-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://binaryplex.com/2008/06/05/architectural-principles-for-enterprise-social-software/</link>
	<description>The often random thoughts of an Eclectic Architect, Enterprise Technologist, Coffee Addict &#38; Social Media Junkie</description>
	<pubDate>Thu, 04 Dec 2008 22:36:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: binaryplex.com &#187; Blog Archive &#187; 10 Architectural Principles for Enterprise Social Software - Take 2</title>
		<link>http://binaryplex.com/2008/06/05/architectural-principles-for-enterprise-social-software/#comment-442</link>
		<dc:creator>binaryplex.com &#187; Blog Archive &#187; 10 Architectural Principles for Enterprise Social Software - Take 2</dc:creator>
		<pubDate>Fri, 13 Jun 2008 15:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://binaryplex.com/?p=80#comment-442</guid>
		<description>[...] first draft of the Architectural Principles for Enterprise Social Software was posted here. I invited feedback and was fortunate to get some comments from Luis Benitez, an IBM architect who [...]</description>
		<content:encoded><![CDATA[<p>[...] first draft of the Architectural Principles for Enterprise Social Software was posted here. I invited feedback and was fortunate to get some comments from Luis Benitez, an IBM architect who [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Benitez</title>
		<link>http://binaryplex.com/2008/06/05/architectural-principles-for-enterprise-social-software/#comment-441</link>
		<dc:creator>Luis Benitez</dc:creator>
		<pubDate>Tue, 10 Jun 2008 22:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://binaryplex.com/?p=80#comment-441</guid>
		<description>Great post!  You've hit the nail right on the head -- mutliple times!!! Principle 3 is key... how easy is it to use Facebook and Twitter from a BlackBerry?  Ubiquitous access *drives* social software adoption.  That's why I think Lotus Connections is great.. it ships with plug-ins out of the box for BlackBerry, Microsoft Office, Outlook, Windows Explorer, Lotus Notes, Sametime, and WebSphere Portal!!   

Principle 6 it's also right on! In fact, I'm blogging about this as we speak (stay tuned to my blog).  As a developer, one of the reasons why I like Lotus Connections is because there's so much you can do simply by configuration and NOT customization.  

Here are a couple of principles I would add:
* Principle 8: Simple, easy to use UI (Google, Twitter have no documentation)
* Principle 9: No workflow to create content -- requiring workflow, I argue, is a barrier to social software adoption
* Principle 10: Internationalization -- Facebook has faced increased growth after they translated their UI into multiple languages

What do you think ?</description>
		<content:encoded><![CDATA[<p>Great post!  You&#8217;ve hit the nail right on the head &#8212; mutliple times!!! Principle 3 is key&#8230; how easy is it to use Facebook and Twitter from a BlackBerry?  Ubiquitous access *drives* social software adoption.  That&#8217;s why I think Lotus Connections is great.. it ships with plug-ins out of the box for BlackBerry, Microsoft Office, Outlook, Windows Explorer, Lotus Notes, Sametime, and WebSphere Portal!!   </p>
<p>Principle 6 it&#8217;s also right on! In fact, I&#8217;m blogging about this as we speak (stay tuned to my blog).  As a developer, one of the reasons why I like Lotus Connections is because there&#8217;s so much you can do simply by configuration and NOT customization.  </p>
<p>Here are a couple of principles I would add:<br />
* Principle 8: Simple, easy to use UI (Google, Twitter have no documentation)<br />
* Principle 9: No workflow to create content &#8212; requiring workflow, I argue, is a barrier to social software adoption<br />
* Principle 10: Internationalization &#8212; Facebook has faced increased growth after they translated their UI into multiple languages</p>
<p>What do you think ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
