Questions before papers
Start with a question someone needs to answer, then link the papers, evaluations, data, and models that could help.
Discussion proposal · Updated October 2026
Should each field team keep a short list of research themes and pivotal questions it thinks we should focus on? For each one, we could say who might use the answer and what research would help.
This is a proposal for discussion. Suggestions on the idea and the examples below are welcome.
David Reinstein uses AI assistants to draft and revise this page. Codex reviewed the Hypothes.is comments and revised the page at his request on . David decides what to take forward.
Each team could maintain a few questions or research Clusters of research questions, approaches, and environments. where better evidence could change important decisions. Members could also maintain their own prioritization. The team list could record their different views.
Start with a question someone needs to answer, then link the papers, evaluations, data, and models that could help.
Members can rank items differently, suggest alternatives, and explain their reasons. Keep those differences in the record.
Someone could take responsibility for each active item and set a date to revisit it. When the team drops an item, keep a short explanation in a folded or filtered view.
Teams already discuss papers, assess priorities, vote on evaluations, and consider who could manage them. A short list of broader questions might help with some of that work, especially when choosing which research to look for next.
A single table could hold the team shortlist, members' suggestions, ideas from existing prioritization work, and items the team has set aside.
| Question or cluster | Who might use the answer? | Why it may matter | Current disagreement | Promising next work | Owner and review |
|---|---|---|---|---|---|
| Short, decision-relevant formulation | Named types of funders, policymakers, researchers, or advocates | A concise path from better evidence to better decisions | What informed people disagree about, including minority views | Evaluation, synthesis, replication, modeling, new data, or experiment | Human owner Review every 6–12 months |
These examples draw on papers The Unjournal has discussed or prioritized and on our Pivotal Questions work. What would your team add, change, or drop?
AI can suggest questions, find related research, and help identify disagreements. Members should decide which suggestions deserve a place on the list.
Ask members for their own questions before showing AI suggestions. That gives us a better chance of hearing ideas the prepared material missed.
Label suggestions from AI or our databases with their source and date. Keep them in a separate view until members have discussed them.
A person should check, rewrite, and take responsibility for each item the team adds. Preserve members' judgments and record later changes.
Here's one possible schedule. Teams could spend most of a meeting on papers awaiting decisions, or give more time to broader research questions when that seems useful.
Adjust the timings and sections to suit the meeting. The extra 20 minutes are optional for anyone who wants to stay.
We could try this with two or three active teams. Ask members for their own suggestions, then bring in existing Unjournal prioritization material. Aim for at most five to seven items per team and check after one or two meetings whether the list helped.
A page is easy to share and comment on while we work out whether the idea is useful. If teams want to keep their lists, we could put them in Coda or connect them to the existing research-prioritization database.