Every codebook question will meet a document it wasn't written for.
Every codebook question will meet a document it wasn’t written for.
Ask a clear question of a document and you get an answer. Ask an unclear one and you get a guess.
A cell comes out right when three things work together:
- The document says it plainly.
- The codebook asks it clearly.
- The reader attends to both.
When any one of the three falls short, careful readers can defend different answers. That is ambiguity, and it is the fundamental problem of this work.
Lots of projects fail here. The ambiguities were there. Nobody saw them.
The good news: readers who disagree show you where the ambiguity is. Data Mint runs several readers, so the disagreement is visible.
Resolving them is craft. The reward is real: you understand your question better than you did before. Your measurement gets sharper. Every downstream answer gets stronger. What follows is mostly about this craft.