📖 Source→⚡ Observation·Where the pattern works/Where the pattern breaks·Interpretation ≠ Conclusion

Peeragogy in Practice

Misunderstanding power

⏱ 3 min

Definition:

Wikipedia: Zipf’s law states that given some corpus of natural language utterances, the frequency of any word is inversely proportional to its rank in the frequency table. Thus the most frequent word will occur approximately twice as often as the second most frequent word, three times as often as the third most frequent word, etc. [1]

Related formulations, called power laws, model the size of cities, and describe energy use in animals and social network effects. Creativity and other social network effects – like crime – are more prevalant in large cities. Power laws also describe the forces governing online participation. But it is easy to forget this.

Problem:

How many times have we been at a conference or workshop and heard someone say (or said ourselves) “wouldn’t it be great if this energy could be sustained all year ’round?” Or in a classroom or peer production setting, wondered why it is that everyone does not participate equally. “Wouldn’t it be great if we could increase participation?” But participation in a given population will fall off according to some power law (see Introduction to Power Laws in The Uncertainty Principle, Volume II, Issue 3). It would be an illusion to assume that everyone is coming from a similar place with regard to the various literacies and motivations that are conducive to participation.

(Bogus) Solution:

It can be tempting to adopt a “provisionist” attitude, and say: “If we change our system we will equalize participation and access.”

Challenges:

Power laws are an inherent epiphenomenon of network flows. If you can adjust the way the way the network is shaped, for example, through moderatation, then you may be able to change the “exponent” in the power law. But even so, “equality” remains a largely abstract notion. Note, also, that participation in a given activity tends to fall off over time. It’s easy to imagine writing a hit song or a best selling novel, but hard to pull this off, because it takes sustained effort over time. See the anti-pattern Magical Thinking.

What’s Next:

As Paul Graham wrote about programming languages – programmers are typically “satisfied with whatever language they happen to use, because it dictates the way they think about programs” – so too are people often “satisfied” with their social environments, because these tend to dictate the way they think and act in life. Nevertheless, if we put our minds to it, we can become more “literate” in the patterns that make up our world and the ways we can effect change.

References:

  1. Zipf’s law. (2013). In Wikipedia, The Free Encyclopedia.

  2. Graham, P. (2001). Beating the averages.

⚡ Unpeeragogy · Friction · Observation

Power Is Misunderstood Even When Analyzed

⏱ 4 minaudit-v2misunderstanding_powerpowerhierarchy

The Assumption

Power exists in flat groups but remains hidden and unaddressed, creating invisible dynamics that complicate accountability and decision-making through mechanisms like knowledge-hoarding and authority-attrition.

Operational Reality

Three engineers at a fintech startup spent six months building “consensus-driven architecture decisions.” They documented every choice, rotated meeting facilitation, and tracked participation metrics. The system worked — until the day their lead architect quietly migrated the entire codebase to a framework none of them had discussed. When confronted, she shrugged: “You were debating database schemas. I was solving the real problem.”

Power does not announce itself with org charts and voting procedures. Not formal authority. Not documented processes. Not even explicit hierarchy. It flows through the gaps — who controls the narrative, who frames the questions, who decides what counts as a problem worth solving. The Wikipedia editor who writes the daily summary email shapes tomorrow’s priorities more than the elected board members who meet monthly.

GitLab shows that documented governance boundaries between stakeholder groups can create structural limits on power. Wikipedia shows that visibility can institutionalize power imbalances rather than eliminate them. Debian’s DPL bits newsletter demonstrates that curation itself is a form of power that transparency alone does not dissolve.

Perturbatore: “What if naming the dragon does not kill it — sometimes it just teaches the dragon better PR — and the most dangerous power is the kind that insists it does not exist?”

Empirical Evidence

Resilience Cases (Confirming):

  • GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction in open-core projects. Documented governance boundaries between stakeholder groups can create structural limits on power.

Fracture Cases (Complicating):

  • Wikipedia Deletion Debates — Consensus processes produce de facto hierarchies through participation inequality — those who show up consistently gain disproportionate influence. Visibility can institutionalize power imbalances rather than eliminate them.
  • Debian DPL Bits Newsletter — Regular leadership summaries in peer-governed projects create agenda-setting power — what gets summarized is what gets attention. Curation itself is a form of power that transparency alone does not dissolve.

Operational Heuristics

Positive Boundary: The pattern works when visibility is coupled with explicit redistribution mechanisms — documented governance boundaries between different stakeholders reduce friction by creating structural limits on asymmetric power.

Negative Boundary: Do not assume that making power dynamics visible dissolves them automatically — transparent processes can institutionalize power imbalances; visibility without redistribution is performative transparency.

Epistemic Synthesis

Power analysis fails when it focuses on visible structures instead of invisible rhythms. The sponsor who documents governance boundaries can reduce friction — but the documentation itself becomes a form of control, determining what can be contested and what stays off the agenda. Peer governance that produces leadership summaries creates the illusion of transparency while concentrating agenda-setting power in the hands of those who choose what deserves attention. The most effective power operates through curation — not blocking access, but shaping what seems worth accessing.

Perturbatore: “What if naming the dragon does not kill it — sometimes it just teaches the dragon better PR — and the most dangerous power is the kind that insists it does not exist?”

The quietest voice in the room still sets the agenda.

Evidence Status

Status Count
Confirmed cases 1
Cases under study 0
Unverified cases 0
Ambiguous cases 0

Traceability

Run: audit-v2 · Delta: 1.5 → 1.6792 (±0.1792) · Diversity D: 2

References

💬 Field Report: Power Is Misunderstood Even When Analyzed

Every pattern in the Handbook has been tested in the real world — and the real world usually has something to say about it. If you tried something similar, or saw it fail differently, share the story here.

Write in your native language — the browser will translate. Lowering the entry barrier is more important than choosing the "right" language. GitHub translates threads automatically so everyone can follow along.
Read how evidence is collected →

What happens after I share my story?

1. Your post appears in GitHub Discussions in the Field reports category.

2. Once a week, the project reads new threads and checks for patterns worth integrating.

3. If your story reveals a new Failure Vector, a revision to tension_index, or a sharper edge for the Perturbator — the entry gets updated.

4. The change is logged at /log and goes live on the next deploy.

Don't have a GitHub account? Here's how it works

GitHub Discussions is free. You need a GitHub account (30 seconds to create one).

Once you're signed in, click "Share your story" above. Write in your own language — the thread will be translated for everyone else automatically.

You don't need to know how to code. You don't need to know what "git" is. You just need an observation that the theory didn't match reality.

What are GitHub Discussions? →

Every pattern raises more questions than it answers.
Read the theory. Then look at what happened.