{"id":1061,"date":"2008-02-07T11:07:20","date_gmt":"2008-02-07T18:07:20","guid":{"rendered":"https:\/\/www.roughtype.com\/wp\/?p=1061"},"modified":"2008-02-07T11:07:20","modified_gmt":"2008-02-07T18:07:20","slug":"sneaking_behind","status":"publish","type":"post","link":"https:\/\/www.roughtype.com\/?p=1061","title":{"rendered":"Sneaking behind IT&#8217;s back"},"content":{"rendered":"<p>There are two ways that big advances happen in business IT. One way is top down: the powers that be &#8211; IT departments and corporate executives &#8211; make a decision to bring a new system into a company, and employees are required, either happily or unhappily, to use the system. Think, for instance, of the installation of a big ERP system from SAP or Oracle. The other way is bottom up: individual employees or business units begin using a new technology, without any formal imprimatur from higher-ups, and it proves so valuable that IT departments and corporate execs have no choice but to embrace it. Think of instant messaging or, on a much larger scale, the PC revolution. Top-down technologies tend to be expensive (requiring their own line in a corporate budget), while the bottom-up ones tend to be fairly cheap (a person can put it on a credit card).<\/p>\n<p>Web apps &#8211; the ones that run in the &#8220;cloud&#8221; rather than from your hard drive or from the server room down the hall &#8211; are mainly taking the bottom up route. The early adopters of Salesforce.com&#8217;s CRM service tended to be the salespeople in smaller companies or in individual business units. Because adopting Salesforce didn&#8217;t require a capital outlay &#8211; it was just a monthly expense &#8211; it didn&#8217;t require a lot of formal approvals from higher-ups. IT departments weren&#8217;t always happy, but they had little choice but to adapt as the service took hold. In most companies, after all, business units have more power than IT units.<\/p>\n<p>Google&#8217;s <a href=\"http:\/\/www.nytimes.com\/idg\/IDG_002570DE00740E18002573E70076F8A2.html?ref=technology\">announcement<\/a> yesterday of a new &#8220;team edition&#8221; of its Apps suite of personal productivity programs is an effort to spur the bottom-up adoption of the programs in companies and other organizations. Up to now, there have been two ways to use Google Apps. You could sign up for a Google account and use the separate programs &#8211; Docs, Spreadsheets, etc. &#8211; as an individual. That&#8217;s free and easy, but it has some limitations when it comes to business use. For one thing, it lacks security controls &#8211; documents can be shared easily with anyone, whether inside or outside a company. More important, there&#8217;s no easy way to see who else in your company or your unit is using the programs, so setting up collaborative efforts is a bit cumbersome.<\/p>\n<p>The second, more formal way is to have your company set up a formal Google Apps account linked to its Internet domain. This method provides a lot more security and eases collaboration, but it requires the involvement of IT staff. Your company has to formally approve Apps before you can use it &#8211; and that approval can be hard to come by, particularly in a large company with all its bureaucratic rigamarole.<\/p>\n<p>The team edition offers a third route. It&#8217;s basically the Facebook model: your email address is your personal identifier and, because it&#8217;s tied to your company&#8217;s domain, provides an easy way to define the company you&#8217;re associated with. So if you sign up for a team account, you can immediately see who else in your company has signed up and, for security purposes, you can easily restrict access to just your coworkers. You can, in other words, gain most of the advantages of the formal Google Apps system without having to get approval or assistance from your IT department. As Google&#8217;s Rajen Seth <a href=\"http:\/\/blogs.zdnet.com\/BTL\/?p=7911\">told<\/a> Dan Farber, \u201cIn previous versions of Google Apps &#8230; the IT department had to get involved in verifying domains and centrally managing users. With the Team Edition a project group can use Google Docs on a project or the Calendar, and individuals on a team can sign up just using their email address.&#8221; And the team edition is free, so you don&#8217;t even need a credit card.<\/p>\n<p>By easing the grassroots adoption of Apps, Google hopes to begin reshaping the way employees &#8211; and then employers &#8211; think about personal productivity apps. The idea isn&#8217;t to displace, say, Microsoft Office, but to complement it, providing a simple way to collaborate on documents and other files. As the use of Apps becomes more established, it becomes natural for companies to formally adopt the programs to gain further capabilities and controls. In the process, they&#8217;ll probably also sign up for the premium edition, which requires a $50 per user subscription. And then, in the long run, people start realizing that they&#8217;re doing pretty much everything they need to do within the web apps, and they start asking themselves: why exactly are we still licensing the old-fashioned versions of these programs and suffering the expense and nuisance of installing and running them on all our PCs?<\/p>\n<p>And then the bottom-up revolution is complete. Or so Google hopes &#8211; and Microsoft fears.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There are two ways that big advances happen in business IT. One way is top down: the powers that be &#8211; IT departments and corporate executives &#8211; make a decision to bring a new system into a company, and employees are required, either happily or unhappily, to use the system. Think, for instance, of the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-1061","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/1061","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1061"}],"version-history":[{"count":0,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/1061\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1061"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1061"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1061"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}