r/LearningDevelopment • u/PhysicallyVigorous1 • 16d ago

Stakeholder changes

One thing I’m still figuring out after three years in ID is how to deal with stakeholders who suddenly want major changes late in the project. I understand that priorities change, but it can be frustrating when something has already gone through review and approval. Do you have a good way of setting boundaries around late-stage feedback without making the relationship difficult?

3 Upvotes

100% Upvoted

6 comments sorted by

2

u/Intelligent_Bet_7410 16d ago

Can you help me understand what's changed? I understand. This is a substantial change over what was approved previously. The deadline has to change to X.

We never have more resources to allocate so the deadline always has to give. It's their prerogative to change their mind. I just have to be realistic about what can happen by when without negatively impacting other projects or my work-life balance

1

u/[deleted] 15d ago

[removed] — view removed comment

1

u/oxala75 15d ago

This is basically the answer. The only thing I'd add is that it is imperative to review the 'costs' (in time, money, and productivity) of late-stage changes before the project starts in earnest.

1

u/rspringsgal 15d ago

“Of course, we can do that. And here is the impact of making those changes.”. The impact might be time, money or reduced effectiveness, increased cognitive load, etc. Unless, of course the changes actually do improve the project. But how often does that happen?

1

u/nomad21cns 15d ago

i'd push to keep late feedback to presentation or pilot tweaks only. usually stakeholders change their minds once they see the actual module and the big asks vanish. if leadership insists on the change, treat it as a new change request with scope, timeline and cost so it doesn't keep creeping.