Here is the "How we work" section of an engineering README at an invented company:
How we work
We're a flat team. No PMs, no approval chains. Anyone can ship anything, and every engineer has a coding agent. If you have a product question, ask in #product.
And here is who actually decided the last five product changes, and where:
- Free plan capped at three projects. Two founding engineers, in a DM, after a customer call.
- No discounts on annual plans. The CEO and the head of sales, on a walk.
- SSO only on the Business plan. The same two engineers, in a group DM with the CEO.
- Webhook retries capped at five. Nobody. An agent picked the number and the pull request passed review.
- Welcome email removed. Three people, at lunch.
None of it reached #product. An engineer who joined last month asked there why their agent's change to the free plan was reverted. The answer was "we decided that a while ago."
An activist described this pattern more than fifty years ago, about a very different kind of group.
There is no such thing as a structureless group
Jo Freeman, writing as Joreen, first gave "The Tyranny of Structurelessness" as a talk in May 1970, at a conference in Beulah, Mississippi, called by the Southern Female Rights Union. Versions were published in The Second Wave in 1972, the Berkeley Journal of Sociology (vol. 17, 1972 to 1973), and Ms. in 1973. The text on Freeman's own website, quoted here, is her blend of those three.
Her subject was the leaderless, structureless groups the women's movement had adopted as a reaction against what she called "the over-structured society in which most of us found ourselves" and "the continual elitism of the Left." Her first claim is in the section "Formal and Informal Structures": "Contrary to what we would like to believe, there is no such thing as a structureless group." Any group that comes together for any length of time "will inevitably structure itself in some fashion."
Rejecting structure, she argues, only removes the visible kind. The idea of structurelessness "does not prevent the formation of informal structures, only formal ones." And the informal kind is hard to see from outside: "As long as the structure of the group is informal, the rules of how decisions are made are known only to a few and awareness of power is limited to those who know the rules."
Elites are friends, not conspiracies
In "The Nature of Elitism," Freeman is careful about who runs an unstructured group. "Elites are not conspiracies." They are "groups of friends who also happen to participate in the same political activities." What makes them powerful is that they talk to each other: "These friendship groups function as networks of communication outside any regular channels for such communication that may have been set up by a group."
She gives a test anyone can apply. "Once one knows with whom it is important to check before a decision is made, and whose approval is the stamp of acceptance, one knows who is running things."
She also doesn't say informal structure is the enemy. She says her criticism is not made in the belief that informal structures are "inevitably bad," but that they are "merely inevitable." The problem is what happens when they are the only structure. "Informal structures have no obligation to be responsible to the group at large. Their power was not given to them; it cannot be taken away." And people with full-time commitments elsewhere usually can't put in the hours it takes to join the inner circle. "That is why formal structures of decision making are a boon to the overworked person."
Flat teams with agents
The mapping that follows is ours, not Freeman's. She was writing about political groups, and a product team is not a movement. But the README makes the same promise her groups made, and the list underneath it shows the same result. The product decisions were made by a few people who talk to each other, in places the rest of the team doesn't see.
Coding agents sharpen this in two ways. They make it true that anyone can ship, which means more people and more agents acting on decisions they were never told about. And an agent is the most outside member a team has. It can't notice who listens to whom in a meeting, which was Freeman's way of spotting the informal structure. It sees the code and whatever was written down. The fourth item on the list is what happens when nobody decides at all: the agent's guess becomes the rule.
Our essay on the modern product development lifecycle proposes the opposite of "anyone can decide anything": "Material decisions go to a named owner, routine ones stay with the team." That is close to Freeman's first principle. We've written before about what happens when everyone can see a problem and nobody owns it. Freeman's case is different: most decisions do have someone making them, but the rules for who decides are known only to a few.
Making the structure explicit
Freeman's remedy is not a return to rigid hierarchy. "For everyone to have the opportunity to be involved in a given group and to participate in its activities the structure must be explicit, not implicit. The rules of decision-making must be open and available to everyone, and this can happen only if they are formalized."
Her closing section, "Principles of Democratic Structuring," lists seven principles. Two are directly about decisions. The first is "Delegation of specific authority to specific individuals for specific tasks by democratic procedures," because "Letting people assume jobs or tasks only by default means they are not dependably done." The sixth is "Diffusion of information to everyone as frequently as possible." She explains it in three words, "Information is power," and in the risk it guards against: "When an informal network spreads new ideas and information among themselves outside the group, they are already engaged in the process of forming an opinion."
Where Brief fits: writing down the structure you already have
Brief is the product strategy agent. The homepage says it "captures decisions where they happen, connects them into one graph, and acts on them." In Freeman's terms, it is a way to make the decisions a flat team already makes explicit, without adding the approval chain the README was written to avoid.
Each open question gets a named owner. Freeman's first principle is specific authority for specific people. In the Brief app, Propose turns an open question into a pending decision and can name Who should decide?, which records who the question belongs to. A question about plan limits no longer goes to whoever happens to be in the right DM. With the user's approval, an agent can record a pending decision too, and agents can call brief_list_pending_decisions to see what is waiting.
Decisions are written down with their reasons. Freeman's sixth principle is diffusion of information. Recording a decision requires both What was decided? and Why? before Record Decision will save it, and a decision can also carry Tags and a Re-evaluate when condition. "Free plans are capped at three projects, because customers on larger free workspaces weren't upgrading" turns a DM into something the new engineer could have read.
Decisions are read from the channels teams use. The homepage says Brief "reads decisions from Slack, Jira, Confluence, and GitLab, self-hosted included." A decision settled in a thread or a ticket comment can be recorded without someone retyping it into a wiki.
Agents check before they act. Coding agents set up with Brief search the recorded decisions before they start work, and ask Brief to check significant changes with brief_ask in check mode, which compares a planned change against existing decisions and flags conflicts. The new engineer's agent could have found the free plan limit before opening its pull request. People can run the same check with brief ask --mode check.
An agent can wait instead of guessing. When a decision is pending, an agent can hold. The homepage shows an agent asked to add per-seat pricing to the checkout API learning that D-241, the seat-based pricing decision, is pending, and replying: "Holding the pricing change until D-241 is decided." That is the alternative to the webhook retry limit: a question with an owner, not a number nobody chose.
Changes stay visible. When a decision changes, its History shows its status changes, so the next person can see that a rule moved and not just find it gone.
None of this removes the informal structure, and Freeman wouldn't expect it to. Writing a structure down, she wrote, does not destroy the informal one: "It usually doesn't." A decision made on a walk stays invisible until someone records it, and when nothing has been recorded, check mode finds no conflict and the agent goes ahead. What Brief changes is how far the informal structure can get without being seen. A decision made in a DM can become one that everyone, including the newest engineer and their agent, can find and question.
Freeman's test was knowing whom to check with before a decision is made. On your team, could a new engineer, or their coding agent, find that out without asking around?
Objections
What is "The Tyranny of Structurelessness"?
"The Tyranny of Structurelessness" is an essay by Jo Freeman, first given as a talk in 1970 under the name Joreen and published in several versions in 1972 and 1973. It argues that "there is no such thing as a structureless group": groups that reject formal structure still develop an informal one, in which a few people make decisions that others can't see or hold to account.
Who was Jo Freeman?
Jo Freeman is an American political scientist, writer and activist who was involved in the women's liberation movement in the late 1960s. She wrote "The Tyranny of Structurelessness" about the movement's leaderless groups, and publishes the essay on her own website.
What did Freeman mean by informal structure?
Freeman meant the networks of friends within a group who talk to each other and consult each other before decisions. She argued that in groups without formal structure, these networks become the real decision-makers, and that "the rules of how decisions are made are known only to a few."
How does the tyranny of structurelessness apply to product teams?
Teams that describe themselves as flat, where anyone can ship, still make product decisions, but often in direct messages, calls and side conversations among a few people. Engineers outside those conversations, and coding agents that only see code and written records, act without knowing what was decided or who decided it.
How does Brief help make a team's decision structure explicit?
Brief lets open questions be proposed as pending decisions that name who should decide, and records decisions with their reasons, including decisions it reads from Slack, Jira, Confluence and GitLab. Coding agents set up with Brief search recorded decisions before they start work and use check mode to flag conflicts in significant changes. Brief only knows the decisions a team records, so a decision that stays in a private conversation stays invisible.