Published on Development Impact

Weekly links November 10: how to properly pre-register, trade and inequality, surprising findings and more…

This page in:
  • Data Colada on how to properly pre-register a study: “it may be helpful to imagine a skeptical reader of your paper. Let’s call him Leif. Imagine that Leif is worried that p-hacking might creep into the analyses of even the best-intentioned researchers. The job of your preregistration is to set Leif’s mind at ease. This means identifying all of the ways you could have p-hacked – choosing a different sample size, or a different exclusion rule, or a different dependent variable, or a different set of controls/covariates, or a different set of conditions to compare, or a different data transformation – and including all of the information that lets Leif know that these decisions were set in stone in advance”…but on the other hand “it should contain only the information that is essential for the task at hand… We have seen many preregistrations that are just too long… you don’t need to say in the preregistration everything that you will say in the paper. A hard-to-read preregistration makes preregistration less effective…” – comes with a nice example table of what bad specifications and good specifications look like.

Authors

David McKenzie

Lead Economist, Development Research Group, World Bank

Join the Conversation

The content of this field is kept private and will not be shown publicly
Remaining characters: 1000