Today I had a meeting that could be the beginning of the end of RFPs to buy software. RFPs are the tool established buyers and vendors use to keep new entrants at bay. However I haven’t met anybody that says they love writing or responding to them. The effect of RFPs on software is perverse. The main problem is that you can’t ask if your software is beautiful, easy to use, fast to integrate, efficient, effective at solving a business problem, secure, etc. Instead you ask if you provide training, because you assume it is ugly and difficult. You ask if they offer consultancy services and an SDK or connector library because you assume it is difficult. You assume you need to customise it for months because it will not be effective out of the box. But most importantly since you will be stuck with the software for years, you ask if it supports any potential feature that perhaps in 5 years might be needed for 5 minutes. It is this last set of questions that kill any innovation and ease of use in business software. A product manager in the receiving end will get funding to add those absurd features when customers ask for them. A career limiting move would be to ask for budget to reduce useless features or tell that your product looks worse than Frankenstein.
So how can you make sure that software is beautiful, does what it supposed to efficiently and effectively, is fast, nimble, easy to use, secure, scalable, fast to integrate, is future proof, etc.? You do what you do when you buy a car, you go and ask the keys of different models and take them for a serious spin and put them to their limits.
So what you propose is a three months PoC for each potential solution?
No what I propose is being able to get your hands on all different alternative software solutions and deploying, integrating and scaling them in hours or even minutes and then release a bunch of automatic performance tests and rough end-users, even some ethical hackers or competitors.
If the software does what it says on the tin, is effective, efficient, beautiful, secure, fast, scalable, easy, etc. then you negotiate pricing or use it for a minimum valuable product.
It used to be impossible to do all of this in hours but with solutions to deploy quickly private clouds and cloud orchestration solutions like Juju, we are actually planning on trying this approach with a real customer and real suppliers. To be continued…
Charles – Chuck – Butler, a colleague at Canonical, wrote a very nice blog post explaining the basics of Big Data. It does not only explain them but it also allows anybody to set up Big Data solutions in minutes via Juju. Really recommended reading:
This is a good example of the power of cloud orchestration. Some expert creates charms and bundles them with Juju and afterwards anybody can easily deploy, integrate and scale this Big Data solution in minutes.
Samuel Cozannet, another colleague, used some of these components to create an open source Tweet sentiment analysis solution that can be deployed in 14 minutes and includes autoscaling, a dashboard, Hadoop, Storm, Kafka, etc. He presented it on the OpenStack Developer Summit in Paris and will be providing instructions for everybody to set it up shortly.
Internet of Things, or IoT in short, is going to be the biggest revolution of this century. However the engineering challenges are massive. Billions of low-energy sensors will have to be invented, produced, integrated, operated and maintained. These sensors will talk to millions of gateways over new network protocols. The gateways will communicate via next-generation network devices and software-defined networks to public and private clouds. These clouds will run scale out big data solutions that will dwarf even the biggest supercomputers today. Billions of containers will be running massive micro-services IoT business solutions. One mistake and a hacker from a country you don’t even know to locate can bring down a whole house, a whole company, or worse a whole country.
The business side is looking even less clear. The open source IoT tsunami that is coming means asking for licenses is suicide. Open source hardware and 3D printing result in razor thin hardware margins. Privacy will be central when technology is so central to people’s home and businesses. If it is free then you are the product will become harder if a dot com can know what you are doing in bed, with whom and even if you liked it. Business SLAs will be stricter than ever because customers will expect answers in sub-seconds however human operators will no longer be able to find and fix problems because of the overall system complexities. Roll-outs will be global even if telecom operator’s networks don’t cross borders and electricity plugs and voltage are super local. Ask a customer what IoT solution they want and they will answer you what is IoT.
In these circumstances you might be surprised that I will be focusing on solving these challenges and Telruptive readers will be the first to know when some are resolved…
I just saw Eric Dishman’s TED session on “Health care should be a team sport“. I love the idea of providing people with chronicle illness the means to be diagnosed and treated remotely and use big data to learn of a large group of patients with similar issues. Personally this would mean that when my sons have breathing problems we would not have to drag them in the middle of the night to a hospital where they are exposed to many viruses. Instead by measuring their oxygen level and listening to their longs a personalized remote diagnose could be made and some nebulizers or other things administered. At scale all equipment would probably cost less than £200 because Maplin already sells the nebulizer and oxygen level meter for a combined £110. Add another £90 at worst for a stethoscope that can be connected via bluetooth to a smartphone. Now via Hangout a doctor could remotely diagnose the results and even in the future a computer programme. All results of millions of patients would be collected in order to improve treatment. So no need for an expensive hospital in London with a receptionist, nurse and doctor dedicating 2 hours. By just avoiding one hospital night, the whole system would be enormously profitable. Additionally Ubuntu’s Juju can be used to set up all the big data and diagnostic software in minutes in any cloud or server on any place in the world. If other open source solutions are used then the total solution would be in reach for any developing country. There are probably more than one developer whose kids are asthmatic, and would happily contribute time. It sounds like an ideal Gates Foundation or Kickstarter project. If you think you can help please reach out to me because this is not work for me, this is personal engagement.
It is not often that one is responsible for cloud [and Big Data and IoT] strategy in a company of 600 people and you get told by the OpenStack foundation that your solution went from 55% market share to 64% while competitors like RedHat, HP, VMWare, etc. are spending hundreds [or more] of times more on marketing and engineering than you. Now I would love to claim responsibility for it but I would be lying. My mentors, Mark Shuttleworth and Simon Wardley, have laid the foundations years before I joined the company. But Ubuntu and Canonical, the company behind it, are the poster child example of why promoting chief financial officers into strategic roles in the last ten years was a terrible idea. Bean counters are about to inflict potentially irreparable damage onto iconic hardware and legacy software vendors. The reason is really easy: disruptive innovation. The innovator’s dilemma explained it years ago already. When some initial inferior technology comes along like Cloud Computing and OpenStack, then existing vendors will not get any demand from existing customers. Only when technology matures will customers start defecting en masse. But then already other companies have years of a head-start. Add to it that Ubuntu OpenStack is not only the most innovative solutions but also wants to be the most flexible [see our Autopilot, OIL, MAAS and Juju for more details] and the cheapest. So if you are on a quarter-based projected revenue track and you find out that your competitor is doing those three things extremely well, then it might be time to brush up those skills and experiences on your CV. Regarding the future, let me just tell you that the best is still to come :-)