Como criar uma cultura de nuvem na fintech?

Cloud Mindset is one of the single greatest contributors to the success of adopting a cloud solution. Particularly in the arena of Finance which has its own selection of challenges when it comes to adopting Cloud Solutions. Be clear with what you want to achieve by transitioning to cloud, and be prepared to follow best practice processes in the path to success when transitioning to cloud.

The fintech sector has seen huge growth over the last few years and fleshing out you processes with proof of concepts and generating an internal community to drive integration is key. With so many areas for automation a "free for all" culture creates pockets of innovation contrasted with good ideas that result in poor user experience. In an industry where compliance is key its often over regulated internally with manual checklists and micro management that create top heavy, stressed teams. Creating an internal community to share ideas, demonstrate to each other what works allows you to adopt the ideas that work well and keep iterating the ones that don't. Democratising development ideas to a community across many teams (not just IT).

The “propagation” of the cloud message starts before you even build the framework in the cloud. You have to build the culture early on. Assure your technical teams, get their thoughts, accept their feedback and incorporate their ideas. Adoption of new technologies, when done well is something that the user and the engineers see as a must have and not forced or job concerning.

Cloud platforms enables teams to focus on solving business problems fast by outsourcing technology provisioning to vendors. Also technology teams have access to current innovations at their fingertip without standing up required infrastructure to support it. The key then becomes how to modernize the release train to automate code delivery and validation. This will lead to continuous delivery and feedback loop that can charge up a product lifecycle.

DevOps and SecOps are concepts that need a slight revision for cloud. Developers need to understand the concept of the cost and ensure they utilize the resources correctly and “turn off” when not in use. Maintain security and protection of boundaries and code at all times. SecOps needs to view cloud in a new way, elements, assets, threat detection and vulnerabilities take new shape and form in the cloud. Having these teams adopt to the new coding and security concepts starts well before you deploy your first corporate asset in the cloud.

Very well said. And this is certainly an area where there are a lot of surprises if the concepts of cloud are not fully understood.

Well said again. It’s not only security by design but security in depth. Not only the infrastructure and border devices but the code itself. Not only patching and management but the understanding of virtualization and it’s complexities in the security realm.

A cloud strategy is not just designed once and forgotten. It’s under constant improvement, revision and re- engineering. It’s not just the platform, it’s the people, process, procedures and tools.