I’m currently facing a challenging situation where quick decisions and clear communication are crucial. During a crisis, how do I effectively keep my team informed and coordinated, especially when emotions run high and information changes rapidly? What tools or strategies have helped you manage communication and teamwork under pressure? Saving Changes...
PMO Leader | Speaker & Mentor | Content Leader – PMOGA Latin America
Hub| Catholic University of UruguayMontevideo, Montevideo, Uruguay
In high-pressure situations, I rely on a mix of empathy and structure to lead effectively. These are the strategies I’ve found most useful:
• Frequent, clear updates, even when there’s no new information—transparency builds trust.
• Short daily check-ins to align priorities and listen to team concerns.
• Active listening, acknowledging emotions and offering support.
• Collaborative tools like Miro or Notion to maintain visibility and coordination.
• Flexible leadership, empowering team members to lead from their strengths.
The goal is to create clarity and trust—even when everything is changing fast. Saving Changes...
Don't wait for the crisis to establish procedures and communications channels. Sometimes, you have to experience a crisis before you figure out everything you need in place for the crisis, so make sure to run a post-mortem/lessons learned session to help prepare for the future.
Yo can also run a pre-mortem to identify major issues and how to 1) prevent them, 2) prepare for them, and 3) respond to them. Taking a step back from Project Management, I've been involved with BC/DR (Business Continuity/Disaster Recovery) planning and exercises. You may not need anything that elaborate for most projects, but the idea is the same. If you're working on the types of projects where major crises are possible, you'll want to have procedures in place for establishing communications channels and not just keeping people up to date, but making sure people are okay, making sure people who are able to work have the tools they need to work (possibly including recreating the infrastructure, tools, and software needed to do the work). There's more to consider, but you get the point.
For most projects, a BC/DR plan is overkill, but if you understand the principles, you can scale them back and establish a framework that you can customize and apply when a project is in crisis mode. Saving Changes...
Giorgos SioutzosSenior Business Analyst| NetcompanyAthens,, Greece
In a crisis, the priority is creating clarity, cadence, and calm.
Establish a single source of truth, communicate frequently — even when the update is “no change” — and use a consistent structure: what we know, what we don’t, what we’re doing, and what we need.
Decision cycles get shorter, roles become explicit, and blame is off the table.
Separate fact-finding from decision-making to avoid chaos and keep people focused.
After stabilization, capture lessons immediately so the next crisis finds you stronger, not surprised. Saving Changes...