The five dimensions that determine how an executive team performs.
Individual executives are reviewed many times over. Their teams rarely are. Performance reviews, one-on-ones, and hiring decisions all take the single leader as their subject, which leaves the more consequential question largely unexamined: how a group of leaders thinks, communicates, decides, and operates together under pressure. This is what the Five Signals were built to measure. They describe properties of a group rather than traits of the people in it.
The team says the hard things, to each other, in the room.
Effective executive teams say the hard things. They challenge each other's ideas, surface real concerns, and have the conversations that actually matter. They're as willing to receive difficult feedback as they are to give it, and they do both well.
The important things go unspoken. The room gets agreeable. Meetings feel smooth but nothing actually gets resolved. At its worst, leaders are aligned in the room and corrosive outside of it. The CEO often senses problems beneath the surface but can't get the team to name them.
Research into psychological safety: the shared belief that a team is safe for interpersonal risk-taking, that a concern can be raised or a mistake admitted without punishment. It also draws on the well-documented value of productive, task-focused conflict, the finding that the strongest teams argue about the work rather than smoothing everything over. There are two halves at play: the safety to speak and the willingness to actually do so. Strong teams have both.
The team gets measurably better over time because it works on itself.
High-performing executive teams are always working on themselves. They actively seek feedback, test their assumptions, and change their behavior when they're wrong. They treat their own development as seriously as they treat the development of their people, and the team gets measurably better over time.
The team settles. They fall back on what they know and stop questioning whether it still works. They stop failing, but they also stop improving. The gap between where the team is and where the business needs it to be widens quietly, because nobody is naming it. The CEO is the only one pushing for change.
The difference between a fixed and a growth orientation: the belief that ability is developed rather than fixed, and that feedback is information rather than threat. It also draws on the literature on feedback-seeking behavior and on learning agility, the capacity to learn from experience and apply it somewhere new. At the team level it echoes double-loop learning, where a group questions the assumptions behind its behavior rather than just correcting the behavior.
Outcomes have owners, and the team holds each other to them.
High-performing teams win, and they hold each other to it. Targets have owners; outcomes belong to everyone. When things go wrong, they find the root cause and fix it; they don't explain it away. And they hold their people to the same standard they hold themselves.
Effort gets celebrated instead of results. Goals slip, often with reasonable explanations. Cross-functional work stalls and the can gets kicked. There's no momentum, just motion. The CEO watches targets get missed without clear answers for why, or any real confidence that next quarter will be different.
Goal-setting and commitment research: the finding that clear, owned, committed-to goals drive performance in a way that vague or externally imposed ones don't. Its cross-functional failure mode has a specific behavioral basis in the diffusion of responsibility, the well-studied tendency for people to assume someone else will act when responsibility is spread across a group. That is the mechanism behind work falling between two functions. The team-level twist is mutual accountability, leaders holding each other to standards, which is a property of the group rather than a trait of any one person.
The team leads the business instead of just running their day-to-day.
Executive teams exist to lead the business, not just run their departments. The best ones treat the leadership team as their primary team, putting company-wide objectives ahead of individual or departmental interests. When they're in the room together, they're talking about where the business is going, what's in the way, and what it needs to get there. They're also looking around corners, anticipating problems before they surface rather than responding to the latest fire.
Leaders go heads-down. They're consumed by their own functions and can't see past the next month. Leadership meetings become status reports. Decisions that should take minutes take weeks because nobody owns the company-wide view. The company is being managed, not led, and the CEO carries a strategic burden the team should be sharing.
The tradition of adaptive leadership, and the distinction between working in the business and working on it, often described as the difference between being down on the dance floor and up on the balcony where you can see the whole pattern. It also draws on the concept of a leader's primary team, the idea that an executive's first loyalty belongs to the leadership team and the whole enterprise rather than to the function they represent. Leaders who consistently defend their own turf have inverted that priority.
The team decides together, commits fully, and moves as one.
A great executive team is more than a collection of talented individuals. They share a clear picture of what the business is trying to accomplish and what that requires from all of them. They've built the muscle to make decisions together, commit to them fully, and leave the room moving as one.
Leaders talk past each other. Decisions feel arbitrary to the people being asked to execute them. Goals get set that nobody actually believes in. The team looks unified on paper but functions like a group of individuals who happen to report to the same person. The CEO spends more time managing individual dynamics than leading the team as a whole.
Shared mental models: the finding that high-performing teams hold a common picture of the goal and of each other's roles, which lets them coordinate and commit without constant re-litigation. It resonates with the large-scale findings that the best predictors of team performance are things like safety, dependability, and clarity of purpose rather than the raw talent of the members. Cohesion sits downstream of the other four, which is why we treat it as an outcome rather than something you can install directly.
The Five Signals didn't come from nowhere. The framework is a synthesis of several decades of well-established work in workplace and behavioral psychology, applied at a level most of that research never targeted directly: the executive team as a unit. It's also informed by our work building and deploying employee engagement models across a wide variety of industries and company types, and over a thousand hours coaching CEOs. The ideas below are individually well-supported and most of them will already be familiar to a thoughtful executive.
The deepest root of the framework is a simple idea: a team is more than the sum of its members. It has properties that don't live in any one person, and those properties are what determine whether the group performs. A team cannot be understood by grading its individuals and adding up the scores.
This lines up with a long tradition in team-effectiveness research that distinguishes a real team from a working group: a collection of capable people who happen to report to the same person but never actually operate as a unit. That failure state, which shows up in the break language for Cohesion, is a direct description of a working group masquerading as a team.
It also draws on research specifically into senior leadership teams, which behave differently from teams lower in the organization and are studied far less often. Interdependence is highest at the top and the cost of a breakdown is greatest there, yet top teams are the least likely to have ever been assessed as a team. That gap is the one Helm was built to fill. The practical consequence is methodological: we gather input from many raters, in a long-standing tradition, but we point it at the group rather than at ranking individuals.
Every statement in the diagnostic describes something a leader does rather than something a leader is. Whether concerns get raised in the room rather than in the hallway. Whether a commitment is followed through. Whether a decision gets connected to what matters most for the business. The distinction is not a matter of phrasing.
Personality is relatively stable, and typing people rarely tells a team what to do next. Behavior is contextual, which means a leader who reads low on a signal in one environment can read differently in another, and it is coachable, which means a score describes something that can move rather than something to be worked around. It also makes the input more trustworthy. Colleagues can report accurately on what someone does far more often than they can assess what someone is.
It follows that a low signal is a description of how a team is operating today, not a verdict on the people in it. That distinction is most of the difference between an assessment that produces defensiveness and one that produces work.
Helm treats team capabilities as things that develop along a continuum rather than as conditions a team either has or doesn't. This is a deliberate departure from the popular framing that sorts teams into healthy or broken, which tends to be binary and a little pathological. A team isn't broken or healthy. It's somewhere on a path, stronger in some signals than others, and every signal can be developed.
The language of the model follows from that. Nothing in it is meant to read as a permanent verdict on a person or a team, because a growth model that hands down verdicts stops being a growth model.
Reading about the signals is one thing. Seeing where your own team sits on all five, and what the spread between your leaders says, is the part that can change your business. If you want to learn more, we'd be glad to talk.