Rimon Cohen
The Minds · Strategy and ownership

You have several technology vendors. Who owns the whole picture?

By Rimon Cohen

CEO, YouCC Technologies ·

In most organizations, nobody does. Each vendor and each team owns its own layer, and the handoffs between them belong to no one. That gap does not show up in any contract, but it lands on management the moment something breaks. The answer is not necessarily one vendor for everything. It is one accountable owner for every critical business service, shared metrics across domains, and a partner that is measured on the outcome, not on the product it sold.

Real accountability starts with one shared picture

Cloud providers work on a shared responsibility model: they secure the infrastructure, and the customer is responsible for configuration, identities and data. Inside the organization, that customer share is then split again, between the cloud team, the security team, the data team, an integrator, an MSSP and a few SaaS vendors. Each one can do excellent work. The exposure sits in the seams between them.

This is not a failure of people. It is what fast growth looks like: Microsoft 365 and Azure next to AWS, SaaS everywhere, AI projects launched by business units, and an org chart that was designed for a simpler world.

The question a CEO should be asking

The question is not how many solutions we bought this year. It is who gets the call at three in the morning when a change in one system takes down a service that depends on four others, and who stands in front of the board the next day.

That question is getting sharper. Regulation, including Amendment 13 to Israel's Privacy Protection Law, puts more weight on management's duty to oversee how data is protected. Customers ask for evidence, not assurances. And AI raises the stakes: launching an AI product needs reliable infrastructure, precise permissions, data governance, predictable cost and operations that can absorb change, all at the same time. If each domain has its own plan, someone has to make sure the plans meet.

What a cross-domain ownership model looks like

Start from the business, not the technology. List the services the business cannot run without, map what each one depends on, and give each one a single accountable owner. Agree on a small set of shared metrics, such as availability, time to an operational decision and cost against plan, and review them at management level every quarter.

This is also why we built YouCC as a group: cloud, security, data and AI under one roof, with YouCC, INNO by YouCC and Bleader working from the same picture. Not because every customer should buy everything from one place, but because someone has to own the connections between the pieces, before go-live and on the day after.

Five questions for the management table

  • Do we have one list of our critical business services, and do we know what each one depends on: infrastructure, identities, data, security and vendors?
  • Does every critical service have one named owner, a person, not a team or a vendor?
  • When an incident crosses teams or vendors, is it written down who decides and who reports to the business?
  • Have we rehearsed a cross-domain failure with IT, security, data, finance and our key vendors in the same room?
  • Does management review a small set of shared metrics every quarter, such as availability, time to decision, ownership coverage and cost against plan?

Common questions

What is the cloud shared responsibility model?

It defines what the cloud provider secures and what the customer secures. In general, the provider is responsible for the underlying infrastructure, and the customer is responsible for configuration, identities, access and data. Many incidents start in the customer's share.

Do we need to consolidate vendors to close ownership gaps?

No. You can keep the same vendors and close the gaps by assigning one owner to each critical service, agreeing on a RACI and defining a decision rule for incidents that cross teams. Consolidation is a separate decision, made on value and total cost.

What is a service owner?

One named person accountable for a business service end to end: its availability, its changes and its reporting to the business, regardless of how many teams or vendors operate parts of it.

How does YouCC work with organizations on this?

YouCC works across cloud, security, data, AI and managed operations as a group, together with INNO by YouCC and Bleader. That lets us map dependencies across domains and help build one plan with clear ownership, instead of a separate plan per vendor.

More from The Minds