Ask better questions about columns, rows, and meaning
Unit ID: AIT-M08-U01 Estimated active time: 15-20 minutes
The main idea
Good table prompts define what columns mean and what question matters.
A column heading is an abbreviation of a definition that lives in someone's head. Without it, any interpretation is a guess.
Why this matters
Most wrong analysis comes from a misunderstood column rather than from bad arithmetic. "Status" and "date" are the usual culprits.
Safe example
A table of registrations needs date, channel, status, and count definitions.
Is the date the registration date or the event date? Does "cancelled" still count as a registration? The answer changes every figure.
Better working habit
Explain column meaning before asking for interpretation.
One line per column. It is the fastest way to find out that two people in your team define a column differently.
What to watch for
Do not ask for insight before checking data meaning.
An insight built on a misread column is worse than no insight, because it is specific and memorable.
Mini practice
Write a table question brief with column definitions.
Then check your definitions against whoever produced the data.
Check yourself
Before moving on, answer:
- What does each column actually mean?
- Does anyone else define these columns differently?
- Which definition would change my answer if it were wrong?