The actions a team can take together depend on the situation you’re facing, but the core principle is always the same: clarify roles, communicate constantly, and move toward a shared goal. Whether your team is navigating a crisis, resolving internal conflict, pushing through a project’s execution phase, or generating new ideas, there are specific, proven actions that turn a group of individuals into a coordinated unit.
During a Crisis or Emergency
When something goes wrong and the pressure is high, the single most important team action is assigning clear roles immediately. Someone needs to own the problem (the coordinator), someone needs to manage communication to stakeholders, and the rest need to focus on diagnosis and resolution. Without this structure, teams waste critical time with duplicated effort or, worse, everyone assumes someone else is handling it.
Emory University’s crisis management protocol offers a useful blueprint. The coordinator opens a shared communication line, gathers the right people, and works with a designated crisis manager to push out status updates at regular intervals. The technical team follows a structured sequence: identify the source of the problem, review recent changes, examine logs, and bring in outside help if needed. Once a fix is identified, the team organizes it into steps, estimates a timeframe for each step, tests the solution, and validates it before declaring the issue resolved.
Two actions matter most here that teams often skip. First, update your notes in real time. Document every troubleshooting step as you go, not after the fact. Second, after resolution, complete an after-action report while the details are fresh. This single habit separates teams that keep repeating mistakes from teams that actually improve.
During Conflict Between Team Members
Conflict on a team isn’t inherently bad. It becomes destructive only when it’s ignored or handled with the wrong approach. The Thomas-Kilmann Conflict Model, developed by organizational psychologists, identifies five strategies your team can use, and the right one depends on how much the goal and the relationship each matter in the moment.
- Collaborating is the gold standard when both the goal and the relationship are important. Both sides work together to find an outcome that meets everyone’s core needs. It takes more time but produces the most durable solutions.
- Compromising works when you need a quick resolution and both parties can give up something. Neither side gets everything, but you move forward.
- Accommodating makes sense when preserving the relationship matters more than winning the point. One person yields to the other’s needs.
- Competing fits rare situations where the stakes are high and the outcome matters more than the relationship, like safety decisions or ethical boundaries.
- Avoiding is appropriate only when both the goal and the relationship are low priority. In most team settings, this is the least useful strategy because unresolved tension tends to resurface.
The team action here is choosing the strategy deliberately rather than defaulting to whatever feels instinctive. Most people have a habitual conflict style. Naming the approach openly (“Let’s try to collaborate on this rather than just splitting the difference”) helps everyone engage constructively.
During a Project’s Execution Phase
Once a project is underway, the biggest risk is drift. People lose track of priorities, blockers go unreported, and small misalignments compound into missed deadlines. The most effective team action during execution is a brief daily check-in where each person answers three questions:
- What did you accomplish yesterday?
- What will you work on today?
- Is anything blocking your progress?
These meetings should take 15 minutes or less. They’re not status reports for a manager. They’re synchronization points for the team. The value comes from surfacing blockers early so someone else can help remove them before they stall the work.
Equally important is clarifying who does what. The DACI framework gives every team member one of four roles on any given decision: the Driver leads the work, the Approver makes the final call, Contributors provide input, and Informed stakeholders are kept in the loop. When these roles are ambiguous, decisions stall or get made twice by different people. Assigning them explicitly at the start of each major task prevents that.
During Brainstorming and Idea Generation
When a team needs to generate ideas together, the worst thing you can do is open with “Does anyone have any thoughts?” and wait. Structured techniques consistently outperform unstructured discussion because they give quieter team members a way in and prevent the loudest voice from dominating.
Three approaches work well. Round-robin brainstorming gives each person a turn to contribute an idea, rotating around the group so no one is skipped. Mind mapping starts with a central concept and branches outward, with team members adding connected ideas visually. The “Yes, and…” exercise, borrowed from improv comedy, requires each person to build on the previous idea rather than critiquing it. This keeps momentum going and prevents the premature killing of ideas that need development.
The key team action during ideation is separating the generation phase from the evaluation phase. When people worry their idea will be shot down immediately, they self-censor. Set a clear rule: for the first portion of the session, every idea gets captured. Critique comes later.
During Organizational Change
When your team is going through a restructuring, a new strategy rollout, or any significant shift, the most important collective action is aggressive, repetitive communication. MIT Human Resources recommends that leaders communicate about each step of a change “seven different times and in seven different ways” to ensure the message actually lands. That means emails, meetings, one-on-ones, visual updates, and informal conversations all reinforcing the same core message.
At the start of any change process, the team should meet with every major stakeholder group: staff, customers, suppliers, and sponsors. These meetings need to combine two things that teams often do separately. Share the benefits and tradeoffs of the change honestly, and actively listen to concerns. Skipping the listening half is why so many change initiatives meet fierce resistance. People don’t resist change itself as much as they resist being changed without being heard.
Building ongoing feedback loops matters just as much as the initial communication. Schedule regular check-ins where team members can surface what’s working and what isn’t. The goal is making transparency a habit rather than a one-time event.
Building Psychological Safety in Any Situation
Underneath all of these actions is a prerequisite that determines whether any of them actually work: people on the team need to feel safe enough to speak honestly. Research from Harvard Business School identifies specific behaviors that build this kind of environment. The most effective teams use direct invitations like “We’re going to need all the ideas you have” or “What do you think?” rather than vague openings that only confident speakers respond to.
The critical behavior, though, is what happens after someone speaks up. If a team member shares bad news or a dissenting opinion and gets met with frustration or dismissal, the rest of the team learns to stay quiet. Teams that perform well protect the messenger. They respond to unwelcome input with curiosity (“Tell me more about that”) rather than defensiveness. This isn’t about being soft. It’s about getting access to information you need to make good decisions.
After the Work Is Done
One of the highest-value actions any team can take is reviewing what happened once a phase of work is complete. The after-action review, originally developed by the U.S. Army and now widely used in business, centers on four questions:
- What did we intend to accomplish?
- What actually happened?
- Why was there a gap between intention and execution?
- What will we do differently next time, or how do we repeat what went well?
This works best as a live discussion, not a form someone fills out alone. The conversation itself is where the learning happens, because team members often have different perspectives on why things went the way they did. Run the review within a day or two of the event while details are still fresh, keep it blame-free, and document the takeaways somewhere the team will actually reference later.