Every department can produce a reasonable plan and the organization can still end up with an unreasonable whole. Two functions may need the same scarce people. Several projects may depend on one technology capability. One department’s target may undermine another’s operating requirement. That is why departmental translation has to come back to the enterprise before leaders commit resources.
Reasonable departmental plans can collide
In an enterprise integration session, Technology asks for six developers to support a customer portal. Operations wants four of the same developers for exception visibility. Finance has budgeted only enough capacity for one major build. Meanwhile, Sales has a growth target that assumes both initiatives will happen by the second quarter.
Each department can defend its plan. The problem appears only when the plans are seen together. This is the point of bringing translations back to the enterprise: dependencies, contradictions, duplicate work, and resource collisions become strategic decisions rather than private negotiations after the workshop.
Put the competing claims on one visible map and return to the enterprise choices. Which investment most directly supports where the organization chose to play and how it intends to win? Is there a shared capability that can serve both needs? What must wait? The integration session is not about rewarding the best presentation. It is where the strategy meets the budget and discovers whether leadership is willing to fund its own choices.
Review plans against the strategy, not against presentation quality
Ask each department to explain how its plan translates the enterprise choices. The purpose is not to reward the most polished deck. It is to test whether the pieces add up.
Require departments to show strategic contribution, resource needs, major dependencies, risks, and proposed stops. This makes conflicts visible early.
Create an enterprise board for scarce resources: budget, critical people, technology capacity, leadership attention, and major dependencies. When two plans make competing claims, do not solve the conflict privately after the workshop. Make the strategic trade-off explicit.
The question is not which department argues best. It is which allocation best serves the enterprise choices.
Several departments may have proposed similar initiatives without realizing it. Combine them where a shared capability or system would create more leverage. At the same time, look for strategic requirements that everybody assumes somebody else will own. Integration often reveals gaps that no departmental plan could see from inside its own boundaries.
A plan can say one thing while the budget says another. Compare resource allocation with the declared strategic priorities. If yesterday’s projects still absorb most of the money and talent, the organization has not yet committed to the new choice. Commitment becomes credible when resources follow strategy rather than historical habit.
Use an enterprise integration wall
Put the major departmental objectives, projects, resource requests, and dependencies on one visible map. Mark where several departments rely on the same people, technology, data, supplier, or executive decision. Then identify contradictions: one function increasing customization while another is standardizing, one target pushing volume while another protects margin.
Seeing the pieces together changes the conversation. What looked reasonable inside one department may become clearly incoherent at enterprise level.
Do not pretend resource choices are purely technical. Leaders have commitments, histories, and teams behind their requests. Acknowledge those consequences, then return to the strategic choices and agreed criteria. The facilitator cannot remove politics, but can make the basis of allocation more visible than bargaining power alone.
Do not let each department present while everyone else waits for their turn. Give participants an enterprise lens. Ask what assumptions the plan makes about other functions, what shared capability it depends on, where it competes for the same resource, and whether its measures reinforce the strategy. This changes the session from a sequence of presentations into integration work.
After reconciling the plans, build one visible list of work that will stop, shrink, combine, or wait because of the strategy. Without that list, the organization may approve the new plans while continuing to fund the old portfolio.
The stop list is not a symbol of austerity. It is evidence that commitment has consequences.
Make every department challenge another department
After each department posts its translation, assign another department to test it. The challenge is not “Do we like this plan?” Ask instead: Which enterprise choice does this serve? What dependency are you assuming from us or someone else? What resource collision do you see? Which measure could drive behavior against the strategy? What work appears to have survived only because it existed last year?
This cross-check creates conversations that serial presentations rarely produce. A dependency becomes visible before a deadline is promised. Two projects discover they are trying to build the same capability. A target that looked sensible inside one function is exposed as harmful to another. Integration is not a final polish; it is where departmental logic is forced to become enterprise logic.
When integration has done real work
The enterprise review changes at least one departmental plan, resolves a real dependency, reallocates a scarce resource, or stops work that no longer fits. The plans become more coherent because they were tested together. Only then should ownership, rhythm, and proof be finalized.
Put the major department plans on one integration wall and force at least one cross-functional change before resources are committed. Then End With Owners, Rhythm, and Proof.