Breaking Down Silos Between IT and Business Units
The silo between IT and the business is one of the most persistent structural problems in enterprise organizations — and one of the most misdiagnosed. Leaders treat it as a cultural problem ("IT and the business don't communicate well") and apply cultural remedies: workshops, town halls, joint offsites. These interventions produce temporary improvement and then revert.
:::kicker Module 6: Organizational Leadership · Article 12 of 14 :::
The IT-business silo is not primarily a cultural problem. It is a structural one — created by organizational design choices that separate the people who understand business problems from the people who build technology solutions. Cultural remedies don't fix structural problems. Structural changes do.
Why Silos Persist
The IT-business silo persists because the organizational design creates conditions for its persistence:
Separate planning cycles. The business plans its strategy in Q3 and Q4. IT develops its plan in Q1. The disconnect is not intentional — it is structural. When plans are developed independently, they are rarely fully aligned.
Separate accountability frameworks. The business is accountable for business outcomes. IT is accountable for project delivery and operational performance. When something falls short, the accountability boundary becomes a blame boundary: "IT didn't deliver" vs. "the business kept changing requirements."
Physical and organizational separation. IT is organized as a function, often co-located. Business units are organized separately. Without deliberate connection mechanisms, the two groups interact primarily through formal request processes — which is the least effective form of collaboration.
Asymmetric urgency. Business units operate at business speed — responding to market changes, customer needs, and competitive pressures. IT operates at implementation speed — which is governed by architecture, testing, security, and capacity. The resulting friction generates frustration on both sides.
The Structural Interventions That Work
:::checklist Breaking down silos: Structural interventions that produce lasting change:
- Embedded IT business partners: Place dedicated IT relationship managers in each major business unit. Their job is not to take IT requests — it is to understand the business unit's problems before they become IT requests and to be a continuous presence in business-side planning.
- Joint accountability for outcomes: For every major technology-enabled initiative, assign joint accountability to an IT lead and a business lead. Both own the outcome metric. Neither can succeed without the other.
- Synchronized planning cycles: Move IT's planning cycle to align with the business's — not the reverse. IT's plan should be a response to and enabler of the business's plan, not a parallel document.
- Cross-functional product teams: For major platform capabilities (customer data, supply chain visibility, employee experience), organize joint IT-business product teams with shared ownership of the capability roadmap and shared accountability for outcomes.
- Rotation programs: Create formal paths for IT professionals to spend 6–12 months in a business unit and for business professionals with technology interest to spend time embedded in IT. Nothing breaks down silos faster than shared experience. :::
The Business Partner Role in Practice
The IT business partner (ITBP) role is the most consistently underinvested and highest-value role in enterprise IT. Done well, it eliminates the silo at the point of contact — replacing the request-response dynamic with a continuous partnership.
An effective ITBP:
- Attends business unit planning meetings and leadership team sessions — as a contributor, not a note-taker
- Surfaces technology implications of business plans before they become projects — including the honest assessment of what is feasible and what isn't
- Translates IT's capabilities and constraints into terms the business unit can use for planning
- Owns the relationship with business unit leadership and is accountable for IT's performance in that relationship
The ITBP role fails when it becomes a sophisticated help desk — fielding requests and escalating to IT rather than shaping the relationship. The measure of a successful ITBP is not request resolution speed; it is whether the business unit leader considers the ITBP a peer.
Shared Metrics as Silo Barrier
One of the most powerful anti-silo mechanisms is a shared measurement framework: metrics that IT and the business both own and both report against. When the customer onboarding time is a metric both the COO's team and the CIO's team are accountable for, the silo disappears by definition — both parties need the other to succeed.
Connecting to the outcome ownership framework from Owning Outcomes, Not Systems, joint metrics create the structural foundation for the cultural collaboration that silo-reduction workshops only aspire to produce.
Next: Measuring What Matters: KPIs for Strategic CIOs
Previous: Building High-Impact IT Teams
Related reading: From Technology Leader to Business Architect · Embedding AI into Business Processes