No Product is an Island

by stevew on February 12, 2010

Post image for No Product is an Island

As I left Reuters (now Thomson Reuters) at the tail end of 1998, grand dreams about the kind of business I was going to build soon gave way to cold harsh reality – that in fact I didn’t have a clue what I was doing. Compared with the present, 1999 was a very different time to start a business. The internet was in its relative infancy, with little more than 40% of Americans on-line (probably even less people in the UK). Although invented some ten years earlier, xDSL was still a way from becoming mainstream and most people were getting by on V.34 dial-up modems running at 28.8 kbps. Although it was the height of the dot-com era, unless you were in a cool start-up venue like Silicon Valley, you were largely on your own. The first Joel on Software article wasn’t due for another twelve months and In Search of Excellence was the only business book I owned – given its follow-up publicity, it was perhaps fortuitous that I never got round to reading it. Any success we subsequently enjoyed in my business was largely due to a combination of good luck and the presence of some genuinely bright, hard-working people around me.

Things are very different these days, in great part because the Internet has made everything so much more accessible. Through the magic of the web, I’ve been able to learn from dozens of blog authors who, in terms of founding companies, have been there, done that, and got the T-shirt. (There is even a place to go and ask questions of many of these founders.) Since my last firm was acquired roughly four years ago, I’ve also had the opportunity to read more books about entrepreneurship (many of which have been written in the last decade) – again the Internet has made the process of identifying and buying good business books so much easier. One book I was challenged by last year was Geoff Moore’s Dealing with Darwin – How Great Companies Innovate at Every Phase of Their Evolution – it was this book that convinced me initially to propose a spin-off business to my then current employers, and subsequently to leave and start another business. (Prior to Darwin, Moore wrote the seminal technology marketing book Crossing the Chasm). So you can imagine how pleasantly surprised I was to be sitting at breakfast with the author himself at the Business of Software conference in San Francisco last November, and hear about some of his ideas close-up.

My point is that as one of this current generation of entrepreneurs, I feel incredibly privileged to be able to learn from other people’s successes and failures at close hand – this really wasn’t possible ten years ago.

Lessons learnt from recent research

Don Norman at Business of Software 2009Another well-respected speaker at Business of Software 2009 was Don Norman, famous for his insightful classic The Design of Everyday Things. Norman, despite turning 75 this year, is highly active in the field of user experience as both university professor and independent consultant. (I hope I have his energy as/when I make it to his age.) In his talk ‘Ten rules for successful products‘, he introduced the audience to the concept of “Systems Thinking” in terms of delivering product. He discusses these ideas some more in an article entitled Systems Thinking: A Product Is More Than the Product he wrote for interactions magazine. My takeaway from all this is that we so often think of a software product in terms of the bits that get installed onto the user’s machine (or that are hosted in the case of SaaS), but his point was that successful companies take a much more holistic view.

Take Apple, for example. It’s quite instructive to watch the first iPod launch video. At the point that Apple released iPod, there were plenty of MP3 players in the market, but in pretty much all cases, the big issue was getting music onto the device. Recognising this, Apple didn’t just launch an MP3 player, they provided the customer with a complete portable music solution, tying together the purchase and download of music through iTunes to its subsequent enjoyment on the device. The Amazon Kindle story is very similar – there are plenty of e-book readers out there, some arguably better, but Amazon have delivered a complete electronic book solution for their customers, one which is designed to work world-wide.

Coming to grips with this concept, I started to wonder how it could have hypothetically been applied to my previous business, to see what we could have done differently (i.e., better). We provided business to business connectivity software to the financial market community and we took a decision very early on that as product businesses scale much better than service businesses, we would get out of the consulting space and focus on product development. On the face of it, this makes sense – if you have three developers that can either consult or build product, then long-term, you get much better leverage from them building products that can be sold to dozens of customers than you do from them working on specific customer projects. However, the logic is slightly flawed, as we found out as we attempted to grow the business.

In our business, it was all too often the case that prospects needed some small tweak or some little piece of integration undertaken in order to make use of our product. (Generally they were willing to pay for this.) Had we taken a more holistic view of our business, we would have seen that providing such a service alongside the product would have strengthened the overall offering, as customers would have got a complete solution to their specific problem, rather than a piece of software and a whole new set of problems.

Going forward, what have I learned for my new business? The key lesson is that providing a piece of software, even if it is reliable, easy to use and comes with great customer service, is still not enough. We need to look beyond the raw bits to the heart of the customer’s business problem, and by taking a holistic approach, find ways to add value by gnawing away at those same problems. This could be through an accompanying integration service or perhaps finding some way of helping them with their customer’s problems. I have no doubt that seeing the solutions we provide as a form of eco-system rather than a raw product is a sure-fire way to build a more successful business. To quote Don Norman, “No product is an island“.

Have you come across other examples where “systems thinking” has really made a difference to business? Is this something you’ve experienced yourself? Please leave a comment and let me know.

Post to Twitter Post to Delicious Post to Digg Post to StumbleUpon

{ 7 comments… read them below or add one }

Christian Bjerre February 14, 2010 at 1:22 pm

Geoffry Moore is one of the most relevant authors to read, when you’re in software. And even more true when you start selling your product. The concepts he presents in his books are very much spot on and can help the software startup move across the chasm – mainly because they can read the book and recognize the current situation.

Moore has worked extensively with SAP. His ideas are being put into the main product developement as well the way it is presented to customers and partners. Really taking it to the full. This is a very interesting approach. Many companies could learn from putting themselves and their product(-s) into a core/context – and let their products live and die according to this.

I can only recommend his earlier books – and have added “Dealing with Darwin” to my wishlist.

Your paragraphs on “complete product” are also relevant. As a software company we tend to focus on new features, new technologies and many things, but not always what brings most value or satisfaction to the customer. We think they always want more new features to be happy – or to see that we can deploy with [insert any 3-5 letter acronym or alternative a code word for a forthcoming solution from a major software vendor].

I remember some years ago, where I was asked to plan what new features or modifications we should do in the coming release. Having a domain structure with expert users around the World I asked them… and was surprised then the feature most would “pay” for was the ability to press CTRL+S in a module! Why? Well, I had to admit that the current solution when saving a file was cumbersome and not in anyway user friendly (steps to save: click with mouse on save icon (no keyboard shortcut), click ‘save’ button in ‘save as…’ dialog box, press ‘yes’ button to ‘do you really want to overwrite file foo.bar’). And a normal workflow will include saving files 5-10 times per hour.

This is a small item, but one of the things we tend to forget when we plan for next release of our software product.

So I think that you point about letting existing customers decide what goes into the product is sound. It strengthens the product in general, it increases the usage at at least one client – and you will likely have a better fit at the new prospect. Adding that they will pay for it upfront part of your development time is funded upfront. That is not bad either…

Reply

ibagrak February 14, 2010 at 1:39 pm

Thanks for sharing your thoughts, Steve. A lot of recent product successes have indeed been system-minded, i.e. the product came with its own ecosystem of services or support products that made a qualitative difference in the way the product was used. I talked a little bit about this in my own blog post here: http://wp.me/pNvjA-y

I definitely plan to look at Don Norman’s stuff.

Reply

stevew February 19, 2010 at 8:22 pm

Ilya – many thanks for leaving your feedback. I could a quick look at your blog – interesting – I wish you well with the new enterprise – Steve.

Reply

Ole Klinkby February 17, 2010 at 11:36 am

Complete solutions doesn’t mean you have to provide all parts of the solution – small companies often try to include too much in their products and they often aren’t able to provide the whole complete solution in a satisfying quality, either the user experience or the knowledge of details in the complete solution isn’t deep enough. So my advice for small companies is to partner up with other companies that are experts in related fields and go to market together – doing so you often bring the cutting edge to your customers in more fields than you could provide yourself.

Reply

Christian Bjerre February 17, 2010 at 8:48 pm

That’s good advice, Ole! It is just very difficult to implement in real life. First of all the extra feature makes really good sense to include. The customers will pay for it and the developers will have fun implementing it. So that’s at least three reasons to put it into the software anyway.

The mindset you need is to understand the big picture. Holistic (or No Product is an Island) viewing of your product, the supplements, the alternative suppliers is difficult at all stages, but doing it will make your market position stronger. There will be more people pushing for your product at more potential clients than you can ever do yourself. Partnering up, giving away some of your potential income can be very profitable – and help to keep you at your core products. You have to consider the “ecosystem” from an early cycle in your company’s/product’s life cycle. The right attitude and communication in these matters can give you the extra factor 10 to your company’s market value.

Reply

stevew February 19, 2010 at 8:38 pm

Ole – thanks for this perspective. I think it probably depends on the size of the market opportunity (i.e., can it support you and the partner commercially?) and the availability of partner organisations with a good fit to your business, where strategic objectives are aligned and conflicts of interest are minimised. Definitely worth looking out for though, I agree.

Christian – I agree – having a decent ecosystem around your product, beyond the raw software, can make a factor of 10 difference to the value of your company. Correspondingly, it’s probably ten times as much effort to achieve :-) .

Reply

Christian Bjerre February 20, 2010 at 2:11 pm

I am not sure about the effort being 10-fold, Steve! The right product will attract the partners and add-on suppliers. The big effort is to convince yourself that they are not taking away money you could have booked to your P/L. It is a win/win situation to foster and run a good ecosystem. It is not for free, but it saves you a lot of effort and risk.

Reply

Leave a Comment

CommentLuv badge

Previous post:

Next post: