Demand Management
Capture Every Idea and Fund Only the Right Ones
Give the business one route to request technology investment, and give governance a structured way to qualify and decide.
Demand Management provides a register and workbench for incoming demand, a pipeline through qualification stages, decision-support analytics and configurable governance.
Demand arrives through the back door
Projects start because someone asked the right person, while other requests wait without an answer.
Invisible backlog
Nobody knows the total demand.
Inconsistent scoring
Each request is judged differently.
Slow answers
Requesters wait months for a decision.
What Demand Management covers
Select a capability group to see what it includes.
Intake & register
One route in.
- Demand lifecycle
- Workbench and register
Demand governance is not about saying no — it is about giving every request a fair, fast and recorded answer: yes, no, or not yet. Demand Management gives the business one route in, applies the same criteria to every request, and makes the pipeline visible to requesters and governors alike, so good ideas stop depending on who you know.
Signature view
The Demand Pipeline
Demand is visible, assessed consistently and either rejected, deferred or promoted to the portfolio.
From idea to portfolio decision
Trigger: A business unit submits a demand.
- Step 1
Submit
Demand registered.
- Step 2
Qualify
Completeness checked.
- Step 3
Assess
Value and effort scored.
- Step 4
Decide
Board decision.
- Step 5
Promote
Sent to portfolio.
- Participants
- • Requester
- • Demand manager
- • Architects
- • Governance board
- Work items
- • Demand record
- • Assessment
- • Decision
- Decisions & approvals
- • Qualify or reject
- • Priority
- • Promote to portfolio
- Automation
- • Routing to assessors
- • Stage notifications
- Governance controls
- • Defined criteria per stage
- • Decision record
- Outcome
- Each demand receives a recorded decision and approved items enter the portfolio.
Inside the Demand Management lifecycle
The decisions, exceptions, automation and analytics that make the practice enterprise-grade.
Qualification decisions
The qualify stage checks completeness and fit against explicit criteria; incomplete demand returns to the requester with what is missing, rather than stalling in an unowned queue.
Exception handling: the rejected request
Rejection is a first-class outcome, not a failure: the decision, its rationale and any conditions for resubmission are recorded and visible to the requester, so a 'no' is an answer, not a disappearance.
Automation with accountability
Routing to assessors, stage notifications and similar-demand detection run automatically; qualification, priority and promotion decisions remain with the governance board.
Pipeline analytics
Pipeline health — volumes by stage, decision cycle time, demand by business unit — gives the demand manager and the board a shared, current picture of what the organization is asking for.
Integration across Nexus
Promoted demand enters the Strategy & Portfolio pipeline, cost estimates draw on IT Financial Management, approved demand delivers through Release Management, and Analytics Hub reports pipeline health.
Demand Management in practice
Representative situations drawn from common enterprise strategy and governance patterns.
Shadow demand through the back door
Projects start because someone asked the right person in the corridor, while formally submitted requests wait without an answer.
How Nexus helps: One intake route with a visible register makes total demand known; work that bypasses the pipeline has no record, no assessment and no funding path — so the back door stops being the fast door.
Three requests, one problem
Two departments and a regional office each submit overlapping requests for essentially the same capability, each unaware of the others.
How Nexus helps: Similar-demand detection highlights the overlap at registration, so the assessor can consolidate them into one demand with three sponsors — assessed once, funded once, delivered once.
The requester who waited a year
A business unit submits a request and hears nothing for months; they cannot tell whether it was rejected, forgotten or approved.
How Nexus helps: Every demand receives a recorded decision with its rationale, visible to the requester; stage notifications keep them informed as the request moves, so silence is never the answer.
Aligned with recognized governance and management practice
How specific capabilities support practices from international frameworks. This describes alignment of practice, not certification or formal conformity.
- ITIL 4
Demand Management
Structured intake, consistent assessment criteria and pipeline visibility support the ITIL 4 practice of understanding, anticipating and governing demand for services.
- COBIT 2019
APO05 — managed portfolio
Recorded qualification and promotion decisions, with defined stage criteria, support the COBIT management objective of maintaining a portfolio of programmes and investments governed by consistent criteria.
- ISO/IEC 20000
Service planning and delivery
A governed demand pipeline feeding the service and project portfolio supports the service-management system practices this standard family describes for planning new or changed services.
Why enterprises choose Nexus for demand management
One register for all demand
Every request — from a small enhancement to a transformation programme — enters the same register, so total demand is known and nothing lives only in an inbox.
Consistent criteria, visible decisions
Each stage has explicit criteria and every decision is recorded with its rationale and shared with the requester — assessment is fair because it is consistent and explainable.
A pipeline, not a queue
Demand moves through qualification, assessment and decision stages with defined ownership, so requests progress or are answered — they do not wait indefinitely.
How AI supports Demand Management
Decisions remain with governance boards.
- Recommendation
Similar-demand detection
Overlapping requests are highlighted.
- Assistance
Assessment summaries
Key points summarized for the board.
Enterprise controls built into the lifecycle
Criteria
Stages have explicit criteria.
Decision trail
Outcomes are recorded and visible to requesters.
Tenant isolation
Records are scoped to the organization's own environment.
How Demand Management connects across Nexus
Part of the Enterprise Strategy & Financial Management Function.
What changes for the organization
Full visibility
Total demand is known.
Fair assessment
Consistent criteria.
Faster answers
Requesters get decisions.
Aligned investment
Only qualified demand is funded.
Where this module is used
