What keeps Platform Owners up at night? We asked 100+ POs.

[john_mag]

We Asked 100+ Platform Owners What Keeps Them Up at Night. Here's What They Told Us.

Over the past month, we heard from Platform Owners at companies of every size—managing everything from 26,000 employees to 450. And the questions they're wrestling with? They're the same ones, again and again.

So we compiled the top 10 things that keep Platform Owners up at night. And we're posting them here—not because we have all the answers, but because you probably do. Or at least, someone in this community does.

Pick one. Tell us how you're solving it. Tell us how you're not.

THE TOP 10 THINGS THAT KEEP PLATFORM OWNERS UP AT NIGHT

Drawn from real 1:1 conversations and a survey

1. "Is our structure right?" — How are other similar-sized companies organized? What's the benchmark for team size, roles, and reporting lines?
2. "How do we justify this investment?" — What's the ROI? What metrics prove the Platform Owner team (and my role specifically) is worth the cost to my CFO?
3. "What's the career path?" — If I'm a Platform Owner, where do I go next? Is this a dead-end role or a launch pad to something bigger in my organization?
4. "How do we compete for talent?" — How do other companies hire and retain ServiceNow expertise? Finding ServiceNow-skilled people is nearly impossible.
5. "How do we prevent burnout?" — Some of us are working 12-hour days. Is that normal for this role, or are others finding a way to distribute the load?
6. "How do we standardize internally?" — Should all our business units use ServiceNow the same way, or is autonomy acceptable? What's the right trade-off?
7. "What should our governance actually look like?" — The textbook says one thing; reality is messier. What does governance actually look like when it works?
8. "How do we align with the business?" — My executive stakeholders see IT as a cost center, not a strategic partner. How do I change that narrative?
9. "How do we stay ahead of the ServiceNow roadmap?" — Between patches, quarterly releases, new features, and surprise pivots (like product replacements), how do we keep pace without being consumed by it?
10. "How do we break down silos and get real cross-functional alignment?" — Getting IT, HR, Finance, and business unit leaders on the same page about platform direction feels impossible. How do other companies solve this?

Which one hits closest to home for you? Drop a reply below.

[Paer]

These are very good thoughtful points and I think most of us are struggling with most of these.

One that is very topical for us right now is How do we justify this investment?

In an outsourced support model where we have a SN partner that is contracted to keep the light on, mature the platform and advise us on innovation and strategically aligned roadmaps, why do we need to spend additional funds on internal capabilities?

I have worked on both sides of the fence for many years, and I think the platform ownership is critical.

An external party will never have the business insights, contacts and strategic alignment as an internal lead will have. So I think a platform owner is critical and decently easy to motivate as you do not want the outsourcing partner to "run around" internally to all your internal stakeholders.

AND you have invested a lot into SN as a platform, and only an internal owner can drive ROI of the investment, which easily covers the role cost.

Where I think it gets tricky is auxiliary roles such as data owner, cmdb owner, testing resources, citizen developer roles and such. How many of those also critical roles can you motivate to put more focus onto those areas and prevent burnout of the platform owner?

[john_mag]

You're hitting a good point there in terms of the investment ROI being weighed against other models of running ServiceNow - fully owned, managed services/outsourced, or some hybrid. This highlights the finding that Platform Owners can and should be invested in as a strategic internal role. To your point, only an internal employee would have access to more sensitive data, financials, and more importantly, having a stake in the culture overall.

[ARScheuvront]

I think I could have written each of these. Many of these are topics my boss and I discuss in some way every week.

The one that hits hardest for me is burnout. We all wish there was more time in the day, but honestly I do not think it is really about the hours. What has made the biggest difference for me is having an open and honest relationship with leadership. That can make or break burnout. I do not remember where I first heard it, but this quote sticks with me in nearly everything I do as a Platform Owner: "Communication is the key to any working relationship worth having."

Being able to say we need clearer intake and stronger prioritization and that we cannot take on more work without stopping something else first. It is not about saying no, it is about saying maybe now is not the right time. The team also cannot continue to implement new products while ignoring the maturity of the ones we already have.

The more we anchor decisions to business value, the less reactive the team becomes and the more sustainable the model gets.

Easier said than done… I know I am not exactly setting the standard here every time and still catch myself doing the exact opposite some days.

[john_mag]

100% with you regarding burnout. We heard that a lot too. Every PO we spoke with felt pulled in a 1,000 directions - you're not alone. I read your reply after I had typed the above - that direct line/ongoing communication with executive stakeholders is indeed a make-or-break aspect platform ownership. Hence, going by to my point, having an internal PO who has room to be strategic (whenever possible!) is so important to the ROI.