Research design as code
Treating survey instruments, discussion guides, codeframes and analysis as versioned, testable, reusable files.
Research design as code borrows from infrastructure as code. A questionnaire lives in a repository with a history. A discussion guide is a template with parameters. A codeframe has a changelog. Analysis is a script that reruns on new data.
It makes research repeatable and easier to improve instead of bespoke every time. Of all the engineering habits in the insights engineer role, it is the clearest.
Related terms
Part of the insights engineer definition hub.