Project Management

Please login or join to subscribe to this thread

In fast-paced projects, how do you handle conflicts during change management without slowing down delivery?

linkedin twitter facebook   Change Management  
avatar
Srikana Ray
Community Champion
IT Project Manager

In fast-paced project environments, traditional, slow-moving change control boards can block progress. However, bypassing them leads to misalignment and team conflict over shifting priorities.

I would like to learn how project managers handle these conflicts and maintain speed of project delivery while keeping stakeholders aligned.

What strategies do you use to resolve conflicts quickly and effectively?

Sort By:
< 1 2 >
avatar
Robert Snyder Founder & President| Innovation Elegance, LLC Chicago, Il, United States
Srikana, another consideration for you is to recommend a formal frequency for the Change Control Board (such as monthly) and a formal LOW latency of their work. For example ... a schedule ...

Monday: draft the Change Log & any other materials
Tuesday: review & revise the materials
Wednesday: approve the materials
Thursday: distribute the materials
Friday: contingency

The goals are simplicity, transparency, low latency.
The authority sits with the person assigned "Approve."
If the board shrugs at latency, you have license to exaggerate the latency into absurdity.
An example of absurdity is a monthly process that requires 6 months to finish (i.e., the processes overlap, which is absurd). 😊
...
1 reply by Srikana Ray
Jul 20, 2026 11:56 AM
Srikana Ray
...
Thank you for the suggestion.
The Change Control Board already runs on a schedule, however urgent project changes and last-minute project manager requests sometimes require more careful consideration and expedited approvals before proceeding making the wait time a significant challenge.
avatar
Srikana Ray
Community Champion
IT Project Manager
Jul 18, 2026 6:16 AM
Replying to Robert Snyder
...
Srikana, another consideration for you is to recommend a formal frequency for the Change Control Board (such as monthly) and a formal LOW latency of their work. For example ... a schedule ...

Monday: draft the Change Log & any other materials
Tuesday: review & revise the materials
Wednesday: approve the materials
Thursday: distribute the materials
Friday: contingency

The goals are simplicity, transparency, low latency.
The authority sits with the person assigned "Approve."
If the board shrugs at latency, you have license to exaggerate the latency into absurdity.
An example of absurdity is a monthly process that requires 6 months to finish (i.e., the processes overlap, which is absurd). 😊
Thank you for the suggestion.
The Change Control Board already runs on a schedule, however urgent project changes and last-minute project manager requests sometimes require more careful consideration and expedited approvals before proceeding making the wait time a significant challenge.
avatar
Robert Snyder Founder & President| Innovation Elegance, LLC Chicago, Il, United States
So are there two goals that are mutually exclusive? Or do you see the goals as congruent? I'm unsure if the two things can be true at the same time.

One (absurd) idea is to remove the interdependency. Perhaps urgent projects should start independent of the waiting on the CCB.

Is the waiting more painful than the dependency integrity?
avatar
John Henchy Program Manager| Sanofi Nazareth, Pa, United States
My experience supports the change control governance implementation as a funnel moving from "Wide Open" to "Very Narrow" over the course of engineering. Early stages the project team and leadership must be open to wide varieties of I-Wants as the scope is uncertain and the stakeholders are fighting for there own accountability. This takes patience, flexibility, and a fast moving change control assessment team. Later on of course the role of the Project Manager must become firmer, driving hard boundaries of change control management resulting in only critical changes being approved. I like to use the terms as is it unsafe, will it not work, and is it not compliant at execution phases of a major project.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Forgive your enemies, but never forget their names."

- John F. Kennedy

ADVERTISEMENT

Sponsors