Sunday, January 5, 2014

Story of Quantity vs Quality… from Conception to Execution to Perfection!

There is always a new technology in the market claiming to override its predecessor. Yesterday’s solutions and experience may not be relevant today. It is important that we analyze the trends and make continuous improvements to the solution we offer. We may be making some mistakes along the way. But the learning lessons acquired from these mistakes along with the endeavor to continuously enhance the solution result in the creation of a flawless product. Let me tell talk about a story to start with.

A school teacher recently conducted a very interesting experiment that corroborates this fact further. He conducted this experiment to see if we need to change the way we set goals, make progress and become better at what we do. He divided his class in two groups, one that would be graded solely on the quantity of work that they produced and the other that would be graded solely on quality. Both groups were asked to create pots. The ‘Quantity’ group would be graded based on the number of pots they produced in a day. The ‘Quality’ group on the other hand would be required to produce only one pot, albeit a perfect one, to get an A. The outcome was remarkable. It was seen that the best quality pots were those created by the ‘Quantity’ group. As the ‘Quantity’ group was churning out the piles of work, learning from their mistakes, and thereby producing the perfect work, the ‘Quality’ group sat theorizing about perfection and had little more than grandiose theories to show for at the end of the day.


We followed a similar approach in the development of Cloud360: conceptualized it, developed it, implemented it for active engagements during every stage of the product, and made multiple enhancements making it the perfect solution.  

Around 5 years ago, we saw that the industry was moving towards fluid computing models, and infrastructure was soon becoming available as as-a-service models. We noticed that economics of scale could not justify legacy infrastructure models. Even before the term ‘cloud’ was coined, we had started exploring the idea of building a solution that would address the changing landscape at customer organizations, retain their investments, and create new modes of infrastructure delivery. We eventually developed Cloud360, a comprehensive, service-oriented cloud management platform integrating consulting, professional and IT services to fundamentally transform a client’s environment.

We had customers using the Cloud360 at a time when the very concept was very new in the market. We were not merely reacting to the need of the time, theorizing about a solution but actively managing customer environments where we handled real challenges in real time. Continuous analysis of user feedback and requirements enabled us to constantly enhance its features. These early customer engagements helped us refine our concept, design approach, iterations, product roadmap and our approach towards reliability, availability and serviceability of the product.

Envisioned at a time when the very word ‘Cloud’ did not even exist, the hyperplatform (now Cloud360), with its ability to deploy, manage, and operate modern, dynamic, and scalable architectures swiftly and cost-effectively within a seamless holistic environment, has come a long way in being the most preferred partner for organizations planning operations on Cloud.