On visibility, recourse, governance, and why product decisions quietly determine who gets to act, decide, and be heard
Product teams usually describe their work in terms of usefulness. We solve problems. We reduce friction. We help users get from here to there. All of that can be true while something else is happening at the same time: the product is reorganizing who has leverage over whom.
Who gets seen? Who gets ranked? Who can message first? Who can moderate? Who can assign work? Who can refuse? Who can appeal? Who can disappear? These are not only policy questions. They are product questions.
Once software becomes part of how people coordinate, transact, learn, work, date, create, or speak publicly, it stops being only a tool. It becomes part of the institutional structure through which power is exercised.
Some of this is obvious once you see it. A marketplace platform mediates between buyers and sellers, which means it gets to decide ranking, pricing logic, recourse, identity verification, and reputation rules. A workplace tool gives some people dashboards on others. A social platform chooses what is visible, what counts as acceptable speech, and what forms of coordination are easy or hard.
None of those choices are neutral. They determine who can act with confidence and who has to guess. They determine who gets legibility and who gets opacity. They determine whether a user can contest a decision or simply live with it.
This is one reason I find sociological thinking so useful in product. It makes it harder to pretend that defaults, permissions, ranking systems, and governance tools are merely UX details. They are part of the product's power architecture.
The standard vocabulary of product management is better at describing utility than authority. It talks about needs, value, flows, and engagement. It is less comfortable talking about control, dependency, recourse, asymmetry, or domination.
That gap matters because products often feel most successful precisely when their power becomes least visible. A recommendation system can feel convenient while quietly deciding who gets discovered. An admin dashboard can feel efficient while intensifying surveillance. A moderation policy can feel procedural while defining what kinds of people or politics are easiest to marginalize.
If the product only gets discussed as a tool for solving user pain, those governance effects remain undertheorized until there is crisis, backlash, or regulation.
When I look at a product through this lens, I want to know who can do what to whom, and with what recourse. Who can set the terms? Who can be overruled? Who can coordinate collectively? Who can challenge a ranking, a removal, a deactivation, a score, or a price? If the answer is "almost nobody," then the product may be much more centralized than its marketing suggests.
I also want to know what forms of dependence the product creates. Does it make one group structurally reliant on another group or on the platform itself? Does it lower switching costs or deepen lock-in? Does it let weaker actors gain leverage, or does it mostly make already-powerful actors more efficient?
These questions do not replace usability work. They sit underneath it. A system can be usable and still be organizing power in brittle or unjust ways.
Value Flow Is Product Strategy, Not Just Ethics asks who creates value, who captures it, and who bears the cost. This essay is related but distinct. It is less about economic routing and more about governance: who gets voice, visibility, recourse, and control inside the system itself.
Together, those lenses make products look much less innocent. Not malicious, necessarily. Just more consequential. Once a product becomes part of social infrastructure, it is no longer only solving for convenience. It is organizing a social order.