←
AI for Nonprofits
Aware · M11 · lesson 11 of 23 · queued
Preview — browse every lesson free. Enroll to mark lessons complete, open partner links and save your progress. Login & enroll →
📖
in this lesson

Inclusive Community Guidelines: Dominant-Culture Norms Hidden in Policies

10 min

Most nonprofit policies are written by the people who are already comfortable in the room, and they are written in good faith. That is exactly what makes the problem hard to see. A rule that reads as neutral to its author often carries the unstated habits of one cultural group, and it lands on everyone else as a barrier. Consider a line that appears in countless community handbooks: "We value professionalism and expect professional dress at events." Nothing in it names a group, yet it can exclude people whose culture or gender expression does not match a formal dress code, and it can exclude people who simply cannot afford the clothes. This lesson is about learning to see that pattern in your own guidelines, and then fixing it.

Why "Neutral" Rules Are Rarely Neutral

Every rule encodes an assumption about how people normally behave. When the people writing the rule share a background, their normal becomes the default, and anything outside it becomes a deviation that needs explaining. The rule does not say "behave like us"; it says "behave appropriately," and appropriate quietly means what the authors already do. Nobody has to intend exclusion for exclusion to happen. The test is not whether a policy was written with bad motives. The test is who has to do extra work to comply with it, and whether that extra work falls disproportionately on people who are already carrying more than their share.

This matters more in community settings than in most workplaces, because a nonprofit community is voluntary. People who feel out of place do not file a complaint; they stop coming. The guidelines that pushed them out go on looking reasonable, because everyone still present is comfortable with them. The absence of objections is not evidence that a policy works.

Where Hidden Bias Actually Lives

The examples below are ordinary policy language of the kind that appears in real community guidelines. For each one, look at the stated rule, the group it quietly disadvantages, and a rewrite that keeps whatever legitimate purpose the rule had while dropping the cultural assumption underneath it.

Language and Communication

A policy reading "We speak English in our spaces" excludes people who do not speak English and, just as importantly, people who speak it but are far more precise and confident in another language. Even a narrower version, requiring English only for official documents, pushes out anyone who struggles to read dense English prose, which in practice means the members least likely to complain about it. A better formulation names the working language while opening the door around it: provide translation where you can, hold meetings in English with interpreters available on request, and say explicitly that multilingual discussion is welcome. The purpose of the original rule, a shared language so meetings function, survives intact. What disappears is the implication that other languages do not belong in the room.

Time and Accessibility

"Everyone must attend events in person" is one of the most common exclusions in community work, and it operates on several groups at once: people with mobility disabilities, people without reliable transport, people whose childcare or eldercare obligations do not bend around your calendar, and people whose work schedules were never theirs to control. The rewrite is straightforward and mostly logistical: offer both in-person and virtual participation, and tell people to say what they need in order to take part. Note the second half of that. Offering a video link is a technical fix; inviting people to name their own requirements is what turns it into an inclusive policy, because you cannot anticipate every barrier and you do not need to if you have built a habit of asking.

Expertise and Authority

A rule that only people with formal credentials may speak or lead sounds like quality control. In effect it filters out people without formal education, who are disproportionately from low-income and marginalized communities, even when they hold deep expertise earned by living the thing your organization exists to address. It centers academic knowledge and treats lived experience as anecdote. The alternative is to say plainly that you value both formal expertise and lived experience, and that speakers may come from any background. If you are worried about competence, write a rule about competence: preparation, accuracy, willingness to answer questions. Credentials were always a proxy, and a poor one.

Professionalism and Style

"Use professional language. No slang, humor, or emotion" is where the assumption is most visible once you look for it. Professional, in practice, usually describes a narrow set of norms belonging to white, male, straight, wealthy culture. Cultures with different communication traditions, including call and response, storytelling, and open expressiveness, are read as unprofessional by a standard that never named itself. The emotion clause does something worse: in a community discussing racism, poverty, disability, or violence, it silences the people describing their own oppression while leaving untouched the people for whom the topic is abstract. A workable rewrite asks people to communicate in the ways that work for them, with the goal of being understood and being respectful. That is a real standard. It is simply a standard about outcomes rather than about style.

Appearance and Dress

Rules banning visible tattoos, piercings beyond earlobes, or dyed hair fall hardest on BIPOC communities, LGBTQ+ people, and working-class members, and they install one culture's aesthetic standards as though they were universal. The honest recommendation here is not a softer version of the rule. It is no appearance-based rules at all. The one exception is genuine safety, for instance jewelry in a workshop where machinery is involved, and safety exceptions should be written as safety rules, tied to the specific hazard, rather than as general standards of presentation. Absent a hazard, let people look however they want.

A Decision Framework Before You Write a Rule

The pattern across all five examples is that the rule bundled a legitimate purpose together with a cultural preference, and nobody separated them. The following five questions do that separation, and they work best applied to every line of a draft rather than to the document as a whole. Ask, first, whether the rule protects safety; if it does, keep it, and then check how it lands across different members. Ask, second, whether it advances the mission; if it does, keep it, with the same equity check applied.

The third question is the one that does the real work: does this rule simply enforce the cultural norms of the majority? If the honest answer is yes, question it. Name whose culture you are centering and who is excluded by centering it. The fourth question is procedural rather than substantive. Have marginalized people been part of deciding this? If not, pause before you finalize anything, because the previous three questions cannot be answered accurately by a group that shares one vantage point. The fifth is about the future: would you enforce this equally across everyone in the community? If you would not, you have written a biased rule regardless of how it is phrased, because unequal enforcement is the rule as it will actually exist.

Equity in Enforcement

A well-written rule can still be applied inequitably, and this is where most damage occurs in practice. The same behavior draws a friendly private word when it comes from someone inside the in-group, and immediate removal when it comes from an outsider. Nobody records a decision to treat the two cases differently, because nobody experiences it as a decision. It feels like context. From outside, it looks exactly like what it is.

Four practices make enforcement defensible, and they reinforce each other: a written record is what allows consistency to be checked rather than assumed, and hearing both sides is what stops a record from simply documenting the first account you received. The fourth practice is the one people resist, because it cuts against the instinct to protect the community's leaders, but the harm from a broken rule scales with the power behind it.

  • Document enforcement. Who did what, and what did you do about it? A written record is what prevents selective enforcement from going unnoticed.
  • Apply consistently. The same behavior draws the same consequence, whoever the person is.
  • Get multiple perspectives. Hear the other side before you act. Do not assume the first account is the whole account.
  • Consider power dynamics. Someone with power violating a rule is a more serious matter than someone without power doing the same thing.

Writing Guidelines That Work for Everyone

Fixing the language is the visible part of this work; the process that produces the language matters at least as much. Start by including diverse people in the writing itself, with input from members of different races, genders, abilities, class backgrounds, and ages, because each person notices barriers that others cannot see from where they stand. This is not a review step bolted onto a finished draft. A draft written by one group and reviewed by another arrives with its assumptions already load-bearing, and reviewers end up negotiating over sentences instead of over premises.

Then, for every rule that survives, ask whose norms it represents. If a rule expresses the habits of a single cultural group, that is the moment to test whether it is necessary at all. Make space for difference in the terms you use most: professionalism should accommodate different communication styles, respect should mean something that works across cultures rather than within one, and appropriate should include diverse expressions of identity. Be explicit about exceptions and accommodations rather than leaving them to be requested as favors, since an accommodation that must be asked for individually is a tax on the people who need it most. Finally, review and update on a regular cycle with community feedback, asking each time whether a rule is still necessary, whether it still excludes people, and what you have not yet noticed.

A Worked Example: Before and After

Here is a set of community guidelines of the sort many organizations already have in place. "Members must attend monthly meetings. Members should speak clearly and concisely. We expect professional dress. Disagreement is okay, but keep emotion out of discussions." Read quickly, it sounds mild, even generous. Read against the five questions above, every sentence has a problem. Mandatory monthly attendance assumes a body, a schedule, and a transport situation that not everyone has, which makes it both ableist and classist in effect. Speaking clearly and concisely rewards fluent English speakers and penalizes accents, translation lag, and communication styles that build context before making a point. Professional dress centers dominant cultural norms. Keeping emotion out silences marginalized members at precisely the moments when they are discussing their own lives.

The revision keeps the community's actual requirements and drops the cultural ones. "We meet monthly in person and via video. If you cannot attend a particular month, no problem, catch up when you can. We welcome all communication styles, including those that might be unfamiliar. Wear what makes you comfortable. When discussing difficult topics, emotion is natural and welcome. We ask that you aim to listen and respect each other." What changed is worth naming precisely, because the improvements are structural rather than decorative. Attendance became flexible and dual-mode. Communication style became explicitly plural, with unfamiliarity named as acceptable so that nobody has to guess. Appearance rules disappeared entirely. Emotion moved from prohibited to expected. And the respect baseline survived, because inclusivity did not require giving up a standard; it required stating the standard in terms of how people treat each other rather than how they present themselves.

Reviewing What You Already Have

Begin with the guidelines currently in force, read line by line with a diverse group in the room. For each line, ask who these rules might exclude, who benefits from them, and what is genuinely necessary as opposed to what is simply enforcing dominant norms. That third distinction is the whole exercise, and it is harder than it sounds, because necessity is exactly what a cultural norm feels like from the inside.

Then revise with input from the people most affected by the rules, who in most communities are the members from marginalized groups. That is not the same as circulating a draft for comment; it means those members shape what the rule is for before anyone phrases it. Expect some rules to get shorter, some to get more specific about their purpose, and a few to disappear because nobody could say what they were protecting.

Anti-Patterns to Avoid

  • Writing the guidelines first and consulting afterward. A finished draft carries its assumptions in its structure. Review at that stage becomes a negotiation over wording, and the premises never get examined.
  • Treating "professional" as a definition rather than a preference. The word feels precise and is not. Whenever it appears in a draft, replace it with the specific behavior you actually want.
  • Keeping appearance rules because they have always been there. If you cannot name the hazard a rule prevents, it is not a safety rule, and it should not survive the review.
  • Building accommodations as individual favors. Requiring people to request an exception every time places the cost of your policy on the members least able to absorb it. Build the flexibility into the rule.
  • Banning emotion in discussions about people's own lives. This reads as decorum and functions as silencing, and it silences the members with the most at stake in the conversation.
  • Enforcing informally for insiders and formally for everyone else. Undocumented enforcement always drifts this way, because familiarity reads as context and unfamiliarity reads as a violation.
  • Treating a lack of complaints as validation. People excluded by a policy usually leave quietly. Silence tells you nothing about whether the rules are working.

Practice Prompts

  • Take your current community guidelines and mark every instance of the words professional, appropriate, respectful, and clearly. For each one, write the specific behavior you actually want in its place.
  • Run the five decision-framework questions against every rule in your document, writing your answers down rather than doing it in your head. Note which rules survive question three intact.
  • Draft the accommodations paragraph for your guidelines so that flexibility is stated as the norm rather than as something to be requested.
  • Write your enforcement record template: what gets logged when a rule is applied, who logs it, and who reviews the log for patterns.
  • Rewrite your attendance expectation to work for someone with a disability, someone with caregiving obligations, and someone working a shift pattern they do not control.
  • List the people you would need in the room to review your guidelines credibly, then note which of them are already in your community and which relationships you have not built yet.
  • Take the before-and-after example in this lesson and repeat the exercise with a paragraph from your own handbook, naming the problem with each sentence before you rewrite it.

Reflection

Think about the last person who drifted out of your community without explanation. You probably attributed it to a schedule change, a house move, or a loss of interest, and you may well be right. But sit with the alternative for a moment: which of your rules would have been most costly for that person to keep following, and how would you have known if it was the reason? Most organizations have no mechanism for hearing that answer, which is why guidelines can exclude people for years while everyone still present reports satisfaction with them. The question worth carrying out of this lesson is not whether your policies are biased. It is how you would find out if they were.

Glossary

  • Dominant-culture norm. A behavioral expectation belonging to the majority or most powerful cultural group in a setting, which is treated as neutral or universal rather than as one group's practice among others.
  • Hidden bias in policy. Exclusion produced by a rule that names no group and was written without discriminatory intent, but whose burden falls unevenly on particular members.
  • Lived expertise. Knowledge earned through direct experience of the conditions an organization addresses, as distinct from knowledge certified by formal education or credentials.
  • Selective enforcement. Applying the same rule differently depending on who broke it, typically leniently for members of the in-group and strictly for outsiders.
  • Accommodation. A modification to a standard expectation that allows someone to participate fully. Built into a policy it is inclusion; granted case by case on request it becomes a favor.
  • Equity check. The step of asking, for a rule you intend to keep, how its burden is distributed across different members before you finalize it.
  • Community guidelines. The stated expectations governing how members behave with each other in a nonprofit's shared spaces, whether physical, virtual, or both.

This lesson assumes you already have a document to review. If you do not, start with How to Write a Code of Conduct for Your Nonprofit Community, and use Community Guidelines vs Code of Conduct vs Terms of Service: Differences to work out which of your policies should carry which rules, since inclusive language matters most in the document members actually read. The enforcement half of this lesson is treated at length in Enforcement Without Ego: How to Handle Code of Conduct Violations, which is the natural next step once your rules are written well. For online spaces, where dress and attendance give way to a different set of unstated norms, see Digital Conduct Policies for Nonprofit Staff and Board. The accessibility material behind the attendance and participation examples is developed in Accessible Programs and Communications: Implementation Guide. Two further lessons address the conditions that make this work stick: Anti-Bias Training That Actually Changes Behavior and Community Representation in Nonprofit Leadership: Practical Pathways, the latter because who writes the rules is ultimately a leadership question.

Closing

Inclusive guidelines are not achieved by adding a diversity statement to the top of an existing document. They are achieved by taking each rule apart, finding the legitimate purpose inside it, and rewriting the rule to serve that purpose without the cultural packaging it arrived in. Often the result is a more specific document, because vague words like professional were doing work that specific words now do openly. The organizations that get this right treat their guidelines as a living document reviewed with the people it governs, rather than a settled artifact that changes only when something goes wrong. Start with the line in your handbook you would least want to defend to a new member, and work outward from there.

Key Takeaways

  • A rule written without discriminatory intent can still exclude, because the majority's habits become the unstated default and everything else becomes a deviation.
  • Bias hides in five recurring places: language requirements, in-person attendance, credential requirements, definitions of professionalism, and appearance rules.
  • Before keeping any rule, test it: does it protect safety, does it advance the mission, does it only enforce majority norms, were marginalized people part of the decision, and would you enforce it equally?
  • Appearance rules should be dropped entirely unless a specific safety hazard justifies them, and then written as safety rules tied to that hazard.
  • Well-written rules still fail if enforcement is selective. Document decisions, apply consequences consistently, hear both sides, and weigh the power of the person involved.
  • Build accommodations into the policy rather than granting them on request, so flexibility is not a favor the excluded have to ask for.
  • Review guidelines on a cycle with the people most affected by them, and remember that the absence of complaints is not evidence the rules are working.

Frequently Asked Questions

Is it okay to have any appearance rules? Only where there is a safety reason. In healthcare or food service settings, certain standards may genuinely be necessary, and those should be written as what they are: hazard-specific requirements. In most nonprofits no such reason exists, and the rule is doing cultural work rather than protective work. If you cannot state the hazard a given appearance rule prevents, drop it entirely rather than softening the wording.

What if people from the majority culture feel excluded by inclusive guidelines? Good inclusive guidelines do not exclude majority-culture members. They stop treating dominant-culture norms as universal, which is a different thing. People from dominant groups usually have considerable flexibility already, because they are accustomed to their norms being accepted everywhere they go. Guidelines that no longer center those norms will feel different, and that unfamiliarity is worth acknowledging rather than dismissing, but it is not exclusion.

How do we balance inclusivity with having any standards at all? By separating standards from conformity. You can require that people treat each other with respect and that nobody harasses anyone, without requiring that everyone speak, dress, and communicate in a particular style. The first kind of standard protects people; the second enforces norms. Most difficult cases resolve once you ask which of the two a given rule is doing.

Should we have different rules for different groups? No. The same rules should apply to everyone. What you should recognize is that equal rules can produce unequal impact, which is the entire premise of this lesson. The response is not a second rulebook; it is building flexibility and accommodations into the single set of rules, so that people starting from different positions can all meet the same standard.

Who should be in the room when we review our guidelines? Members from a range of races, genders, abilities, class backgrounds, and ages, and specifically people who are most affected by the rules under review. If your current membership cannot supply that range, treat the gap as the first finding of the review, because a set of guidelines shaped by one vantage point will keep reproducing the community that produced it.