The Bearing Wall and the Flowers: Leadership and Invisible Labor in an Online Community
In one sentence. A large online strategy game became a useful case study of how voluntary organizations coordinate people, distribute responsibility, recognize invisible work, and balance performance with participation.
Why this case belongs here
This case examines organizational mechanisms in a setting where participation is voluntary, information is incomplete, authority is partly informal, and collective outcomes depend on coordination.
The setting was a well-known multiplayer strategy game released under different regional names, including 无尽冬日 and 寒霜启示录. For a period, I served as the in-game “king” of a server with roughly one thousand players. In that role, I coordinated across alliances during large-scale competitions, including several successful campaigns.
Those details establish the scale of the experience; they are not the point of the article. The more interesting question is what the experience revealed about leadership and system design. To protect the people involved, I deliberately omit the server number, alliance names, player identities, dates, private conversations, and specific battle records.
Leadership without formal authority
An online community is not a company. Members are not employees, and an in-game title does not create the same authority as a formal management position. Most participation depends on trust, shared goals, reputation, and whether a plan feels worth following.
This makes coordination an unusually clear design problem. A leader cannot rely only on instructions. A workable plan must also answer several practical questions:
- Can people understand the goal quickly?
- Do they know what action is expected from them?
- Is the cost of participating reasonable?
- Can the plan survive incomplete information and last-minute changes?
- Do members still feel that they have agency?
Winning required more than choosing a technically strong strategy. It required turning analysis into a plan that many people could execute under time pressure.
The reliability loop
When one organizer repeatedly solves difficult problems, a reinforcing loop can emerge:
- competence becomes visible;
- more questions and decisions flow toward that person;
- responsibility becomes concentrated;
- others begin to treat that reliability as part of the environment;
- the organizer becomes both more valuable and a larger single point of failure.
This process does not require bad intentions. Delegating a problem to the person most likely to solve it is locally rational. But repeated many times, that choice can make the whole organization dependent on a small number of people.
The lesson is not that reliable people should contribute less. It is that a healthy organization should convert individual reliability into shared capacity through documentation, role rotation, reusable procedures, and clearer ownership.
The bearing wall and the flowers
A metaphor helped me understand why some contributions are easier to recognize than others: people notice the flowers by the window, but rarely discuss the bearing wall.
Public encouragement, entertaining messages, and visible achievements are like flowers. They are immediate, memorable, and easy to celebrate. Scheduling, risk assessment, conflict prevention, contingency planning, and repeated explanation are more like a bearing wall. Their value often becomes visible only when they are missing.
Neither form of contribution is superior. A durable community needs both. The problem appears when visible contributions receive nearly all the recognition while maintenance work quietly accumulates around a few dependable organizers.
This recognition gap matters because feedback shapes future effort. If a community celebrates only final victories, it may underinvest in the less visible work that makes those victories repeatable.
Performance and participation are different objectives
The experience also revealed a recurring tension between two legitimate goals:
- a performance objective values accurate analysis, efficient coordination, disciplined execution, and winning;
- a participation objective values autonomy, belonging, enjoyment, and the feeling that many members have a meaningful role.
A plan can improve performance while weakening participation. For example, a small expert group may produce a better strategy, but a fully specified plan can leave other members feeling that their judgment is unnecessary. Conversely, a highly participatory process may strengthen commitment while making decisions slower or less consistent.
The management question is therefore not “serious or casual.” It is how to design a process that preserves enough analytical quality without turning the rest of the community into passive executors.
From heroic leadership to system design
Several practical responses follow from these observations:
- rotate responsibilities before dependency becomes normal;
- turn repeated explanations into short, reusable guides;
- separate strategic analysis from community-facing communication when the roles require different strengths;
- assign clear owners to recurring tasks instead of relying on whoever notices the problem first;
- create explicit recognition for maintenance and coordination work;
- preserve some decisions that members can genuinely shape;
- design fallback plans so that one unavailable organizer does not stop the system.
These interventions are not only about reducing workload. They create redundancy, distribute knowledge, and make collective performance more robust.
Evidence, scope, and privacy
This article is an anonymized reflection based on one participant-observer’s experience in one online community. The scale was large enough to expose real coordination problems, but the observations are not a controlled study and should not be treated as general conclusions about games, companies, or other organizations.
The account also intentionally leaves out operational and interpersonal details. That limits how closely a reader can audit individual events, but it is the appropriate trade-off for discussing organizational mechanisms without exposing other participants or turning a personal homepage into a record of private community history.
The relevant outcome is not that an alliance won particular battles. It is that the experience made several mechanisms easier to see: informal authority, concentrated responsibility, invisible labor, recognition, and the tension between performance and participation.
What transfers
The same analytical sequence appears in many settings:
- observe an unexpected collective outcome;
- reconstruct the incentives and information available to each participant;
- identify where responsibility or knowledge is concentrated;
- distinguish visible success from the mechanisms supporting it;
- redesign the process so that the result depends less on individual heroics.
That is why this case belongs in the Understanding Series. The object happened to be an online game, but the subject is a broader one: how people coordinate inside a complex system, and how good leadership gradually turns personal effort into organizational capability.