Opportunity, demand and value

Every organization faces more possible work than it can do. Users ask for new features, managers propose projects, suppliers pitch new technologies and incidents expose things that should be fixed. The service value system begins with this raw material: opportunity and demand. What happens next decides whether the organization delivers value or simply stays busy. This lesson looks closely at the inputs to the system, how they are captured, filtered and prioritized, and how the organization knows whether the value it intended has actually been realized.

Two kinds of input

Lesson 1 defined the two inputs. Demand is a need or desire for products and services from internal or external consumers. Opportunity is an option or possibility to add value for stakeholders or improve the organization. The distinction matters because the two arrive differently and are handled differently.

Demand usually arrives through known channels: a service request, a call to the service desk, a sales enquiry, a project proposal from a business unit. It is attached to a stakeholder who expects a response. Opportunity often arrives without an owner. It might be noticed by an engineer reading release notes, an analyst reviewing incident trends or a manager talking with peers at a conference. Unless the organization has a way to capture opportunities, many are simply lost.

Demand is not uniform

Demand varies in volume, timing and predictability. Some demand is steady: password resets arrive at a fairly constant rate every working day. Some is seasonal: a tax-preparation firm sees enormous demand in the spring, a university at the start of each term, a retailer before major holidays. Some is driven by events: a new software release produces a wave of how-to questions; an outage produces a flood of incident reports.

Understanding these patterns lets an organization plan capacity. ITIL calls this demand management in older material and capacity and performance management as a practice; the details belong to ITIL-141. At the system level, the point is that the plan and engage activities must understand demand patterns, otherwise teams will be idle at some times and overwhelmed at others.

Capturing opportunity

Because opportunities lack a natural owner, organizations need deliberate ways to capture them. Common approaches include an idea portal open to all staff, a regular review of problem records and incident trends, a technology radar that tracks emerging tools, and structured conversations with customers about their future plans. The continual improvement register described in ITIL-120 can hold improvement opportunities alongside other ideas.

Capturing an opportunity is not the same as committing to it. A good capture process asks for a short description of the expected value, the stakeholders affected and a rough size. That information lets the plan activity and governance compare opportunities fairly with demand, rather than favouring whichever arrives with the most enthusiasm.

Filtering and prioritizing

Since capacity is limited, the system must decide which demand to fulfil, in what order, and which opportunities to pursue. ITIL leaves the method to the organization, but the decisions should be guided by value and made transparently. Typical filters include alignment with strategy, legal or regulatory obligation, risk reduction, cost, and the size of the benefit.

One widely used technique is weighted shortest job first (WSJF), introduced in ITIL-120. It divides the cost of delay of an item by its size, so that small, high-value items rise to the top. Cost of delay combines the value to users, the time sensitivity of that value, and any risk reduction or opportunity enablement.

Saying no, or not yet

Filtering means some demand will be declined or deferred. How that is handled affects the relationship with the consumer as much as the decision itself. A request that disappears into a backlog without a response damages trust. A clear explanation (what was decided, why, and what alternatives exist) preserves it. The engage activity, covered in lesson 5, is responsible for this communication.

Some demand cannot be refused. Legal and regulatory obligations, security vulnerabilities and safety issues must be addressed regardless of their WSJF score. Many organizations handle these as a separate class of work with reserved capacity, so that mandatory items do not crowd out everything else unpredictably.

From value intended to value realized

When an item enters the system, someone usually has an idea of the value it should create: faster processing, fewer errors, new revenue, lower cost or reduced risk. That is value intended. Value is realized only when consumers actually use the product or service and achieve the outcome. The gap between the two can be large. A new self-service portal that nobody uses realizes no value, however well it was built.

For this reason, the system should track items beyond delivery. Useful questions include: Is the service being used? By whom? Did the expected outcome improve? Did new costs or risks appear? These questions feed back into the plan and improve activities and into governance.

Value for whom?

Different stakeholders value different things, and a single item can create value for some while imposing costs on others. A tighter security control may create value for the organization by reducing risk while imposing friction on users. A new feature may delight one customer group while confusing another. ITIL-110 introduced the idea of balancing outcomes, costs and risks for each stakeholder. At the system level, governance must decide how to weigh these interests, and the engage activity must make sure each stakeholder's view is heard.

Public-sector organizations face particular versions of this question. In Canada, a federal service must weigh the value to the individual client against obligations such as official languages, accessibility under the Accessible Canada Act and privacy under the Privacy Act. A change that is cheaper for the department but less accessible may not be acceptable at all.

Inputs, outputs and the rest of the course

The remaining lessons follow opportunity and demand into the value chain. Lessons 3 to 7 explain the six activities that process them. Lessons 8 and 9 show how value streams combine those activities for specific kinds of demand. Lessons 10 and 11 add the holistic view of the four dimensions and the role of partners and suppliers. Lesson 12 returns to governance and improvement, which keep the whole system pointed at value.