How to Establish Clear Ownership in Large-Scale IT Organizations

Posted on by Mark Myers Leave a comment

Ownership and responsibility in IT organisations, especially at scale, can feel like a never-ending battle. In fact, it’s rare to find any corporation that doesn’t struggle with it.

This challenge becomes even more complex with the rise of cloud services, where nebulous infrastructure and cross-functional dependencies blur the lines of accountability. Here’s a closer look at why ownership is so difficult to define, and some practical steps for making it work.

1. Understanding the Ownership Challenge

  • People want power without overhead: Many individuals appreciate the influence that comes from ownership but are less enthusiastic about the responsibility of ongoing support, budgeting, and paperwork.
  • Cloud systems complicate matters: Traditional IT ownership is usually tied to physical devices—servers, switches, and firewalls. In a cloud environment, resources are abstracted and often spread across multiple locations or services. This makes it harder to say, “That belongs to me.”
  • Support is expensive and convoluted: When something breaks in a cloud-based system, it can be difficult to know which component is responsible, leading to finger-pointing, delayed resolutions, and confusion about who should pay for fixes.

2. Why Cloud Ownership Is So Hard

  • No clear line of demarcation: A cloud service could span several different areas—networking, databases, microservices, etc.
  • Cross-billing and cost centres: In many organisations, different departments pay for different parts of the infrastructure, and nobody wants unexpected charges.
  • Uncertain support paths: When a service fails, teams must track down the specific issue. The blame game often starts, and ownership becomes something people try to avoid rather than embrace.

3. The “Last Person Touched It” Dilemma

As projects come and go, ownership often falls to the last person who made a change. This unofficial assignment can persist, even if the individual isn’t the designated owner. When something breaks, teams scramble to find that “last person” and push the responsibility (and cost) onto them.

4. Three Layers of Ownership

Official (Paper) Owner

  • Who they are: The individual or team listed on the org chart.
  • What they do: They may have the budget authority and are often responsible for official sign-offs.
  • What’s the problem: If they don’t respond to issues or don’t want to be involved, they may not be the real point of accountability or person that can get things done in a crisis such as disaster recovery.

Escalation Owner

  • Who they are: Often a senior architect or hands-on manager.
  • What they do: Steps in when urgent decisions are needed, especially if the official owner is unresponsive.
  • What’s the problem: They end up doing the real work of ownership, even if it’s not on paper.

Issue Owners

  • Who they are: specialists who know a particular system or tool inside and out.
  • What they do: Fix problems that no one else can.
  • What’s the problem: Because they’re indispensable, others bypass official channels to get them to help, often without official requests or funding.

5. Common Pitfalls of Poor Ownership

  • Overworked Subject Matter Experts: Specialists become overwhelmed by ad-hoc demands, in the worst case getting burnt out and leaving.
  • Cost Center Confusion: Bills and charges get shifted around, causing tension and delaying project progress.
  • Blame Instead of Praise: Support work rarely gets celebrated, but any outage can spark intense criticism.
  • Stalled Innovation: When senior management fears their team will be stuck with endless support work, they may resist taking on new projects.

6. Strategies for Clear Ownership

Define Ownership Boundaries

  • Be explicit about who owns what, especially in cloud environments.
  • Clearly demarcate functional areas: networking, databases, infrastructure, etc.
  • Eliminate confusion by documenting responsibilities in easily accessible formats.

Establish Rock-Solid Budgets

  • Make sure all stakeholders know how costs are allocated post-deployment.
  • Prevent “stealth” additions to production that drive up expenses for unsuspecting teams.

Maintain Transparent Support Models

  • Articulate what support includes and how it is funded.
  • Set expectations for response times, communication channels, and escalation paths.

Align Costs with Accountability

  • If someone owns a service, ensure they also have the budget to maintain it.
  • Provide clear metrics to show how usage increases cost, justifying budget requests.

Recognize and Reward Good Support

  • Make support work visible and acknowledge achievements.
  • Encourage a culture where reliability is celebrated, not taken for granted.

Conclusion

Clear ownership in large-scale IT environments, and particularly cloud-driven ones, requires effort, transparency, and a willingness to tackle the uncomfortable parts of responsibility.

By defining boundaries, clarifying budgets, and establishing clear support expectations, organisations can reduce the chaos of finger-pointing and create an environment where ownership is both feasible and rewarding.

Key Takeaways:

  • Clarify who owns each resource and service (on paper and in practice).
  • Align budget authority with the responsibility for support.
  • Keep communication open and transparent so everyone understands costs, dependencies, and escalation paths.
  • Foster a culture where taking ownership is valued and rewarded, minimising the stigma of blame.

Doing these kinds of things can break the cycle of avoidance and ensure that ownership is something teams want to hold, rather than something they sidestep at all costs.

Communication vs Hard work

Posted on by Mark Myers Leave a comment

 

In a large corporation, would you think communication would be as valuable as real, honest-to-goodness hard work?

Well, the short answer is yes.

It’s easy to get so absorbed in solving technical and business problems that we forget how critical it is to keep everyone else in the loop. You bury your head in code or hardware issues, tackle one problem after another, and hope that once you emerge ‘voilà’ you’ll be hailed as the hero who got it all done.

But here’s the catch: long-term projects, especially those spanning months or years, demand consistent communication. Your customers, whether internal teams or external clients, need updates.
Their priorities shift, their customers ask questions, and they rely on your transparency to know what’s happening. If you disappear and hope they trust you, don’t be surprised if they assume the worst and act on it in ways that can knock everything off track and make your hard work pointless. Lack of communication breeds doubt.

A Dedicated Role for Communication

This is why it’s best to have someone (not one of your buried-in-code tech staff) serve as a dedicated liaison. That person’s job is to keep everyone in the loop about progress, delays, or changes.
Your tech team’s time is too valuable to be wasted on constant status reports, but that doesn’t mean no one should be doing it. It’s crucial to maintain trust by ensuring your customers know exactly what’s going on, even if the news isn’t always great.

Dealing with Delays and Outrage

Of course, consistent communication means facing frustrated customers head-on. People will be upset if a deliverable is late, or if you can’t give them everything they want right away.
But that’s better than letting them stew in uncertainty. Yes, many tech professionals want to please everyone and might feel guilty about having to say “no” or “not yet,” but being honest builds trust in the long run.

Agile as a Communication Framework

Although agile methodologies can sometimes feel tedious, one thing they do well is set realistic expectations. Sprints, user stories, and burndown charts are all tools that help show how long something will take and why.
When customers push for more, you can point to the sprint plan and timeline, then let them negotiate priorities with each other, rather than with you. Once they agree on what’s most important, you can adjust and proceed.
Bottom Line

Hard work is valuable, but without communication, even the hardest-working team risks losing trust and damaging relationships. Keep the lines open, stay transparent about what’s going on, and let your customers know exactly what to expect. In the end, this approach saves everyone time, energy, and stress.

Corporate term: “PowerPoint Overhead”

Posted on by Mark Myers Leave a comment

Definition:

PowerPoint Overhead refers to the time and effort spent transforming actual work or progress into PowerPoint presentations.

Explanation:

Often colleagues or stakeholders only appreciate information in the form of PowerPoint slides and then only in the summary form, and even worse, they may not fully review or value them.

This phrase is a somewhat cynical acknowledgment of the “lost” productivity in creating visually appealing slides rather than focusing on substantive tasks themselves. This phenomenon can be measured by tracking how many hours are devoted to drafting, reviewing, and polishing slides that, in many cases, receive minimal attention or appreciation.

Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.

 

The Starving Project Manager

Posted on by Mark Myers Leave a comment

Have you ever witnessed a moment where a team spends ages perfecting a deliverable, pouring their heart and soul into it, only to present it to a project manager or senior leader who responds with a perfunctory “Great, now next I want you to…”

I’ve seen this from both sides throughout my career, but on a previous client I watched the entire scenario unfold in real time, and recently it clicked in a new way.

When this happens, the team is often stunned at how quickly their hard work is glossed over.

The project manager, from the team’s vantage point, seems impatient, never satisfied, and always hungry for more.

I like to call this situation “Starving Project Manager syndrome.” Here’s why it happens:

Remote Progress is Invisible

In a remote or distributed work setting, project managers might not witness the day-to-day grind. They see tasks stuck in limbo and get harassed by senior stakeholders for updates. From their perspective, progress looks stagnant.

Mounting Pressure

Because nothing outwardly changes for days or weeks, the manager faces constant pressure. Stakeholders demand progress and question why tasks are still open. This increases the project manager’s anxiety and eagerness to “move the needle.”

Ravenous for Results

When the deliverable finally arrives, the project manager is “starving.” It’s as if they’ve been waiting hours at a restaurant, unaware of the intricacy of the chef’s (the team’s) cooking process. The moment that “meal” arrives, they devour it and immediately want more.

The solution lies in finding balance in communication:

Project managers should make a conscious effort to acknowledge the work done even if they don’t know the details of how it is achieved, celebrate wins, even small ones, and communicate the value of what the team has delivered.

Teams might consider providing more frequent progress updates so the project manager (and stakeholders) can see and appreciate the ongoing effort, rather than waiting until the very end.

When both sides understand each other’s perspectives, it becomes easier to manage expectations, celebrate milestones, and maintain morale.

After all, a well-fed, well-informed project manager is less likely to be impatient or “starving” for the next big deliverable, and a recognised, appreciated team is more motivated to deliver quality work.

Final Thoughts

The “Starving Project Manager” phenomenon highlights the importance of communication and empathy in collaborative work.

While it’s natural for a project manager to push for results, it’s equally vital to acknowledge and celebrate the achievements of the team. By doing so, we foster a healthier work environment, one where everyone feels seen, heard, and valued.

Contracting vs. Permanent Employment

Posted on by Mark Myers Leave a comment

 

I’ve spent most of my career working as a contractor. Early on, I moved into contracting after my second job because it offered the skill growth opportunities I wanted.
Since then, I’ve accumulated around 25 years of experience as a contractor, consultant, and vendor. During that time, I only spent two years in a permanent position, and even that was something I did reluctantly.

From my perspective, whether to go permanent or remain a contractor depends entirely on what you want out of your job and your life. Below, I’ll walk through the pros and cons I’ve encountered, in the hope that it helps you make the right decision for yourself.

Why Contracting Can Be Rewarding

Varied Experience
As a contractor or consultant, you often get to work with different companies, cultures, and technologies. This variety accelerates your growth and widens your skill set far more quickly than many permanent roles.

Higher Immediate Earning Potential
Contractors are typically paid more on a day-to-day basis because they forgo benefits such as holiday pay, pension contributions, and company perks. If you’re comfortable managing your own benefits like pension plans and health coverage, contracting can be financially rewarding.

Autonomy
Contractors can usually say “no” more easily. Well, that is not exactly right; everybody can say no, but the ramifications are not normally as extreme for a contractor. You’re not as tied to a single job, and if a project or client doesn’t fit your style, you have the option to move on even at the risk of your reputation.
You also escape the often rigid performance reviews that can happen in permanent roles.

Direct Recognition
In many permanent positions, outstanding work can be overshadowed by bureaucratic performance review processes, like forced ranking and “bell curves.”, this is particularly true for people that do consistently good work year on year.
As a contractor, your performance is judged more on individual tangible results: if you do well, you keep the contract (or earn more); if not, you’re replaced.

Why Permanent Roles Still Appeal

Stability and Security
While contractors may earn more up front, permanent employees usually have stronger legal and social protections, along with a built-in support system for pensions, benefits, and paid holidays.

Goodwill and Longevity
As a permanent employee, you build a reservoir of goodwill within an organization. If you eventually slow down or need flexibility, it’s often easier to negotiate within a

long-term employment relationship.
As a contractor, if you’re not “up to date” or performing at the required level, you can be let go much more quickly, and a client is right to do this after all. “Angels have no memories.”

Reduced Administrative Burden
Pension plans, paid time off, training, and other HR-managed benefits are typically handled for you. If managing the “business side” of your career, taxes, insurance, finding new gigs, doesn’t appeal to you, a permanent role can be much more comfortable.

Camaraderie and Team Culture
Some people thrive in a stable team environment and enjoy growing with colleagues over time. While you can build meaningful friendships as a contractor, permanents often participate more fully in corporate culture and team-building activities.

Making the Right Choice for You

Ultimately, there’s no universal “better” path, only the path that aligns with your goals, preferences, and circumstances. If someone tells you one is unequivocally better, it could mean it’s better for them (or for their organization) rather than for you.

If you value autonomy, variety, and immediate recognition for your work, and if you’re comfortable handling your own finances and benefits, contracting might be a perfect fit.

If you prefer stability, comprehensive benefits, and a long-term growth path (hopefully) within a single organization , a permanent role might suit you better.

Before you decide, take the time to:

Reflect on your career goals: Do you want variety and frequent changes of scenery, or do you want to focus on growth within a single organization?

Evaluate Your Financial Habits: Can you responsibly manage your own benefits, or do you prefer a structure where that’s taken care of for you?

Consider Your Lifestyle Needs: How important is predictability versus flexibility?

Talk to Those Close to You: Personal circumstances and family considerations can heavily influence which path is more sensible.

No one else can make this decision for you. By weighing the trade-offs honestly and thinking about what matters most to you, you’ll be more likely to choose a path that leads to satisfaction and success, whether that means going permanent or being a contractor.