Blogs

RedMonk

Skip to content

What is packaging? It’s all about the barrier to entry.

Something my esteemed colleagues James and Steve been talking about for years here 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 and use, 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, as I’ve been talking about over the past week using the metaphor of chemical reactions.

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. Here are some examples of packaging:

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

Winning customers with superior packaging holds true from the cheapest mobile apps to the 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 Predictive Analysis) and IBM (the Cognos family), which focus on ease of use for anyone, not just experts.

Nobody is free from the need to do this well, particularly with broader trends like the consumerization of IT taking a solid grip on the world.

Disclosure: IBM and SAP are both clients.

by-sa

Categories: adoption, ibm, open-source.

Comment Feed

7 Responses

  1. I recently came across a great form of packaging that is not only automatic, it is free.
    If you’re one of the multitude of developers at github, all you needdo to package your code is to tag it. Github then automatically creates zip and tgz files for you, and puts them in the Downloads section! No more that dreary task of zip ./…  and tar cfz … . Just write the code and tag it.

    dave shields

    dave shieldsJuly 23, 2012 @ 10:40 pmReply
  2. great post donny. this is exactly why we’re doing the Adobe PhoneGap distro of Cordova and also PhoneGap Build.



Some HTML is OK

or, reply to this post via trackback.

Continuing the Discussion

  1. […] system, and I expect anything resembling a successful app server in the future will in reality be a packaging exercise of many components that have already gained developer traction, with mix-and-match pieces […]

  2. […] experience, which surprisingly focuses on a lot of things that coders consider peripheral, such as packaging, barriers to entry, and convenience. My colleague James describes it briefly in this off-the-cuff […]

  3. […] is completely the wrong model. We’ve been talking about the importance of the barrier to entry for many years, and a PDF writeup and illustration of a reference architecture is a perfect example […]

  4. […] In my mind this always starts with installation – essentially your packaging, its the first experience a user has of your product. If the install experience is poor you have already started on a very difficult path in convincing your customer that your technology is the right one for them to use. The folks over at Redmonk have been highlighting packaging for years. […]

  5. […] In 2013, the major unappreciated theme was packaging Big Data so it was consumable by end users. That no longer seems to be the case, with packaging dropping down from 2nd to 6th place in the list. This implies that Hadoop has become much easier to get up and running than it was in 2013, which is a key blocker to adoption. […]