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 whose replies always arrive late because their attention is spread thin across too many things. 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 practical 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 surfaces the knowledge flow, the informal expertise network.

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

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

Whose absence would you feel most? — This surfaces 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.

These are just example questions — the approach is what matters. You’re not grading anyone. You’re surfacing what’s already there.

From this simple data, patterns emerge. Who is consistently named across all four questions — your connectors, the load-bearing members. Who is named for internal support but not external output — your internal glue. Who starts new ideas but doesn’t sustain them — your engines who may be burning out. Who is rarely named at all — your structurally displaced members, or your genuine gaps.

Who reads these patterns is a separate question. Not a manager from a position of authority. Not HR from a position of process. The participants themselves, together. No AI or HR process can assess the depth of systems thinking better than another systems thinker. When you evaluate others, your own ability to see gets calibrated. A team that systematically looks at itself becomes a better observer after every cycle.

A separate question — does the team itself get calibrated, not just its ability to see. Direct answer: observation by itself doesn’t change the structure. But it adds a new level — the level from which the team sees itself. And action starts from that level. A person who sees that they’re a connector consciously preserves that role or shares it with others. A gap in the spectrum, once noticed, starts filling in — through redistribution of attention, through hiring, through conversation. The gyrator reshapes itself, but not from the gaze alone — from the cycle of look → analyze → correct → look again. Observation without action is just a release valve. Only a closed loop calibrates.

That’s already valuable information. But it isn’t complete.

What we don’t measure yet

Let me say where the 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 which team qualities are pronounced and which ones are sagging. 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.

Circulation is hierarchical

There’s something worth naming before we build a value map. A gyrator operates at each hierarchical level separately. A working group is a gyrator. A department that contains several groups is a gyrator of a different order, with different elements — the elements here are the groups themselves, not people. The company is a gyrator at a higher level still. And so on up.

This means value circulation is hierarchical too. When you help someone in a neighboring department, that interaction is an element of a higher-level gyrator — the one that contains both departments. You don’t see it from the inside, the same way an electron inside a molecule doesn’t “see” the molecule. But that’s where the loop actually closes.

That’s why return value often comes from somewhere else, sometimes somewhere unexpected. Not because “the universe is fair,” but because the higher level of hierarchy — which you don’t directly observe — really exists and really influences where the system directs its attention and resources next. Indirectly: through decisions, priorities, through the distribution of future opportunities. The hierarchical gyrator closes its loop in places you’re not looking.

And one more thing: the question isn’t whether the helper got something back personally. A gyrator works through circulation across the whole, not through direct barter between two. The return flow also shows up in the quality of the interaction itself. Whether the reply came in time. Whether there was gratitude. Whether the person said an honest “not right now, I’m swamped.” Whether the request was received as shared work or as someone else’s burden. That’s a signal too, and it’s visible immediately — not in a month, not in a quarter, but in the interaction itself.

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 — which departments benefited? When a member of one department helps someone from another, where does the value go next — does it flow into the wider circulation the whole company draws from, or does it stall and get lost in friction?

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.

One caveat that follows from what’s said above: don’t try to reduce value to pairwise interactions. If the flow map shows some group giving a lot but “not getting anything back” — that’s not yet a diagnosis. You may be looking at the wrong level. Check what’s happening one floor up.

The honesty dilemma

There’s a contradiction here that needs to be named directly. For peer evaluation to work — you need honesty. And honesty only holds where answers don’t have direct consequences for people’s careers. But if the answers don’t influence anything at all — why collect them? A manager who has seen that without Olya nothing moves cannot “not take that into account” in the next decision about promotions or team composition. They have to take it into account. And at that moment people start answering not honestly but strategically.

This is not a performance management tool. It’s not for ranking people and it’s not for finding 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.

How do you resolve this? That’s why it’s a dilemma — there’s no simple answer. I think it depends on the culture of the company and the maturity of the people in it. Roughly, it gets handled through cross-evaluation — when answers are analyzed not one by one but by groups, so that strategic gaming becomes visible.

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

The goal is to build stronger transformation reactors. Not structure for its own sake — a whole, coherent structure is itself what generates value. The mission gets realized through it, because without coherence there’s nothing to realize it with.