What You Assume vs. What They Live

What you assume vs. what they live. Making inclusion work - a newsletter by Ainsleee Hooper
Picture of Ainslee Hooper

Ainslee Hooper

Applied Anthropologist | Disability Inclusion Consultant | Helping DEI, P&C, HR and Community Development folk remove invisible barriers in communities and workplaces | Living and working on Wadawurrung land. ♿️🧠

Share this post

A manager is looking at a job candidate’s file. The candidate has disclosed a disability. The manager wants to do right by them, so she starts guessing: quieter workspace, maybe. Flexible hours. A standing desk, if it comes up.

She never asks. She doesn’t mean any harm by it — she thinks she’s already helping. She’s about to be wrong in a way she won’t find out about for months, if ever.

Anthropology has a word for exactly this mistake, and it’s one of the oldest and most useful ideas in the discipline: the gap between etic and emic.

Etic is the outsider’s account — categories imposed from outside, built from what an external observer’s own framework predicts should matter. Emic is the insider’s account — the meaning the person actually living the experience gives it, on their own terms. A linguist named Kenneth Pike coined the pair in the 1950s, borrowing the logic from phonetic versus phonemic sounds; anthropologists kept the distinction because it names something that happens constantly and is remarkably easy to miss happening.

The manager’s guesses are pure etic. Reasonable-sounding, generic, built from “what disability usually needs” rather than from this person. The emic account might not resemble any of them — not a quieter room, but permission to leave a meeting early without explaining why. You cannot get there from the file. You can only get there by asking, and actually listening to the answer.

Four places this quietly wrecks disability inclusion work

Nearly three-quarters of Australian workers who requested a workplace adjustment were rejected, according to Deloitte’s 2024 global survey — even when the adjustment cost the employer nothing. The most common reason given was that the request was “unreasonable.” Ask what standard that reasonableness was measured against, and the honest answer is usually: nobody wrote one down. That’s an etic judgement dressed as a rule — an outside sense of what should be enough, applied to a request nobody actually measured against what the task requires.

Compliance checklists have the same blind spot built in. A ramp gets installed. Signage gets updated. The box is ticked — etic, top to bottom. I worked in a building for twenty years that I never once managed to open the front door of myself. Whoever signed off on that building’s access compliance never had to ask the only question that actually mattered to me: can you get in. Etic was satisfied the whole time. The emic answer was no, for two decades.

Here’s the sharper version of the same failure: an organisation runs a proper consultation. Real questions, careful listening, genuine emic data walks in the door. Then someone translates it back into the categories the budget and the policy already know how to process — because that’s what the system can act on — and what comes out the other end often isn’t what was actually said. The organisation didn’t fail to listen. It listened, then quietly overwrote what it heard.

And “just ask people” doesn’t fix any of this on its own, because a careless question can still smuggle an etic frame in through the back door. “What accommodations do you need?” already assumes the answer will be a named, formal adjustment — when the real answer might be “ask my colleague to stop making that joke,” which doesn’t fit the category at all. Ask once at intake and call it done, and you’ve made the same mistake the manager made with the file: treating a single guess as if it generalises forever.

What the question actually needs to sound like

The difference between an etic-coded question and one that actually opens the door for an emic answer usually isn’t subtle once you hear it side by side.

“What accommodations do you need?” already assumes the answer is a named, official adjustment. “What’s the hardest part of a normal day here, and where exactly does it get hard?” assumes nothing — it leaves room for an answer that never occurred to whoever wrote the form.

“Is this adjustment reasonable?” asks whether a request clears someone else’s unstated bar. “What would need to be true for this task to actually work for you?” asks the only question that was ever going to produce a real answer, because it starts from the task and the person instead of from a policy category.

“Do you have any accessibility concerns about the building?” invites a yes/no that closes the conversation. “Walk me through what it’s actually like to get from the car park to your desk” invites an account — the door you couldn’t manage yourself, the workaround nobody official ever knew about, the twenty years nobody asked.

None of these take longer to ask. They just don’t assume the shape of the answer before the person has said it.

If you hold positional or budget authority

Look at your own adjustment-request form. If it only has boxes for named, standard adjustments, it cannot capture an emic account that falls outside them — add an open field, and actually read what people write in it.

Pull any request from the last year that got called “unreasonable.” Find out what standard that word was measured against, and whether it was ever stated to the person who asked.

If you run consultations, follow the trail from what people said to what got decided. The moment lived accounts get re-coded into the categories your systems already know how to process is the moment emic data quietly becomes etic again — and it deserves to be someone’s explicit job to catch.

If you don’t hold that authority

If you’re the one being asked what you need, you don’t owe anyone a tidy category. “I need X” doesn’t have to match a form field to be true, and saying so out loud is useful information, not an inconvenience.

If you’re supporting someone else through this, watch for their account getting smoothed into something neater on its way up the chain. “That’s not quite what they said” is a small sentence that keeps the real answer from disappearing before it reaches whoever’s deciding.

Back to the file

The manager finishes her guesses, feeling like she’s done the thoughtful thing. She has no way of knowing the candidate would have told her, in about ten seconds, that none of it was what she actually needed — because nobody asked, and a closed file doesn’t volunteer that information on its own.

That’s the whole problem in one sentence: an etic guess and an emic fact can look identical from the outside, right up until the moment someone checks.

Over to you

Where have you seen a reasonable-sounding outside guess stand in for someone’s actual account of their own experience? Naming that it happened is worth doing, even without naming where.


Sources

Pike, K. (1954), Language in Relation to a Unified Theory of the Structure of Human Behavior (origin of the etic/emic distinction)

Harris, M. (1976), “History and Significance of the Emic/Etic Distinction,” Annual Review of Anthropology

Deloitte, “Disability Inclusion @ Work” global survey (2024)


Work With Me

If your organisation’s consultation or adjustment processes are gathering genuine emic accounts and still translating them into the same etic categories on the way to a decision, that’s a structural gap worth naming before it costs you the trust of the people you asked.

Ainslee Hooper Consulting works with organisations on:

  • DIAP development and review
  • Governance and committee reviews
  • Co-design and stakeholder engagement
  • Disability Inclusion Outcomes Framework™
  • The Inclusion Lens

📅 Book a free intro conversation 📋 Workplace Disability Inclusion Assessment (free resource) 🧭 Framework Strategy Call

Making Inclusion Work is written by Ainslee Hooper, disability inclusion consultant and applied anthropologist. Remove invisible barriers. Reduce the risk of ableism.

Book a free call

More to explore