Why Project-Based Firms Keep Rolling the Dice on Their Teams

A contract gets signed on a Friday. By Monday, someone has to staff it.

In project-based firms, that moment happens hundreds of times a year, and it usually looks the same. A leader scans who is rolling off another engagement, who has the right skills on paper and who has a reputation for getting things done. A team is assembled, introduced on a kickoff call and told, in so many words, to figure it out.

Sometimes it works beautifully. Often it doesn’t. And because nobody can predict which outcome they’ll get, the firm is in effect rolling the dice with its revenue, its client relationships and its people.

The pattern shows up in consulting, engineering services and agencies alike. The leaders inside these organizations are not careless. Most are under real pressure to deliver fast. But the way they form teams tells me something important about what they do and do not know.

They know the work. They don’t know the people.

Ask a delivery leader to describe the scope of a project, and you’ll get a precise answer: the requirements, the milestones, the budget, the technology. Ask the same leader how the four people leading that project prefer to communicate, what each of them naturally solves for or what tends to spark conflict between them, and the room usually goes quiet.

That gap is where the dice come in. When you staff on skills and reputation alone, you are betting that talented people will work out how to work together on their own. Some will. Others are gifted but hard to work with. Put two of them on the same team without any shared way of operating, and the project absorbs the friction.

You see it later in the numbers. Timelines slip. Hours stretch. Rework piles up. Someone burns out quietly, and someone else loses their temper in a meeting. Clients sense the tension before anyone names it. And the people with the most options, often your best ones, start looking elsewhere because they are tired of fighting the same battles on every new team.

Why the gamble feels like a strategy

It’s worth asking why smart organizations keep making the same bet.

Part of the answer is that the gamble pays off often enough to feel reliable. Every firm has a story about the team that came together at the last minute and saved an account. Those stories become proof that the system works, even when the averages say otherwise.

Another part is that the cost of a poorly formed team rarely shows up on a single line. It’s spread across overtime, missed handoffs, extra people added to rescue a project and the resignation that arrives three months later. No one connects those costs back to the moment the team was formed, so that moment never changes.

And part of it is habit. In a high-pressure business, slowing down to understand people feels like a luxury. “Just get it done” becomes the operating model, and people start to be treated like interchangeable pieces on a board. But the pieces are human beings, with different strengths, different triggers and different ways of contributing their best.

Replace the gamble with a playbook

None of this requires a firm to slow down. It requires a firm to be deliberate about something it already does dozens of times a year.

Know your people before you need them. The most useful information for staffing a team isn’t on a résumé. It’s how a person approaches problems, how they handle pressure and where they add the most value. Organizations that capture this, through assessment data and real conversations, can build teams with intention instead of instinct. I wrote about this in What Do Your People Naturally Solve For?, and it matters even more when teams change every few months.

Give every team the same starting line. The skills will vary from project to project. The way a team forms shouldn’t. A consistent first week, with clear expectations for how leads align, how disagreements get raised and how problems get escalated, gives talented people a shared foundation. Their individual strengths then have something solid to build on.

Build relationships before the pressure arrives. The most effective project leaders spend their first days on a new team getting to know people, with conversations that have nothing to do with the project. Their teams move faster later, because trust is already in place when problems surface. In project work, relationships belong in the delivery infrastructure, right next to the timeline and the budget.

Measure team formation like any other business process. If you track utilization and margin by project, you can also track which team combinations delivered on time, which needed rescue and which lost people. Patterns emerge quickly, and they will tell you more about your delivery model than any post-mortem.

The firms that stop gambling

The competitive edge in project-based work is shifting. Clients can find technical skill in many places. What they cannot find easily is a partner whose teams work well together from day one, communicate clearly and deliver without drama.

That kind of reliability comes from pairing two things most firms treat as opposites: a consistent way of forming and leading teams, and real knowledge of the individuals on them. Get both right and you stop depending on luck. You also become the place talented people want to stay, because they no longer have to start from scratch every time a new contract is signed.

Every staffing decision is a bet on people. Make sure you’re placing it with your eyes open.

Want to explore these ideas further? Learn more about my work on leadership, identity and conviction at www.theglennllopis.com.