# Demand

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/demand

## Quick definition

Demand in ITIL 4 is simply the need for IT services. It comes from users and customers who require something from IT, like access to an application or support for a problem. Managing demand helps IT provide the right services at the right time without wasting resources. Think of it as the signal that tells IT what to deliver.

## Simple meaning

Imagine you run a small coffee shop. Your customers come in and order lattes, cappuccinos, or pastries. Each order is a demand for a specific product. If you don't track these orders, you might run out of milk or have too many pastries left at the end of the day. In ITIL 4, demand works the same way. It is the requests and needs that users and customers have for IT services. These demands can be for new software, access to a network, help fixing a problem, or even just information.

In a company, demand comes from many places. A salesperson might need a new laptop. A manager might request a report from a database. A customer might call for support with a billing issue. All of these are types of demand. IT must understand what demand looks like, how much there is, and when it occurs. This helps IT plan its resources, like servers, staff, and budget, so that it can meet those needs without delays.

If IT ignores demand, problems happen. Too many requests at once can overload the team, causing slow responses and unhappy users. Too few requests might mean IT is overstaffed or has unused equipment. By managing demand, IT can balance the load. For example, if demand for password resets spikes every Monday morning, IT can schedule extra staff to handle it. That way, users get faster service and IT works efficiently.

Demand is not just about requests coming in. It also includes future needs. IT works with the business to predict demand based on projects, new product launches, or seasonal changes. This is called demand forecasting. It helps IT prepare before the demand arrives, rather than reacting after problems occur. Overall, demand is the driving force behind everything IT does. Without demand, there would be no need for IT services at all.

## Technical definition

In ITIL 4, demand is a key concept within the Service Value System (SVS). It is defined as the input to the service value chain that triggers the creation, delivery, and improvement of services. Demand represents the need for value from users and customers, and it can come in many forms: service requests, incidents, changes, or even strategic initiatives. ITIL 4 uses the concept of demand to connect business outcomes with service management activities.

Demand is managed through the demand management practice, which is one of the 34 ITIL 4 management practices. This practice ensures that the organization can anticipate, understand, and respond to demand in a way that optimizes resource utilization and service performance. It involves activities such as demand forecasting, capacity planning, and pattern analysis. Demand management is closely tied to capacity and performance management, as well as service financial management, because demand directly affects resource consumption and costs.

From a technical perspective, demand can be expressed in several forms. In ITIL 4, common demand types include:

- Service requests: standard requests for information, access, or minor changes (e.g., password reset, software installation).
- Incidents: unplanned interruptions or reductions in service quality (e.g., server down, application error).
- Changes: requests for modifications to IT infrastructure or services (e.g., upgrading a database, adding a new feature).
- Projects: larger initiatives that require significant IT resources (e.g., migrating to the cloud, implementing a new CRM).

Each type of demand has its own characteristics. For example, incidents often require immediate attention, while changes may be planned and have less urgency. Understanding the patterns of demand helps IT allocate resources effectively. ITIL 4 introduces the concept of "demand patterns" which are recurring demand profiles that can be analyzed to predict future needs. For instance, marketing campaigns may generate a predictable spike in website traffic, which IT can prepare for by scaling infrastructure.

Demand management also involves defining and managing the service portfolio. The service portfolio includes all services offered by the IT organization, both current and planned. Demand is often compared against the service catalog, which lists services that are available for consumption. If demand exceeds capacity, the organization may need to prioritize, defer, or reject requests. This is where demand prioritization and service level management come in.

In the ITIL 4 examination context, particularly for the ITIL 4 Foundation and Managing Professional modules, candidates must understand that demand is the trigger for value creation. They need to know how demand relates to the service value chain, the four dimensions of service management, and the guiding principles. Questions often ask about the role of demand in the SVS, the relationship between demand and service management practices, and how demand impacts service financial management and capacity planning.

Real IT implementation involves using tools like IT service management (ITSM) platforms (e.g., ServiceNow, Jira Service Management) to capture, categorize, and track demand. These systems allow IT to monitor demand in real time, generate reports, and automate responses. For example, a high volume of password reset requests can be handled by a self-service portal, reducing the demand on the service desk. This is an example of demand shaping, where IT influences demand to align with available capacity.

Standards and frameworks like ITIL 4, ISO/IEC 20000, and COBIT emphasize the importance of demand management. ISO/IEC 20000 specifically requires organizations to have a process for managing demand and capacity. In ITIL 4, demand management is not a standalone process but an integrated practice that supports the entire service value system.

## Real-life example

Think about a popular ride-sharing service like Uber. When you open the app and request a ride, you are creating demand for a car. Uber has to manage this demand in real time. If you are in a busy area during rush hour, there might be many people requesting rides at the same time. That is high demand. Uber uses its algorithms to match drivers with riders based on location, availability, and surge pricing. The drivers are like IT resources, and the ride requests are like service requests.

Now, imagine you are a driver. You see a surge pricing zone because demand is high. You decide to drive there to earn more money. This is similar to how IT scales up resources when demand increases. For example, if many employees log in to a company portal at 9 AM, IT might allocate more servers to handle the load. If demand is low, Uber might send promotions to riders to encourage more demand, like offering discounts for off-peak times. In IT, this could be encouraging users to submit requests during less busy hours.

Another part of the analogy is planning for demand. Uber knows that demand is high on New Year’s Eve, so they prepare by having more drivers available. They also communicate with drivers in advance. Similarly, IT knows that a new product launch will create high demand for support, so they train staff and provision extra capacity beforehand.

What happens if Uber ignores demand? During a big concert, if there are not enough drivers, riders will wait a long time, become frustrated, and maybe use a competitor. The same happens in IT: if the service desk is understaffed during a system outage, users get angry and business operations suffer. Managing demand is about balancing supply and demand so that everyone gets the service they need without waste or delay.

## Why it matters

Understanding demand is critical in IT because it directly affects service quality, cost efficiency, and customer satisfaction. In a practical IT context, every day brings a stream of requests, incidents, and changes. Without a clear understanding of demand, IT teams can become overwhelmed, leading to long wait times, missed deadlines, and burnout. For example, if a help desk receives 200 calls on Monday but only has 10 agents, the average wait time will be very high. Users will be unhappy, and the team will struggle to keep up.

Demand management helps IT plan its capacity. By analyzing historical demand data, IT can forecast future needs and allocate resources accordingly. This might mean hiring more staff during peak seasons, scheduling off-peak maintenance, or investing in automation to handle repetitive requests. For instance, if IT notices that 30% of all service requests are password resets, they can implement a self-service password reset tool. This reduces demand on the help desk and frees up staff for more complex issues.

From a financial perspective, demand drives costs. Every service request or incident consumes time, hardware, or software resources. If demand is not managed, IT may overspend on unnecessary capacity or fail to meet service level agreements (SLAs). Understanding demand helps IT budget accurately and justify investments. For example, if demand for cloud storage is growing 20% per month, IT can negotiate better pricing or implement storage optimization policies.

Demand also influences service design. When IT knows what types of demand are common, they can design services that are easier to consume and support. Self-service portals, automated workflows, and knowledge bases are all ways to shape demand and reduce manual effort. In ITIL 4, the concept of "value co-creation" means that demand helps define what value looks like for the customer. By listening to demand, IT can continuously improve its services.

Finally, demand management aligns IT with business goals. If the business is launching a new product, IT needs to anticipate the demand for related services. Without this alignment, IT may be caught off guard, causing delays that affect the launch. In the real world, companies that manage demand well have higher user satisfaction, lower costs, and more efficient operations.

## Why it matters in exams

Demand is a core concept in the ITIL 4 Foundation exam and appears throughout the ITIL 4 Managing Professional modules, especially in the Create, Deliver, and Support (CDS) and Drive Stakeholder Value (DSV) modules. In the Foundation exam, candidates must understand the role of demand in the Service Value System (SVS). The exam objectives specifically state that demand is an input to the service value chain, triggering the value creation process. Questions may ask: 'What triggers the service value chain?' or 'Which of the following is an input to the SVS?' The correct answer is demand.

In the CDS module, demand management is one of the 34 management practices. Candidates need to know the purpose of the demand management practice: to understand, anticipate, and influence customer demand for services. Exam questions may ask about the activities within demand management, such as demand forecasting, pattern analysis, and capacity planning. For example, a question might present a scenario where a company experiences spikes in demand every Monday morning. The candidate must identify the best response, such as scheduling extra resources or automating common requests.

In the DSV module, demand is linked to the journey from customer need to value realization. The exam covers how demand is captured, prioritized, and fulfilled. Questions might ask about demand prioritization techniques, such as using a service catalog or defining service requests. Candidates should also understand how demand relates to service level agreements (SLAs) and service financial management.

Question types in the ITIL 4 exams include multiple-choice, multiple-response, and scenario-based questions. For demand, scenario questions are common. For example: 'A retail company experiences a 300% increase in support calls during the holiday season. What should the IT department do to manage this demand?' The correct answer is to analyze historical patterns, plan for extra capacity, and possibly implement automation. Distractors often include ignoring the pattern or hiring temporary staff without proper planning.

Demand also appears in the context of the four dimensions of service management. Candidates need to know that demand influences the partners and suppliers dimension (e.g., whether to outsource), the value streams and processes dimension (e.g., how to design workflows), and the information and technology dimension (e.g., using analytics). A common exam trap is confusing demand with capacity. Demand is the need, capacity is the ability to meet that need. Understanding the difference is crucial.

For the ITIL 4 Foundation exam, demand is a relatively straightforward topic, but it can be overlooked. Many candidates focus on processes and practices and forget that demand is the starting point. Reviewing the ITIL 4 Foundation syllabus, demand appears under the SVS and the guiding principles, particularly the principle 'Focus on Value.' Demand represents what customers value, so managing it effectively is central to value creation.

To prepare, candidates should practice with sample exam questions, read the ITIL 4 official publications, and use study guides that explain demand in context. Flashcards for key terms like 'demand pattern' and 'demand shaping' can help. Understanding demand as a concept also helps with other topics like incident management, change control, and service request management because demand drives all these practices.

## How it appears in exam questions

Demand appears in ITIL 4 exam questions in several patterns. The most common is the definition question where the candidate must identify the correct term. For example: 'What is the term for the need or request for services that triggers the service value chain?' The answer is demand. This type is straightforward but tests basic vocabulary.

Another pattern is the scenario question that describes a business situation and asks about managing demand. For instance: 'A university IT department notices a 50% increase in help desk calls during exam week. Which practice would help the IT department prepare for this predictable increase?' The answer is demand management. Sometimes the question includes distractors like incident management or change enablement, which are related but not the best answer for predictive planning.

Configuration-type questions involve analyzing graphs or tables of demand over time. For example: 'Based on the demand pattern shown, which month requires the most capacity?' The candidate must interpret the data and apply capacity planning concepts. These questions test the ability to link demand to resource allocation.

Troubleshooting questions present a problem caused by poor demand management. For instance: 'The IT service desk is overwhelmed with calls, and users are complaining about long wait times. What is the most likely root cause?' The answer could be that demand was not anticipated or capacity was insufficient. The candidate must diagnose why demand exceeded the service capacity.

Multiple-response questions might ask: 'Which of the following are examples of demand in an IT organization? (Choose two.)' Options could include a user logging a service request, a customer reporting an incident, or a server upgrade being planned. The planned upgrade is not demand in the sense of current need; it is a change. The correct answers are the service request and incident because they represent immediate needs.

Another question pattern involves the relationship between demand and other practices. For example: 'Demand management is directly related to which other practice for ensuring that resources are available to meet service requirements?' The answer is capacity and performance management. Understanding these connections is important for scenario questions.

Finally, some questions ask about demand in the context of the service value chain. For example: 'In which step of the service value chain does demand directly trigger activities?' The answer is 'Engage' because that is where customer interactions and demand are captured. Candidates need to know the service value chain steps: Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support. Demand is primarily captured in the 'Engage' step but affects all steps.

To handle these questions, candidates should practice with official sample papers and review the ITIL 4 glossary. Memorizing key definitions is helpful, but understanding how demand works in practice is even more crucial. When reading a scenario, identify the source of demand, the type of demand, and the appropriate management response.

## Example scenario

A medium-sized company called TechFix provides IT support to several retail stores. Every November, the stores prepare for Black Friday sales, which means a sudden increase in support requests. Lisa works as the IT service desk manager. She has noticed that in previous years, the number of calls about point-of-sale system errors triples during the two weeks around Black Friday. She also knows that many store managers request access to sales reporting tools at the last minute.

This year, Lisa decides to manage demand proactively. She reviews historical data from the past three years and identifies a clear demand pattern: support calls peak between 8 AM and 10 AM on Black Friday, and access requests spike the day before. She meets with the IT team to plan. They agree to schedule two extra support staff during peak hours and to set up a self-service portal for access requests that is available 48 hours before Black Friday.

Lisa also coordinates with the retail stores. She sends an email to all store managers, reminding them to request access at least three days in advance. She also creates a knowledge base article with common point-of-sale troubleshooting steps. By doing this, she shapes demand, reducing the number of incoming requests.

On Black Friday, the IT team is prepared. The extra staff handle the increased call volume without delays. The self-service portal works smoothly, and only a few access requests need manual approval. The stores operate without major issues, and the IT team avoids burnout. This scenario shows how understanding demand patterns, forecasting, and proactive planning can turn a potential crisis into manageable operations. In the ITIL 4 exam, a similar scenario could ask what Lisa did well or what she could have done differently. The answer would highlight demand management practices.

## Common mistakes

- **Mistake:** Confusing demand with capacity
  - Why it is wrong: Demand is the need for services, while capacity is the ability to deliver them. They are related but separate concepts.
  - Fix: Remember: demand is the 'what' (requests), capacity is the 'how much' (resources). You manage demand by understanding needs and capacity by ensuring resources.
- **Mistake:** Thinking all demand is unpredictable
  - Why it is wrong: While some demand is unpredictable, many patterns are consistent and can be forecasted using historical data.
  - Fix: Look for recurring patterns such as time of day, month, or events (like payroll or holidays). Use these to predict and prepare.
- **Mistake:** Ignoring demand in service design
  - Why it is wrong: If services are designed without considering demand, they may not handle user volumes or may be too rigid.
  - Fix: Incorporate demand patterns into the design phase. For example, if demand for a portal spikes after updates, design it to auto-scale.
- **Mistake:** Treating all demand as equally urgent
  - Why it is wrong: Different types of demand have different priority levels. Treating a password reset the same as a critical system outage wastes resources.
  - Fix: Categorize demand by type (incident, request, change) and assign priority based on impact and urgency. Use a service catalog to standardize.
- **Mistake:** Not having a demand management process
  - Why it is wrong: Without a process, demand is handled reactively, leading to inefficiency and poor user experience.
  - Fix: Implement a formal demand management practice that includes forecasting, monitoring, and shaping demand. Document the process and train staff.

## Exam trap

{"trap":"In a scenario, the question describes a sudden increase in demand, and the candidate is expected to choose 'Incident Management' as the answer instead of 'Demand Management'.","why_learners_choose_it":"Because the scenario mentions something going wrong or a problem, learners associate it with incidents and incident management. They forget that preparing for the demand beforehand is the demand management practice.","how_to_avoid_it":"Read the scenario carefully. If the question asks how to prepare for a predictable increase, the answer is demand management. If it asks how to handle an unexpected outage, then incident management is correct. Focus on the timing: proactive vs. reactive."}

## Commonly confused with

- **Demand vs Capacity:** Demand is the need for services, while capacity is the maximum amount of service that can be delivered using available resources. You manage demand by predicting and influencing requests, and you manage capacity by ensuring you have enough resources to meet demand. (Example: A coffee shop might have demand for 100 lattes per hour (demand) but only have machines that can make 80 per hour (capacity). Managing demand could mean offering discounts for less popular drinks.)
- **Demand vs Service Request:** A service request is one type of demand. Demand is a broader concept that includes incidents, changes, and even strategic needs. Service requests are typically standard, low-risk requests like password resets. Not all demand is a service request. (Example: A user asking for a new laptop is a service request (demand). But the overall increase in new employee onboarding that causes a spike in all IT requests is a demand pattern.)
- **Demand vs Incident:** An incident is an unplanned interruption or reduction in service quality. Incidents are a type of demand, but demand also includes planned changes and service requests. Managing incidents focuses on restoring service; managing demand focuses on anticipating and influencing all types of needs. (Example: When a server goes down, that is an incident. The resulting flood of user calls is demand. The IT team uses demand management to plan for such spikes, and incident management to fix the server.)

## Step-by-step breakdown

1. **Demand Identification** — IT systems and users generate demand through various channels: service desk calls, email, self-service portals, monitoring alerts, and business meetings. This step involves capturing all demand in a centralized system like a service management platform. Accurate identification is crucial because uncaptured demand can lead to unplanned work and resource shortages. For exam purposes, this step is often represented by the 'Engage' value chain activity where customer needs are first recognized.
2. **Demand Categorization** — Once demand is captured, it must be categorized by type (incident, service request, change), priority, and impact. This helps IT understand the nature of the demand and determine the appropriate response. For example, a password reset is low impact, while a critical system outage is high impact. Categorization also supports reporting and pattern analysis. In ITIL 4, categorization aligns with the service catalog and ensures consistency in handling similar requests.
3. **Demand Analysis and Forecasting** — IT analyzes historical data to identify patterns. This might show that demand for password resets peaks on Monday mornings or that support calls increase after software updates. Forecasting uses these patterns to predict future demand. Tools like trend analysis and predictive modeling can be used. This step is core to the demand management practice because it enables proactive planning rather than reactive scrambling. In exams, candidates must recognize that forecasting is a key activity of demand management.
4. **Demand Shaping and Prioritization** — After analysis, IT can take steps to shape demand, such as encouraging self-service for common requests, scheduling maintenance during low-demand periods, or implementing policies that limit certain types of requests. Prioritization involves ranking demand based on business value, urgency, and resource availability. This ensures that critical requests are handled first. Demand shaping can reduce the load on IT and improve user satisfaction. It is also a way to align demand with available capacity.
5. **Resource Allocation and Delivery** — Based on prioritized demand and forecasts, IT allocates resources (staff, budget, technology) to fulfill the demand. This includes adjusting staffing levels, provisioning infrastructure, and managing timelines. The service value chain activities 'Deliver and Support' and 'Obtain/Build' are directly involved. Proper resource allocation ensures that SLAs are met. Without this step, even the best forecasts would not result in improved service. In exams, this step is often tested through scenario questions about capacity planning.
6. **Monitoring and Improvement** — Demand management is not a one-time activity. IT must continuously monitor demand patterns, compare actuals to forecasts, and adjust. This includes measuring key performance indicators like average response time, fulfillment rate, and user satisfaction. Lessons learned feed back into the improvement cycle, helping refine forecasts and shaping strategies. The ITIL 4 continual improvement model applies here. Monitoring also helps detect new trends or anomalies before they become problems.

## Practical mini-lesson

Demand management is a practical skill that every IT professional should understand, not just managers. In a typical IT environment, demand arrives constantly: password resets, new software installs, network issues, and project requests. Without a structured approach, the team can be overwhelmed. The first step is to set up a service management tool that captures all requests in one place. This could be an ITSM tool like ServiceNow, Jira Service Management, or a simpler ticketing system. Every request should be recorded with a timestamp, category, and requester details.

Once the tool is in place, IT should analyse the data weekly or monthly. Look for patterns: which types of requests are most common? When do they arrive? Which user groups create the most demand? For instance, the finance department might submit many requests during month-end closing. IT can then schedule additional support during that period. This is an example of using historical data to forecast.

Professionals should also think about demand shaping. If 40% of help desk calls are about password resets, implement a self-service password reset tool. This reduces demand on live agents and improves user satisfaction. Similarly, if many requests are for software that the company does not support, create a knowledge base article or a request form that routes to the correct team. Demand shaping can also include communication: send reminders to users about cut-off dates for requests before a holiday season.

What can go wrong? Common pitfalls include ignoring demand patterns, failing to collect data, or not prioritising. For example, if one department submits a large number of low-priority requests, IT might need to discuss with the business to align expectations. Without prioritization, high-impact work can get delayed. Another issue is not having enough capacity during predictable peaks. If IT knows that backups run at 2 AM and want to do maintenance, but demand for incident support spikes at that time, there could be conflicts. Coordination with other teams is essential.

For ITIL 4 exam candidates, the practical lesson is to apply demand thinking to every service. Understand that demand is the reason services exist. When designing a new service, consider who will demand it, how often, and what resources are needed. When evaluating a problem, ask if poor demand management contributed. The exam will test this ability to connect demand to real outcomes. To practice, use the ITIL 4 Foundation app or online sample questions. Study the ITIL 4 glossary and the official publication's chapter on the Service Value System. Remember that demand is the spark that lights the fire of IT service delivery.

## Memory tip

Demand Drives Design, Delivery, and Decisions. Remember the 3 D's: Demand is the Driving force for IT.

## FAQ

**Is demand the same as a service request?**

No, demand is a broader concept. A service request is one type of demand. Demand also includes incidents, changes, and even needs that have not yet been formally requested. All service requests are demand, but not all demand is a service request.

**How does demand management relate to capacity management?**

Demand management and capacity management are closely linked. Demand management predicts and influences the need for services, while capacity management ensures that the organization has the resources to meet that demand. They work together to balance need with ability.

**What is a demand pattern?**

A demand pattern is a recurring trend in service requests or incidents over time. For example, a company might see a spike in password reset requests every Monday morning. Recognizing these patterns helps IT plan resources and automate responses.

**Can demand be negative?**

Demand itself is neutral. However, too much unmanaged demand can overwhelm IT, and too little demand might indicate that services are not valued. The goal of demand management is to achieve the right balance, not to eliminate demand.

**Do all IT organizations need formal demand management?**

While not all organizations have a formal demand management process, every IT team deals with demand. Even a small team benefits from understanding patterns and planning ahead. Formalizing the process improves efficiency and service quality.

**Is demand management part of the ITIL 4 Foundation syllabus?**

Yes, demand is covered in the ITIL 4 Foundation exam as an input to the Service Value System. Candidates should understand its role and relationship to other practices, even though demand management as a specific practice is covered in more advanced modules.

## Summary

Demand is a foundational concept in ITIL 4 that represents the need for IT services from users and customers. It acts as the trigger for the entire Service Value System, turning customer needs into value. Understanding demand helps IT teams forecast, prioritize, and shape the requests they receive, ensuring that resources are used efficiently and services are delivered effectively. Without demand management, IT would constantly react to issues, leading to burnout, wasted capacity, and unhappy customers.

In the real world, demand management involves capturing data, analyzing patterns, and taking proactive steps to influence demand. This can include automating common requests, scheduling extra support during peak times, or communicating with users to set expectations. The practice is deeply connected to capacity management, service financial management, and service level management. For ITIL 4 exam candidates, demand appears in the Foundation exam and in advanced modules. It is tested through definition questions, scenario analysis, and questions about the service value chain.

The key takeaway for learners is to remember that demand is the starting point of IT service delivery. By treating demand as a data-driven practice, IT professionals can improve efficiency, reduce costs, and increase user satisfaction. In the exam, avoid confusing demand with capacity or incident management, and always think about whether a situation involves proactive planning (demand management) or reactive response. With a solid grasp of demand, you will understand the heartbeat of ITIL 4.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/demand