OBLYTECH Logo
OBLYTECH Logo
ServiceNow Demand Management for Media and Entertainment
Home / Guides, Services and Solutions / by Industry / for Media and Entertainment / ServiceNow Demand Management for Media and Entertainment

ServiceNow Demand Management for Media and Entertainment

Demand management in media is the process of ranking production, content, technology and audience work when specialist people and fixed broadcast dates set the limits. The guide covers each demand category, resource bottlenecks, sequencing and dependencies, go-to-market timing, and the pitfalls that differ from traditional IT.

The Media and Entertainment Demand Landscape

Media and entertainment organizations juggle multiple concurrent demands: new content series and episodes, maintenance of production infrastructure, technology upgrades for broadcast or streaming platforms, marketing campaigns and audience engagement initiatives. Unlike traditional IT organizations where demand is mostly incremental improvements and maintenance, media organizations have discrete, often time-bounded projects (a new season of content, a limited-time marketing campaign).

Resources are highly specialized and often limited. A cinematographer or sound engineer cannot be easily substituted for another role. Scheduling conflicts are common; people move between projects. Demand prioritization must account for resource constraints and availability, not just business value.

Deadlines are often immovable. A broadcast date is set by contracts and audience schedules. Content must be ready by that date or the broadcast does not happen. Unlike IT projects where dates sometimes slip, media projects rarely have that option.

Demand Categories Specific to Media

Production demands: create new content (series, episodes, specials, films). These demands include script development, preproduction, filming and post-production. Content demands: create or update editorial content (articles, social media, graphics). Technology demands: infrastructure upgrades, platform improvements, technical debt reduction. Audience demands: marketing campaigns, viewer engagement initiatives, platform features for retention.

Each category has different resource requirements and urgency profiles. Production demands have immovable deadlines. Technology demands often have more flexibility. Audience demands respond to market opportunities and can have tight timelines.

Resource Management and Allocation Challenges

Demand Management must address resource availability and allocation. A studio may have five projects in flight but only one head of post-production who is needed on all of them. How do you prioritize when a resource is the bottleneck? Design your prioritization to account for resource constraints.

Specialized skills create bottlenecks. A color grader skilled in a particular medium is harder to replace than a general technician. Capture these expertise requirements explicitly so you can identify when resource constraints drive prioritization decisions.

Seasonal variation is common. Summer is high-production season with many projects launching. Winter is lower. Demand Management should account for this variation in capacity planning. Hiring during summer and reducing through other seasons is normal in the industry.

Sequencing and Dependency Management

Media production has natural sequences. Scripts must be written before hiring crew. Pre-production must be complete before filming. Post-production happens after filming wraps. Some of these sequences are strict; you cannot film before you have a script. Others have flexibility; some editing can happen before filming is complete.

Design Demand Management to capture dependencies between demands (series season 2 depends on season 1 reaching audience thresholds). Sequences are enforced automatically so higher-level demands are not scheduled before their prerequisites complete.

Cross-project dependencies also matter. A marketing campaign for a new series cannot start before content is locked. A platform feature for streaming must be ready before the series launch date. Capture these dependencies so scheduling accounts for them.

Go-to-Market Timing and Windows

Media organizations often have promotional windows: a limited time window for marketing a series launch, a seasonal timing for holiday content, release windows coordinated with other networks. Demand prioritization must account for these external timing constraints.

A demand prioritized long after it was submitted may miss its window. Design your intake process to capture timing constraints. Is this content tied to a specific release date? Is this campaign tied to a seasonal window? These constraints drive prioritization independent of business value.

Checklist for Demand Management in Media

  • Capture demand type (production, content, technology, audience) with appropriate fields for each
  • Capture resource requirements and constraints
  • Capture timeline constraints and go-to-market windows
  • Capture dependencies between demands (sequence, resource conflicts)
  • Design prioritization that accounts for deadlines and resource constraints
  • Establish capacity planning by resource group (camera crew, post-production, etc)
  • Build demand dashboard showing by-status view and by-resource view
  • Integrate with production scheduling to prevent overcommitment

Design Differences from Traditional IT

Traditional IT Demand Management prioritizes by business value and strategic alignment. Media Demand Management adds timeline constraints as a primary factor. A lower-value demand that has immovable deadline often ranks higher than higher-value demand with flexible timeline.

Traditional IT allocates resources by skillset and availability. Media often allocates by specific people. You do not need “a director,” you need Director X who is the right fit for this content. This specificity requires different resource management than generic IT allocation.

Traditional IT capacity is measured in team-months. Media capacity is measured in specific roles and availability windows. A cinematographer is available only during non-filming periods. Design capacity planning around this reality.

Common Pitfalls

Treating all demands as equally flexible is a critical mistake. Production demands have fixed deadlines. Flexibility on production creates cascade failures (can’t launch marketing, audience disappointed, revenue missed). Build rigidity into scheduling for production deadlines.

Ignoring resource constraints in prioritization creates conflicts. A demand is prioritized high but the resource needed is unavailable. The demand stalls. Better to account for resource availability during prioritization.

Not tracking how much is actually being delivered versus how much is committed leads to overcommitment. Capacity planning tools help prevent this by showing current utilization and available capacity.

Separating fixed-date requests from requests that only feel urgent

In many media portfolios, the intake queue is full of requests that carry the word urgent, and very few of them are. The real test is whether a request is tied to a date that another party controls: a broadcast slot already sold to an advertiser, a festival submission window, a licensing renewal that expires whether or not the work is done. Those are fixed-date demands. Everything else is a preference with a deadline attached by the person who wants it. Demand management in a media organization starts by forcing that distinction at intake, because the two kinds of request need different treatment and they compete for the same few specialists.

The person best placed to make that call is often the production or channel planning lead, not the requester. Requesters tend to rank their own work highest, and that is not a fault, but it means the intake form should ask for the external date and the party who set it, rather than a priority field that everyone fills in with the highest value.

Intake fields that expose the real constraint

Five intake questions do much of the work in separating a real constraint from an enthusiastic request. Keep the form short enough that people complete it honestly, and make the external date field mandatory for anything marked as fixed.

Intake field What a good answer looks like What it changes in the decision
External date owner A named contract, schedule or partner, not a department Moves the request into the fixed-date queue
Specialist roles needed Roles such as editor, sound mixer, colorist or motion designer, with hours Shows whether the work competes with a scarce role
Consequence of missing the date A description of what is lost, such as a slot, a rights window or a campaign launch Separates a cost problem from a missed opportunity
Dependency on another project Named project or asset that must be finished first Prevents work from starting against an unfinished input
Reversibility Whether the outcome can be redone after launch Lowers the bar for a fast decision on reversible work

The specialist roles field matters more than the rest in production work. A project that needs one colorist for three days is not the same as one that needs a full post-production crew, even if both are scored as high value. Capacity planning in media is largely a question of who can do which work, and a portfolio view that ignores individual specialists will approve more work than the team can deliver.

A prioritization sequence for a constrained production calendar

When the calendar is full, the sequence below keeps decisions in the right order. It assumes that the planning lead has authority over specialist allocation, which is often the real constraint.

  1. Sort every open request into fixed-date and flexible groups, using the external date owner field as the test.
  2. Place the fixed-date requests on the calendar first, starting from the external date and working back to the latest feasible start.
  3. Check each fixed-date request against the specialist roles field, and flag any role that is booked beyond what is realistic.
  4. Fit flexible requests into the remaining capacity, and state the earliest date each one could start.
  5. Return any request that cannot fit to its requester with the reason and the option to wait, shrink the scope or find another resource.
  6. Re-run the calendar when a fixed date moves, because a single slipped slot can push several flexible requests out at once.

How to tell the process is working

A demand process in media is working when the fixed-date queue is empty of surprises. A surprise here means a request that arrived with a date the planning lead did not know about, or a specialist who was double-booked and only discovered it in the week of the work. Track how often a fixed-date request is accepted without a confirmed external date owner, and how often specialist conflicts are found after approval rather than before it.

Also watch for requests that keep returning. A flexible request that is deferred cycle after cycle is a sign that the business does not really want it, or that it has been mislabelled. Either way the portfolio owner should make an explicit decision, rather than letting the item sit in a queue that nobody reads.

When a formal demand process will slow the work down

Small creative teams working on a single short series often do better with a weekly planning meeting and a shared board than with a full demand process. A formal intake makes sense when several channels, productions or partner deals compete for the same specialists. Below that threshold, the overhead of intake forms and scoring outweighs the benefit. Make the decision on the number of competing demands and the number of scarce roles involved, not on how important the work feels.

A second caution is about scoring. A scoring model that rewards audience reach will systematically favor the most visible channel and starve the work that keeps the archive usable. Keep a separate line for maintenance and rights housekeeping, and protect it from the scoring model.

Questions to resolve before a media demand model is set up

Confirm who holds the authority to move a specialist between projects, which external dates are recorded in a system the planning lead can see, and whether the rights team is part of intake. The third question is often skipped, and it causes the most expensive rework when a license window turns out to be shorter than the project timeline.

Once the fixed dates and scarce roles are on paper, the scoring model is the next thing to test.

Frequently asked questions

How do we handle last-minute demands that are high priority?

Plan for a small reserve capacity (a significant portion) for urgent demands. When urgent demands arrive, pull from reserve. If reserve is consumed, pull from planned work at low risk to execution. This is better than promising to add urgent work on top of full capacity.

Should Demand Management integrate with production scheduling?

Yes. Demand management captures what to build. Production scheduling captures when and who will do it. The two systems must sync so promises in demand align with actual resource capacity and schedules.

How do we prioritize between seasons of a series?

Based on broadcast or release date primarily. Earlier release dates have higher priority. If release dates are the same, consider production complexity, resource availability and strategic importance.

Talk to Oblytech

Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.

Contact us