What Does It Actually Take to Get Two Legacy Departments to Share a Single Digital Platform?

It takes admitting that this is not a technology problem. It is a power problem. Finance and Operations both need a new system. The business case says they should share one platform. The CFO and the COO both nodded in the steering committee meeting. The vendor assured you their platform handles both. And now, six months into implementation, Finance and Operations are barely speaking to each other, the shared data model is a disaster, and both departments are quietly asking whether they can just have their own systems. This is not a technical failure. This is a political failure that everyone pretended was a technical problem.

Deloitte's 2025 research found that 99% of organizations are experiencing operating model changes because of AI adoption. That means processes designed for human workers do not work for agents. Security models built for perimeter defense do not protect against threats at machine speed. And IT operating models built for service delivery do not drive business transformation. But here is what that research also means: getting two departments to share a platform is harder than it has ever been, because the platform is no longer just a tool. It is the operating model. And no two departments want the same operating model.

Here is the practitioner moment: You are the transformation director leading a shared platform implementation for Finance and Operations. The steering committee approved it nine months ago. Both departments were aligned. Now Finance wants the system configured their way because "financial controls are non-negotiable." Operations wants it their way because "operational speed is non-negotiable." The vendor is building two parallel configurations. The shared data model you spent three months designing is being torn apart because Finance and Operations cannot agree on who owns the customer record. Your program is three months behind schedule and 30% over budget. And at the steering committee meeting on Monday, you have to explain why.

This is where Fostering AI-Ready Teams becomes the only pillar that matters. Shared platforms fail because organizations treat them like technology projects when they are actually operating model redesigns. You are not asking two departments to use the same software. You are asking them to give up control, share data they used to own, and trust another department not to break their processes. That is not a technical ask. That is a trust ask. And trust does not get built in a requirements workshop.

The infrastructure built for cloud-first strategies cannot handle AI economics, according to Deloitte's Tech Trends 2026. Organizations that succeed are those with the courage to redesign rather than automate. That applies here. You cannot automate two departments into sharing a platform. You have to redesign how power and accountability flow between them. And that means having three conversations most transformation leaders skip because they are uncomfortable.

So what do you actually do? Not next quarter. This week.

WHAT TO DO MONDAY MORNING

1. Name the power problem in the room. At Monday's steering committee meeting, do not start with the technical update. Start with this: "This project is behind schedule because Finance and Operations do not agree on who owns the customer record, who has final say on system configuration, and what happens when their priorities conflict. We have been treating this as a technical problem. It is not. It is a decision rights problem. And unless we resolve it, the technical work does not matter." Then stop talking. Let the room react. The CFO and COO will probably defend their positions. Let them. Your job is not to solve it in that meeting. Your job is to surface it so the steering committee understands that the delay is not about the vendor or the timeline. It is about decisions the business has not made. Once the committee understands that, they can make the call. If they cannot, the project is going to fail anyway.

2. Separate the shared from the sovereign. Right now, you are probably trying to build one platform that does everything for everyone. Stop. Finance and Operations do not need to share everything. They need to share the things that create value when shared, and keep separate the things that break when forced together. Sit down with the Finance lead and the Operations lead. Draw a line down the middle of a whiteboard. On the left: things that have to be shared for this to work (customer data, transaction records, reporting). On the right: things that can stay separate (workflows, approval chains, how each department actually uses the system). Then build two platforms on one database. Finance gets their workflows. Operations gets theirs. The data layer is shared. The experience layer is not. This is not a compromise. This is architecture that matches the organization. Most vendors will tell you they can do this. Make them prove it. If they cannot, you picked the wrong vendor.

3. Put one person in charge of resolving conflicts. Right now, when Finance and Operations disagree, the issue probably escalates to you. Then to the steering committee. Then to the CFO and COO, who kick it back down with no decision. That loop is why you are three months behind. Break it. Pick one person -- not you, someone closer to the work -- and give them decision rights on any conflict the departments cannot resolve in 48 hours. Finance and Operations have 48 hours to work it out. If they cannot, it goes to this person. They make the call. Their call is final. No appeals to the steering committee. No "let's take this offline." Done. This will make both departments uncomfortable. Good. Discomfort is what breaks the stalemate. If the steering committee will not empower someone to make those calls, tell them you cannot deliver on the timeline. Because without decision velocity, you are just holding meetings while the platform rots.

Getting two departments to share a platform is not about building the platform. It is about redesigning how two departments work together. Written by Transformation Leader. Published at t4leader.com.