Tensions facing the analyst

Transcript

1. Tension Generating simplified and clear stories of change Vs Vs Vs Faithfulness to the primary data Reflecting complexity of the data Inductive coding of the data Pulling in extra contextual data from other source Deductive coding from the project’s Theory of Change (ToC) Confirming expected theory of change Vs Exploring unexpected drivers of change Accommodating challenges to the findings (e.g. pushback from the project staff) Vs Presenting the findings as you originally intend to There is no right or wrong side to this table, these are challenges which will need to be agreed upon and resolved between the analyst and the commissioning team, but the analyst can sometimes feel pulled in different directions. The next slide shows some possible responses...
2. Back-checking with the field research team where you have concerns about the primary data, or you have been challenged on some statements. Facilitate internal and external peer review and audit, sharing access to your coding file. Code data blind first (inductively) then repeat with reference to the ToC (deductively) if you are concerned about introducing bias into the analysis process. Response Engage in post-analysis discussion of provisional findings (with commissioner, project staff, respondents and/or other intended beneficiaries). Tension Generating simplified and clear stories of change Vs Vs Vs Faithfulness to the primary data Reflecting complexity of the data Inductive coding of the data Pulling in extra contextual data from other source Deductive coding from the project’s Theory of Change (ToC) Confirming expected theory of change Vs Exploring unexpected drivers of change Accommodating challenges to the findings (e.g. pushback from the project staff) Vs Presenting the findings as you originally intend to