There’s a pattern I keep seeing in organizations that are struggling with AI governance, and it starts the same way every time: the CISO or the General Counsel gets assigned ownership of “the AI policy,” produces a document, and then watches as the rest of the organization ignores it — not out of bad intent, but because nobody connected the policy to how work actually gets done.
A little over a year ago, I wrote that the build vs. buy debate was the wrong frame — that the real question was how to orchestrate the right blend of built, bought, and integrated capabilities to deliver value faster. I still believe that. Composability and platform thinking haven’t gone anywhere.
A while back, I wrote about building a modern engineering career ladder — the competency dimensions, the dual-track progression, the principle that growth should be behavior-based, not time-based. I still stand behind all of it.
But I also have to be honest: if your career ladder was written before 2025 and hasn’t been touched since, it’s already out of date. Not because the fundamentals changed — they didn’t. Because the job changed.
A few years ago, I wrote about scaling an engineering team from 6 to over 100 — the lessons learned, the hard pivots, and the patterns that held up under real pressure. That article was grounded in a specific kind of scaling: more people, more process, more structure.
A year ago, the conversation around AI in the workplace was still largely theoretical for many organizations. Leaders were asking “should we adopt AI?” Today, that question is obsolete. The real questions are: How fast are you moving? And do you have a strategy — or are you just reacting?
Artificial Intelligence (AI) is reshaping the modern technology landscape. In autonomous engineering teams, AI offers incredible opportunities to enhance CI/CD, governance, team structures, and overall productivity. However, adopting AI requires caution and awareness of potential pitfalls. Let’s explore how AI can improve each area we’ve discussed so far—and where teams should tread carefully.
As engineering teams embrace autonomy, the risk of shadow IT—unauthorized technology solutions that bypass official channels—can grow. This article explores how to balance autonomy with visibility, governance, and trust.
Autonomous teams often innovate faster, but this freedom can lead to hidden or unauthorized solutions, known as shadow IT. According to Gartner, shadow IT can represent 30% to 40% of IT spending in large enterprises (Gartner Report).
Supporting autonomous engineering teams requires a strong foundation of CI/CD, Infrastructure as Code (IaC), and automation tools. This article explores real-world tools, best practices, and integration strategies to help your teams scale effectively.
Modern engineering teams thrive when they can deploy, test, and iterate rapidly. Autonomous teams especially need robust pipelines and infrastructure that support independence without sacrificing governance or stability.
Autonomous engineering teams are reshaping the way technology organizations deliver value. Let’s explore real-world case studies from leading tech companies, showcasing both successes and challenges, to understand the impact of scaling autonomous teams.
Spotify’s engineering culture is often cited as the blueprint for autonomous teams. Their Squad model empowers small, cross-functional teams to own specific features end-to-end. Squads align with Tribes (related groups), Chapters (discipline-based communities), and Guilds (interest-based communities) to balance autonomy with knowledge sharing.
As organizations embrace autonomous teams to drive innovation and speed, they face a critical challenge: how to maintain effective governance without undermining autonomy. Let’s explore practical strategies, frameworks, and tools that enable this balance in modern engineering organizations.
Autonomy accelerates decision-making and ownership, but without governance, it risks misalignment and compliance gaps. Governance frameworks ensure accountability, regulatory adherence, and consistency across teams.
Copyright © Ledwith Technology Consulting, LLC. All rights reserved. 2009 - 2026.
Template by Bootstrapious. Ported to Hugo by DevCows.
