by Mark Greatorex
•
31 Jan, 2021
In 1985, Sir Clive Sinclair launched his C5 to the world. The successful businessman who had brought the world the first sub £100 home computer had a new vision. For those who aren’t old enough to remember, the C5 was a new form of personal transportation. It was perhaps best described as a combination of a tricycle and an open top single seat electric car. It had rechargeable batteries designed to help you whizz(!) along through traffic and pedal power when it needed help, such as going up hills. It was launched in a fan-fair of promotion and almost instantly became a flop. Within months production had all but stopped and many see the C5 as one of the biggest product flops in history. So, what had gone wrong? Almost instantly, when launched it was criticised for being unsafe due to its low height, having too little power (you had to peddle when going uphill!), restricted battery range, and because it was open, riding around the UK streets in the middle of winter was not going to be a desirable alternative to the car or bus. The biggest failure and the most relevant question here must be this: why did Sir Clive Sinclair not anticipate the reaction he got for his product? In an investigation for the European Journal of Marketing, Andrew Marks found that the company believed they could create a market without ever doing research into what customers actually wanted. In other words, they thought they had a great idea, and therefore wrongly presumed customers would love it! The same is true of projects today. It can be easy to focus on delivering what you believe is a great idea without getting a clear understanding of what your customers want. Of course, in this context, customers could easily be another part of your company as well the external customers you are selling to. Our ability to listen to customer requirements and make sure we fully understand them can be the difference between the complete success, and the complete failure of a project. Those who’ve worked with me before will be familiar with a method I’ve used to depict this to teams. I would start with a table of objects at one end of the room and an empty box at the other. The team would then be given a list which contained about half of the products on the table. The concise instructions read: “I’m your customer and I want you to find the items on the list. Then, in order, and one object at a time, place them in the box. As a team you can only touch one object at any time. I will time you to see how quickly you can do it. Tell me when you are ready to start” Nearly every time I would see the teams doing the same thing. They would quickly jump to a solution, quite often involving a chain of people. One person would frantically try to find the items from the list on the table, passing them down the chain, to the box. At the first attempt the teams would usually complete the task in 1 ½ to 2 minutes. They would think the results were good but could be better. Giving them a second attempt usually shaved a few seconds off and sometimes led the teams to congratulate themselves. The real moment of clarity for many would come when I told them how far off the pace they were, and that I expected completion in under 15 seconds! Some would simply laugh and say it’s impossible. Others would start to ask questions: does the box have to be on the other table, or can we bring it to the same table as the objects? Can we organise the objects before we start the task to make them easier to find? Of course, the answers were yes. My instructions didn’t say you couldn’t do it, but they just hadn’t asked the questions. They didn’t seek clarity on what the customers full requirements actually were. As a result, they were never going to meet my expectations on time taken, which again I cannot recall any team asking me for. Too many projects fail to capture this fundamental element. Unless you are fully clear on your customers requirements and constraints, how will you ever meet their needs. And how will you be sure that your customer themselves even fully understands their needs. If we just take a moment to go back and look at Sir Clive Sinclair’s C5. Undoubtedly he didn’t understand his customers requirements. However, more than 35 years later, we see customer demand for electric vehicles. Maybe, if he had engaged with customers and truly understood their priorities, the C5 would have looked very different and maybe we would be hailing his creation as a revolution rather than as a high-profile failure.