Demand Management — The Art of Making Users Behave (Mostly)

"Demand is not a naughty child to be spanked. It's a climate to be understood and, when useful, slightly nudged."

You already know where we stand in the Service Strategy lineup: service portfolio management decided what services we should offer, and financial management told us how to price and measure them. Demand management sits between those two like a behavioral scientist with a spreadsheet — it watches, predicts, and gently steers usage so the portfolio and finances don’t implode during peak season.

---

What is Demand Management? (Quick, not boring definition)

Demand Management is the practice of understanding, influencing, and predicting consumer demand for IT services so that supply (capacity, budget, service levels) aligns with actual and expected usage.

It’s less about making everything cheaper and more about making service delivery scalable, predictable, and cost-effective. Think forecasting + behavioral economics + communication.

---

Why this matters after Portfolio and Financial Management

• Service Portfolio Management decided what we offer — demand tells us whether people actually want it, when, and how much.
• Financial Management gave us costs and pricing rules — demand tells us how to set prices, chargeback models, and when to invest more capacity.

If portfolio tells you what to sell and finance tells you how to charge, demand management tells you when to open extra lanes at the checkout and when to post a friendly tweet asking people to come after 7pm.

---

Core components of Demand Management

1. Patterns of Business Activity (PBAs)
   • Identify recurring business cycles (daily, monthly, seasonal) that drive service use. Example: payroll spikes, end-of-quarter reports, holiday e-commerce traffic.
2. User Profiles
   • Segment users by behaviour, role, SLA needs. Different personas = different demand patterns.
3. Demand Forecasting and Modeling
   • Use historical data, trends, and business plans to predict future loads.
4. Influencing Demand
   • Techniques like pricing, scheduling, throttling, communication campaigns.
5. Measurement and Feedback
   • KPIs, SLAs, usage metrics, and continuous improvement loops.

---

A snackable analogy: The Popular Restaurant

Imagine you run a restaurant that used to be quiet but then got Instagram famous.

• Service Portfolio Management: You decided to add a tasting menu and late-night snacks.
• Financial Management: You calculated cost per plate and set menu prices so you still make profit when busy.
• Demand Management: Now you must manage the chaos — reservations, waitlists, happy hours, and peak pricing. You study when people come, who orders what, and if you can shift customers to slower times with discounts.

Same for IT services: shiftable demand reduces brutal capacity spikes, which saves money and keeps users happy.

---

Real-world examples

• Cloud service provider: Forecasts daily traffic spikes from a client sprints and autoscale rules, while nudging customers to use spot instances for noncritical batches.

• University IT: Notices network load during online registration windows, schedules maintenance outside those windows, and emails students encouraging off-peak registration.

• Enterprise payroll system: Predicts heavy processing at end-of-month; schedules batch jobs and limits interactive reporting during heavy windows.

---

Techniques to influence and manage demand

• Pricing strategies and chargeback: Encourage off-peak usage with lower rates or discounts.
• Scheduling and throttling: Queue or defer non-urgent tasks to less busy times.
• Capacity gating: Limit certain features during peak to protect core service (graceful degradation).
• Communication and education: Inform users about best times and ways to use services.
• Self-service and automation: Reduce human-driven demand spikes with better tooling.

Pro tip: Influencing demand is often cheaper than buying infinite capacity. It also makes you look like a wizard to CFOs.

---

How Demand Management links to other processes

Process	Demand Management Role	Why it matters
Service Portfolio Management	Validates which services are actually needed and when	Avoids investing in unused offerings
Financial Management	Provides usage data for pricing and cost allocation	Enables chargeback, showback, budget planning
Capacity Management	Supplies forecasts and PBAs to inform capacity plans	Prevents over/under-provisioning
Service Level Management	Aligns SLAs to realistic, forecasted demand	Ensures achievable commitments

---

A tiny pseudocode to visualize a forecasting loop

Collect historical usage data
Identify PBAs and user segments
Train simple forecast model (e.g., moving average / ARIMA / ML)
For each upcoming period:
  predict demand
  if predicted > capacity_threshold:
    trigger capacity_plan + cost_estimate
    propose demand_influencing_actions
  else:
    optimize costs (scale down)
Feedback actuals -> retrain model monthly

This captures the continuous cycle: measure, predict, act, learn.

---

Common pitfalls and exam-style traps

• Treating demand as purely technical: it is socio-technical — users, business cycles, and psychology matter.
• Ignoring PBAs: one-time spikes (marketing campaign) vs recurring ones require different responses.
• Confusing demand management with capacity management: demand predicts and influences; capacity provides the supply.
• Overreliance on historical data when the business is growing or changing rapidly — always tie forecasts to business plans.

---

Quick checklist for implementing Demand Management

• Identify PBAs and user profiles for each critical service
• Implement usage metrics and dashboards
• Build a basic forecasting model and review monthly
• Design demand-influencing options (pricing, scheduling, throttling)
• Integrate forecasts with capacity and financial plans
• Run tabletop exercises for sudden business events (campaigns, launches)

---

Closing — Key takeaways (read me twice, exam and boss-friendly)

• Demand Management links portfolio choices and financial plans to reality by predicting and shaping how services are used.
• It uses PBAs, user profiles, forecasting, and behavioral levers to avoid costly overprovisioning and disappointing outages.
• The smartest demand strategy is a mix: better forecasting + smarter influence beats simply buying more capacity.

Final thought: Demand management is where empathy meets economics. If you understand your users like a barista knows regulars, and your spreadsheets like a CFO, you can design services that are sustainable, performant, and surprisingly human.

Version notes: This builds on portfolio decisions and financial inputs, so go re-check the previous modules if you need to link specific services or budgets into your demand plans.

---

Actionable next step: pick one critical service in your org, map its PBAs, and run one week of forecasting. Then propose a single demand-influencing pilot (discount, schedule change, or throttling window). See what happens. Be bored no more.