6. When not to evaluate

View

Not all OAD projects need to or even should be evaluated, for example projects that

  • are not clearly defined (replicable project)
  • are too complex: evaluate replicable components, not complex combinations.
  • have no aims to change observable outcomes (e.g. projects aimed to improve inspiration, which is not an observable outcome)
  • test no clear hypothesis

 Evaluation is a low priority when the results of efforts are easily observable. It is also a low priority when a project is conducting basic scientific research, developing but not distributing products or tools, or creating new data sets or analyses. In such cases, a projects’ self-reported progress data and existing protocols (such as for clinical trials) provide sufficient feedback for decision making and improvement.


 < BACK     NEXT

Last modified: Sunday, 1 July 2018, 3:35 PM