Building a high-performing team is not a theory. It is a discipline. I have been building and leading teams in construction, roofing, and home improvement for over 20 years. The teams that produce elite results share specific traits. They are not accidents. They are built.
TL;DR: High-performing teams share five traits: aligned on expectations, built on accountability, strong at honest communication, supported through coaching, and protected from unmanaged underperformers. Building them requires intention at every stage — hiring, onboarding, managing, and developing. The principles that worked at $3M work at $35M. Scale the discipline, not just the headcount.
Why high-performing teams outperform
Most companies talk about performance. Few build the conditions that make it possible. Research from McKinsey and other management consultancies consistently finds that top-performing teams are significantly more productive than average ones, often by a substantial margin depending on the domain. In construction, where margins are thin and schedules unforgiving, the difference between a cohesive team and a dysfunctional one shows up in every estimate, every project close, and every customer relationship.
High-performing teams share five traits that average teams lack: shared clarity on expectations, genuine accountability, direct communication, strong coaching from their manager, and protection from underperformers who are allowed to drag the team down. Remove any one of those five and performance drops. Remove two or more and you are managing a team in name only.
I have run crews with 10 people and organizations with hundreds. The fundamentals do not change at scale. What changes is how deliberately you have to engineer the conditions, because the more people you add, the more entropy you fight.
What it takes to build a high-performing team
The first thing is hiring for fit, not just competence. Technical skills matter. They are also table stakes. Everyone you consider has them at some level. What separates sustainable performers from one-cycle wonders is character: reliability, honesty, the ability to receive feedback without shutting down, and the drive to get better. Those traits are harder to assess than a resume, which is why most managers shortcut the process and end up surprised when technically capable people fail for entirely predictable reasons.
When I started Penebaker Enterprises in 2002, my first hires were people I had worked with before. I knew their character. Over time, I had to develop a process that approximated that personal knowledge with people I had not yet met. The three-stage screening I use now covers a phone assessment focused on reliability and trajectory, a field or role-based evaluation with a trusted lead, and a reference check that goes beyond the names the candidate provides. The goal is to answer one question before an offer: when this person hits a hard week, what do they do? Do they double down or do they disappear?
The second thing is clarity on expectations from day one. Most managers skip this step or do it once and never revisit it. The best teams I have run operated with explicit written expectations: what does excellent performance look like in this role, what are the non-negotiables, how is performance measured, and what is the cadence for feedback? When those expectations are clear, accountability conversations are easier because everyone is working from the same standard.
Third is a coaching culture. The difference between a manager and a leader is that a manager enforces standards while a leader develops people. I have had managers working for me who were excellent at holding people accountable but terrible at developing them. The result is a team that performs adequately but never grows. In a competitive market, adequate is a liability. The teams I am proudest of are the ones where I watched people arrive at one level and leave significantly better. That does not happen by accident. It happens because someone made time for it.
Gallup research consistently shows that employees who feel their managers are invested in their development are significantly more engaged and far less likely to leave. In an industry where the BLS JOLTS report shows total annual separation rates above 40%, retention is a competitive advantage. The cost of replacing a skilled field supervisor, accounting for recruiting, onboarding, and the performance dip during the learning curve, can equal six months of their salary. Development is not soft. It is one of the highest-ROI investments a manager can make.
How to handle underperformers
Not addressing underperformance is itself a performance decision. Every day a low performer operates without consequence, the message to the rest of the team is that the standard is lower than you said it was. High performers notice. They calibrate to the real standard, not the stated one. And eventually, if nothing changes, they leave, because talented people do not stay in environments where the rules apply unevenly.
My approach has three stages. First, clarity. Most underperformance begins as a gap between what the manager expects and what the employee understood was expected. Before concluding that someone cannot do the job, I make sure they know exactly what the job requires. That conversation, done honestly and specifically, resolves a significant percentage of performance issues before they become formal problems.
Second, a documented improvement plan with a timeline. Not a bureaucratic exercise, but a genuine tool: here is the specific gap, here is what closing it looks like, here is the timeline, here is the support available, and here is what happens if the gap is not closed. Most people, given clear direction, real support, and a fair timeline, respond. The ones who do not have told you what you need to know.
Third, a decision. If the gap persists after genuine effort from both sides, the answer is clear. Keeping someone in a role they cannot fill does not help them and it actively hurts everyone around them. I have had to make that decision more times than I would have liked. Every time I waited too long, I watched the high performers on the team lose patience and start planning their exits. The cost of delay was always higher than the cost of the decision itself.
What keeps a high-performing team together
Retention at the team level is about belonging and growth. People stay where they feel their work matters, their contribution is recognized, and they are moving forward. Compensation matters but it is rarely the primary driver of voluntary departures among high performers. The drivers are almost always about the manager, the team culture, or the absence of growth. All three are directly within a manager’s control.
I have a standing practice with every team I lead: I spend time every week with people who are not bringing me problems. The people who bring me problems are visible. The people who are quietly excelling, quietly struggling, or quietly deciding whether to stay are often invisible until they are gone. Thirty minutes a week across a team catches most of what would otherwise become surprises.
Recognition matters. Not performance reviews that happen once a year, but specific, timely acknowledgment of excellent work when it happens. Research from SHRM consistently shows that employees who feel regularly recognized are significantly more likely to report high job satisfaction and strong intent to stay. In construction, where the pace is fast and the margin for error is small, recognition is often the first thing that gets cut when a manager is under pressure. That is exactly backwards. When times are hard, recognition is more important, not less, because people are deciding whether the investment they are making in your team is worth it.
The hardest part of keeping a high-performing team together is what happens when you scale. The team of five that built something extraordinary often does not survive the growth to fifty intact. Not because the people failed, but because growth without deliberate culture work dilutes what made the original team function. I have watched this happen in construction companies and in home improvement operations. The founder or division leader who built an excellent 20-person team hires 30 more people over 18 months and wonders why the team does not feel the same. It does not feel the same because the informal behaviors, norms, and expectations that defined the original team were never made explicit. The only thing that scales is what you write down.
Now, as Division President at MetalMaster-RoofMaster, I apply these principles across the Upper Midwest division. The industry has changed and the scale is different, but the fundamentals have not. The teams that win are the ones where the standard is clear, accountability is real, people are developed rather than managed, and the manager is paying attention to the ones who are not in crisis. That is not complicated. It is just rare.
Common questions
What is the most common reason high-performing teams fail?
Unmanaged underperformance. When managers allow people who are not meeting standards to stay in their roles without consequence, high performers recalibrate their expectations downward and eventually leave. Protecting team standards, including making hard decisions about people who cannot or will not meet them, is the single most important thing a manager can do to preserve a high-performing culture.
How do you build a high-performing team when you inherit one that is already struggling?
Start with a clear-eyed assessment of who you have, not who you wish you had. Spend the first 30 days listening: to the team members individually, to the people they interact with, and to the results. Identify the top 20% and make sure they know you see them. Identify the bottom 20% and start the clarity conversation immediately. Most inherited teams have two or three people who are either in the wrong role or operating without adequate direction. Fixing those two things often unlocks performance that was always there.
How much time should a manager spend on development versus operations?
There is no universal ratio, but a useful benchmark is that if you are spending less than 20% of your management time on people development, coaching, and growth conversations, you are likely over-invested in operations and under-invested in your team. In construction, the pressure is always toward operational execution because deadlines are real and the cost of delay is visible. The cost of not developing people is equally real but invisible until someone resigns or a critical role goes unfilled.
What is the biggest mistake managers make when building teams?
Hiring for immediate need rather than long-term fit. When a role is open and projects are waiting, the pressure to fill the seat is intense. Managers rush the process, skip the reference checks, and extend offers to people who can do the job adequately but who do not share the team’s values or work style. The cost of a bad hire, in direct expenses and team disruption, consistently exceeds the cost of the delay. Hire slowly. It sounds like advice that does not survive contact with a deadline. It survives contact with reality.
