The Devil's Triangle

This may come as a shock to you, but leadership, IT, and the people doing the work aren’t always on the same page. And it’s usually not because someone has bad intentions or is deliberately getting in the way. It happens because each group is operating from a different perspective, with different pressures and priorities shaping how decisions get made.

For any successful technology implementation, this misalignment is obviously a huge issue.

Leadership is thinking about direction, timing, and outcomes. IT is focused on system stability, security, and long-term architecture. The business is trying to keep things moving day to day, often under tight deadlines and imperfect conditions. All of those viewpoints make sense on their own, but they don’t automatically line up.

That gap is something we like to call the Devil’s Triangle. It shows up when strategy, systems, and execution drift just far enough apart to create friction, even when everyone is acting in good faith.

The Three Sides of the Triangle

Each side of the Devil’s Triangle plays a necessary role, but they experience the business in different ways.

Leadership is responsible for setting direction and making tradeoffs. The focus is on outcomes, timing, and how the organization moves forward. Most technology conversations at this level stay intentionally high-level, because leaders have to think across the entire business, not inside individual workflows.

IT operates with a different set of responsibilities. Systems have to be secure, scalable, and reliable. Decisions made in one area ripple across the organization, so IT is naturally cautious and detail-oriented. That perspective is critical, but it can also create distance when the business needs quick answers or immediate relief.

The business lives closest to the actual work. These are the teams dealing with day-to-day execution, manual steps, and workarounds that never show up in a strategy deck, and if they do, they’re likely wrong. They feel pressure first and often adapt just to keep things moving. Which is why we see so many spreadsheets.

Problems start when these perspectives stay siloed. Leadership assumes strategy will translate. IT assumes the system design is clear. The business assumes someone else understands what it actually takes to get the job done. Over time, those assumptions compound, and the triangle stretches and often breaks. We can’t build on a broken foundation.

None of this is unusual. It’s the natural result of complexity. The risk comes from ignoring it instead of designing for it.

How Misalignment Shows Up

Misalignment in the Devil’s Triangle rarely announces itself in obvious ways. At first, things mostly work. Projects move forward. Systems go live. Reports get delivered.

The issues tend to surface in smaller, quieter ways. Teams start creating workarounds because the system doesn’t quite match how the work happens.

Data tells slightly different stories depending on where it’s pulled from. Decisions take longer because confidence in the information starts to erode. IT spends more time reacting than planning. The business becomes hesitant to ask for changes because the process feels heavy. Leadership senses (hopefully) something is off, but struggles to pinpoint where the breakdown is happening.

This is also where shadow tools and sneaky side systems appear. Not out of rebellion (most of the time), but out of necessity. When pressure is high and clarity is low, teams solve the problem in front of them, even if it means stepping outside the approved path. Then we start to get those calls like “fix my system,” and IT had no idea those systems existed.

Over time, these small disconnects add up. Trust erodes between groups. Conversations become defensive. Technology starts feeling like an obstacle.

By the time the problem is obvious, the triangle has already stretched further (or broken completely) than most organizations realize.

What Makes Alignment Stick

Alignment across leadership, IT, and the business comes down to staying connected as decisions move from strategy to execution.

Leadership sets direction, but that direction has to remain visible and consistent as work unfolds. When priorities shift without context, teams start filling in the gaps on their own. When outcomes are clear and steady, decisions tend to line up without constant escalation. And remember, this is a journey, not a destination. If they’re not aware of milestones and progress, then we start to hear the “why are we doing this again,” and nobody wants that.

IT plays a critical role in translating intent into systems. That translation improves when context is shared early and often. Understanding how work flows, where data is created, and what constraints exist allows technical decisions to support the business instead of compensating for it later. In my humble opinion, they should oversee all systems and technical strategies.

The business brings reality into the conversation. Operators know where processes break, where time is lost, and where systems fall short. When that perspective is missing, designs slowly drift away from how work actually gets done. We can’t design a system without talking to the end user first.

What holds these perspectives together is shared visibility and support. Process mapping. Open discussion of dependencies. Clear tradeoffs made in real time. Seeing how decisions in one area affect another changes the quality of the conversation almost immediately.

This kind of alignment takes discipline. It doesn’t come from templates or one-time workshops. But when it’s in place, technology supports execution instead of adding friction.

Tying It Together

The Devil’s Triangle describes a pattern that exists in most organizations, especially as technology becomes more central to how work gets done. When leadership, IT, and the business operate with limited visibility into one another, technology decisions begin to compensate for misalignment instead of supporting progress.

Organizations that navigate this well focus less on tools and more on connection. Priorities remain clear as they move from strategy to execution. Technical decisions are grounded in how work actually flows. Operators are involved early enough to prevent drift between intent and reality.

This approach takes more discipline than simply selecting a platform or rolling out a new system. But it creates something far more durable. Technology that reinforces trust, supports decision-making, and strengthens the business without adding unnecessary complexity.

Curious to hear your thoughts on this concept or any additional insights on how to ensure the triangle stays strong.