Why Performance Data is the Foundation

Last week we talked about how Carolina Hurricanes GM Eric Tulsky evaluates players and how a lot of his thinking connects to what HELIOS measures on the ice. If you missed it, the short version: speed, effort, and consistency are the variables NHL front offices chase. They’re also the variables your HELIOS data already tracks.

That got us thinking about a bigger question. One that’s worth sitting with.

If a team like Carolina is building a complete picture of a player, what does “complete” actually mean? What are all the layers and which ones matter most?

Because here’s the truth: not all data is created equal. Especially when the goal is development.

Start with the foundation.

Before a player can execute a system, they need an engine. Skating ability. Physical conditioning.

The compete level to sustain effort through a third period when the game is on the line. The work ethic that shows up in practice on a Wednesday in February when nobody’s watching.

Those aren’t soft qualities. They’re measurable. And they’re the foundation everything else in hockey is built on.

This is what HELIOS was designed to capture: the physical layer underneath the game. Sprint speed, acceleration, sustained effort, shift load, fatigue accumulation across a game and across a full season. 

The data that tells you not just what a player did, but what it took to do it, and whether they’re building the physical foundation to do it better.

Without this layer, you’re evaluating a player on outcomes without understanding the engine producing them. That’s a significant blind spot, whether you’re a coach building a practice plan, a parent tracking development, or a program making decisions about where to invest time.

Where the real work happens.

Here’s the part that doesn’t get talked about enough. 

Game strategy is only as good as the engine underneath it. A breakout system, a forecheck, a power play structure — none of it matters if the players running it don’t have the skating ability and physical capacity to execute for 60 minutes.

And that engine isn’t built on game day. It’s built in practice.

Systems analytics platforms like InStat, TPE, and 49ing are built around game film. They break down what happened on the ice: shot locations, zone entries, faceoff percentages, breakout success, forechecks.

That’s valuable context. But it only captures the game, and it typically takes 12–72 hours to turn that footage into usable data. By the time you see it, the teaching moment has passed.

HELIOS works everywhere, games and practice, and the video and data comes back instantly. That means a coach isn’t walking into a game wondering whether the team has the conditioning and skating foundation to execute the system. They already know. They’ve seen the effort and intensity data all week. They’ve watched individual players build, or not build, the physical readiness the system demands.

Readiness isn’t a game-day question. It’s a Tuesday-practice question. 

And it’s the question systems tools were never built to answer.

Where systems analytics fits in.

Systems tools do something specific well: they tell you what happened in the game and where. Shot locations, zone entry rates, puck possession: that’s legitimate context for understanding tactical execution and hockey IQ. There’s a reason serious programs use them.

But here’s the limitation worth understanding. 

Systems platforms show you the outcome of a play. They can’t tell you whether that back check was a max-effort sprint or a lazy coast that happened to get there in time. 

They can’t tell you whether a player’s speed in the third period matched their speed in the first And they definitely can’t reveal if a player possesses the underlying skating mechanics required to reach an elite level of speed.

They can’t tell you whether a player is physically declining or just going through a cold streak. And they can’t tell you anything at all about what’s happening in practice where the foundation is either being built or neglected.

That’s not a knock. It’s just what those tools are designed to do.

The question is whether you want the complete picture or just the part that shows up on film.

What the complete picture looks like.

Go back to Tulsky. His edge isn’t any single data source. It’s refusing to rely on only one layer.

Possession stats alone don’t tell you who’s driving play. Point totals alone don’t tell you who’s declining versus who’s just unlucky. He stacks physical data on top of tactical data to get answers no single source could give him. The same logic applies at every level of the game. 

HELIOS gives you the foundation: the physical output, the effort, the conditioning, the skating development happening shift by shift and practice by practice. 

Systems tools give you some tactical context layered on top of that foundation.

But if you only have the tactical context and not the physical foundation, you’re missing the most important part. You’re watching what happened without understanding what made it possible or what’s quietly limiting it.

A player whose tactical execution looks fine on film but whose physical numbers are declining? That’s something a systems tool will never surface. 

A player whose points are down but whose effort and speed data are holding strong? That’s a cold streak, not a development problem. 

A team that looks sharp in games but has been coasting in practice all week? That shows up in HELIOS before it shows up in the score.

Performance analytics don’t just add to the picture. For player development and season-long optimization, they are the picture. Everything else is context.

Why this matters right now.

If you’re a coach, the most valuable question you can answer heading into any game isn’t what your opponent did last week. It’s whether your team is physically ready to execute what you’re asking them to do. HELIOS answers that — every day, in real time.

If you’re a parent, the most important development signal isn’t a point total or a highlight clip. It’s whether your player is building the physical foundation that gives their game somewhere to grow. HELIOS tracks that across a full season.

If you’re running a program, the difference between a player who develops and one who plateaus often comes down to whether someone was paying attention to the right data at the right time. Systems tools show you the game. HELIOS shows you the player.

Use both if you have them. But know which one is the foundation.

BUILD YOUR FOUNDATION