The $10 Million Question: Does Your Interview Team Actually Perform Like a Team?
Qualified firms lose major contracts because they can't demonstrate unity when it matters most
Tell me if you’ve seen this one before: Six highly credentialed professionals walk into a conference room to present for a $900 million infrastructure project. On paper, they're unbeatable—decades of experience, impressive portfolios, and technical expertise that exceeds requirements.
Sixty minutes later, they walk out having lost the contract.
What happened? They presented as six individuals, not as one team.
I've watched this scenario play out repeatedly. Brilliant firms with superior qualifications lose to competitors who master one critical skill: demonstrating they function as a cohesive unit. After working with teams to win over $30 billion of infrastructure projects, I learned important lessons.
The panel doesn't just evaluate your technical capabilities. They're asking themselves: "Can these people actually work together to deliver this project?"
Why Team Cohesion Wins Contracts
When I first started my career, I noticed a pattern. The winning teams weren't necessarily the most technically qualified. They were the ones who made the selection panel confident that this exact group could navigate the inevitable challenges of a complex, multi-year project.
Here's what evaluators are really assessing:
Do they finish each other's sentences or trip over each other's words?
Do they demonstrate shared ownership or defend individual territories?
Do they reference collective experience or compete for airtime?
Do transitions feel rehearsed or awkward?
These aren't minor presentation details. They're billion-dollar tells.
How to Ensure Your Interview Team Looks Cohesive
Over three decades in the infrastructure world, I've developed four essential elements that distinguish winning teams from those that wonder what went wrong.
1. Shared Language and Narrative
Cohesive teams don't just know the project—they tell the same story about it. When your project manager describes the approach, then your lead engineer later references it, the terminology, priorities, and framework should align seamlessly.
I once coached a team pursuing a $1.2 billion transit project. In early rehearsals, the PM talked about "community-centered design" while the engineer emphasized "technical optimization." Both were valid priorities, but the disconnect signaled a team that hadn't unified around a singular vision. We spent time building a common vocabulary and narrative structure. Every team member could articulate the same three-part approach in their own words, but with consistent themes. It was a winning combination.
The test: Can every team member articulate your key differentiators using the same essential framework?
2. Deliberate Interconnectivity
Watch a disjointed team present, and you'll see individuals delivering sequential monologues. Watch a cohesive team, and you'll see a story develop like a good conversation.
The difference shows up in how team members reference each other:
"Building on what Sarah mentioned about the phasing strategy..."
"John's experience with a similar LA Metro project directly informs our approach here..."
"This connects to the risk mitigation framework that our team developed together during the pursuit phase..."
These aren't scripted lines. It's evidence that your team actually collaborates.
The test: Does your presentation structure create natural opportunities for team members to acknowledge and build upon each other's contributions?
3. Unified Body Language and Energy
Here's something most teams miss: cohesion isn't just verbal. Selection panels read non-verbal cues constantly.
When one team member is presenting, what are the others doing? Looking engaged or checking phones? Nodding at key points or staring blankly? Sitting forward or slouching back? Positioned as a connected group or scattered individuals?
I coached a team where the lead architect visibly tensed whenever the construction manager spoke. We addressed the underlying tension during preparation, worked through their different perspectives on the project approach, and aligned them before the interview. The body language shift was dramatic.
The test: If you muted the audio and watched your practice sessions on video, would observers see a unified team or a group of strangers?
4. Collaborative Problem-Solving Under Pressure
The real test of team cohesion comes during Q&A. When a panel member asks a challenging question, does your team all look at each other wondering who should answer? Jump in talking over each other? Or demonstrate fluid collaboration where one person takes the lead while others provide supporting expertise?
Cohesive teams have an invisible choreography. They've practiced enough together to know who should lead on different types of questions, how to signal support or expansion of an answer, and how to gracefully redirect if someone goes off track.
One team I coached faced an aggressive question about community opposition. The project manager provided the framework for the answer, the public affairs lead added specific engagement strategies, and the lead engineer explained how community input had already influenced design choices. Three people, one seamless answer.
The test: During Q&A practice, do your transitions feel natural, or are there awkward silences while team members figure out who should respond?
Building Real Cohesion (Not Just Performing It)
Here's the trap most teams fall into: they try to script cohesion during interview prep. They add lines like "As my colleague mentioned..." or choreograph where people sit.
That's not cohesion. That's theater.
Real team cohesion requires actually working together before the interview—not just rehearsing together. The most successful teams I've coached spend time in the pursuit phase collaboratively developing their approach, not just dividing responsibilities:
Holding working sessions where technical and non-technical team members solve problems together
Creating shared frameworks that everyone contributes to and owns
Building genuine relationships that translate into authentic chemistry
Practicing enough to develop natural rhythms and transitions
This is why I argue that interview coaching should begin during the proposal phase, not after shortlisting. By the time you're called for an interview, your team should already have months of shared problem-solving experience.
If your team can't demonstrate cohesion in a 60-minute interview, why would a panel believe you can maintain it through a five-year project delivery?
Start Building Your Team Now
If you're pursuing major infrastructure contracts, ask yourself these diagnostic questions:
Could any team member convincingly explain another member's role and contributions?
Do team members reference collaborative work or just individual deliverables?
If two team members were asked to describe your approach independently, would their answers align?
Does your team have inside jokes, shared references, or demonstrated camaraderie that comes from real collaboration?
If you're answering "no" to these questions, you're not just at risk of looking disconnected during interviews—you actually are disconnected. And selection panels can always tell the difference.
The Bottom Line
Billions of dollars in awarded contracts taught me one undeniable truth: in major infrastructure pursuits, technical qualifications get you shortlisted, but team cohesion wins the contract.
The teams I've coached to success didn't just have better credentials than their competitors. They had something more powerful: the demonstrated ability to work as a unified force toward a common goal.
That's what selection panels are buying. That's what you need to prove.
Your team's chemistry—or lack thereof—is on display the moment you walk into that interview room. The only question is whether you've invested the time to build something worth showing.