Delusions > Trickle down is not knowledge flow

Knowledge is Hierarchical Authority

Knowledge emerges through reciprocity, not rank. When people, teams, and tools exchange perspective, context, and care, they create meaning none could generate alone.

Knowledge is Hierarchical Authority

Help! Help! I’m being epistemologically repressed! — not Monty Python and the Holy Grail

This delusion treats organizational hierarchy as a knowledge system. It assumes that knowledge can be handcrafted in a boardroom and handed down to teams like Halloween candy. If knowledge isn’t a possession, it can't be something owned by "leadership" or dispensed by institutions.

In the United States this myth is practically an origin story. The founders believed that landed gentry were inherently more rational, better informed, more fit to decide. Corporations inherited this monarchical structure, and our education system was built to produce expectation-meeting industrial labor for a small leadership class.

We still confuse social position with knowledge. Academic prestige, job title, wealth, brand visibility, follower counts, and election are forms of authority, not (necessarily) knowledge skills. We might apply knowledge from a powerful position but power is not epistemology.

When a group has the authority to decide who gets to speak, who get believed, and who is ignored, they reinforce epistemic gated communities. Defining who counts as knowledgeable. Gender essentialism is a good example, The myth that men are objective and women are emotional was produced by a culture in which women had no authority to define objectivity. Or, biology.

Knowledge is a social process. It arises through reciprocity -- exchanging information, perspective, and experiences across a system of relationships. People working together to interpret, synthesize, and act.

Relational reciprocity doesn't mean "everyone's opinion is equally valid". Opinion is not knowledge. The goal isn't agreement. The goal is coherence, soundness and ... making sense.

Knowledge flows when the CTO's systemic pattern recognition meets the Head of Product's understanding of user behavior meets the junior engineer's intimate knowledge of the code. It emerges in relationships, not boardrooms.

Key concept: Knowledge emerges through reciprocity (not rank) when people, teams, and tools exchange perspective, context, and care.

Gateways

Enter Through Many Doorways

All roads lead to knowledge flow. Whether you read the book, do a practice, build the studio, explore the knowledge ontology or browse the library of resources ... this world is intertwingled.

Sociotechnical Systems

Systems where human, organizational, and technical dynamics intertwine.

Knowledge is Relational Reciprocity

Knowledge doesn’t trickle down; it moves laterally through people who understand why their actions matter and how they connect to others.

Cultivating Coherence

Meaning doesn’t live in one person, one doc, or one tool; it lives between them.

The conversation is happening ...
in our community space.

Weekly Dispatches

Systems ReArchitected

Navigate complexity. Embrace uncertainty. Change What Matters.

Get Involved in the Knowledge Experience

Use the input form to share your feedback on this page.
Or join the community. Discuss your experiences, share knowledge, learn more, together.

Knowledge Flow by Diana Montalion

A learning journey through the fireswamp of modern knowledge work — where how you learn matters more than what you know.

© 2026 Mentrix Group | All systems rearchitected

Learn

Explore

Connect