{"id":525,"date":"2006-12-12T11:24:15","date_gmt":"2006-12-12T18:24:15","guid":{"rendered":"http:\/\/www.redmonk.com\/cote\/wp\/?p=525"},"modified":"2006-12-12T11:24:15","modified_gmt":"2006-12-12T18:24:15","slug":"is-free-the-easiest-way-to-change-corporate-culture-or-low-barriers-to-entry-redux","status":"publish","type":"post","link":"https:\/\/redmonk.com\/cote\/2006\/12\/12\/is-free-the-easiest-way-to-change-corporate-culture-or-low-barriers-to-entry-redux\/","title":{"rendered":"Is Free the Easiest Way to Change Corporate Culture? Or, Low Barriers to Entry Redux"},"content":{"rendered":"<p>I often comment on how tedious it is for folks like me with shiny object syndrome to introduce new technologies into the enterprise. Indeed, <a href=\"http:\/\/www.drunkandretired.com\/category\/technical\/blogging\/\">many of the posts in my other blog over the years<\/a> were about <a href=\"http:\/\/www.drunkandretired.com\/2005\/01\/22\/enterprise-blogging-in-practice-notes\/\">the challenges<\/a> and <a href=\"http:\/\/www.drunkandretired.com\/2005\/01\/25\/re-enterprise-blogging-in-practice-notes\/\">&#8220;failures&#8221;<\/a> of getting blogs, wikis, and search setup behind-the-firewall.<\/p>\n<h2>Change by Committee<\/h2>\n<p>In my own experience and talking with others, even though introducing &#8220;Web 2.0&#8221; technologies was always tedious they eventually took hold or, at least, managed to hold on as they were slowly adopted. These technologies were always free &#8212; often open source &#8212; and rarely decided on officially by the company.<\/p>\n<p>In contrast, the stories I&#8217;ve heard about companies officially going through the motions of choosing a collaborative technology have been costly and long to deliver.<\/p>\n<h2>Low Risk Change<\/h2>\n<p>Now, these &#8220;technologies&#8221; are simple, user-centric applications like blogs, wikis, and search rather than <a href=\"http:\/\/en.wikipedia.org\/wiki\/Morlocks\">Morlock<\/a> stacks like ESBs, SOA stacks, and other nut-n-bolts complexities. A little before-hand architecture is called for when selecting what nuts-n-bolts you&#8217;re going to use. Or, at least, it&#8217;s good to try out several and then evaluate the bake-off winner.<\/p>\n<p>The key is that most collaborative and social software is low risk as far as wasting employee effort, cost, and damage to the business. Any application introduction will cause distraction, making command-and-control Scrooges think <a href=\"http:\/\/www.businessweek.com\/the_thread\/blogspotting\/archives\/2005\/10\/wasting_time_on.html\">employees are stealing time<\/a>; those folks probably need to shut off the &#8216;net.<\/p>\n<h2>Free Change<\/h2>\n<p>Back to the point though. This all begs the (rhetorical?) question: is free the easiest way to change corporate culture? If you have to pay for change, then you start thinking and evaluating change which has the potential to slow down that change.<\/p>\n<p>For vendors, this means using free offerings for long term corporate change. <a href=\"http:\/\/www.redmonk.com\/cote\/archives\/2006\/09\/we_do_what_the.html\">As I&#8217;ve bemoaned in the past<\/a>, vendor&#8217;s outbound product management often like to say they do only what the customer wants. That&#8217;s half of what product management should do when coming up with features and requirements: the rest of the time they should be coming up with new things customers will want once they see it.<\/p>\n<p>Invention is the child and parent of desire.<\/p>\n<p>And, as it goes, free is a great price for trying out change.<\/p>\n<p><!-- technorati tags start --><\/p>\n<p>Tags: <a href=\"http:\/\/www.technorati.com\/tag\/change\" rel=\"tag\">change<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/search\" rel=\"tag\">search<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/wikis\" rel=\"tag\">wikis<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/blogs\" rel=\"tag\">blogs<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/pricing\" rel=\"tag\">pricing<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/free\" rel=\"tag\">free<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/lowbarriers\" rel=\"tag\">lowbarriers<\/a><\/p>\n<p><!-- technorati tags end --><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I often comment on how tedious it is for folks like me with shiny object syndrome to introduce new technologies into the enterprise. Indeed, many of the posts in my other blog over the years were about the challenges and &#8220;failures&#8221; of getting blogs, wikis, and search setup behind-the-firewall. Change by Committee In my own [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[12,13,17,33],"tags":[],"class_list":["post-525","post","type-post","status-publish","format-standard","hentry","category-enterprise-software","category-ideas","category-marketing","category-social-software"],"acf":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/comments?post=525"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/525\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/media?parent=525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/categories?post=525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/tags?post=525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}