{"id":546,"date":"2012-07-23T17:03:51","date_gmt":"2012-07-23T22:03:51","guid":{"rendered":"http:\/\/redmonk.com\/dberkholz\/?p=546"},"modified":"2012-07-23T21:42:16","modified_gmt":"2012-07-24T02:42:16","slug":"what-is-packaging-its-all-about-the-barrier-to-entry","status":"publish","type":"post","link":"https:\/\/redmonk.com\/dberkholz\/2012\/07\/23\/what-is-packaging-its-all-about-the-barrier-to-entry\/","title":{"rendered":"What is packaging? It’s all about the barrier to entry."},"content":{"rendered":"

Something my esteemed colleagues James and Steve been talking<\/a> about<\/a> for<\/a> years<\/a>\u00a0here<\/a> at RedMonk is the value of packaging<\/strong>. But what is packaging, you ask? It’s not just the boxes you used to buy software CDs in, or the way software is supplied in most Linux distributions.<\/p>\n

Packaging means the user experience of software delivery and use<\/strong>, whether it’s run locally or in the cloud, as a command-line script or a Web 2.0 SaaS app. It’s about catalyzing the barrier to entry<\/a>, as I’ve been talking about over the past week using the metaphor of chemical reactions<\/a>.<\/p>\n

It’s often not the technically superior solution that comes out on top, but rather the one that’s easiest to discover, obtain, install and use<\/strong>. Here are some examples of packaging:<\/p>\n

    \n
  1. Obtaining and installing software is easier through mobile app stores than downloading individual apps, and the latter is often made purposely difficult;<\/li>\n
  2. For open-source software, using a standardized build system like autotools or ant instead of a homegrown, handwritten set of Makefiles;<\/li>\n
  3. Providing software as a SaaS app instead of requiring people to download it and set it up;<\/li>\n
  4. If they need it locally, giving them a virtual or physical appliance, preferably one that’s managed for them;<\/li>\n
  5. Improving the usability and modernity of your software to fit the latest standards in look and feel;<\/li>\n
  6. Creating a great set of documentation that makes your software a pleasure to use;<\/li>\n
  7. Redesigning your website to make it easy for people to find the information they want and download your software;<\/li>\n
  8. Building a superb community that draws new users to your software because of its helpfulness;<\/li>\n
  9. Having a tiered pricing structure including a very cheap or free model to encourage people to try your software before they need to commit; and<\/li>\n
  10. Enabling self service to the greatest extent possible so users can quickly and easily begin using your software.<\/li>\n<\/ol>\n

    Winning customers with superior packaging holds true from the cheapest mobile apps to\u00a0the most complex and expensive software. Even the biggest enterprise companies, like IBM, believe this. At this spring’s IBM Tivoli conference (Pulse), I saw a demo of the old and new versions of Maximo asset-management software, and the visual difference (ease of use, thus packaging) boggled the mind. It went from something that looked like it came out of Windows 95 to a modern, user-friendly app. We’re also seeing it with analytics software coming out of places like SAP (BusinessObjects\u00a0Predictive Analysis) and IBM (the Cognos family), which focus on ease of use for anyone, not just experts.<\/p>\n

    Nobody is free from the need to do this well, particularly with broader trends like the consumerization of IT<\/a>\u00a0taking a solid grip on the world.<\/p>\n

    Disclosure: IBM and SAP are both clients.<\/em><\/p>\n

    \"by-sa\"<\/a><\/div>","protected":false},"excerpt":{"rendered":"

    Something my esteemed colleagues James and Steve been talking about for years\u00a0here at RedMonk is the value of packaging. But what is packaging, you ask? It’s not just the boxes you used to buy software CDs in, or the way software is supplied in most Linux distributions. Packaging means the user experience of software delivery<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[3,9,13],"tags":[],"class_list":["post-546","post","type-post","status-publish","format-standard","hentry","category-adoption","category-ibm","category-open-source"],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p23Tsn-8O","_links":{"self":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/posts\/546","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/comments?post=546"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/posts\/546\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/media?parent=546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/categories?post=546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/tags?post=546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}