Case Study · ServiceNow SPM · May 2026
How do you give a CEO visibility over $1.55 million of strategic investment she currently can't see at all?
This is the story of building a complete Strategic Portfolio Management implementation on ServiceNow — from blank PDI to executive dashboard — for a fictional company called Acme Corporation.
Act I — The Problem
Acme Corporation is a mid-sized IT services company. 500 employees. Three major initiatives running simultaneously. A cybersecurity expansion. A cloud migration. A new ServiceNow consulting practice.
Combined budget: $1,550,000. Combined visibility for the CEO: zero.
No single view of active projects. Resources double-booked across teams. A board requesting a quarterly roadmap that nobody could produce. Demand arriving from every direction with no process to separate strategic priorities from noise.
Most organizations don't fail at execution because their people are incompetent. They fail because strategy and execution live in different systems — or no system at all.
Act II — The Architecture
Before any demand was entered or any project created, the organizational foundation had to exist. In ServiceNow SPM this means thinking in layers — and getting the layers right before anything else.
Act III — The Governance Test
The first test of any portfolio management system is not whether it can track projects. It is whether it can prevent the wrong projects from starting.
Before a single resource was allocated, the Zero Trust Security initiative went through a structured evaluation process that most organizations skip entirely. The result was a defensible, financially justified, strategically aligned project — not just a good idea from a senior manager.
DMND0001101 → PRJ0010001
Zero Trust Security Implementation
Capital Expenditure
$500,000
Operating Expenditure
$250,000
Total Planned Cost
$750,000
Financial Benefit
$1,500,000
ROI
100%
Assessment Score
65–70
Assessment scores
Five stages. Each one a gate. The project exists because the business case earned it.
Act IV — The Execution
PRJ0010001 was generated automatically from the approved demand. Not created manually. That distinction matters — it means the financial case, the strategic linkage, and the program ownership all carried forward without anyone having to remember to fill in a field.
The dependency chain is deliberate: Security Audit → Gap Analysis → Implementation → SOC Setup. You cannot start phase two without completing phase one. That is not overhead. That is the difference between a project and a plan.
Act V — What the CEO Sees
Phase 5 answers the CEO's actual question — not "what are we building" but "are we on track to meet our goals."
The CEO no longer asks which project to fund next. The data answers that question before the meeting starts.
The Access Model
Seventeen users. Nine groups. Zero direct role assignments. Adding a new project manager takes one action: add them to the ACME Project Managers group. Everything else follows.
| Group | Key Roles | Members |
|---|---|---|
| Portfolio Leaders | it_portfolio_manager, itfm_admin | John Smith |
| Demand Managers | it_demand_manager, assessment_admin | Lisa Wong |
| Executive Viewers | business_stakeholder | CEO, CFO |
| Program Managers | it_program_manager | Ahmed, Hassan, Khan |
| Project Managers | it_project_manager, resource_user | 9 PMs |
| Security Engineers ★ | it_project_user, resource_user | Lee, Wilson, Farooq |
| Cloud Architects ★ | it_project_user, resource_user | Sharma, Carter, Malik |
| SN Consultants ★ | it_project_user, resource_user | R.Khan, Ahmed, Hussain |
| Resource Approvers | resource_manager, timecard_approver | Robert Chen |
★ Group Type: pps_resource — required for Resource Management Workspace. Most common SPM config mistake. Easiest to miss.
The Delta
What This Taught Me
Governance before execution.
The demand intake process is more important than any technical configuration. Organizations that skip scoring and strategic linkage build fast and deliver wrong. Every rogue project I've ever seen started because someone with seniority asked for it. The intake process is how you say no to that politely.
pps_resource is the detail that breaks implementations.
Resource groups without this group type are invisible to the Resource Management Workspace. It's not in the obvious documentation. It's the kind of thing you only know if you've actually built it.
SPM is an organizational discipline, not a technology project.
ServiceNow is the structural body that makes decisions visible and enforceable. But the decisions themselves — who approves demands, what goals everything links to, how resources are governed — have to exist before you open the platform. The technology amplifies your governance. It cannot replace it.
Architecture boundaries are design decisions, not failures.
Phase 4 resource management here is role-based rather than fully automated. That was a deliberate choice given the PDI environment. Identifying what's out of scope and why is a sign of implementation maturity. Forcing an incomplete feature into production to look thorough is the opposite.
Implemented by
Abdul Hadi Sheikh
ServiceNow CSA · CIS-SPM
ServiceNow Australia Release
dev375412.service-now.com · May 2026