Ownership and responsibility can be a never-ending challenge in large IT organisations. In fact, it’s rare to find a corporation that doesn’t struggle with these issues. Many people want the authority and control that come with ownership, but they’re wary of the overhead involved, especially in complex cloud environments. This post explores why ownership can be so complicated and offers strategies for clarifying and streamlining it.
Why Ownership Gets Complicated
The Cloud Factor
When dealing with traditional on-premises systems, like physical servers, switches, and firewalls, it’s relatively straightforward to identify who “owns” each piece of infrastructure. But cloud systems often lack the same physical presence and involve more abstract services. For instance, setting up networks across multiple cloud environments or even inside a single cloud environment can involve numerous layers of security and function-specific configurations. Because these configurations are invisible and frequently shared across teams, pinpointing a single owner can be tricky.
Support Costs and Billing
Support in the cloud world is more expensive and convoluted. If something breaks, it could be failing in one of many places, a network misconfiguration, a permissions issue, an application bug, or a problem with the underlying cloud service. Finding who is accountable can feel like detective work:
- Identify which piece is failing.
- Prove that this failure lies in a particular team’s domain.
- Negotiate any associated costs (e.g., cross-charging or project billing).
Because support often entails additional expenses, teams may not want ownership if it means they’ll be on the hook for increased costs. This can lead to a cycle where no one steps forward to take responsibility, and “the last person who touched it” becomes the de facto owner.
Three Layers of Ownership
In many large organisations, ownership tends to break down into three informal layers:
Official (Paper) Owner
The person who appears on the org chart as the owner. They often have sign-off authority and budget oversight. However, this owner might not be the one who reacts quickly when things go wrong.
Escalation or “Real” Owner
Often a senior architect or hands-on manager who steps in during a crisis. This person makes quick decisions, coordinates teams, and resolves technical or logistical bottlenecks.
Issue Owner or Specialist
The subject matter experts who actually fix problems. They hold deep knowledge of a specific system or process. Everyone goes directly to them for specialised help, sometimes bypassing formal channels to avoid paperwork and costs.
This layering can create confusion. The “paper” owner might not actively manage the system, while the “real” owner and specialists handle the day-to-day issues without official recognition or the resources to do so.
The Impact of Fuzzy Ownership
When ownership is unclear, or people avoid it, multiple problems arise:
- Overburdened Specialists: The same experts get called on repeatedly, leading to burnout and capacity issues.
- Budget Battles: Cost centres fight over who pays for support, making cross-charging and billing an administrative nightmare.
- Slowed Innovation: If key people are always dealing with “firefighting,” they have less time for new projects or strategic initiatives.
- Blame Culture: Support rarely gets recognition for maintaining the status quo, but mistakes draw immediate criticism.
How to Fix Ownership Challenges
Define Clear Boundaries
Document who owns what, especially for cloud services. Even if a service is abstract, outline the specific responsibilities of each team or role. Invite technical architects to clarify details for senior management, ensuring everyone understands the scope of each service.
Establish Transparent Budgets
Make sure that ongoing costs (beyond initial project budgets) are well-defined. If a new service or feature will increase the support burden, communicate this early. Agree on how expenses will be allocated so that nobody is surprised.
Prevent “Sneak-Ins”
Some projects quietly introduce new dependencies, only to leave the supporting team footing the bill. Insist on a formal review whenever something new enters production. Ensure that the project’s budget covers the required support or that the correct owner is identified from the start.
Track and Justify Costs
As environments grow more complex, support will inevitably cost more. Keep detailed records of what each service or system requires to run smoothly. This way, you can demonstrate the value provided and justify budget increases when necessary.
Reward Ownership
People often avoid ownership because support work is undervalued. Leadership should incentivise and recognise the teams or individuals who keep critical services running. Providing career growth opportunities, bonuses, or public praise for effective ownership can shift the culture from blame to appreciation.
Final Thoughts
Ownership in large-scale IT isn’t just about assigning a name on an org chart; it’s about ensuring that the right people have both the responsibility and the resources to manage complex infrastructures. By clarifying boundaries, aligning budgets, and recognising the contributions of those who take on support roles, organisations can foster a culture where ownership is genuinely shared and valued, rather than avoided.