Leave the Logo at the Gate: Building One Team on Large Capital Projects

Around the world, large capital projects assemble owners, designers, contractors, specialist trades, suppliers and financiers who will never form a single permanent organisation. They arrive with different employers, different scorecards and different colours on their jackets. Kick-off photographs celebrate "one team," and partnering charters are signed with every logo on the cover. Yet within months the same people often optimise for their own firm's float, claim position and career path, while the asset's opening date has no shared defender. This comprehensive blog will explore what it means to leave the logo at the gate on large capital projects, why firm identity so often wins under pressure, how a single delivery organism is designed through identity, incentives, experience and voice, how that differs from owner-side integration and from small real-team cells, and how leaders take logos off in practice and keep them off when schedules and claims bite.

1. Logos on the Hard Hats

Consider a progress meeting on a large capital project. Around the table sit the owner's project director, the PMC planner, the civil package manager, the mechanical contractor, the systems integrator and two trade supervisors. Every jacket carries a different logo. The agenda is the integrated baseline. Each party reports green against its own milestones. The interface that actually holds the opening date — a sequence of design release, embedment, cable pull and commissioning — has no clear owner in the room. When the conversation turns to a late design input, the civil package protects its float; the mechanical package asks for a variation; the systems integrator notes that its float was already thin. Nobody is lying. Each is doing what their home organisation rewards.

The pattern is familiar on large capital projects of every kind: plants, terminals, rail systems, data centres, hospitals, ports. Multi-logo kick-offs are common. One delivery "us" is rare. The project has paid for the ceremonies of a team — the shared schedule, the partnering workshop, the branded site office — without redesigning who people believe they work for when a trade-off arrives. Coordination without a shared identity is fragile. It holds while plans go well and dissolves as soon as the plan comes under pressure.

The failure is easy to misread as a soft-skills problem. It is not. The people in the room are usually competent, committed to their crafts and loyal — to the organisations that employ them. Large capital projects that treat "one team" as a cultural overlay on top of firm-first incentives discover that culture loses. The ones that redesign identity, incentives and membership together discover that people will defend a shared result when the shared result is real.

The central claim of this blog is straightforward. On large capital projects, people leave their employer logos at the gate — or they do not. Leaving the logo at the gate means redefining identity to the project delivery unit for the duration of delivery, so that when two goods collide, the project result outranks the firm's claim position. That identity only holds when commercial incentives, experienced squads, visible project symbols and a climate for bad news travel with it. A slogan alone will not fuse rivals.

2. What Leaving the Logo Means — and What It Does Not

Leaving the logo at the gate is an identity redesign, not a soft appeal. For the life of delivery, the answer to "who is my team?" becomes the project, not the firm on the payslip. Symbols, facilities, recognition and language are arranged so that project membership outranks company membership when choices have to be made.

It is equally important to say what the idea is not.

It is not dissolving legal employers. People still have contracts of employment, career paths and professional licences. The point is temporary subordination of firm loyalty at the moments that decide the asset.

It is not the same as integrating the owner's own functions. An owner team is integrated when the needed owner disciplines — operations, maintenance, commercial, health and safety, engineering — sit on the project during scope development, are empowered to decide for their function, enjoy reasonable continuity, and report to the project director rather than only back to functional managers. That is essential on complex large capital projects, and it is a different layer. Owner-side completeness does not automatically produce a multi-firm delivery "us."

It is not the same as declaring that everyone on site is a "real team." A real team in the classic sense is a small group — typically small enough that members can interact and hold one another mutually accountable — with a team-specific purpose, clear goals and a shared approach. A delivery organism on a large capital project can number in the thousands across many firms. The organism is a system design. Inside it, small cells still need the discipline of real teams. Labelling a programme of two hundred people a team without that discipline produces another pseudo-team.

Identity, then, is a design choice. Who is named as in? What symbols compete with firm logos in joint rooms? Whose recognition is celebrated? Which result is publicly declared as the one that matters? Projects that never answer those questions leave the default answer in place: people work for the logo on their jacket.

A useful test is simple. In a joint room, when a painful trade-off appears, do people argue first as representatives of their firms or as members of the project? The first sentence of the argument usually reveals which identity is live. Another test: can a supervisor from one contractor raise a miss that implicates their own firm without needing a private channel to survive? If not, the logo is still on.

Figure 1: Logos on versus logo at the gate. On the left, people face their firm marks and report home; on the right, the same people face a single project identity and act as one delivery "us."

3. Why Logos Stay On

Firm identity wins on large capital projects for structural reasons, not because people are uncooperative.

Firm and package status. The most damaging distraction in a team is caring about something other than collective results. Two status pulls dominate. Team status says that belonging to a prestigious project is enough, so specific results are desirable but not worth great sacrifice. Individual status says that one's own position, career or department matters more than the group's outcome. On large capital projects those pulls transfer easily to company and package status: claim position, variation entitlement, design authorship, the pride of being the "flagship" contractor. When recognition rewards those things, logos stay on.

Matrix reporting. Many people are matrixed to the project while still reporting to a functional manager or a home profit-and-loss account. Under mild pressure the matrix is managed. Under delay, liquidated damages and internal year-end targets, the home incentive usually wins. The project director who believes a dotted line equals loyalty discovers otherwise at the first serious dispute.

The pseudo-team trap. Groups that are labelled teams without a collective performance challenge sit at the bottom of the team performance curve. There is team talk — partnering charters, multi-logo cover pages, "one team" banners — and little team action. Pseudo-teams perform worse than honest working groups, because they carry the overhead of teaming without its benefits. The signed integrated schedule and the kick-off photograph are favourite disguises.

Contracts that reward finger-pointing. When commercial forms pit firms against each other, punish early bad news, or make every interface a battleground for entitlement, logos are rational armour. People do not "fail to collaborate"; they collaborate with the incentives they are given.

Partner misalignment. On joint ventures and multi-sponsor large capital projects, value that was never shaped — who gets what, and therefore who will support which scope — reappears as weak controls, funding delays and quiet competition inside the delivery room. Leaving the logo at the gate cannot repair a deal that was never aligned. Identity work after a mis-shaped deal is asking people to behave as one team while their sponsors still pull in different directions.

Career and professional identity. Engineers, planners and commercial managers also carry discipline identities. A design lead may defend design authorship; a planner may defend the integrity of the baseline; a commercial lead may defend the purity of the claim file. Those identities are valuable. On large capital projects they become harmful when they outweigh the collective result at the moment of choice. Leaving the employer logo at the gate includes leaving the unchecked dominance of discipline pride when the asset needs a cross-discipline call.

None of these forces requires villains. A package manager who protects float is often protecting people whose bonuses and reputations sit inside that package. A commercial manager who documents entitlement is doing the job the contract describes. The failure is systemic: the project never made collective results more important, more visible and more rewarded than firm results. Until that changes, logos stay on.

The result is a room that looks coordinated and behaves as a coalition of firms. Each package can be "green" while the asset drifts.

4. The Organism Package: Identity Needs Incentives

Leaving the logo at the gate is not a poster campaign. It is a package. One of the clearest illustrations is Heathrow Terminal 5. Facing a company-threatening schedule risk, the owner treated the delivery team as a single determined organism rather than a collection of lowest-bid fragments.

The package had several bands, and each mattered.

Aligned contracts and shared risk. The owner led actively and shared risk rather than pushing it all down the chain. Commercial arrangements used cost-reimbursable structures with milestone profit, and positive incentives were aligned to finishing the terminal on time. Experience was preferred over lowest bid, and subcontractors were encouraged to follow the same logic. Identity without incentives is theatre; incentives without identity leave people still thinking as strangers.

Experienced squads. Where possible, proven joint crews outperform assemblages of strangers hired on price alone. Preferring people who have delivered together before is not nostalgia; it is risk management when the expensive window of construction is short and unforgiving.

Project identity. The instruction was blunt: leave the employer mark behind; for this job, people worked for Terminal 5. Purpose language — "making history" — was matched by facilities and personal protective equipment that made the rhetoric believable. Symbols that contradict behaviour destroy trust faster than silence.

Worker standards and voice. Workers were consulted. Roughly fourteen hundred worker-owned quality benchmark samples set the standard from the floor up. Speak-up was backed by the owner so that bad news could travel fast. A climate that punishes early warning keeps logos on, because people protect their firms by staying quiet.

The contrast. The same era's New Wembley stadium illustrated the opposite pattern: conflict, stoppages, costs roughly doubling, litigation and little shared pride. The lesson is not that every alliance form works. The lesson is that get-the-team-right is a delivery-system design — identity, incentives, experience and voice — not a workshop exercise.

The investment case for the package is often misunderstood. Spending on team dynamics, site welfare and risk-sharing can look expensive next to a lowest-bid comparison. On large capital projects where a typical overrun would threaten the sponsor, that investment is frequently cheaper than the average miss. The Terminal 5 campaign treated people as a strategy equal to simulation and modular assembly, not as a soft afterthought.

A further practical point: the organism has to be priced into the business case early. Retrofitting identity onto a set of adversarial contracts mid-flight is possible but costly. Leaders who wait until conflict is already public usually discover that logos have hardened into armour.

Collaborative delivery families — integrated project delivery and alliance-style arrangements — aim at the same commercial spine: mutual respect, shared risk and reward, early involvement of key participants, open information, and team success tied to project success. Traditional forms that allocate and transfer risk without sharing it make firm-first behaviour the rational default. Forms alone do not create one team; forms that punish one-team behaviour will undo any identity campaign.

Figure 2: The single delivery organism stack on large capital projects. Aligned contracts, experienced squads, project identity, welfare and standards, and speak-up sit as stacked bands. A slogan alone is an empty stack.

5. Three Answers to "Who Is My Team?"

Confusion about leaving the logo at the gate often comes from collapsing three different answers into one phrase.

The employer or firm. Who pays the person and rates their career? That answer never disappears. Career systems, professional licences and firm profit-and-loss accounts remain. The design task is to ensure that, at trade-offs that decide the asset, this answer does not automatically win.

Owner-team integration. Are all needed owner functions present during scope development, empowered, reasonably continuous, and reporting to the project director? Without that, information needed for correct scope is missing, wrong or late, and large capital projects absorb change that should have been decided earlier. Leaders who treat engineering or controls as their personal craft, rather than listening and boarding functions, deter integration. This layer is owner-side organisational design. It is not multi-firm identity.

The delivery organism. Do people from many employers act as one "us" toward delivery? That is the logo-at-the-gate question. It sits at programme interfaces and across contractor boundaries. It is built with incentives, symbols, experience and voice.

Inside the organism, subdivide. Design-interface cells, commissioning crews and claims war rooms can be real teams only if they are small enough to interact, have a team-specific purpose and hold themselves mutually accountable. A programme "team" of fifty or two hundred people is not a real team under those basics. Leaving the logo at the gate without cell discipline produces another pseudo-team with better branding. At steering level, a strong working group of accountable individuals is often healthier than a forced multi-firm "executive team" that never had a collective performance challenge.

Multi-contractor programmes also need forums that own interfaces across packages — systems thinking rather than civil feats alone — so that "who owns the connection?" has an answer that outranks "whose package is green?" Shared consciousness across many cells helps; it does not replace either the organism package or the small-team basics inside it.

Leaders on large capital projects often try to skip a layer. They push multi-firm "one team" language while the owner team itself is incomplete — missing operations, maintenance or commercial voices during scope development. Or they integrate the owner team carefully and then assume contractors will fuse by proximity. Or they charter excellent small cells and leave programme interfaces as a free-for-all of firm-first negotiation. The three answers have to be stacked. Firm identity is managed, not denied. Owner integration is designed. The delivery organism is designed. Cells inside it are chartered. Miss one layer and the others compensate badly.

Figure 3: Three answers to "who is my team?" on large capital projects. Employer identity sits outside; owner-team integration is the middle layer; the delivery organism is the inner "us," subdivided into small real-team cells.

6. Taking Logos Off in Practice

Leaving the logo at the gate is a sequence of design moves, not a pep talk.

Bound the delivery team. Name who is in the organism for this phase. Stop treating "everyone with a logo on site" as a team. Bounded membership is an essential condition; without it, coaching and workshops are theatre.

Make project identity explicit. Symbols, facilities, recognition and language should match "you work for this project." Kill competing firm-first rituals in joint rooms — separate seating by company, firm-only celebrations of package milestones that hurt the interface, kick-offs that showcase logos more than the result.

Align incentives — or manage where they still conflict. Shared milestones and risk-sharing make identity credible. Where contracts still reward firm-first behaviour, name those interfaces and govern them deliberately rather than pretending partnering language has cancelled the commercial form.

Fold firm and personal agendas into process goals. Unspoken agendas leak as claim posture and solo visibility. Surfacing them early lets the team decide how this project will handle recognition, communication and decisions — one consistent way for this team, not each firm's inherited way.

Check goals and roles before personality. When conflict flares across firm lines, test whether objectives are clear and role boundaries make sense before assuming interpersonal failure. Ambiguous goals and overlapping roles often look like personality clashes. A cascade that starts with goals, then roles, then work processes, and only then interpersonal relationships, prevents expensive team-building theatre aimed at the wrong problem.

Write and sign a team contract. Task goals and process goals, roles, rules and accountability metrics, kept visible and rebuilt when membership changes. Signing solidifies expectations; a living document beats a forgotten charter in a drawer.

Declare collective project results publicly. Opening date, safety outcomes, interface closure — the results the organism exists to achieve — should be more salient than package prestige. Rewards that celebrate effort without outcomes signal that results do not matter; rewards that celebrate only firm metrics keep logos on.

Prefer experienced joint squads. When schedule risk is existential, paying for team dynamics and proven crews is often cheaper than the average overrun. Hiring a master builder and their traveling crew, where the work allows it, beats assembling strangers on price alone.

Revisit when membership changes. Large capital projects are long. Packages join and leave; leaders rotate; the "us" of year one is not the "us" of year three. Each material change in membership is a reason to rebuild the contract, restate collective results and re-check whether incentives still match the identity the project claims.

Design conditions come before coaching. If membership is unclear, purpose is a slogan and the mix of people is wrong, no amount of facilitation will create one team. Organisational supports — rewards, information, career signals — must promote teamwork rather than obstruct it. A project that rates people only on firm margin while asking them to leave the logo at the gate has already chosen which instruction will be obeyed.

Figure 4: A leave-the-logo gate before delivery mobilisation. Bound membership, project identity, incentive check, agendas folded, goals-and-roles review, and a written contract with declared collective results precede mobilisation. If firm status wins a trade-off, reopen identity and incentives.

7. Keeping Logos Off When the Schedule and Claims Bite

Under delay, liquidated damages and variation pressure, logos snap back on. The practices that hold the organism are ordinary and relentless.

Use a trade-off rule in joint rooms: which option moves the project result, not my firm's claim position? Make that question spoken, not implied.

Give interface ownership status that outranks package ownership. Systems integration of the whole is the product; a green civil package that leaves an unworkable interface is not success.

Recognise and give airtime to cross-firm problem-solving, not only to package green reports. What leaders celebrate becomes what people protect.

Protect speak-up when bad news threatens a firm's standing. If the first messenger of a miss is punished commercially or socially, logos become shields and bad news travels late — which is when it is most expensive.

Refresh the team contract and membership when major packages join or leave. Identity decays with turnover unless it is rebuilt.

At steering level, prefer honest individual accountability when a forced multi-firm "team" is fake. Keep real-team discipline where joint products exist — commissioning cells, interface crews, recovery war rooms — and do not dilute it by calling every meeting a team.

A second pressure point is the claims war room. When entitlement work intensifies, the people closest to the facts are often the same people who must still collaborate at the next interface. Projects that wall commercial warfare off from delivery collaboration — clear rules for how disputes are run without poisoning joint problem-solving — protect the organism. Projects that let every interface meeting become a negotiation about whose delay caused whose dissolve it.

A third pressure point is recognition. Awards, newsletters and steering slides that celebrate only package milestones teach the workforce what matters. Awards that celebrate interface closure, early warning and cross-firm recovery teach something else. Leaders who want logos off must look at what they publicly praise.

Leaving the logo at the gate is easiest at kick-off and hardest in month eighteen. That is exactly when the design either proves itself or reveals that it was only a slogan.

8. The Logo That Matters Is the Project's

Large capital projects do not fail only from thin front-end definition or weak schedules. They fail when capable people still work for their logos at the moments that decide the asset. Leaving the logo at the gate is identity redesign backed by incentives, experience and voice. Owner-side integration remains necessary and distinct. Small real-team cells remain necessary inside the organism. Collaborative commercial forms help when they make one-team behaviour rational.

The work is not glamorous. It is naming who is in, aligning what people are paid and promoted for, preferring crews that have delivered together, matching symbols to behaviour, and declaring a collective result that outranks package prestige. Done early, it is cheaper than the average overrun. Done late, it is damage control.

A shared date without a shared "us" is a schedule nobody will defend. The logo that matters, for the life of delivery, is the project's.

References

• Flyvbjerg, B., with Gardner, D. How Big Things Get Done (2023)
• Katzenbach, J. R., & Smith, D. K. The Wisdom of Teams
• Lencioni, P. The Five Dysfunctions of a Team (2002)
• Merrow, E. W., & Nandurdikar, N. S. Leading Complex Projects (2018)
• AIA / AIA CC. Integrated Project Delivery: A Guide (2007)
• Shapiro, M. HBR Guide to Leading Teams (2015)
• Benator, B., & Thumann, A. Project Management and Leadership Skills for Engineering and Construction Projects (2003)