> Markdown version of [/videos/485-we-adopted-devops-and-are-cloud-native-now-what](https://www.wearedevelopers.com/videos/485-we-adopted-devops-and-are-cloud-native-now-what). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # We adopted DevOps and are Cloud-native, Now What? Bruno warns the real bottleneck to digital transformation isn't your tech stack, but your fractured engineering culture. Discover how to finally build sustainable, cross-functional excellence. - **Speakers:** Bruno Amaro Almeida - **Event:** World Congress 2022 - **Published:** June 15, 2022 - **Duration:** 34:46 - **URL:** https://www.wearedevelopers.com/videos/485-we-adopted-devops-and-are-cloud-native-now-what ## Summary Adopting "DevOps" and "Cloud-native" approaches in a sprawling enterprise often leads to fragmented definitions, isolated toolchains, and cultural friction. Rather than simply bolting new technologies onto legacy processes—a mistake that results in a "broken digital thing"—organizations must bridge the gap between software engineers, legal teams, and cybersecurity. Drawing from his experience directing technology architecture at Fortum, Bruno highlights that the real bottleneck to digital transformation is rarely the tech stack; it is the absence of a unified, cross-functional engineering culture. By establishing transparent, virtual governance groups, organizations can elevate operations from a traditional cost center into a core value-creation hub. To drive sustainable engineering excellence, leaders must empower developers with practical, team-owned exercises rather than rigid mandates. Establishing structured "golden paths" using internal tech radars—such as Spotify's Backstage.io—helps mitigate shadow IT. Furthermore, peer-facilitated STRIDE threat modeling and routine Cloud Well-Architected Reviews give teams a comprehensive 360-degree perspective on their workloads without defaulting to punitive audits. Crucially, companies need to abandon toxic, top-down metrics like pull-request counts or lines of code. Instead, they should facilitate bottom-up discussions around DORA metrics and business-aligned reliability targets like RTO (Recovery Time Objective) and RPO (Recovery Point Objective). Ultimately, scaling these practices requires an embedded culture of continuous, organic learning. Utilizing the 70-20-10 learning model and hosting weekly "Lean Coffee" sessions allows disparate engineering teams to share knowledge iteratively. Looking toward the future evolution of DevOps, organizations should leverage reliability "game days" and adopt self-service platform engineering guardrails. This holistic approach ensures that modern cloud practices fundamentally change the fabric of the company, resulting in secure, resilient, and highly aligned product development. **Keywords:** cloud-native adoption, enterprise devops culture, software engineering governance, shadow it mitigation, well-architected framework reviews, stride threat modeling, developer portals, backstage.io, bottom-up engineering metrics, dora metrics, disaster recovery rto rpo, continuous learning routines, lean coffee format, 70-20-10 learning model, cross-functional technical alignment, reliability game days, self-service platform engineering ## Chapters 1. **Operating software across enterprise domains and startups** (00:26) — Balancing complex software environments spanning large energy production infrastructure and emerging digital products. 1. **Establishing shared definitions for devops and cloud architectures** (03:00) — Recognizing devops as a cultural shift rather than a job role resolves organizational misalignment around cloud deployments. 1. **Approaching technology strategy from an organizational perspective** (05:31) — Operating across multiple cloud providers ensures regional compliance and enables expansion into restricted international markets. 1. **Building virtual governance groups to eliminate shadow engineering** (09:27) — Bringing developers together with legal and cybersecurity domains transforms operations into a value creation center instead of a cost center. 1. **Enabling successful digital transformation through cultural empowerment** (13:29) — True engineering excellence requires empowering teams and adapting foundational culture before implementing strict process guardrails or adopting specialized operational tools. 1. **Directing architectural adoption with a centralized technology radar** (17:11) — Implementing developer portals highlights approved technology stacks and establishes golden paths for engineering alignment across disjointed teams. 1. **Measuring systemic health with bottom-up engineering metrics** (18:54) — Equipping engineering teams to analyze uptime metrics and data restoration objectives uncovers financial considerations for maintaining highly available architectures. 1. **Assessing cloud workloads using well-architected framework reviews** (21:17) — Using collaborative workshops evaluating cross-functional cloud pillars exposes structural risks without creating punitive technical audits. 1. **Introducing collaborative threat modeling workshops in engineering teams** (24:20) — Applying the stride framework reveals subtle system vulnerabilities and generates actionable remediation consensus on legacy code components. 1. **Fostering organizational knowledge sharing using lean coffee sessions** (27:27) — Organizing unstructured weekly technical discussions surfaces engineering insights and dismantles the knowledge silos forming between divergent platform groups. 1. **Gamifying technical learning with guided cloud infrastructure exercises** (30:04) — Running site resilience simulation days alongside cloud platform partners upskills engineering preparedness and operational mastery rapidly. 1. **Scaling threat modeling independently from external security consultants** (31:13) — Cultivating an evolving selection of internal software vulnerability facilitators preserves architectural context without relying completely on outside contractor resources. 1. **Evolving devops towards platform engineering and self-service principles** (32:26) — Formalizing platform services accelerates developer pipeline interactions through continuous delivery patterns instead of exclusively consolidating cloud account administration duties. ## Related Moments - [Overcoming cultural friction and scaling DevOps team practices](https://www.wearedevelopers.com/videos/855-fast-flow-not-fast-fluff-embracing-an-eclectic-devops-coaching-approach) (from "Fast Flow, Not Fast Fluff: Embracing an Eclectic DevOps Coaching Approach") - [Introduction to cloud native infrastructure and platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?") - [Expanding devops culture to non-technical executives](https://www.wearedevelopers.com/videos/332-hosting-a-modern-justice-system) (from "Hosting a modern justice system") - [Fostering a genuine devops culture through cross-training](https://www.wearedevelopers.com/videos/332-hosting-a-modern-justice-system) (from "Hosting a modern justice system") - [Architecting the platform with modern cloud and mobile technologies](https://www.wearedevelopers.com/videos/64-shared-mobility-for-everyone) (from "Shared mobility for everyone!") - [Summarizing the organizational benefits of platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?") ## Related Articles - [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development) - [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed) - [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production) - [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it) ## Related Jobs - [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub** - [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx** - [Senior Cloud Native Solution Architect (all genders welcome) - Kubernetes, CNCF, MlOps](https://www.wearedevelopers.com/jobs/ext/101488-senior-cloud-native-solution-architect-all-genders-welcome-kubernetes-cncf-mlops) at **Rosenxt Group** - [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub** - [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.** - [Cloud-Native Architect (all genders welcome) - Kubernetes, CNCF, MLOps](https://www.wearedevelopers.com/jobs/ext/101479-cloud-native-architect-all-genders-welcome-kubernetes-cncf-mlops) at **Rosenxt Group**