Zoom is a popular video conference platform which popularity skyrocket recently. Because of the social isolation, their easy-to-use interface, helped them to become the go to application in the video conference market, surprising traditional players in the market such as GoToMeeting, Microsoft Skype and Microsoft Teams and Google.
However, they had a little secret. Their infrastructure wasn’t prepared to handle such a big load in specific regions of the world. This trigger them to seek resources in data centers which were not so overloaded. One of those is in China, where there are laws which could provide to their government all the data which is stored or passed in their country. You might think this is still not a big deal since the communication is encrypted end to end and no one beside the people in the meeting have access to it.
It turns out this is also not true and only the communication between the Zoom client and the Zoom server is encrypted. What happens after that is in plain sight.

This triggered more discussions and restrictions of the usage of Zoom. Official emails were sent inside corporations and governments to warn about this threat. 
Luckily for Zoom, they reacted fast and at least reduce some security concerns. Now the administrator of the meeting can blacklist countries where the video conference signal must not be routed to.
Zoom announced in the end of May 2020 a big release version 5.0 which will fix the rest of the security concerns.
In the middle of this privacy and concern storm, Zoom stands still like a big oak tree in the middle of a field. 
The moral of the story is sometimes being fast helps, sometimes being fast wins.
The only thing you must consider is to acknowledge when you had made a mistake. And with fast reaction, fix the problem when the damage in your reputation is low.
What we can learn from this story is how to handle a crisis in a good way:

  1. Be transparent.
  2. Use facts when they support the message, in Zoom case the good news was that only small amount of traffic was affected.
  3. Work hard and provide fix as soon as possible.

It seems like in this case asking for forgiveness pays off.

Aleks Vladimriov is a Senior Software Developer, recognized Project Manager and Soft-skilled trainer and a coach.

Aleks Vladimirov

Solution Engineering Manager at Thales | Senior IT Professional | Startup Mentor and Product Manager

Aleks is experienced Product Manager with an engineer background and over 10 years of experience as a software developer. He works with different governments and is responsible for negotiation features and requirements, understanding the customers’ needs and supporting the senior management with regular reports and analysis. He held various positions starting as a software developer, moving to a team leader and software architect.

He strives in waterfall and agile environment alike. He is certified Scrum Master and Prince2 Practitioner and he knows how to design business processes and help teams optimize their work.
During his tenure, he had to wear many hats, prioritizing business requirements, delegating work and mentoring team members, creating mockups with Balsamiq, providing MS Project plan to the senior management.

He had worked in many international teams, located in the same city or distributed in different countries and continents. He had been a team leader of cross functional international team of 8 people.

In his current position, he is very much client focused. He has excellent presentation skills.
He delivers training sessions on presentation skills and leadership and he had helped hundred of people to improve their presentation skills.

He is also interested in creating more positive changes in the workplace by using entrepreneurship skills.
He had won startup competition where his team had validated and develop a business idea from scratch.

In his free time, he writes in his blog about effective product development.

[cp_modal display="inline" id="cp_id_f014e"][/cp_modal]
[cp_slide_in display="inline" id="cp_id_ca87c"][/cp_slide_in]