The IT Portfolio No One Can Hold in Their Head Anymore
September 17, 2026
A CIO running a single, centralized IT team can hold the entire project portfolio in their head. A CIO running IT across six business units, three countries, and a compliance function that reports separately to the board cannot. That gap is not a matter of degree. It is a different problem, and it is why the same portfolio management conversation plays out so differently once IT investment decisions stop running through one room.
At that scale, the portfolio is no longer a list of projects. It is a competition for a finite pool of capital, skilled people, and executive attention, playing out across business units that each believe their initiative is the priority. Spreadsheets and disconnected project tools do not fail here because they are poorly maintained. They fail because the coordination problem has outgrown the tool.
The numbers back this up. Tempo Software's 2026 State of Strategic Portfolio Management report, based on a survey of 667 planning and PMO leaders across 43 countries, found that nearly one in three enterprise projects fails to deliver meaningful ROI. The same report found a stark performance gap: organizations with mature, data-driven portfolio practices deliver measurable value on 81 percent of projects, compared to just 45 percent among organizations still relying on static, spreadsheet-driven planning cycles. In a modeled scenario, that gap translated into as much as $260 million in lost annual value for a large organization.
PMI's Pulse of the Profession research puts a similar number on the waste: organizations lose an average of 9.9 percent of every dollar invested in projects to poor project performance. For an enterprise running a $200 million annual project portfolio, that is roughly $20 million a year leaking out through misallocated capital, duplicated initiatives, and projects that should have been stopped two quarters earlier.
McKinsey's research adds a sharper edge: 17 percent of large IT projects go so badly that they threaten the survival of the organization that funded them. That is not a missed deadline. That is a governance failure, and it is the specific failure mode that portfolio management at scale exists to prevent.
Mid-market organizations manage a portfolio. Large enterprises manage a portfolio of portfolios, and the difference shows up in four places.
Below a certain size, IT investment decisions run through a handful of people who can meet in one room. Once decision-making is distributed across multiple business units, each with its own P&L and its own executive sponsor submitting demand independently, that room no longer exists. Without a shared intake and scoring model, the loudest sponsor wins, not the highest-value initiative.
A core banking platform upgrade, a regulatory compliance initiative, and a customer experience redesign rarely stay in their own lanes at enterprise scale. They share infrastructure, share the same senior engineers, and share the same change windows. When those dependencies live in separate spreadsheets maintained by separate teams, nobody sees the collision until it happens.
Large enterprises, particularly in banking, insurance, and government, answer to regulators who want to see how capital allocation decisions were made, not just what was decided. A portfolio that cannot produce an audit trail of demand, prioritization, and funding decisions creates real exposure, independent of whether the underlying decisions were sound.
Growth by acquisition brings in workforces, systems, and PPM methodologies that a parent organization's existing tools were never built to absorb. Reconciling three different project taxonomies after a merger is a portfolio management problem before it is anything else.
That governance complexity connects directly to data quality. As explored in CMDB & AI Agents in ServiceNow: The Real Dependency, any system that promises to prioritize investment or automate decisions is only as reliable as the configuration data underneath it. The same principle applies to portfolio management: an SPM tool sitting on top of an unreliable CMDB will produce confident, wrong prioritization.
ServiceNow Strategic Portfolio Management, formerly known as IT Business Management (ITBM), is the portfolio layer of the Now Platform. It brings demand intake, resource management, financial planning, and performance analytics into a single system rather than a set of tools that require manual reconciliation.
Four capabilities matter most at enterprise scale:
Because SPM runs natively on the Now Platform, portfolio data lives alongside the operational data already in ITSM and CMDB. For an enterprise that has already invested in ServiceNow for service management, that shared data model is the practical argument for extending into SPM rather than adopting a separate, standalone PPM platform: one source of truth for what is running, what is planned, and what it costs, instead of a manual export-and-reconcile process between systems.
Enterprises that have gone through this transition report the earliest, most visible wins in governance and visibility rather than in raw delivery speed. Standardized intake and prioritization workflows cut the coordination overhead that used to consume entire planning cycles. Executive dashboards replace the monthly ritual of assembling a portfolio status deck from six different spreadsheets. Resource conflicts that used to surface mid-project, when they are expensive to fix, surface during planning instead.
The same governance logic that makes SPM valuable for portfolio oversight applies to other categories of enterprise risk. End the Vendor Risk Compliance Chaos with ServiceNow covers a parallel case: continuous, workflow-driven oversight replacing an annual questionnaire cycle that cannot keep pace with how fast vendor relationships change.
SPM is not a plug-and-play deployment, and enterprises considering it should go in with clear eyes about where the friction lives.
Not every organization needs the full weight of enterprise Strategic Portfolio Management. The complexity and licensing structure that make sense for a large, multi-business-unit organization running dozens of concurrent, interdependent initiatives are more than a smaller organization with a single, centralized PMO typically needs. Organizations below that scale are usually better served by lighter-weight project and work management tools that solve the same visibility problem without the governance overhead.
The clearest signals that an organization has crossed into enterprise SPM territory:
These signals show up consistently in regulated, large-scale environments. How Government Agencies in LatAm Are Modernizing Operations: ServiceNow for Public Sector and Legacy Systems in Banking: The Real Cost of Not Migrating both describe the same underlying pattern from different verticals: large, regulated organizations discover that fragmented systems and manual reconciliation are no longer a productivity inconvenience but a genuine strategic risk.
This kind of portfolio complexity is not evenly distributed across industries. In Latin America and the Caribbean, it concentrates most heavily in banking, insurance, telecommunications, and public sector institutions, and each of those verticals hits SPM's value proposition from a slightly different angle.
Large banks in the region are already running parallel transformation portfolios: core banking modernization, regulatory compliance programs, fraud and AI initiatives, and customer experience redesigns, often at the same time and often competing for the same scarce engineering talent. A bank's PMO cannot treat these as four separate portfolios managed in four separate spreadsheets without eventually double-booking the same senior engineer across two supposedly unrelated projects. SPM's resource management workspace exists precisely to catch that collision during planning instead of during a missed go-live date.
Government institutions carry a version of the same problem with an added layer: multi-year budget cycles, procurement rules that constrain how quickly funding can move between initiatives, and public accountability for how capital was allocated. A portfolio governance system that produces a defensible audit trail is not a nice-to-have in this context, it is close to a legal requirement. Agencies modernizing their operations tend to adopt SPM as part of a broader platform investment rather than as a standalone purchase, since the same underlying data model that supports service management also supports portfolio oversight.
Telecom operators managing network infrastructure, customer service platforms, and regulatory compliance simultaneously face a similar cross-portfolio dependency problem, compounded by the sheer physical scale of infrastructure projects that span years and touch thousands of field technicians. Portfolio visibility that spans both the digital and the physical side of the business becomes a genuine competitive differentiator, since delays in either domain cascade into the other.
Across all three verticals, the pattern GB Advisors sees repeatedly is the same: organizations delay a formal SPM rollout until a portfolio failure becomes visible enough to force the conversation, usually a missed regulatory deadline, a very public project overrun, or an executive discovering mid-year that three business units had independently funded overlapping initiatives. Enterprises that get ahead of that moment, rather than reacting to it, tend to have an easier and less politically fraught implementation.
ServiceNow SPM is not the only enterprise-grade option, and a fair comparison matters more than a partner pitch. Planview and Clarity-class platforms are built specifically for large enterprises that need deep portfolio governance and standardization across programs, independent of any particular ITSM vendor. Planisware tends to fit R&D-intensive organizations managing long product-development cycles and stage-gate processes. Both categories can outperform SPM on portfolio-management depth alone.
Where SPM wins is context, not raw PPM feature depth. An enterprise that already runs ServiceNow for IT service management, HR, or CMDB gets portfolio data living alongside operational data in the same system, rather than a second platform that requires its own integration layer and its own data reconciliation process. For organizations already committed to the Now Platform, that integration advantage typically outweighs the marginal feature gap with a specialized PPM tool. For organizations without an existing ServiceNow investment, a standalone PPM platform deserves genuine consideration before defaulting to SPM on brand familiarity alone.
Timelines vary with scope, but a phased rollout starting with demand intake and prioritization for a single business unit or portfolio typically reaches initial production use within a few months. Expanding into full resource management, financial planning, and multi-business-unit rollout across a large, multi-entity organization is a multi-quarter program, not a single project, and vendors that promise a full enterprise cutover in weeks are underselling the change management work involved.
Not necessarily. SPM operates at the portfolio layer, above individual project execution. Many enterprises keep team-level execution tools in place for day-to-day work and use SPM for the layer that those tools were never built for: cross-portfolio prioritization, resource allocation across teams, and executive-level financial tracking. The practical question is less "replace or keep" and more "which layer does each tool own."
Enterprises evaluating ServiceNow SPM should treat it as a portfolio governance initiative, not a software rollout. That means securing executive sponsorship that spans business units before configuration begins, since a tool that standardizes intake will surface uncomfortable prioritization conversations that some sponsors would rather avoid. It means auditing the state of the underlying CMDB and ITSM data first, since SPM inherits any data quality problems already present in those systems. And it means planning the rollout in phases, starting with the business units and portfolios where the coordination pain is most visible, rather than attempting an enterprise-wide cutover on day one.
GB Advisors works with large enterprises across Latin America and the Caribbean on exactly this kind of phased ServiceNow SPM implementation, from initial portfolio assessment through configuration and change management. If your organization is managing project demand across multiple business units without a shared system of record, talk to our team about what a phased rollout could look like for your specific structure.
Schedule a conversation with GB Advisors' ServiceNow team to assess whether enterprise SPM fits your portfolio.
