Epistemic Territory in Interviews: Ask People About What Is Theirs to Know (2026)

Every interview question assigns the participant a position on a knowledge gradient -- someone who knows, or someone who is guessing -- and the answer comes back in the same grammar either way. Conversation analysts call this epistemics: the study of who has the right to know what, and how talk displays it. The practical rule for researchers is short. Ask people about what is theirs to know. A participant's own experience, their own last decision and their own workflow are in their territory. Other people's motives, their company's future behaviour and what users like you want are not -- and the participant will still answer, fluently and confidently, with nothing behind it.

This guide covers where the idea comes from, how to map the territory of each question before you ask it, and how to read the agreement tokens that tell you whether a participant is confirming something from their own access or just going along with yours.

The research behind epistemic territory

Territories of knowledge

The linguist Akio Kamio proposed in 1997 that speakers treat information as falling inside or outside their territory, and choose their wording accordingly: direct statements for what is theirs, hedged or reported forms for what is not. John Heritage built on this in two 2012 papers in Research on Language and Social Interaction (45(1)), Epistemics in action and The epistemic engine, arguing that information imbalances are what drive conversational sequences in the first place.

K+ and K-, status and stance

Heritage's key distinction is between two things that usually travel together and sometimes do not:

• Epistemic status is a person's actual access to a domain -- K+ if they know more, K- if they know less. A customer is K+ about how they used your product yesterday. You are K+ about what the product was designed to do.
• Epistemic stance is how a turn presents the speaker's knowledge. A question presents the asker as K-. A declarative presents them as K+. You use the export feature weekly? and You use the export feature weekly. ask for different kinds of response.

The research problem is the gap between them. A question can position a participant as K+ in a domain where their status is K-, and they will usually accept the position rather than disclaim it.

Agreement is not all the same

Heritage and Geoffrey Raymond's 2005 paper The terms of agreement (Social Psychology Quarterly, 68, 15-38) studied what happens after someone makes an assessment. Going first with an assessment carries a small claim to authority. The second speaker can simply agree, or can use practices that mark their agreement as independent -- based on their own access, not on the first speaker's lead. That difference is visible in the words, and it matters enormously when the first speaker is the interviewer.

Mapping the territory of a question

Before a question goes into a guide, ask whose territory the answer lives in.

The last four rows are not bad questions to want answered. They are bad questions to ask this person. The fix is either to find the person whose territory it is -- the economic buyer, the teammate, a sample of the population -- or to reframe the question into the participant's own territory: not what does your team think? but what has your team said to you about it, and when?

Grade findings by access

Once you think in territories, it becomes natural to tag each piece of evidence by how the participant came to know it:

1. Did -- first-hand experience (I exported it twice last week).
2. Saw -- witnessed (I watched my manager try and give up).
3. Was told -- reported (finance told me it was the price).
4. Think -- inferred or predicted (I guess most people would).

A finding supported mainly by level 4 answers from twelve participants is not twelve pieces of evidence about the thing. It is twelve pieces of evidence about what participants imagine. Reporting the access level alongside the quote is one of the cheapest rigor upgrades available to a research team.

When the interviewer goes first

Interviewers constantly make small assessments without meaning to: that sounds frustrating, so the setup was pretty slow?, a lot of people find that confusing. Each one positions the interviewer as having a view, and gives the participant something to agree with.

Three ways to say yes

Heritage and Raymond's work gives you a way to read the reply. Compare three responses to So setup was pretty slow?:

• Yeah. A minimal agreement. It accepts the interviewer's framing without adding access of its own. Weak evidence -- it may be politeness.
• It was slow, yes. A confirmation that repeats the claim in the participant's own words before agreeing. The participant is asserting the matter as theirs, not merely going along.
• Oh, it was terrible -- it took us three weeks. An upgraded, independent assessment with detail the interviewer did not supply. Strong evidence: the participant has shown their own access.

The strength of an agreement is readable from its form. A transcript full of yeah after leading assessments has less evidence in it than its word count suggests, because the participant has been ratifying the interviewer's view rather than reporting their own. The better fix is not better reading but better asking: How long did setup take? has no assessment in it to agree with.

The known-answer problem

The reverse trap is asking a question the participant knows you already know the answer to -- their plan tier, their company size, what they told the sales team last month. In ordinary conversation, a K- question about something the asker is plainly K+ on is odd, and participants respond to the oddness: they give short answers, they wonder what the real question is, or they treat it as a test.

Confirm instead of asking

Researchers who have looked at this in qualitative interviews recommend acknowledging it -- I know we covered this earlier, but could you tell me again... -- which resolves the oddness. A better fix is to not ask at all: state what you know and invite correction (You moved to the annual plan in March -- is that right?), which puts the participant in the K+ position on the part that is genuinely theirs: whether the record is accurate.

Designing a guide around territory

• Open in the participant's territory. Start with recent, first-hand, concrete behaviour. It is the easiest ground to be expert on and warms up detail for everything after it.
• Move out of it explicitly. When you need a second-hand view, say so: You may not know this directly, but what have you heard about why the decision was made? The permission to not know makes a don't know possible, and makes a real answer more trustworthy.
• Route population questions to populations. Would people pay for this? belongs in a survey of the people, not in one person's mouth.
• Remove your own assessments. Replace that sounds frustrating -- was it? with what was that like? so any assessment in the transcript is the participant's.
• Do not ask what you already know. Confirm it instead.

Common mistakes

• Treating fluency as access. Participants answer out-of-territory questions just as smoothly as in-territory ones.
• Counting agreement tokens as evidence. Yeah after your own assessment is ratification, not testimony.
• Asking one person about a population. A prediction about people like me is a guess with a sample size of one.
• Asking known-answer questions. They make the interview feel like a test and shorten the answers.
• Reporting quotes without access level. Did, saw, was told and think are four different grades of evidence.

How Koji applies epistemic question design

An interview guide can be written with territory in mind, but it is the live follow-up where epistemic drift happens -- the unscripted so that was frustrating? that plants an assessment. That is where an AI interviewer can be more disciplined than a tired human moderator on their eighth session.

• Consistent, non-assessing follow-ups. Koji's AI interviewer runs voice and text interviews with the same follow-up discipline in every session, asking what happened next? and how long did that take? rather than offering its own evaluations for participants to agree with.
• Probing for access. When a participant makes a claim about someone else, Koji's AI follow-up questions can ask how they know -- did you see that, or did someone tell you? -- so the access level ends up in the transcript.
• Context instead of known-answer questions. Putting what you already know about the audience into the study brief lets the AI interviewer confirm facts rather than quiz participants on them.
• Population questions go to structured items. Koji's structured questions support six types -- open_ended, scale, single_choice, multiple_choice, ranking and yes_no. A willingness-to-pay or preference question asked as a scale or single_choice item across the whole sample gives you a population answer instead of asking each person to guess one.
• Analysis that keeps the quote. Koji's automatic analysis links every theme to the underlying quotes, so you can check whether a finding rests on did answers or think answers before you present it.

Traditional survey platforms like SurveyMonkey or Qualtrics fix the wording but cannot follow up on a claim to ask how the participant knows it. Moderated interviews can, but depend on the moderator remembering to. Koji gives you the follow-up of an interview with the consistency of a survey, at a fraction of the time.

Frequently asked questions

What is epistemic territory in an interview?

It is the domain of knowledge a participant has a genuine right to speak about -- their own experiences, decisions and workflows. Questions inside that territory get answers backed by access. Questions outside it, such as other people's motives or predictions about a market, get answers in the same confident grammar with nothing behind them.

What do K+ and K- mean?

They are John Heritage's labels for relative epistemic status: K+ is the more knowledgeable party in a domain and K- the less knowledgeable. Questions present the asker as K- and the recipient as K+. Research problems arise when a question positions a participant as K+ in a domain where they are actually K-.

Why is yeah weak evidence in an interview?

Because a minimal agreement after the interviewer's own assessment ratifies the interviewer's view rather than reporting the participant's. Heritage and Raymond showed that speakers who have independent access tend to mark it -- by confirming in their own words or upgrading with new detail. Those forms are much stronger evidence than a bare yeah.

How do I avoid asking questions participants cannot answer?

Map the territory of each question before you ask it. If the answer belongs to someone else, find that person or reframe the question into what the participant has directly seen or been told. If it is a prediction about a population, ask the population with a structured question, as Koji's scale and single_choice types allow.

What is a known-answer question and why does it cause problems?

It is a question the participant knows the interviewer can already answer, such as their plan tier. It makes the exchange feel like a test and tends to produce short answers. State what you know and ask the participant to confirm or correct it instead.

Should I grade interview evidence by how the participant knows it?

Yes. Tagging quotes as did, saw, was told or think separates first-hand evidence from reports and guesses. A theme supported mostly by think answers is evidence about what participants imagine, not about what happened. With Koji, every theme links back to its quotes, which makes that check quick.

Related Resources

• Structured questions in AI interviews -- sending population questions to scale and single_choice items.
• Presupposition in interview questions -- what your question asserts before anyone answers.
• What participants mean but never say -- reading the answer side of the exchange.
• Backchannels and continuers in research interviews -- the listener's minimal tokens.
• Avoiding leading questions -- keeping your assessments out of the transcript.
• Expert interviews guide -- when the territory you need belongs to a specialist.