How to See What's Invisible

Everything I’ve described so far — the gyrator structure, the complementary spectrums, how well a team turns resources into value — is invisible in a traditional organization. There’s no report for it. No dashboard. No metric in your quarterly review.

And yet people know. People inside teams know exactly who contributes and how. They know who responds at 2am because they care. They know who blocks requests because they can’t be bothered. They know whose presence makes the team better and whose absence wouldn’t be noticed.

The information exists. It’s just not captured anywhere.

Peer evaluation as the primary signal

The simplest and most honest way to make the invisible visible is to ask the people who see it every day.

Not their managers — who see output but rarely see the interactions that produce it. Not an algorithm analyzing Slack messages — which measures activity but not value. The people themselves.

A periodic, lightweight peer evaluation where each team member answers a small number of questions about every other member:

Who do you go to when you’re stuck? — This maps the knowledge flow, the informal expertise network.

Who makes it easier for you to do your work? — This maps the support structure, the gyrator interactions.

Who contributes most to achieving our group’s goal? — This maps the output flow, the delivery engine.

Whose absence would you feel most? — This maps systemic importance, the load-bearing members.

Four questions. Each answered about each teammate. Done periodically — once a month or once per project cycle. No ratings, no scores, no numbers. Just names.

From this simple data, patterns emerge: who is consistently named across all four questions (your connectors and load-bearing members), who is named for internal support but not external output (your internal glue), who is named for delivery but not support (your engines who may be burning out), and who is rarely named at all (your structurally displaced members — or your genuine gaps).

What we don’t measure yet

I want to be honest about the limits of where this framework stands today.

The theory tells us that a team’s spectrum should be complete — all necessary qualities covered, no critical gaps. But I don’t yet have a reliable method for calculating completeness as a number. I don’t think anyone does. The math exists in Malyuta’s formalism — the hypercomplex matrix, the completeness of closedness measure — but translating it into something practical for real teams is work that hasn’t been done yet.

What we can do today is make the spectrum visible. When you see the peer evaluation results, you can see the shape. You can see where the team is rich and where it’s thin. You can see whether the spectrums compose or collide. You can have a conversation about it with the team.

Precision will come later. Visibility is the first step.

The value flow map

Beyond peer evaluation, there’s a second layer: tracking how value actually flows between people and between groups.

When a cross-functional team delivers something — a tool, a solution, a decision — which departments benefited? When a member of one department helped someone from another, did that help flow back eventually, or was it a one-way drain?

This doesn’t require surveillance. It requires structured reflection. At the end of each project cycle, each group answers: What did we produce? Who did it serve? What did we need from others? Who provided it?

Over time, this builds a map of value flow across the organization. You can see which groups are net producers and which are net consumers. You can see where resources are turning into value and where they disappear into friction. You can see the connectors — the people and groups who bridge the gaps.

What this is not

I want to be clear about what this measurement system is for.

It’s not a performance management tool. It’s not designed to rank people or find who to fire. If you use it that way, people will game it, and you’ll lose the only thing that makes it valuable — honesty.

It’s a structural diagnostic. It shows you the shape of your teams’ internal architecture so you can improve it. It shows you where value flows freely and where it’s stuck. It shows you where the spectrum is complete and where there are gaps.

The goal is to build stronger transformation reactors — not to optimize individual performance. The system serves the structure. The structure serves the mission.