<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-8670942274168320118.post8440512766189718335..comments</id><updated>2010-06-29T20:50:33.306+01:00</updated><category term='Book Review'/><category term='Mobile SQL'/><category term='XSLT'/><category term='SOA Governance'/><category term='QA'/><category term='Access Manager'/><category term='ESB'/><category term='Web Services'/><category term='SCA'/><category term='IFX'/><category term='Security'/><category term='Custom Functions'/><category term='Oracle'/><category term='ABA Check Digit Validation Java'/><category term='IBAN'/><category term='WebLogic'/><category term='PSR'/><category term='OC4J'/><category term='Testing'/><category term='JDeveloper'/><category term='Fusion CRM'/><category term='SOA Suite'/><category term='Social CRM'/><category term='SaaS'/><category term='Oracle BPEL'/><category term='Agile'/><category term='Oracle XE'/><category term='Siebel'/><category term='JAXB'/><category term='11g'/><category term='Oracle ADF'/><category term='JwscTask'/><category term='SOA Maturity Model'/><category term='Oracle ESB'/><category term='Oracle Lite'/><category term='JAX-WS'/><category term='Glassfish'/><category term='JBOSS'/><category term='JEE'/><category term='Ireland'/><title type='text'>Comments on SOA Station: Mind the gap!: What's the bedrock to your Social CRM Strategy?</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.soastation.org/feeds/8440512766189718335/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8670942274168320118/8440512766189718335/comments/default'/><link rel='alternate' type='text/html' href='http://www.soastation.org/2009/10/whats-bedrock-to-your-social-crm.html'/><author><name>Peter O'Brien</name><uri>http://www.blogger.com/profile/05549543084958276823</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='31' height='32' src='http://3.bp.blogspot.com/_QdWe1hGsnN4/SstOf9bmAeI/AAAAAAAAAEA/qSamqMs5h6Q/S220/pobrien_sydney.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>1</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8670942274168320118.post-793784874714906907</id><published>2009-10-22T06:31:48.421+01:00</published><updated>2009-10-22T06:31:48.421+01:00</updated><title type='text'>Peter,

We are talking miles apart.  

My post tal...</title><content type='html'>Peter,&lt;br /&gt;&lt;br /&gt;We are talking miles apart.  &lt;br /&gt;&lt;br /&gt;My post talks about a top level discussion regarding the organization implementing SCRM.&lt;br /&gt;&lt;br /&gt;Strategically speaking, conversations at the levels where you need the support to embrace SCRM as an organization are far removed from the policy details.  &lt;br /&gt;&lt;br /&gt;The SM policy, as I said in my blog, is part of the rules layer (second from the top) and it is not a stand-alone document.  It is deeply intertwined with metrics, business rules, segmentation and other rules that apply to a business working with customers.&lt;br /&gt;&lt;br /&gt;An SM policy cannot be a stand-alone document - even at the beginning.  You can have some steadfast rules to manage the level of exposure as an organization, but setting a policy before you even know which channels or what objectives you will use is preposterous - is basically what the armed forces did by banning use of SM without knowing why or how to replace it (and look how well it turned out for them).&lt;br /&gt;&lt;br /&gt;There is much more to a SM policy than DOs and DON&amp;#39;Ts, There has to be a reason for them, and a escalation method, and a way to bypass them for specific cases that fall outside of the rules, etc.  In other words, social channels are no different (or should not be any different from the perspective of management and users) than other channels.  There are rules and regulations regarding use of call center channels (i.e. phone), contact center channels (email and chat primarily) and in-person interactions.&lt;br /&gt;&lt;br /&gt;Why would SM be different?&lt;br /&gt;&lt;br /&gt;Very interesting post, thanks for the ping to mine -- much appreciated.  Should cover the use of SM policies in my series around Friday or early next week -- will ping you when it is out.&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;Esteban</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8670942274168320118/8440512766189718335/comments/default/793784874714906907'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8670942274168320118/8440512766189718335/comments/default/793784874714906907'/><link rel='alternate' type='text/html' href='http://www.soastation.org/2009/10/whats-bedrock-to-your-social-crm.html?showComment=1256189508421#c793784874714906907' title=''/><author><name>Esteban Kolsky</name><uri>http://www.estebankolsky.com</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.soastation.org/2009/10/whats-bedrock-to-your-social-crm.html' ref='tag:blogger.com,1999:blog-8670942274168320118.post-8440512766189718335' source='http://www.blogger.com/feeds/8670942274168320118/posts/default/8440512766189718335' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-451874496'/></entry></feed>
