Demand Management

In most organizations, requests for new work arrive from many directions: business units want new capabilities, regulators require changes, technology teams need to replace aging systems and executives launch new initiatives. Without a way to manage this flow, requests either pile up in an unstructured backlog or go straight into delivery teams through informal channels. In both cases, nobody has a clear view of the total demand or of which requests matter most. Demand management brings these requests into a single process where they can be understood, compared, combined and either approved, deferred or declined.

The goal is not to suppress demand but to shape it. Good demand management helps requesters describe what they need, avoids duplicate requests, identifies where existing capabilities could meet the need and makes sure that approved work matches what the organization can deliver. For portfolio leaders and IT finance teams, it is the front door of the portfolio: the decisions made here determine what will later consume budget and capacity.

Definition of Demand Management

Demand management is the set of processes for capturing requests for projects, enhancements and services, assessing their value, cost and urgency, and deciding which to pursue, in line with strategy and available capacity.

The term is also used in supply chain and IT service management with related but different meanings. In supply chain, it refers to forecasting and influencing customer demand for products, and in IT service management, to anticipating demand for services. In portfolio management, it connects closely to project intake, which captures requests, and portfolio prioritization, which ranks them.

Types of Demand

Strategic demand comes from initiatives that carry out the organization's strategy, such as entering a new market or transforming a customer experience.

Operational demand comes from improvements to existing processes and systems requested by business units.

Mandatory demand comes from regulatory, legal, security or contractual requirements that must be met regardless of their business value.

Technical demand comes from the need to maintain, upgrade or replace systems, such as addressing technical debt or end-of-life platforms.

Each type is usually assessed differently, since mandatory work cannot be declined and technical work often has indirect benefits that are harder to quantify.

Stages of Demand Management

Capture collects requests in a consistent format through a single entry point, with enough information to assess them. Short forms work better than long ones at this stage.

Triage screens requests quickly, routing small ones to the right team, combining duplicates and identifying those that need fuller assessment. Fast triage keeps simple requests moving and saves detailed analysis for the ones that need it.

Assessment estimates value, cost, risk, urgency and strategic fit, often with help from architects and finance.

Decision approves, defers or declines each request, usually in a regular portfolio review, and communicates the outcome to the requester.

Importance of Demand Management in Strategic Portfolio Management

Demand management protects capacity. By controlling what enters the portfolio, it prevents delivery teams from being overwhelmed by more work than they can handle.

It improves the quality of investment decisions. Requests that have been clarified, combined and assessed are easier to compare and more likely to deliver value.

It also gives leaders visibility of total demand, which shows the gap between what the organization wants and what it can deliver and informs decisions about budgets and staffing.

Demand Management and Financial Management

Total demand, expressed in cost and effort, gives finance teams an early view of the funding needed in future periods and supports budget planning.

Assessing requests against expected value and cost, using measures such as return on investment, helps direct funding to the strongest proposals.

Identifying duplicate requests and opportunities to reuse existing systems avoids spending on overlapping solutions. Checking requests against the business capability map often reveals that a need is already met elsewhere.

Tracking the demand that was declined or deferred shows the cost of capacity constraints, which can support the case for additional investment.

Common Challenges

Requesters may bypass the process by going directly to delivery teams, especially if the formal process is slow.

Overly detailed request forms discourage submissions and delay decisions on small, simple requests.

Without clear communication of outcomes, requesters may feel their needs are ignored, which reduces trust in the process. Long waits for decisions have the same effect, and encourage requesters to inflate urgency to get attention.