/ABOUT · THE MANUAL
Bought as a technology. Won as an operating model.
ServiceNow is bought as a technology and won or lost as an operating model. This is the manual for that operating model: how the platform is governed, staffed, funded, delivered and run, and who is accountable when the value has to be proven.
Most ServiceNow programmes are told they have a platform problem. They almost never do. They have an org-chart problem, a demand- intake problem, a roadmap problem, a funding-model problem, dressed up as a platform problem.
Why it exists
Search ServiceNow and you drown in the same three things: vendor marketing, partner case studies and certification content. All of it written to sell something, by people who move on the day the SOW closes.
What almost nobody writes down is how the platform is actually operated. Where governance quietly breaks. How demand outruns the team. Why the funding model strangles the roadmap. What happens in year three, when the people who made the early calls have moved on and the decisions they fudged come due. The structural stuff that decides whether the platform pays back, and that no methodology deck was ever stress tested against.
That is the gap the Manual fills. Each edition takes one recurring failure in how ServiceNow gets run and hands you the framework to get ahead of it.
Who writes it
The Manual is written by people who have actually operated ServiceNow at scale, from inside the rooms where these decisions get made, not observing them from a vendor deck. We publish under a single byline, The POM Team, and keep it that way on purpose.
The collective byline keeps the focus on the argument, not the author. It lets us be candid about where programmes fail and which “best practices” don’t survive contact with a real organisation, without dragging in the people and projects the lessons came from. It keeps the analysis clean too: no employer to flatter, no reference client to protect, no personal brand to defend. You get the call as we’d actually make it, not the hedged version.
What you don’t get is theory. Everything here has been deployed, argued for in a real room, and lived with long enough to know exactly where it bends.
What we cover
Every edition is filed under one of thirteen editorial clusters, the recurring shapes of operating ServiceNow at scale:
- Governance & Org Structure
- Platform Strategy
- Finance & ROI
- Delivery & Risk
- Adoption & Change
- Team & Roles
- Stakeholder & Comms
- Security & Compliance
- Demand & Intake
- Vendor & Partner
- Experience & Adoption
- Innovation & Funding
- Support & Enablement
Editions land when there is a framework worth sending, not to hit a calendar slot. The clusters run deep, with far more queued than published, so there is always somewhere to go next. See every cluster.
Editorial stance
There is always a free newsletter.
The core newsletter stays free and the archive stays open. Paid tiers or products may sit alongside it in time, but the free edition never goes behind a paywall.
Editorial stays independent.
When something is sponsored or paid, it is labelled as such and kept out of the editorial. The analysis, and the calls it makes, are ours.
No fixed schedule, no filler.
Editions land when there is a framework worth sending, not to hit a calendar slot. When something reaches your inbox, it is because it earned the send.
Frameworks, not hot takes.
Every edition ships at least one framework, matrix or diagnostic a reader can lift into their own programme docs on Monday morning.
Who it is for
Platform owners deciding how to staff a centre of excellence. Programme leads defending a governance model to an executive steering committee. Architects choosing where demand intake ends and delivery governance begins. Transformation sponsors who need the board paper, not the vendor slide. And the consultants advising all of them, who want something to reference that was not written by a competitor.
If you have ever had to explain a cost model to a CFO, rebuild a CoE charter in a week or justify a platform team’s headcount to someone who thinks ServiceNow runs itself, this is written for you.