When the Mission Teams You: Leadership Lessons from a Crisis Zone

You've probably never had to build a high-performing team while gunfire echoed in the distance. But you've almost certainly faced the challenge of getting people who barely know each other to deliver results—fast.

The conditions that force rapid teaming aren't unique to crisis zones. They're increasingly common in every organisation: project teams assembled for a single initiative, cross-functional groups pulled together to solve urgent problems, merger integrations where strangers must collaborate immediately. The luxury of teaming over time is disappearing.

What I learned coordinating humanitarian response in South Sudan applies directly to any leader facing this reality: you don't need months to build a team. You need the right conditions.

The team that had no time

In July 2011, I arrived in South Sudan days after it became the world's newest nation. I joined Doctors Without Borders as Human Resources Coordinator, stepping into a team of forty people tasked with supporting a local hospital treating severe childhood malnutrition.

The team composition would challenge any organisational theorist: twenty expatriates—doctors, nurses, logistics specialists, finance officers, security experts—from different countries, cultures, and professional backgrounds. Twenty local Sudanese staff from different clans, most without formal professional training in their roles.

Within weeks of my arrival, internal clashes erupted across the country. The hospital filled beyond capacity. Children were dying.

We had to act fast. We had to act together. And we had no time to "build" a team in any conventional sense.

Expatriates rotated every six to nine months. By the time you truly knew your colleagues, you—or they—were leaving. There was no accumulated team history, no shared experiences developed over years, no established trust built through countless interactions.

Yet this team succeeded. Not perfectly, not without conflict, but consistently and effectively. Lives were saved that would otherwise have been lost.

How?

Challenge as the great equaliser

The first insight seems almost too simple: a clear, compelling goal combined with genuine challenge does most of the teaming work for you.

Our goal wasn't to meet a quarterly target or satisfy stakeholders. It was to save lives—many lives, children's lives. This wasn't abstract. You could see the children. You could count them.

The challenges were equally concrete. Solutions weren't obvious. Resources were scarce. Danger was real. Fear was present in every decision.

These conditions did something remarkable to the team dynamics you'd expect from such a diverse group. The challenge made us humble enough to listen. The goal made us brave enough to act.

When the stakes are genuinely high and the path forward is genuinely uncertain, ego becomes expensive. We didn't have time to prove ourselves right. We didn't have energy to defend our positions. We would readily accept someone else's opinion—even when we disagreed—if it offered a workable solution.

The mission was teaming us faster than any workshop or offsite ever could.

For leaders in less extreme contexts, the question becomes: How do you create conditions where the work itself pulls people together? Not artificial team-building exercises, but genuine shared challenges with meaningful stakes?

Shared purpose over personal chemistry

Here's something that contradicts most team-building advice: we didn't all like each other. It didn't matter.

I'll be honest—there was a colleague I'll call Ruth who drove me mad. She was persistent to the point of nagging, questioning decisions I thought were settled, raising concerns I'd rather not hear. Annoying barely covers it.

She was also extraordinarily resourceful. When supply chains failed, Ruth found alternatives. When bureaucratic obstacles appeared insurmountable, Ruth found pathways. The qualities that made her irritating in calm moments made her invaluable in crisis.

Abraham Lincoln reportedly said: "I don't like that man. I must get to know him better." In South Sudan, I learned a variation: I don't need to like this person. I need to respect what they contribute.

We knew we could count on people we didn't particularly enjoy. We knew that personal friction wouldn't prevent professional collaboration. The shared purpose was stronger than personal preferences.

This is liberating for leaders building rapid teams. You don't need everyone to become friends. You need everyone aligned on what matters and clear about what each person brings.

What actually enables rapid teaming

Reflecting on that experience—and observing teams since—I've identified the conditions that enable groups of strangers to collaborate effectively without the luxury of time:

Clarity that eliminates ambiguity. In South Sudan, everyone knew the goal: save lives. Everyone knew their role. Everyone knew the constraints. There was no confusion about priorities because the priority was obvious and urgent.

In organisational settings, this clarity rarely exists naturally. Leaders must create it. What are we actually trying to achieve? What does success look like? What trade-offs are we willing to make? The clearer the answers, the faster the team aligns.

Stakes that matter. People don't collaborate intensely for abstract objectives. They collaborate when they genuinely care about the outcome. In crisis zones, the stakes are self-evident. In organisations, leaders must help people connect their work to outcomes that matter—to them, to customers, to something beyond the task itself.

Constraints that force interdependence. We couldn't succeed alone. The doctor needed the logistics coordinator to ensure supplies arrived. The logistics coordinator needed local staff who understood the context. Everyone needed everyone.

When people can succeed independently, they often will—and the team remains a collection of individuals. Genuine interdependence, where my success depends on your success, creates collaboration that no team-building exercise can replicate.

Permission to contribute regardless of hierarchy. A local staff member with no formal training might understand community dynamics better than any expatriate expert. A junior team member might see a solution that senior leaders missed.

In high-stakes, ambiguous situations, the best idea needs to win—regardless of who offers it. This requires leaders to actively create space for contribution and visibly value input from unexpected sources.

Respect without requiring affection. Teams that wait for everyone to like each other never fully form. Teams that establish mutual respect—for competence, for commitment, for what each person brings—can function immediately.

Translating crisis lessons to organisational reality

You're unlikely to face the conditions I faced in South Sudan. But you're increasingly likely to face their organisational equivalents:

The project team assembled from different departments, expected to deliver in twelve weeks, then disperse.

The integration team formed after an acquisition, bringing together people from different cultures who didn't choose to work together.

The cross-functional task force tackling an urgent problem, with members who've never collaborated before.

The leadership team after significant turnover, where half the members are new to each other.

In each case, the traditional approach—letting the team develop naturally over time—isn't available. The work won't wait.

What you can do:

Make the goal vivid and compelling. Not "improve customer satisfaction" but "ensure no customer waits more than four hours for a response." Not "successful integration" but "every employee knows their role and their manager by day thirty." Specificity creates alignment.

Increase the stakes authentically. Connect the work to outcomes people care about. Show them what's at risk if the team fails. Make success meaningful beyond the task itself.

Design for interdependence. Structure the work so people genuinely need each other. Shared resources, sequential dependencies, collective accountability—these create collaboration that voluntary cooperation cannot.

Establish respect as the baseline. Make clear that personal chemistry is optional but professional respect is required. Model this yourself by visibly valuing contributions from people you might not naturally gravitate toward.

Embrace the constraint of time. Urgency, properly channelled, accelerates teaming. Don't apologise for tight timelines—use them to focus attention and eliminate the luxury of prolonged conflict.

The uncomfortable truth about team development

Most team development models assume time. Form, storm, norm, perform—each stage taking weeks or months. But the teams I've seen succeed fastest didn't follow this progression. They performed from the start because the situation demanded it.

This doesn't mean conflict disappeared. We had disagreements in South Sudan—significant ones. But the conflict served the mission rather than personal positions. We argued about how to save more lives, not about who was right.

The teams that struggle aren't the ones with conflict. They're the ones where conflict becomes about ego rather than outcomes.

When the challenge is clear and the purpose is shared, conflict becomes productive. When people are protecting their positions rather than pursuing the goal, conflict becomes destructive.

Leaders building rapid teams should expect disagreement and welcome it—while constantly redirecting attention to the shared mission. "We disagree about the approach. What would best serve our goal?"

Start with one question

If you're leading a team that needs to deliver results without the luxury of extended team development, start here:

Is our goal clear and compelling enough to override individual preferences?

If people can articulate the goal in the same way, if they genuinely care about achieving it, if success requires genuine collaboration—you have the foundation for rapid teaming.

If the goal is vague, if people are unclear why it matters, if individuals can