Project Management

Please login or join to subscribe to this thread

How do you keep large, cross-functional teams aligned when priorities shift every few weeks?

linkedin twitter facebook   Communications Management   Decision Making   Information Technology  
avatar
Pavan Maddi
Community Champion
Buona Vista, Singapore

Today’s work environment moves fast. New requests come in, leadership direction changes, and external factors influence project timelines. When many teams are involved, alignment becomes even harder.

From your experience, what approaches help maintain clarity, focus, and teamwork even when priorities continue to move?
Sort By:
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
You ask an interesting question, but it makes an assumption that a lot of people just accept. I'm not sure how far back you'd have to go to find a time when things were as slow as some people make it sound, but even back then, large cross-functional teams were rarely truly aligned. In some cases, the command-and-control nature of many organizations hid the lack of alignment. On large cross-functional teams, alignment is often an illusion.

When priorities shift every few weeks, you're even less likely to get alignment. Spending a lot of time trying to force alignment is more likely to slow things down. What matters more is how quickly and effectively people can adapt to change. This requires a few things:

- Clarity on what matters right now, even if you know it's going to change next week
- Tradeoffs are explicit - what should get done versus what gets delayed or dropped is clearly understood
- Not waiting for perfect alignment before taking action.

You don't want to ignore alignment, either. You want to find that balance between order and chaos that allows you to realign quickly when priorities change.
avatar
Michael King
Community Champion
Senior IS Project Manager| Baycare Health Systems Clearwater, Fl, United States
I find that best practices for changes in priority involve trade-offs, for example sure we can do this new #1 priority item this month, which one of the backlog items that are currently scheduled would you like us to push out?

It is not sustainable to contain to add workload to project teams and expect everything to be completed on the original schedule.
avatar
Imran Afzal Cary, NC, United States
I don’t think you keep large, cross-functional teams aligned when priorities are shifting every few weeks.

You design the system so they can realign quickly.

Alignment isn’t a static state in that kind of environment. It’s a continuous process.

And most of the friction comes from two things: unclear decision ownership and invisible trade-offs.

When priorities change, what people really need isn’t more communication.

They need clarity on three things:

What changed
What matters now
What no longer matters

The biggest miss I see is that organizations announce new priorities…

…but don’t explicitly deprioritize anything.

So teams try to absorb the change instead of rebalancing around it.

That’s where misalignment shows up.

What’s worked well in my experience is treating priority shifts as decision events, not updates.

Every shift forces explicit trade-offs:

If this moves up, what moves down?
If this accelerates, what gets delayed?
If this is urgent, what is no longer important?

And those decisions have to be made visibly—not inferred downstream.

The second piece is cadence.

You need a consistent mechanism where these decisions are made, reinforced, and translated into execution.

Not just discussed.

Because alignment doesn’t come from people hearing the same message.

It comes from people making coordinated decisions based on it.

So the goal isn’t perfect alignment.

It’s reducing the time between a priority shift and coordinated action across teams.

That’s what keeps large systems moving.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
The point is the time frame where the priorities change and the type of priorities that change. One of the keys to implement approaches like Agile (agile did not born in software, it was born in manufacturing to face this type of challenges) is to create and environment that moving with the changes. The key is to demonstrate all people that we are anticipating the changes then changes will have low impact or almost no impact. Things like the pandemic demonstrate which organizations were ready for that.
avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic
In that kind of environment, I don’t try to force perfect alignment.
What helps is being clear about what matters right now and what can wait. When priorities change, making those trade-offs visible keeps teams from pulling in different directions.
Having a regular moment to reset priorities also helps everyone stay on track, even when things keep shifting.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"The industrial revolution was neither industrial nor a revolution - discuss"

- Linda Richman

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters