An Invitation

This publication is a first version of the framework. It’s alive and will evolve — through conversations after publication, through practice, through criticism, through communication.

Where this already works

reintech.io is this theory turned into something that runs. I’m its founder, and it’s where the spectrum model stops being a metaphor and becomes a way to build engineering teams for clients. We don’t just match résumés. We look at spectrums: which qualities are already in the team, which ones are thin, how a new member will complement the whole — measured along the cognitive axes a general publication about teams can only gesture at.

It’s the first concrete implementation, not the last. I’m open to applying these approaches more fully wherever the problem is real. Time will tell what comes of it.

Where this is going technologically

I’m thinking about building a simple web application to make the framework visible and usable: a team matrix, baseline and goal, peer evaluation, value flow map, spectrum visualization, group lifecycle. To start, a working prototype — a way to check how the ideas in this publication translate into something practical.

Interestingly, there’s already a whole industry doing part of what I’m describing. Organizational Network Analysis — both active (survey-based) and passive (via communication metadata). Confirm builds everything on ONA and predicts retention with 73% accuracy by detecting declining collaboration. Innovisor formulated the “three percent rule” — the right 3% of employees directly influence 85% of the workforce. HOW4 uses four unbiased questions and achieves 90%+ response rates. Polinode, Microsoft Viva Insights, Worklytics, SWOOP Analytics, Humanyze — all of them measure network metrics, classify ties, build heatmaps of collaboration.

But here’s what matters: none of these tools think in terms of gyrator structure, complementary spectrums, or the rate at which resources turn into value. They measure activity and connectivity, but not structural completeness or the quality of value conversion. With the systems lens this site sketches, the field can go much deeper. The opportunity is real.

Sources

The direction of this thinking was initiated by Oleksandr Malyuta — a Ukrainian radio physicist whose systems writing gave me the vocabulary this site speaks: the gyrator, spectrums, the baseline, homocentrism. That his work remains largely unknown outside Ukrainian- and Russian-language circles is itself an example of the structural problem this publication is about: value that exists but can’t flow across borders.

What I built with that vocabulary — teams as transformation reactors — is my own synthesis, drawn from practice. It converges with a broad body of research on systems, teams, and organizations. For readers who want to go deeper:

Origins of the vocabulary

• Oleksandr Malyuta, Hypercomplex Dynamic Systems (Lviv, 1989); The System of Activity (Kyiv, 1991)
• Bernard D.H. Tellegen, “The Gyrator, a New Electric Network Element,” Philips Research Reports 3 (1948): 81–101 — the original gyrator

Cybernetics and systems

• W. Ross Ashby, An Introduction to Cybernetics (Chapman & Hall, 1956) — the Law of Requisite Variety. Full text
• Stafford Beer, Brain of the Firm (1972); The Heart of Enterprise (John Wiley, 1979) — the Viable System Model
• Ludwig von Bertalanffy, General System Theory (George Braziller, 1968)
• Jay W. Forrester, Industrial Dynamics (MIT Press, 1961)
• Donella H. Meadows, Thinking in Systems: A Primer (Chelsea Green, 2008)
• Peter M. Senge, The Fifth Discipline (Doubleday/Currency, 1990)

Teams and organization design

• Melvin E. Conway, “How Do Committees Invent?” Datamation 14(5), April 1968: 28–31. Original
• Matthew Skelton and Manuel Pais, Team Topologies (IT Revolution Press, 2019)
• Frédéric Laloux, Reinventing Organizations (Nelson Parker, 2014) — the W.L. Gore case
• Gary Hamel and Michele Zanini, “The End of Bureaucracy,” Harvard Business Review 96(6), Nov–Dec 2018 — the Haier case
• “ING’s agile transformation,” McKinsey Quarterly, January 2017 — the ING case

Networks and team effectiveness

• Rob Cross and Andrew Parker, The Hidden Power of Social Networks (Harvard Business School Press, 2004) — the foundation of Organizational Network Analysis
• Amy C. Edmondson, “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly 44(2), 1999: 350–383. DOI
• Anita Williams Woolley et al., “Evidence for a Collective Intelligence Factor in the Performance of Human Groups,” Science 330 (2010): 686–688. DOI
• Scott E. Page, The Difference (Princeton University Press, 2007)
• R. Meredith Belbin, Management Teams: Why They Succeed or Fail (Heinemann, 1981)
• Bruce W. Tuckman, “Developmental Sequence in Small Groups,” Psychological Bulletin 63 (1965): 384–399

Lifecycle and crisis

• Larry E. Greiner, “Evolution and Revolution as Organizations Grow,” Harvard Business Review 50(4), 1972: 37–46
• Ichak Adizes, Corporate Lifecycles (Prentice Hall, 1988)
• Michael L. Tushman and Elaine Romanelli, “Organizational Evolution: A Metamorphosis Model of Convergence and Reorientation,” Research in Organizational Behavior 7 (1985): 171–222
• Barry M. Staw, Lance E. Sandelands and Jane E. Dutton, “Threat-Rigidity Effects in Organizational Behavior,” Administrative Science Quarterly 26(4), 1981: 501–524
• David A. Garvin and Michael A. Roberto, “What You Don’t Know About Making Decisions,” Harvard Business Review, September 2001

Who to write to

If any of this resonated — or if you think it’s wrong and want to say why — I’d genuinely like to hear.

If you’re looking to hire engineers for your team according to the principles described here and with the realities of the AI era in mind — reintech.io is for that.

Sasha Bondar

sasha@gyrator.io · linkedin.com/in/obondar