Change Request

Formal request to modify project scope/schedule/budget. A working definition from the RGM marketing glossary.

Schematic — Change Request

Formal request to modify project scope/schedule/budget.

Term: Change Request
Field: Product Management
Category: Growth & Lifecycle

A working definition

Start here.Treat Change Request as a lifecycle concept with a clear scope. Two people using the term should mean the same thing.

Formal request to modify project scope/schedule/budget.

In product management, this concept guides how products are scoped, prioritized, built, measured, and iterated. It typically affects roadmap decisions, feature trade-offs, and definitions of success.

In Growth & Lifecycle, Change Request names a lifecycle concept. Pin the meaning down early and the strategy stays coherent.

How it works

Hold that thought.Change Request is no fixed dial. How it behaves depends on your audience, your channel mix, and the strategy around it.

Think of Change Request as context-bound. A small shop reads it simply; an enterprise reads it with more nuance. That is normal -- Change Request is shaped by audience and channel mix. Read Change Request without care and the plan wobbles; be precise and the read holds.

One rule always holds. Settle the scope of Change Request up front, then build the plan. Get it backwards and Change Request becomes a word everyone uses and no one shares. Pick one definition.

When to reach for it

Hold that thought.Bring Change Request in when a live call depends on it. With no decision on the table, it stays background.

Use Change Request when it changes an outcome. For growth & lifecycle teams, that tends to be three recurring moments. With no choice live, Change Request is good to know, not to chase.

Setting budget. Change Request guides the team toward the better-paying line.
Choosing a metric. Change Request shows whether the report will hold up.
Comparing options. Change Request corrects two options that look alike but are not.

A concrete walk-through

Keep this in mind.Below, Change Request is put inside a Spotify setting -- real trade-offs, a clear baseline, and a figure to test it.

Look at Spotify. In a churn-save flow, Change Request drove the decision rather than sitting in a footnote. A baseline came first, then a single agreed meaning of Change Request, then the read: involuntary churn fell about 9%.

Worked example for Change Request -- illustrative figures, RGM analysis
Stage	The step taken	What it bought
Baseline	Read the starting point before any change to Change Request.	A reference to judge against.
Define	Agreed a single definition of Change Request.	A shared definition up front.
Act	A churn-save flow — one variable.	Cause and effect, isolated.
Result	Involuntary churn fell about 9%	A call backed by the read.

Treat the Change Request figures as illustrative, labeled RGM analysis. Reuse the sequence, not the digits.

Pitfalls in practice

Look at it this way.Teams slip on Change Request in four familiar ways. Each makes a soft assumption look like a precise number.

No segments. Treating Change Request as one number for all. Break it out before you trust it.
Bare numbers. Showing Change Request on its own. Context is what makes it readable.
Chasing the word. Optimizing Change Request for its own sake. Check it tracks a real outcome.
Bad compares. Benchmarking Change Request with no adjustment. Account for the model differences first.

Common questions

How is Change Request defined?

Formal request to modify project scope/schedule/budget. Agree the scope of Change Request before the planning starts.

What makes Change Request worth knowing?

Change Request shows up in budget reviews and channel reporting. Use it loosely and teams pull apart; use it precisely and the numbers line up.

How do teams use Change Request?

Change Request supports a real choice: where money goes, what gets measured, which option wins. The Spotify case traces it.

What is the most common mistake with Change Request?

Treating Change Request as one blanket rule and reporting it with no baseline. Both hide a soft assumption.

How is Change Request defined?: Formal request to modify project scope/schedule/budget. Agree the scope of Change Request before the planning starts.
What makes Change Request worth knowing?: Change Request shows up in budget reviews and channel reporting. Use it loosely and teams pull apart; use it precisely and the numbers line up.
How do teams use Change Request?: Change Request supports a real choice: where money goes, what gets measured, which option wins. The Spotify case traces it.