<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Where should collaboration sit?</title>
	<atom:link href="http://netjmc.com/intranet-strategy/positioning/where-should-collaboration-sit/feed" rel="self" type="application/rss+xml" />
	<link>http://netjmc.com/intranet-strategy/positioning/where-should-collaboration-sit</link>
	<description>Digital Workplace Strategy &#38; Governance</description>
	<lastBuildDate>Thu, 26 Jan 2012 15:30:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jane McConnell</title>
		<link>http://netjmc.com/intranet-strategy/positioning/where-should-collaboration-sit/comment-page-1#comment-232</link>
		<dc:creator>Jane McConnell</dc:creator>
		<pubDate>Fri, 27 Mar 2009 16:06:49 +0000</pubDate>
		<guid isPermaLink="false">http://wntr.org/tempjmc/2009/03/where-should-collaboration-sit/#comment-232</guid>
		<description>Peter - why will some IA/UX people shoot it down?</description>
		<content:encoded><![CDATA[<p>Peter &#8211; why will some IA/UX people shoot it down?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jane McConnell</title>
		<link>http://netjmc.com/intranet-strategy/positioning/where-should-collaboration-sit/comment-page-1#comment-231</link>
		<dc:creator>Jane McConnell</dc:creator>
		<pubDate>Fri, 27 Mar 2009 16:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://wntr.org/tempjmc/2009/03/where-should-collaboration-sit/#comment-231</guid>
		<description>Mike - one comment on what you have described:
I think making collaboration spaces centralised with a decentralised look and feel is good. Increased visibility. More local appropriation.
However, some global organizations have bandwith issues when too much is centralized and there is lots of &quot;local&quot; activity in these places.</description>
		<content:encoded><![CDATA[<p>Mike &#8211; one comment on what you have described:<br />
I think making collaboration spaces centralised with a decentralised look and feel is good. Increased visibility. More local appropriation.<br />
However, some global organizations have bandwith issues when too much is centralized and there is lots of &#8220;local&#8221; activity in these places.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Smith</title>
		<link>http://netjmc.com/intranet-strategy/positioning/where-should-collaboration-sit/comment-page-1#comment-230</link>
		<dc:creator>Peter Smith</dc:creator>
		<pubDate>Thu, 26 Mar 2009 11:59:50 +0000</pubDate>
		<guid isPermaLink="false">http://wntr.org/tempjmc/2009/03/where-should-collaboration-sit/#comment-230</guid>
		<description>Whilst some of the IA/UX people will shoot it down, I still believe that the top level navigation has a role to play in constantly reminding everyone what &quot;intranet&quot; has turned into today. It also helps to get an shared understanding of how separate technologies, services and stakeholder perspectives can be brought together under the &quot;intranet&quot; umbrella without rocking the boat too much
&quot;Homepage&quot; : Communication
Tab 1      : MyWork/Job (MSS,webapps,role specific tools etc)
Tab 2      : Collaboration (access to and orientation of how to use)
Tab 3      : Me &amp; &quot;the Organization&quot; (ESS, identity etc)
Ok it is not perfect, may want some collab activity around comms, but lets keep it simple so it works.</description>
		<content:encoded><![CDATA[<p>Whilst some of the IA/UX people will shoot it down, I still believe that the top level navigation has a role to play in constantly reminding everyone what &#8220;intranet&#8221; has turned into today. It also helps to get an shared understanding of how separate technologies, services and stakeholder perspectives can be brought together under the &#8220;intranet&#8221; umbrella without rocking the boat too much<br />
&#8220;Homepage&#8221; : Communication<br />
Tab 1      : MyWork/Job (MSS,webapps,role specific tools etc)<br />
Tab 2      : Collaboration (access to and orientation of how to use)<br />
Tab 3      : Me &#038; &#8220;the Organization&#8221; (ESS, identity etc)<br />
Ok it is not perfect, may want some collab activity around comms, but lets keep it simple so it works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Morley</title>
		<link>http://netjmc.com/intranet-strategy/positioning/where-should-collaboration-sit/comment-page-1#comment-229</link>
		<dc:creator>Mike Morley</dc:creator>
		<pubDate>Tue, 10 Mar 2009 22:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://wntr.org/tempjmc/2009/03/where-should-collaboration-sit/#comment-229</guid>
		<description>Greetings - My Company recently converted all the user interfaces (employee and partner) to a WEB 2.0 framework that’s improved communications and cross team collaboration. It’s a game changer for us and the ROI and TCO models I have seen are impressive. It wasn’t a massive IT overhaul rather it’s a thin layer that resides between the user and the core systems.
I&#039;m going to try benchmark the areas in which you&#039;re working on to see how we stack.
Should collaboration sit inside or beside the intranet?  In the intranet yes, the intranet should be the center of the company’s employee access for information and systems.  With a WEB 2.0 portal interface the Intranet should be personalized to the level of system access based on employee credential.
Should the collaborative spaces be distributed or centralized? We choose Centralized with a distributed look and feel based on user login (personalization), e.g. Region, Brand, Department level, ect.
How high up in the navigation should the &quot;Collaboration&quot; area be placed? We have general public collab spaces but then we integrated the collab with our PMO software where blogs and wiki’s can become tied to the specific project which is proprietary and sensitive to the project community of internal and external resources. Thus becoming a valuable knowledge base for our company to search into.
Who owns collaboration? The executives of our company took every tool that is widely used and made it fall under the WEB 2.0 interface.
Each one of these questions can go a mile deep in discussion with right or wrongs.  But I thought I’d make contact and state my experience and commend you on the fine job you’re doing in this space.  Big Fan.</description>
		<content:encoded><![CDATA[<p>Greetings &#8211; My Company recently converted all the user interfaces (employee and partner) to a WEB 2.0 framework that’s improved communications and cross team collaboration. It’s a game changer for us and the ROI and TCO models I have seen are impressive. It wasn’t a massive IT overhaul rather it’s a thin layer that resides between the user and the core systems.<br />
I&#8217;m going to try benchmark the areas in which you&#8217;re working on to see how we stack.<br />
Should collaboration sit inside or beside the intranet?  In the intranet yes, the intranet should be the center of the company’s employee access for information and systems.  With a WEB 2.0 portal interface the Intranet should be personalized to the level of system access based on employee credential.<br />
Should the collaborative spaces be distributed or centralized? We choose Centralized with a distributed look and feel based on user login (personalization), e.g. Region, Brand, Department level, ect.<br />
How high up in the navigation should the &#8220;Collaboration&#8221; area be placed? We have general public collab spaces but then we integrated the collab with our PMO software where blogs and wiki’s can become tied to the specific project which is proprietary and sensitive to the project community of internal and external resources. Thus becoming a valuable knowledge base for our company to search into.<br />
Who owns collaboration? The executives of our company took every tool that is widely used and made it fall under the WEB 2.0 interface.<br />
Each one of these questions can go a mile deep in discussion with right or wrongs.  But I thought I’d make contact and state my experience and commend you on the fine job you’re doing in this space.  Big Fan.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

