What Should Earn a Place on the Roadmap Mid-Cycle?

A product roadmap is a commitment—but not a promise to ignore new evidence. A customer need may become more urgent, a dependency may slip, or a planned feature may cost more than expected. Making room for one change means something else moves back.

What should justify changing an agreed roadmap mid-cycle? How should a team weigh customer impact, cost of delay and existing commitments—and who owns that trade-off? What evidence should be shared with the people whose work or expectations will change?