Technology leaders often describe the future as if it follows a clean, predictable trajectory — progress seemingly guaranteed, with each new tool neatly simplifying the world around us. 

This year continues to look far more complex, shaped by competing priorities that coexist rather than falling into a tidy sequence. 

Organizations will continue to navigate the pull between building and buying, the interplay between innovation and governance and the ongoing balance between creative freedom and the structure needed to sustain it. These are not shortcomings in strategy; they are the natural conditions that emerge when a business grows, matures and begins to understand what sustainable progress requires. 

Below are the shifts I believe will matter most for the remainder of 2026. 

AI Will Redefine Control  

The frenzy around AI is going to get worse before it gets better. We’ve hit the excitement peak, and now we’re moving into the reality phase. The problem in software development has never been writing code; it’s always been people, alignment and dependencies. If we use AI to generate code without structure or understanding, we’ll end up with a mountain of code that no one can maintain. If you hand over control completely to AI, you’ll create millions of lines of code that nobody truly understands, and that’s a huge business risk.  

There’s enormous potential in AI-assisted engineering, but it must be used thoughtfully. It’s an assistant, not an author, and if we don’t treat it that way, things are going to get messy before they stabilize. 

Some companies think they can skip hiring junior engineers because AI can do the basics, but if we stop training juniors, we won’t have senior engineers in 10 years. The best engineering cultures will use AI to enhance capability, not replace it. Junior and senior engineers need to pair on AI-generated code so that learning continues. We need to figure out how to enhance our workforce, because replacing our workforce with AI won’t work. There is a real responsibility on engineering leaders to make sure we don’t create a future where no one knows what questions to ask. 

Build vs. Buy: The True Cost of Ownership 

More companies will feel the financial and operational strain of in-house development as the true cost of ownership becomes impossible to ignore. Building costs money, and owning what you build costs even more. The hidden costs are often in the total cost of ownership, which is rarely linear. Build three separate tools, and the complexity of maintaining them doesn’t triple; it multiplies. You end up investing in areas that aren’t your core competency, and that becomes technical debt, risk and a distraction from what really matters.  

Companies underestimate this every day, and the impact will get more severe as systems become more interconnected and harder to unwind. 

Organizations will also start to rethink the belief that building internally gives them greater control. The burden of maintaining scattered tools, and the investments made in areas that aren’t your core competency will reach a breaking point. There’s a reason for commoditization: Some companies choose to go deep in solving a very specific problem because it genuinely defines their product. Others find themselves building more and more internal tools simply to keep operations moving, until the maintenance load becomes larger than anyone expected.  

I have seen teams reach a place where they had to shift from confidently owning their codebase to simply acting as custodians because the ecosystem had grown too large to properly understand and maintain. Sprawl isn’t just about tools; it’s about technical debt, risk and distraction. The more companies feel that pressure, the more they’ll realize they don’t need to build everything themselves. 

Governance: From Constraint to Condition for Scale 

I believe governance will move from an operational inconvenience to a critical enabler of clarity, consistency and organizational sanity. Companies need governance not just to meet regulations, but to stay consistent. Compliance is driven by law or regulation, while governance is about discipline and consistency — conducting business in a structured way so you can trace, monitor and manage it properly. Without it, you end up duplicating efforts, developing inconsistent practices and creating data silos.  

Governance isn’t bureaucracy; it’s what keeps an organization functional and ethically sound as complexity grows. Compliance matters, but governance is what makes compliance sustainable. Governance is what stops things from breaking down when you have too many teams and too many departments, each with different types of data and no interoperability. Innovation requires exploration. Test new ideas, but have the discipline to merge back once you’ve learned what works and what doesn’t. If you don’t, you end up with duplication, data silos, inconsistent practices and sprawl. The tension between freedom and structure is the eternal challenge of leading in tech and will become an important focal point as AI scales across organizations. 

Unmanaged Email Infrastructure Won’t go Unnoticed 

This is a big one — unmanaged email systems will become impossible for IT leaders to ignore as brand, compliance and consistency risks bubble to the surface. Many organizations simply send out an email template and ask everyone to update their signatures manually, which is inefficient and risky. What’s worse, even people in IT don’t realize they have a problem.  

Once they understand the compliance and brand implications, the case for centralized management becomes obvious. Awareness is shifting, and unmanaged email infrastructure won’t be acceptable anymore. 

Defining Leadership: How Well Teams Manage Tension 

Lastly, the pressure on IT leaders to balance innovation freedom with operational discipline will intensify. The tension between freedom and structure is the eternal challenge of leading in tech. Innovation requires exploration, but you need discipline to roll back once you’ve learned what works and what doesn’t. Without it, organizations risk duplication, inconsistent practices, data silos and uncontrolled sprawl. 

As businesses continue to scale their tooling, data and automation, the tension is only going to get sharper for IT leaders. 

SHARE THIS STORY