Why this distinction matters and where confusion arises
The phrase people and things points to a fundamental grammar and ethics question: how we speak about humans compared to objects. In everyday professional and public communication, treating people as people and things as things supports clarity, dignity, and precision. This evergreen explainer defines key terms, outlines long standing grammatical conventions, and describes practical guidelines you can apply whenever you write or speak. It does not chase passing style fads, but instead focuses on durable principles that remain useful across contexts.
Person-first versus thing-focused language: definitions
Person-first language emphasizes the person before any noun or role, reflecting that individuals are more than a label or function. Many communities prefer this structure to affirm dignity. Conversely, thing-focused language centers the object, process, or concept, which is appropriate when describing artifacts, systems, or nonhuman entities. Grasping when each pattern is suitable is essential to produce clear, audience-aware communication without slipping into ambiguity or disrespect.
Pronouns for people, nouns for things
For humans, standard pronoun sets include she/her/hers, he/him/his, and they/them/their, with some individuals using neopronouns such as xe/xem/xyr. Using correct pronouns is a baseline respectful practice in both speaking and writing. For things, rely on nouns and demonstratives (this, that, these, those) or neutral it when context requires, while avoiding applying gendered pronouns to inanimate objects unless metaphorical intent is clear and deliberate.
Possession and relationships
Use possessive forms carefully: for people, this commonly means apostrophe + s or possessive pronouns (her project, their idea). For things, standard possessive patterns apply (the car’s engine, the system’s output). Mixing these structures in ways that blur human and nonhuman references can create confusion or imply inappropriate equivalence, so maintain consistent patterns within each sentence and across longer documents.
Concrete and abstract things: specificity supports clarity
When referring to things, decide whether you mean concrete objects or abstract concepts such as policies, data, or results. Concrete nouns typically allow straightforward reference (the device, the file), while abstract nouns may need brief contextual anchors (the framework we adopted, the dataset from 2023). Clearly labeling each reference helps readers track who is acting, what is being acted upon, and how responsibilities align.
Examples of clear structures
- The researcher submitted the report on time.
- They reviewed the dataset, and the tool produced the expected output.
- The committee approved the guideline after public feedback.
- We implemented the update, and stakeholders confirmed its usefulness.
- Each participant gave informed consent before the session began.
Cultural, legal, and professional considerations
Regional norms, industry practices, and evolving social expectations shape how people and things are referenced. Some organizations standardize phrasing around person-first patterns to align with inclusion policies, while technical fields may rely on concise, object centered phrasing for precision. Legal and regulatory texts often specify required language, such as rights holders, data subjects, or patients, underscoring that word choice can affect interpretation and compliance.
Quick reference: applying the distinction
| Attribute | Verified Detail | Source Type |
|---|---|---|
| People-first phrasing | Prioritizes person before role or label | Style guides, equity frameworks |
| Thing-focused phrasing | Centers object, system, or concept | Technical documentation standards |
| Pronoun use | Match personal pronouns to stated identity | Diversity and inclusion policies |
| Possession patterns | Maintain consistent structure within context | Grammar references |
| Audience expectations | Align tone and specificity with community norms | Professional communication research |
When the line blurs: ambiguous or metaphorical uses
In literature, marketing, or rhetoric, writers sometimes describe things as people or people as things to create vivid imagery or emphasize agency. In technical writing, avoid mixing these modes unless the intent is deliberately figurative and the context makes that clear. For factual reporting, policy, or service documentation, keep the distinction firm: describe human experiences with human centered language, and reserve thing-focused terms for artifacts, datasets, and processes.
Common pitfalls and how to avoid them
Overgeneralizing it for people, unintentionally implying ownership by phrasing, or inconsistently shifting between person-first and thing-focused patterns can erode trust. To prevent this, audit your drafts for ambiguous references, test them with sample readers from your target audience, and refine phrasing so that each noun and pronoun has a clear, appropriate antecedent. If you are unsure which pattern your audience expects, consult established guidelines from recognized equity, disability, or industry specific bodies, and document your standards for future teams.
Building durable standards for your organization
Create simple internal rules that distinguish people and things across channels, and pair them with training examples. Use templates for common documents, style notes in editing tools, and checklists for final review. By defining roles, pronouns, and reference patterns in advance, teams reduce ambiguity, increase efficiency, and demonstrate consistent respect for audiences, whether the context is policy, research, technical manuals, or public facing content.