Question sorting
SQL is powerful. It is not always the right tool.
Some questions are better answered in a spreadsheet. Some are better answered in a notebook. Some are better answered in a phone call. Data can tell you what happened in a table. It cannot tell you what a coalition partner intended, how a volunteer felt, or what a community member needs unless someone collected that information responsibly.
Use SQL when the work is large, repeatable, structured, and easier to answer from a table than by hand.
Use a spreadsheet when the task is small, one-time, and easy to see on one screen.
Use a conversation when the question is about meaning, intent, trust, or relationship.
Examples
- Which 30 names should I put on tonight's call list? A spreadsheet may work. It is small and one-off.
- Which zip codes had the most volunteer signups last quarter? SQL is better. The report is repeatable and may cover many months of data.
- How many of our 240,000 contacts are missing phone numbers? SQL is better. The dataset is too large to inspect manually.
- What does my coalition partner think about this event? A conversation is better. A database cannot answer a question about intent.
- How many event RSVPs came from each source last quarter? SQL is better. It creates a repeatable summary across many records.
SQL is also one of the core skills in data analysis. Analysts use it to retrieve data, clean and prepare data, run summary calculations, and create datasets behind reports and dashboards. It is not the only data skill. A well-rounded analyst also builds skill in statistics, visualization, tools like Python/R/Tableau/Power BI/Looker Studio, and critical thinking.
For civic tech and organizing work, critical thinking matters. SQL can answer a question. It cannot decide whether the question is fair, strategic, or useful.
Learner action
Write one question your team asks often. Then decide:
- Does this need a spreadsheet, a database query, both, or a conversation?
- What kind of records would help answer it?
- Why might SQL help?
SQL is not always the right tool. Some questions are still better in a spreadsheet, in a notebook, or in a phone call. This activity helps you see when SQL is worth the lift.
| Question | Best tool | Why |
|---|---|---|
| Which 30 names should I put on tonight's call list? | Spreadsheet | Small, one-off, fits on a screen. |
| Which zip codes had the most volunteer signups last quarter? | SQL on a database | Large, repeatable, multiple months of data. |
| How many of our 240k contacts are missing phone numbers? | SQL on a database | The dataset is too big to inspect manually. |
| What does my coalition partner think about this event? | A conversation | Data cannot answer questions about intent. |
| How many event RSVPs came from each source last quarter? | SQL on a database | Repeatable summary across many records. |
Your turn
- Write down one question your team asks often.
- Decide whether that question needs a spreadsheet, a database query, or both.
- Name what kind of records would help answer it.
- Write one sentence explaining why SQL might help.
You will reuse this question in every remaining module. Pick one you actually care about.
When is SQL most worth the lift?
Which scenario most clearly benefits from SQL over a spreadsheet?
Different questions become different queries. The question “how many of our voters live in Fulton County?” becomes a SELECT with a WHERE. Translate it below.
Action: Submit the knowledge check, then continue to the case theory checkpoint.