<?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: A few thoughts on Yammer, a twitter-like for organizations</title>
	<atom:link href="http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/feed/" rel="self" type="application/rss+xml" />
	<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/</link>
	<description></description>
	<lastBuildDate>Thu, 15 Apr 2010 00:55:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Ross Jimenez</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-237</link>
		<dc:creator>Ross Jimenez</dc:creator>
		<pubDate>Fri, 04 Dec 2009 04:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-237</guid>
		<description>Good Post Julien… and I would have to agree with you.  It is especially difficult for the very largest of corporations and will lead simply to a &quot;block&quot; by default mentality.  This loss of confidence is what I have to deal with while trying to evangelize social tools internally which makes my job more difficult. &lt;br&gt;&lt;br&gt;In my mind Yammer could:  &lt;br&gt;&lt;br&gt;1.) Offer an opt-out capability that is allow a user from a company to request that they block users from their company, when someone from @email tries to sign-up they get an email with the person’s message who requested that they “block” sign-ups for the company.  This way the person could still engage with the individual to determine proper usage etc.&lt;br&gt;&lt;br&gt;2.) Would be to simply provide all management features with a limited number of users, say 50/100 users.</description>
		<content:encoded><![CDATA[<p>Good Post Julien… and I would have to agree with you.  It is especially difficult for the very largest of corporations and will lead simply to a “block” by default mentality.  This loss of confidence is what I have to deal with while trying to evangelize social tools internally which makes my job more difficult. </p>
<p>In my mind Yammer could:  </p>
<p>1.) Offer an opt-out capability that is allow a user from a company to request that they block users from their company, when someone from @email tries to sign-up they get an email with the person’s message who requested that they “block” sign-ups for the company.  This way the person could still engage with the individual to determine proper usage etc.</p>
<p>2.) Would be to simply provide all management features with a limited number of users, say 50/100 users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Jimenez</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-234</link>
		<dc:creator>Ross Jimenez</dc:creator>
		<pubDate>Thu, 03 Dec 2009 22:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-234</guid>
		<description>Good Post Julien… and I would have to agree with you.  It is especially difficult for the very largest of corporations and will lead simply to a &quot;block&quot; by default mentality.  This loss of confidence is what I have to deal with while trying to evangelize social tools internally which makes my job more difficult. &lt;br&gt;&lt;br&gt;In my mind Yammer could:  &lt;br&gt;&lt;br&gt;1.) Offer an opt-out capability that is allow a user from a company to request that they block users from their company, when someone from @email tries to sign-up they get an email with the person’s message who requested that they “block” sign-ups for the company.  This way the person could still engage with the individual to determine proper usage etc.&lt;br&gt;&lt;br&gt;2.) Would be to simply provide all management features with a limited number of users, say 50/100 users.</description>
		<content:encoded><![CDATA[<p>Good Post Julien… and I would have to agree with you.  It is especially difficult for the very largest of corporations and will lead simply to a “block” by default mentality.  This loss of confidence is what I have to deal with while trying to evangelize social tools internally which makes my job more difficult. </p>
<p>In my mind Yammer could:  </p>
<p>1.) Offer an opt-out capability that is allow a user from a company to request that they block users from their company, when someone from @email tries to sign-up they get an email with the person’s message who requested that they “block” sign-ups for the company.  This way the person could still engage with the individual to determine proper usage etc.</p>
<p>2.) Would be to simply provide all management features with a limited number of users, say 50/100 users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien Le Nestour</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-131</link>
		<dc:creator>Julien Le Nestour</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-131</guid>
		<description>Hi David -&lt;br&gt;Yes, I&#039;m following up to get more details on the Active Directory&lt;br&gt;integration, looking forward to it.&lt;br&gt;&lt;br&gt;The best model depends of the size and business of the company I think. For&lt;br&gt;large companies or companies in sensitive industries, the claiming model you&lt;br&gt;have and Present.ly adopted is a negative. For small and medium businesses,&lt;br&gt;it can be - wrongly in my opinion - appealing. So in the end, what matters&lt;br&gt;for the start-ups in this space are the respective market size of the 2&lt;br&gt;markets.&lt;br&gt;&lt;br&gt;I actually agree 100% with your last point, especially for social enterprise&lt;br&gt;software. Without directory integration, my reasoning is: employees can&#039;t&lt;br&gt;talk about business critical issues and if Yammer just used for casual&lt;br&gt;points, not much more value than twitter.&lt;br&gt;&lt;br&gt;We agree on the fact that employees should be the ones adopting an&lt;br&gt;application. IT functions need to give them the means to do it.&lt;br&gt;&lt;br&gt;To facilitate this process, I think adopting the right pricing model is&lt;br&gt;critical. I have described one possible model here:&lt;br&gt;&lt;a href=&quot;http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/&quot; rel=&quot;nofollow&quot;&gt;http://www.macroprinciples.com/2009/02/how-to-p...&lt;/a&gt;&lt;br&gt;&lt;br&gt;I would be really interested in your feedback on this point...&lt;br&gt;&lt;br&gt;Many thanks for the stimulating points!&lt;br&gt;&lt;br&gt;Best regards,&lt;br&gt;- Julien</description>
		<content:encoded><![CDATA[<p>Hi David -<br />Yes, I’m following up to get more details on the Active Directory<br />integration, looking forward to it.</p>
<p>The best model depends of the size and business of the company I think. For<br />large companies or companies in sensitive industries, the claiming model you<br />have and Present.ly adopted is a negative. For small and medium businesses,<br />it can be — wrongly in my opinion — appealing. So in the end, what matters<br />for the start-ups in this space are the respective market size of the 2<br />markets.</p>
<p>I actually agree 100% with your last point, especially for social enterprise<br />software. Without directory integration, my reasoning is: employees can’t<br />talk about business critical issues and if Yammer just used for casual<br />points, not much more value than twitter.</p>
<p>We agree on the fact that employees should be the ones adopting an<br />application. IT functions need to give them the means to do it.</p>
<p>To facilitate this process, I think adopting the right pricing model is<br />critical. I have described one possible model here:<br /><a href="http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/" rel="nofollow"></a><a href="http://www.macroprinciples.com/2009/02/how-to-p.." rel="nofollow">http://www.macroprinciples.com/2009/02/how-to-p..</a>.</p>
<p>I would be really interested in your feedback on this point…</p>
<p>Many thanks for the stimulating points!</p>
<p>Best regards,<br />- Julien</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Sacks</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-130</link>
		<dc:creator>David Sacks</dc:creator>
		<pubDate>Tue, 03 Mar 2009 17:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-130</guid>
		<description>Julien-&lt;br&gt;&lt;br&gt;Yammer now offers directory integration / SSO. We are piloting it with some early customers and then it will become part of our basic admin tools package on the website.&lt;br&gt;&lt;br&gt;Since your original article, Present.ly copied our approach of letting employees sign up with a company email address first, before the company claims the network. Obviously they did not believe that their model was the superior one.&lt;br&gt;&lt;br&gt;Seriously, what&#039;s the harm in letting employees test drive a product before the company buys it? Isn&#039;t that better than the alternative? How many times has IT purchased expensive software only to see no one adopt it? Yammer lets the employees prove the need before the company buys it.&lt;br&gt;&lt;br&gt;Regards,&lt;br&gt;&lt;br&gt;David &lt;br&gt;&lt;br&gt;PS: I like your idea of an enterprise TweetDeck. We will support it.</description>
		<content:encoded><![CDATA[<p>Julien–</p>
<p>Yammer now offers directory integration / SSO. We are piloting it with some early customers and then it will become part of our basic admin tools package on the website.</p>
<p>Since your original article, Present.ly copied our approach of letting employees sign up with a company email address first, before the company claims the network. Obviously they did not believe that their model was the superior one.</p>
<p>Seriously, what’s the harm in letting employees test drive a product before the company buys it? Isn’t that better than the alternative? How many times has IT purchased expensive software only to see no one adopt it? Yammer lets the employees prove the need before the company buys it.</p>
<p>Regards,</p>
<p>David </p>
<p>PS: I like your idea of an enterprise TweetDeck. We will support it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien Le Nestour</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-112</link>
		<dc:creator>Julien Le Nestour</dc:creator>
		<pubDate>Thu, 19 Feb 2009 10:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-112</guid>
		<description>Yes, it does.&lt;br&gt;&lt;br&gt;I have sent them an email to get more details on the specifics, as they do have an history of inflating their claims, but it looks certainly much better than before.</description>
		<content:encoded><![CDATA[<p>Yes, it does.</p>
<p>I have sent them an email to get more details on the specifics, as they do have an history of inflating their claims, but it looks certainly much better than before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jiponet</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-110</link>
		<dc:creator>jiponet</dc:creator>
		<pubDate>Wed, 18 Feb 2009 21:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-110</guid>
		<description>Interesting article Julien&lt;br&gt;&lt;br&gt;As Yammer announced that the Yammer software can be installed inside the company firewalls, does this change your views?&lt;br&gt;&lt;a href=&quot;http://blog.yammer.com/blog/2009/02/yammer-extends-microblogging-inside-the-corporate-firewall.html&quot; rel=&quot;nofollow&quot;&gt;http://blog.yammer.com/blog/2009/02/yammer-exte...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Interesting article Julien</p>
<p>As Yammer announced that the Yammer software can be installed inside the company firewalls, does this change your views?<br /><a href="http://blog.yammer.com/blog/2009/02/yammer-extends-microblogging-inside-the-corporate-firewall.html" rel="nofollow"></a><a href="http://blog.yammer.com/blog/2009/02/yammer-exte.." rel="nofollow">http://blog.yammer.com/blog/2009/02/yammer-exte..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bernardlunn</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-98</link>
		<dc:creator>bernardlunn</dc:creator>
		<pubDate>Wed, 07 Jan 2009 16:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-98</guid>
		<description>Julien, interesting thoughts in this and other posts. It is interesting to hear a POV from within a large enterprise. Pease send me an email so we can connect. Bernard</description>
		<content:encoded><![CDATA[<p>Julien, interesting thoughts in this and other posts. It is interesting to hear a POV from within a large enterprise. Pease send me an email so we can connect. Bernard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien Le Nestour</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-92</link>
		<dc:creator>Julien Le Nestour</dc:creator>
		<pubDate>Sat, 20 Dec 2008 20:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-92</guid>
		<description>David -&lt;br&gt;For former employees, SSO is the only viable option, and as you said you&lt;br&gt;don&#039;t provide it, yet you claim you provide a space only accessible to&lt;br&gt;current employees. This is just not true. All other options involve a manual&lt;br&gt;step by either admins or employees which renders them unusable when you have&lt;br&gt;more than a few hundreds users: you can&#039;t ask IT functions to manually&lt;br&gt;manage this, and if you do, you will have mistakes. And yes, all large&lt;br&gt;companies have experience of this type of mistakes in the past.&lt;br&gt;&lt;br&gt;IP filtering: some remote access solutions cannot be allowed with this. This&lt;br&gt;is not the most important point however: a large part of the value derived&lt;br&gt;from Twitter-like applications stems from their accessibility via SMS, from&lt;br&gt;any computer, etc. I don&#039;t see the point of deploying this if it can only be&lt;br&gt;used from the company&#039;s network or assets. Do I want to open my company&lt;br&gt;laptop and connect via VPN each time I want to update my status? Not at all.&lt;br&gt;This workaround limits too much the value of the application, especially as&lt;br&gt;a mobile application accessible on the go.&lt;br&gt;&lt;br&gt;So, no, until you offer SSO, Yammer doesn&#039;t handle former employees well. In&lt;br&gt;fact, claiming that is misleading because former employees can easily slip&lt;br&gt;through the manual monitoring and remain on the network for quite some time.&lt;br&gt;&lt;br&gt;Regarding the value of Yammer for security reasons over email, again this is&lt;br&gt;misleading, since you encourage the employees to create content that&lt;br&gt;companies will want to control, and you make companies pay afterwards. I&lt;br&gt;could go on and on. As Stowe Boyd found&lt;br&gt;out&lt;http://www.stoweboyd.com/message/2008/12/presently---cre.html&gt;as&lt;br&gt;well,&lt;br&gt;Present.ly is a much more attractive Twitter-like application for companies,&lt;br&gt;with a much cleaner business model.&lt;br&gt;&lt;br&gt;Adopting an aggressive tone by arguing my &quot;slandering of Yammer is&lt;br&gt;preposterous&quot; won&#039;t change the fact that your business model is essentially&lt;br&gt;based on a new twist of racketing companies to take back the control over an&lt;br&gt;unsecure discussion space.&lt;br&gt;&lt;br&gt;PS: And when you will have SSO, you will again make companies pay for the&lt;br&gt;privilege to have SSO implemented on their network. I stand by my position,&lt;br&gt;and would advise anyone to ban access to Yammer from the corporate network,&lt;br&gt;make it against policy to contribute to it, while at the same time implement&lt;br&gt;an alternative like Present.ly where price and control can be managed&lt;br&gt;properly.&lt;br&gt;&lt;br&gt;PPS: Reminder of my disclaimer: as anything on this website, this is my&lt;br&gt;personal opinion, not a professional one nor is it related in any way to the&lt;br&gt;positions or actions of my employer.</description>
		<content:encoded><![CDATA[<p>David -<br />For former employees, SSO is the only viable option, and as you said you<br />don’t provide it, yet you claim you provide a space only accessible to<br />current employees. This is just not true. All other options involve a manual<br />step by either admins or employees which renders them unusable when you have<br />more than a few hundreds users: you can’t ask IT functions to manually<br />manage this, and if you do, you will have mistakes. And yes, all large<br />companies have experience of this type of mistakes in the past.</p>
<p>IP filtering: some remote access solutions cannot be allowed with this. This<br />is not the most important point however: a large part of the value derived<br />from Twitter-like applications stems from their accessibility via SMS, from<br />any computer, etc. I don’t see the point of deploying this if it can only be<br />used from the company’s network or assets. Do I want to open my company<br />laptop and connect via VPN each time I want to update my status? Not at all.<br />This workaround limits too much the value of the application, especially as<br />a mobile application accessible on the go.</p>
<p>So, no, until you offer SSO, Yammer doesn’t handle former employees well. In<br />fact, claiming that is misleading because former employees can easily slip<br />through the manual monitoring and remain on the network for quite some time.</p>
<p>Regarding the value of Yammer for security reasons over email, again this is<br />misleading, since you encourage the employees to create content that<br />companies will want to control, and you make companies pay afterwards. I<br />could go on and on. As Stowe Boyd found<br />out&lt;http://www.stoweboyd.com/message/2008/12/presently—cre.html&gt;as<br />well,<br />Present.ly is a much more attractive Twitter-like application for companies,<br />with a much cleaner business model.</p>
<p>Adopting an aggressive tone by arguing my “slandering of Yammer is<br />preposterous” won’t change the fact that your business model is essentially<br />based on a new twist of racketing companies to take back the control over an<br />unsecure discussion space.</p>
<p>PS: And when you will have SSO, you will again make companies pay for the<br />privilege to have SSO implemented on their network. I stand by my position,<br />and would advise anyone to ban access to Yammer from the corporate network,<br />make it against policy to contribute to it, while at the same time implement<br />an alternative like Present.ly where price and control can be managed<br />properly.</p>
<p>PPS: Reminder of my disclaimer: as anything on this website, this is my<br />personal opinion, not a professional one nor is it related in any way to the<br />positions or actions of my employer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Sacks</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-91</link>
		<dc:creator>David Sacks</dc:creator>
		<pubDate>Sat, 20 Dec 2008 18:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-91</guid>
		<description>Julien:&lt;br&gt;&lt;br&gt;In contrast to your assertions, Yammer handles the case of former employees well. First of all, company admins can easily remove former employees. The community can also police itself by requiring any user to re-confirm their company email address at any time. For large companies, Yammer plans to add single sign-on / directory integration shortly. &lt;br&gt;&lt;br&gt;Companies can also restrict access to their Yammer network to a particular IP range, such as their VPN. You fail to explain why this would not keep out former employees.&lt;br&gt;&lt;br&gt;Yammer also provides a huge advantage over traditional communications like email: former employees can easily take company emails with them, or forward them to someone outside the company. Yammer content stays within the company&#039;s network on Yammer, where it can be controlled, deleted, or exported by company admins.&lt;br&gt;&lt;br&gt;Your claim to advance the interests of SaaS by slandering Yammer is preposterous.&lt;br&gt;&lt;br&gt;Regards,&lt;br&gt;&lt;br&gt;David Sacks&lt;br&gt;CEO, Yammer</description>
		<content:encoded><![CDATA[<p>Julien:</p>
<p>In contrast to your assertions, Yammer handles the case of former employees well. First of all, company admins can easily remove former employees. The community can also police itself by requiring any user to re-confirm their company email address at any time. For large companies, Yammer plans to add single sign-on / directory integration shortly. </p>
<p>Companies can also restrict access to their Yammer network to a particular IP range, such as their VPN. You fail to explain why this would not keep out former employees.</p>
<p>Yammer also provides a huge advantage over traditional communications like email: former employees can easily take company emails with them, or forward them to someone outside the company. Yammer content stays within the company’s network on Yammer, where it can be controlled, deleted, or exported by company admins.</p>
<p>Your claim to advance the interests of SaaS by slandering Yammer is preposterous.</p>
<p>Regards,</p>
<p>David Sacks<br />CEO, Yammer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Posts about Web 2.0 as of December 19, 2008 &#124; The Lessnau Lounge</title>
		<link>http://coreedges.com/blog/2008/12/19/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/comment-page-1/#comment-90</link>
		<dc:creator>Posts about Web 2.0 as of December 19, 2008 &#124; The Lessnau Lounge</dc:creator>
		<pubDate>Fri, 19 Dec 2008 19:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2008/12/a-few-thoughts-on-yammer-a-twitter-like-for-organizations/#comment-90</guid>
		<description>[...] range from podcasts, video, wikis, blogs, web syndication, Web 2.0 &#8230; Networks, Web 2.0   A few thoughts on Yammer, a twitter-like for organizations - macroprinciples.com 12/19/2008 Yammer is an SAAS clone of Twitter, providing private networks for [...]</description>
		<content:encoded><![CDATA[<p>[…] range from podcasts, video, wikis, blogs, web syndication, Web 2.0 … Networks, Web 2.0   A few thoughts on Yammer, a twitter-like for organizations — macroprinciples.com 12/19/2008 Yammer is an SAAS clone of Twitter, providing private networks for […]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
