The transition to Cloud Native can be a complex and daunting endeavor. Choosing the right technologies and integrating them into your organisation is a challenge. More often than not cultural change is just as important to allow your organisation to leverage these new technologies and the speed of delivery resulting from Cloud Native.
One of the most impactful changes we can introduce is a culture of experimentation. This can enable our teams to actively test out new ideas, validate or disprove a hypothesis, and make discoveries. With the proper processes and structure in place, technical alignment can be achieved quickly by a data-driven experiment. Feature ideas can be easily proven to be useful (or not!) before going into a lengthy implementation cycle. Time, money, and effort can be saved by eliminating wrong paths, early.
Adopting this kind of culture does not happen overnight. A great place to start is with a proof of concept (PoC). Because we can run such a project at a small scale and in isolation of any ongoing work, a PoC is a cost-effective and time-efficient way of getting to the results that will provide the building blocks for the new culture.
We want to ensure maximum benefit from such projects. When done poorly, a proof of concept is a waste of time, and can sour an organisation’s opinion of PoCs and even experimentation in general. Even though PoCs are often used to come up with creative solutions, a certain amount of structure and process is necessary in order to allow that creativity to emerge.
Here, you can request a free download of The Power of Proofs of Concept, a guide that provides our opinionated approach to running PoCs. We will cover the reasons and benefits for doing so as well as the detailed approach that we recommend. Throughout, we will also cover a case study of a specific project where Container Solutions ran two proofs of concepts with Bell Mobility.
Previous article
