The Power of Proofs of Concept

Read our case study about how small experiments can help a company reduce risk.

Moving to a Cloud Native system can be a daunting project. There are so many choices of tools and vendors, and so many possible ways to get things wrong—costing time, money, resources, and even customer goodwill.

At Container Solutions, we guide the organisations we work with through a stepwise approach, aimed at reducing risk and eliminating wrong moves early. We encourage the use of proofs of concept, or PoCs—inexpensive, time-boxed, small-scale experiments aimed at helping our clients identify the best path forward as they look to solve their challenges.


Bell Mobility, Canada’s largest communications company, had problems related to occasional surges in mobile phone traffic. Over two weeks, a CS team worked with a team of Bell engineers on PoCs to help the company investigate its options, and produced guidelines, recommendations, and areas for further exploration. 

Our whitepaper on the project offers practical tips for conducting a PoC, based on our experience with Bell Mobility, including:

  • What you need to do to prepare for the PoC. 
  • How to conduct a small-scale experiment.
  • The follow-up steps needed to benefit from the PoC.


Register your information to get a free download of our report.

About the authors

Ian Crosby is Field CTO at CloudOps. He  works with companies across many domains as they make the move to Cloud Native. His work spans application design, build pipelines, and cloud infrastructure, with a heavy focus on containers, orchestration, and other Cloud Native tools.

Tristan Lescut, a systems architect at Bell Mobility, has played many roles as a DevOps engineer, Scrum master, technical coach,  and architect. He is leading a modernisation effort of Bell Mobility’s messaging systems as well as growing an internal development practice. This work is at the intersection of process improvement, human interactions, and technology modernisation.