Epistemic Injustice: When a Voice Is Denied the Status of Testimony

Epigraph

“In their capacity as a knower.”

Miranda Fricker, Epistemic Injustice (2007), Introduction, p. 1. Referring to a person being wronged specifically in their capacity as a knower and contributor to knowledge. Introduction on the author's website.

What This Article Is About

Picture a hypothetical scene from the corporate terrarium: a rank-and-file employee timidly reports that the server is on the verge of exploding. Management nods politely, stares sagely at the ceiling, and calmly returns to their critical games of solitaire. Exactly one hour later, a charismatic senior executive saunters into the boardroom, recites the exact same observation verbatim—and suddenly everyone scrambles to save the company, wildly applauding his visionary brilliance. Nobody gagged the first poor soul; he was generously permitted to emit vocal sound waves. However, he was flatly denied the status of a legitimate source of factual knowledge.

Such a delightful glitch in recognition can be a textbook case of epistemic injustice: some people are taken at their word even when spouting unadulterated nonsense, others have their coherent, logical findings written off as background static, and still others are simply scrubbed from collective reasoning altogether. This concept does not claim that every disagreement you encounter is a mortal wound or cosmic discrimination, nor does it demand that everyone blindly swallow every tall tale they hear. Rather, it simply helps distinguish honest, reasoned doubt from blunt, dogmatic skepticism bolted directly to your job title, age, or appearance. The ritualistic corporate refrain “I hear you” holds actual meaning only when your facts are admitted for verification, rather than merely used to vent steam into the void.

I. A Voice Can Sound and Still Remain Excluded

The formal right to open your mouth and the genuine possibility of being perceived as a reliable informant are two drastically different things. A meeting can look like a shining paragon of democratic transparency: rules are respected, timers beep, and everyone is allotted an equitable two minutes on the floor. In practice, however, one person’s input is logged as high-value strategic insight from the get-go, a second person’s words are instantly dismissed as “emotional instability,” and a third is listened to like the hum of an office air conditioner. You have the optics of equality, with none of the substance.

Miranda Fricker coined the term testimonial injustice for situations where a speaker’s credibility is deflated specifically due to prejudice. The pivotal nuance lies in the underlying grounds: if doubt is warranted by the quality of the message, that doubt alone does not make the encounter unjust; conversely, even an erroneous report can still be met with prejudice. The second foundational concept is hermeneutical injustice, which captures unequal conditions in understanding and making sense of social experience. Fricker, Introduction, pp. 1 and 4–7.

In our hypothetical setup, the message content remained identical, yet the audience’s reaction pulled a complete 180-degree flip purely based on the speaker. The root cause remains unproven: perhaps the veteran executive boasts a twenty-year track record of impeccable forecasts, whereas our nervous junior dropped the production database two days ago. But when completely identical reports are routinely trashed merely because they were brought in by someone of the “wrong” gender, age, or background, we are looking at a fundamental malfunction of the recognition apparatus itself.

The damage inflicted is two-fold: the organization misses a critical alarm about an impending crash, and the individual learns that, to this group, they are a non-entity. Even if their flagged facts end up saving the enterprise, credit and participation in repairs may still remain to the tailored suit who parroted them. Restoring justice does not begin with patronizing pats on the back; it starts with an unvarnished audit trail: who sounded the alarm first, when, what did they explicitly say, and on what evidence was it based? If they uttered nonsense, log it as such. What matters is that conclusions hinge on verifiable merit, not on a tribal monopoly on being considered the smartest in the room.

II. Doubt Has Every Right to Exist

Without mutual trust, social life becomes extremely difficult, yet total gullibility is a one-way ticket to a cult or a Ponzi scheme. People get muddled, recycle watercooler gossip, and make honest blunders. Demanding identical, unconditional deference to every whim does not cure injustice; it murders common sense.

In a hypothetical illustration, consider one person insisting that a piece of machinery is a death trap because “a neighbor’s cousin heard something,” though they cannot name the model. Another walks in with thermal logs, incident registries, and calibrated diagnostic metrics. Granting vastly different levels of trust to these two accounts is not just sensible—it is the only rational approach. It is a matter of evidentiary caliber, not personal contempt: the first signal can be clarified and evaluated without ignoring a potential hazard simply because of its crude delivery, yet without elevating it to absolute gospel either.

It is an entirely different story when a rigorous technical audit is instantly rebuffed with: “The author is far too young, and that jacket does not look serious.” Youth might suggest a modest tenure, but it does not repeal the laws of physics or erase calibrated logs. A wardrobe choice does not falsify a spreadsheet.

Separate personal affinity from credibility assessments. You can genuinely adore your eccentric brother-in-law while maintaining healthy skepticism regarding his Flat Earth theories. Conversely, you might find an obsessive colleague utterly unbearable while acknowledging that their ledger balances to the cent. Conflate the two, and every request to double-check the math feels like an existential insult, while a dry acceptance of data feels like an unwanted declaration of love. Healthy skepticism is transparent: “I need the figures for last month.” Prejudiced skepticism constantly moves the goalposts: provide the numbers, and they demand notarized affidavits; bring the affidavits, and they ask for an astrologer’s endorsement. Catching yourself is straightforward: ask yourself what specific evidence could ever change your mind. If the answer is “nothing,” congratulations—you are not vetting data; you are merely rationalizing your snobbery.

III. Manner of Speech Does Not Determine Quality of Information

A booming baritone, a tailored shirt, and charismatic hand gestures are brilliant at selling half-baked nonsense, but they do not make it true. On the flip side, if an informant stammers, takes long pauses, or fumbles grammar, a listener may struggle to follow, yet this does not rule out precise observation—especially when something personally important is at stake.

Envision two disputants in a hypothetical friction. The first attempts to complain about chronic interruptions, growing flustered, repetitive, and visibly distressed. The second smoothly rattles off polished corporate scripts, beaming with measured smiles and poise. The surrounding room instinctively rallies behind the polished speaker. Yet fluency may reflect public-speaking practice, while awkwardness may signal an agonizing search for words to describe an experience no one has ever trained them to package into a sleek deck.

This is no excuse to treat disjointed babble as divine revelation. Incoherent speech is objectively taxing to parse, and florid jargon frequently papers over logical voids. Yet difficulty in perception is not evidence of fraud; cognitive friction does not equal falsity. A competent listener does not shrug off the interaction (“Whatever, this makes no sense”), but helps map the chronology step by step and paraphrases what they heard, offering the speaker room to correct the record.

The hypocrisy peaks when unshakeable composure is demanded exclusively from those with less leverage. When a director screeches in a boardroom, it is hailed as “decisive, passionate leadership”; when an employee tears up over unfair treatment, it is dismissed as “an unstable personality—remove them.” Double standards must be countered with concrete facts, not abstract hand-wringing. Make the mental effort: “This is uncomfortable to hear” does not translate to “this is nonsense,” just as “they sound eloquent” does not mean “they are right.” An informant is not a delivery driver evaluated by the neatness of their cardboard box, but a participant in establishing reality.

IV. Sometimes Shared Language Is Missing

Hermeneutics sounds lofty, but at its core, it is simply the craft of interpretation and mutual comprehension. Hermeneutical injustice does not mean forgetting a fancy dictionary term; it describes a structural condition where an entire group is systematically deprived of equitable resources to articulate their experience because the dominant vocabulary was drafted without them. When critical concepts are absent from the broader culture, it becomes agonizingly difficult not only to communicate the situation to a peer, but even to clarify it to oneself.

Miranda Fricker highlights the philosophical example of a woman subjected to sexual harassment in a culture that has not yet coined that critical term. It is a foundational illustration of the problem’s architecture, demonstrating how the absence of a shared concept renders a concrete reality socially invisible. Fricker, pp. 1 and 6–7.

Take a hypothetical workplace example. An employee tries to explain that their manager bombards them with messages at midnight, expecting immediate replies. The corporate policy handbook only recognizes “official shift,” “approved overtime,” and “informal team camaraderie.” This subtle, domestic encroachment matches none of these neat pigeonholes. The employee stumbles over the word “overtime,” only to be met with the standard rebuttal: “How can it be overtime when you were lounging on your couch?” The conversation terminates; the problem is swept under the rug.

That said, casually minting a flashy neologism will not instantly reorder reality. An overextended term can blur trivial friction with serious malfeasance. Every label must rest on granular facts: Who demanded the reply? Was termination implied? What was the frequency? A new label should facilitate rigorous scrutiny, not bypass an investigation.

The crucial line sits between a speaker struggling to find words and the condescending assumption that their halting speech reflects an empty claim. The former invites patient dialog; the latter arrogantly discards a human account. Allow someone to articulate facts through plain descriptive sentences without demanding an instant fit into predefined operational jargon. Understanding often crystallizes long before an official definition lands in the corporate policy manual.

V. A Concept Clarifies and Can Hijack Experience

A precise term is a powerful asset: it organizes chaos, exposes patterns, and sharpens discourse. Yet drop your guard for a moment, and that very term morphs into a conceptual straitjacket, dictating to reality how it ought to behave. A prefabricated label gets slapped across a forehead, obliterating all practical nuance.

Imagine a hypothetical enthusiast who reads an introductory article on epistemic injustice and experiences an epiphany: “Aha! That explains why Monday standups annoy me!” A useful spark, perhaps. But if, starting today, every pushback from colleagues is denounced as an “act of epistemic violence,” what we have is straightforward deafness. A concept engineered to clear a path for factual verification has been repurposed as an impenetrable bunker against critique.

The sensible sequence is straightforward: dissect mechanics first, affix labels second. Was your credibility actually deflated? On what basis? Who had access to the data? Can the skepticism be accounted for by baseline logic rather than a sinister plot? Answering these practical questions yields far more utility than a semantic battle to secure the most dramatic label. A workflow can be corrected without waiting for total triumph on the theoretical front.

Exercise restraint: by no means is every grievance an epistemic injustice. An unpaid bonus may be an employment issue, a missed deadline an operational problem, and rudeness in the parking lot is plain bad manners. An epistemic dimension is implicated specifically when the capacity to engage in knowledge practices is curtailed: when your reports are discounted without review, when questions are barred, or when you are penalized for attempting to explain what occurred.

Fricker dissects the development of this framework and its intersections with direct and indirect discrimination in Evolving Concepts of Epistemic Injustice. It serves as an excellent reminder not to turn the concept into a catch-all receptacle for life’s daily frustrations. Fricker, 2017, opening pages. Conceptual clarity protects the claimant: when a friction is articulated with granular precision, it becomes far harder for an administration to dodge procedural repairs.

VI. Silence Has Diverse Causes

When a person sits through a meeting with their mouth shut, it is hardly proof of an empty mind. They might lack domain context, they might be utterly exhausted, they might be conserving energy, or they may have recognized that, in this particular office circus, speaking up is a futile expenditure of oxygen. An identical exterior of silence can mask diametrically opposed motives, and slapping a uniform label across it is a hallmark of shallow thinking.

In Silence and Institutional Prejudice, Fricker draws a meticulous distinction between enforced silencing and the attentive, respectful silence of a mindful listener. She also underscores that an innocent mistake regarding competence does not necessarily constitute an injustice. However, the absence of malice is not an automatic pass: prejudice can distort an evaluation without conscious deceit. Fricker, pp. 1–5 of the author’s PDF.

For a hypothetical team lead, this presents two reflections. First, who gets consistently bypassed during standups even though they hold the primary server logs? Second, what occurs when that person is finally handed the floor? If their observations are ignored in the minutes, they may naturally curtail future input. Leadership then solemnly logs in the review: “Employee lacks initiative and engagement.”

At the same time, extracting participation through coercion is equally wrongheaded. The entitlement to be heard carries no guarantee of being correct, and it is inseparable from the voluntary right to withhold information. An individual retains the prerogative to remain silent even in the most benign environment. An invitation to speak must be unambiguous and safe—free of retaliation upon refusal and devoid of intrusive attempts to pry into personal reflections.

For the listener, silence is a vital discipline: allow the speaker to conclude, hold back unprompted solutions, and stop superimposing your personal scripts onto their account. Yet avoid misuse: perpetually declaring “I am holding a safe space for your voice” in lieu of concrete operational decisions is just cowardly buck-passing. Once an issue is identified, silence must yield to workflow: what enters the queue, who oversees verification, and when the findings will be shared.

VII. A System Can Exclude Without a Harsh Word

Discrimination does not need to shout down corridors; it operates seamlessly within sleek digital protocols. An online portal accepts uploads in only one hyper-specific format, meetings are slated when half the field staff is on duty, and a request for reconsideration requires paperwork the applicant was never granted access to obtain. Bureaucrats smile courteously and follow guidelines to the letter, while substantive facts drop straight into the digital shredder.

Consider a hypothetical support portal for banking or civic services. To report a lost form, the interface insists on a sixteen-digit tracking code that was never issued to the user in the first place. Error; submission blocked. Screaming intentional malice or claiming proven discrimination right here is premature, because a defective form does not, in itself, prove discrimination. What is clearly present, however, is an absurd procedural dead-end: the system gates the bug report behind a prerequisite that the bug itself makes impossible to fulfill.

A measured post-mortem is far more productive than hysteria. One can audit the submission requirements, provide alternative conduits, and review which user cohorts were systematically screened out by this awkward barrier. If data demonstrates that a rule consistently sidelined a distinct group, discussions around systemic issues gain concrete footing.

Fricker’s examination of institutional prejudice shifts the lens from isolated individual biases to organizational apparatuses. We adopt this insight as a philosophical analogy for service and interface design, not as an indictment of a specific institution. Silence and Institutional Prejudice.

Dumping full liability for a broken architecture onto the user is the height of cynicism. Training people on “how to properly format a complaint” makes sense only if the intake process corresponds with reality. Otherwise, workshops merely train users to tolerate absurdity. Bureaucracies must acknowledge their margins; otherwise, a flat “not found in our records” morphs into “the problem does not exist,” and the lack of a digital receipt becomes an ironclad alibi for total inaction.

VIII. Redress Requires an Audit Trail

Muttering “Oops, our bad, we missed your email” is a polite concession, but entirely insufficient to remedy the situation. The real work involves reviewing what bad choices were executed in the dark, what decisions must be rolled back, and how to reinstate the affected party as an active reviewer. Apologies decoupled from protocol updates are cheap rhetoric that preserves obsolete dysfunction.

Recall our hypothetical corporate drama. The executive repeated someone else’s solution, the server was fixed, and everyone rejoiced. But if the matter rests there, the originator has once again been reduced to an unpaid prompter whose contributions are claimed by others. Meaningful rectification demands direct operational steps: logging the original author’s name in the formal record, archiving their raw calculations, and inviting them to inspect the patch if they wish to do so.

Grandiose public displays of contrition are unnecessary. It is sufficient to update the record, cite the contributor, and establish a firm standard for routing incoming incident reports. The scale of the remedy should mirror the scale of the failure: if an oversight halted production, convene a formal post-mortem; if it was an ignored comment in a morning huddle, a verbal attribution on the record will do.

Dispense with hollow melodrama. Even with improved procedures, an organization may never fully recover lost time or forfeited opportunities. Candid dialog demarcates the boundaries: this part has been corrected, that loss cannot be undone, and these are the operational steps moving forward. Crucially, no one is entitled to force automatic forgiveness or demand pledges of reconciliation.

All corrective measures must leave an inspectable trail. Who handles reports now? Have review criteria changed? Can an employee bring bad news without facing professional backlash? A single elegant gesture does not guarantee an institution’s recovery, but launching a company-wide witch hunt over a minor hiccup is equally short-sighted. Redress is accomplished only when the person’s functional agency is restored: the ability to submit a fact, receive a reasoned appraisal, and challenge decisions through formal channels.

IX. A Listener Can Also Not Know

Being an effective listener requires an honest assessment of one's own intellectual boundaries. You may stare blankly, unable to grasp a concern simply because you lack familiarity with a specialized software stack or domain-specific jargon. Ignorance on its own does not make you malicious. But encountering the wall of your own understanding brings a fork in the road: you can ask questions, pause to investigate, or pompously proclaim: “If I have never heard of this, it must be irrelevant.”

A hypothetical executive hears an engineer mention undocumented backend failovers for the first time. They could snap: “That is not in our official architectural diagram—stop hallucinating.” Or they could engage their mind: “Walk me through what that step entails.” The latter is not an immediate surrender to the engineer’s claim; it is simply an opportunity to stress-test an abstract presentation deck against reality.

Admitting a gap in knowledge is uncomfortable, particularly when a business card boasts a senior title. Yet blind faith in the infallibility of standard protocols defends status at the expense of empirical contact. A mature leader does not hesitate to state: “I am accountable for this project, but I lack the technical details of this incident; walk me through the mechanics.”

In the second chapter of On Liberty, John Stuart Mill argued that one can deeply understand a position only by actively engaging the strongest counterarguments from opponents, rather than jousting with caricatures. This stands as a classical argument for open discussion, aligning directly with our inquiry. Mill, Chapter II.

Naturally, patience has structural limits. No human being is obligated to serve as a walking archive for every grievance on earth. You are within your rights to say: “This falls outside my expertise; let us route this to the technical review team.” But that handoff must not be a bureaucratic shell game designed to send the person down an endless rabbit hole. Designate a specific reviewer and transfer the gathered files. Otherwise, the listener’s lack of knowledge becomes an endurance test for an informant trapped in a loop of restarting their account from zero without any prospect of resolution.

X. Fairness to an Account Does Not Preordain a Winner

Two people can offer passionately sincere yet mutually irreconcilable descriptions of the exact same incident. Respecting each party’s right to be heard does not compel an oversight body to validate both conflicting accounts as absolute truth. A sound procedure preserves space for dispute, distinguishing contradiction, viewpoint, and unresolved unknowns.

In a hypothetical workplace stalemate, one employee swears their optimization proposal was tossed out unread, while their manager maintains that the rationale was laid out clearly during a team recap. Check the project management board; check the emails. If there is no written log, you are left with two competing personal accounts. Declaring a victor based on who screams louder or who was preemptively designated as the default victim is a total breakdown of procedural integrity. It is entirely valid to conclude: “The specific cause of the breakdown remains undetermined, but starting tomorrow, all rejections require written notes.”

Furthermore, procedural fairness extends equally to the accused. The fashionable label of “prejudice” must not be wielded as a club to silence a counter-explanation. The respondent may possess hard documentation and essential context of which the aggrieved party was genuinely unaware. Hearing out the other party does not mean sanctioning tyranny; it means carrying out an honest assessment.

That said, never confuse parity of formal standing with parity of operational leverage. A director commands records, legal counsel, and organizational authority, whereas a subordinate possesses only raw initiative. Demanding that the latter “present stamped proof” in such circumstances borders on mockery. Weigh asymmetric access to institutional records: demanding documentation from someone barred from the archives is bad-faith gatekeeping.

The finding of an inquiry may be decidedly modest: the flaw was identified and patched, but whether it stemmed from bias or routine carelessness remains unresolved. That is a thoroughly constructive, honest outcome. It permits forward momentum without inventing conspiratorial narratives. Human dignity is not safeguarded by guaranteed victories, but by the robust right to an impartial review of facts. That is far more dependable than relying on the fickle indulgence of a superior assessing how deferentially you served up your findings.

XI. The Right to Know Entails the Right to Reshape Shared Explanations

In a functioning work environment, an individual is not merely a telemetry sensor gathering raw inputs, like an outdoor thermometer. They retain the right to raise challenging questions, critique established assumptions, and propose alternative interpretations of events. When leadership demotes staff to silent suppliers of data points while hoarding the monopoly on strategic synthesis, participation is truncated by half.

In a hypothetical evaluation, a team compiles a pile of customer complaints and brightly deduces: “Our user base is just unsophisticated and unaccustomed to our advanced interface.” An attentive QA engineer raises a hand: “Look at step three in the documentation—the submit button is physically unclickable because the layout broke.” If management patronizingly dismisses them (“Stick to logging clicks and leave the product philosophy to us”), the organization risks overlooking a critical defect. The engineer might be mistaken, but their substantive objection warrants review, not a condescending reprimand.

No one suggests that every junior recruit must master macroeconomic forecasting. Competencies vary. But no title grants a license to discard an argument before its structural link to the issue is vetted. On occasion, a single grounded observation from the field completely dismantles an expensive model crafted by detached theorists.

This is precisely why Fricker’s framing of a person as a “knower” hits the mark. It centers on the ability to alter not merely the values in an intake sheet, but the interpretive lens through which the community understands its operations. No one is promised that their perspective will be carved into stone. But the process must afford it an avenue of consideration and evaluate the rationale. Listening means giving a message an operational path to review, not rubber-stamping it without question.

Returning to our broken machinery: in a healthy environment, a line employee can do more than timidly report “the unit stalled”; they can point out: “You are ignoring the ambient temperature under which these faults occur.” At that moment, a private voice transforms into substantive testimony and a valid counter-inquiry. Fairness converges with utility: the contributor claims their rightful seat at the interpretive table, while the organization gains an opportunity to notice blind spots shielded by corporate hubris.

XII. Trust Can Be Restored Without Demanding Amnesia

When policies are overhauled with corporate fanfare, expecting employees to instantly swoon with gratitude is naive. An individual whose reports were consistently dismissed will eye new initiatives with justifiable caution. This is neither spite nor sabotage: past experience provides legitimate grounds to doubt management rhetoric, and the glossy new charters have yet to be tested by fire.

Suppose a department lead boldly proclaims: “From now on, all concept submissions will explicitly log contributor names!” A burned team member prudently keeps quiet. Demanding unreserved enthusiasm as a “loyalty check” is outright bullying. The dependable course involves tiny, verifiable iterations: take one concrete bottleneck, record authorship, assess the data, retain the artifact, and make the resolution legible. Trust rebuilds through track records, not through aspirational slogans pasted on office walls.

Simultaneously, no one should be made to grovel indefinitely to beg for emotional absolution. The purpose of process rehabilitation is to restore functional operations, not conduct group therapy. Agree on clear ground rules, explicit delivery timelines, and civilized ways to conclude disputes. If an individual finds it emotionally unsustainable to continue on a specific project, the prerogative to decline discussion remains theirs, and no one may frame that refusal as an admission of fault.

Do not confuse functional operational alignment with personal forgiveness. It is entirely possible to collaborate effectively with someone whose past conduct you have not emotionally excused. You can respect an updated operational system while choosing to transfer to a different unit. You can trust your immediate supervisor while maintaining a healthy wariness toward the broader corporate machine. These are personal determinations; the philosophy of just communication offers no mandatory prescriptions for emotional closure.

Authentic progress is evidenced by actions. An incident report receives a reference number, authorship is retained, rejections are justified with granular reasoning, and counterarguments are met with empirical facts. When this cadence repeats without failure, people acquire rational grounds to revise their expectations. Trust cannot be extorted through intimidation or bought with syrupy promises. It crystallizes slowly wherever an individual voice is recognized as genuine testimony and actually influences shared decisions.

What This Means in Practice

If you wish, begin addressing the problem by examining a single overlooked incident. Record the dry facts: who spoke, what information was conveyed, and what specific reaction followed. Avoid psychoanalyzing peers or immediately branding counterparts as closeted bigots. Simply document which precise data points were shelved.
Strictly demarcate three fundamental questions: Was the report itself accurate? Were there sufficient grounds for credibility? Did the review procedure operate fairly? The answers may diverge completely. A speaker could present baseless claims yet face overtly biased treatment; alternatively, they could bring an exceptional insight while the supervisor’s motives for burying it remain unknown. Isolating these questions prevents witch hunts.
If you are in the role of the listener: ask for one concrete example, afford the speaker room to correct your phrasing, and clearly state what facts would lead you to revise your verdict. Run a self-check: do you demand an identical burden of proof from favored peers? If the meaning escapes you, be specific: “These three points are unclear to me,” rather than delivering the dismissive verdict: “This is all purely subjective.”
If you are in the role of the informant: target procedural mechanics directly. Speak clearly: “Please verify the calculations in the attached file,” “Clarify why my colleague’s report was approved while mine was rejected using identical metrics,” or “Your categorization omits this critical step.” You are under no obligation to bare your soul or defend a dissertation on your life to resolve a standard work ticket, and you retain the full right to withdraw from dialog if you feel threatened.
For joint efforts, always preserve a paper or digital audit trail: the initial request, the evaluation stages, and the formal response. Correct the intake architecture itself, not merely the polite wording in chat channels. An acknowledged fact, an uncovered injustice, and an actual systemic reform represent three distinct outcomes. Attentive listening allows them to be separated and work to continue, without demanding performative enthusiasm or forced forgiveness from anyone.

Key Quote

“He who knows only his own side of the case, knows little of that.”

John Stuart Mill, On Liberty (1859), Chapter II. A foundational argument regarding the necessity of engaging counterarguments; it does not mandate accepting every report without verification. Text.

Connections Between Traditions

Comparison	Parallels and Boundaries
Fricker: Testimonial Injustice ↔ Epistemology of Testimony	Grounds of credibility are central. Not every mistaken doubt constitutes prejudice.
Hermeneutical Injustice ↔ Collaborative Articulation of Experience	Shared vocabulary shapes understanding. The absence of a term does not, by itself, prove unequal participation.
Mill: Strong Counterarguments ↔ Fair Hearing	Both approaches insist on directly engaging opposing arguments. A liberal defense of open debate does not fully account for social prejudice.
Fricker: Institutions ↔ Interface and Intake Design	Procedures can restrict the transfer of knowledge. A hypothetical technical scenario does not confirm discrimination in any specific service.
Attentive Silence ↔ Speaker’s Voluntary Non-Disclosure	Both preserve spaces of agency. A listener’s silence and an enforced silencing of a speaker perform opposite functions.

Primary Sources and Research

Miranda Fricker. Epistemic Injustice: Power and the Ethics of Knowing (2007), Introduction. Read: pp. 1, 4–7; the two core concepts, prejudice, epigraph context. The entire volume is not claimed as read.
Miranda Fricker. Evolving Concepts of Epistemic Injustice (2017). Read: initial pages of the author’s PDF; conceptual refinement and intersection with discrimination.
Miranda Fricker. Silence and Institutional Prejudice. Read: pp. 1–5 of the author’s manuscript; types of silence, innocent competence errors, the institutional dimension. The historical criminal case study is not referenced further.
John Stuart Mill. On Liberty (1859), Chapter II. Read: section on engaging counterarguments; key quote and comparison of traditions of debate.

About the Authors

Andrey Zarinsh is an author and the founder of the United Wisdom project. He explores themes of internal transformation, the unity of traditions, intercultural dialogue, and modern spiritual discipline. Instagram: @andrey.zarinsh.

Maria Evilkut is a co-author at United Wisdom. Alongside research, she focuses on testing these ideas in practice, observing how principles of unity and mutual understanding operate in everyday life between people and across cultures. Instagram: @ilkutki.