Key steps to making and using a Table of changes

Click here to download a template Table of Changes (coming soon)
  1. Collect feedback from target intervention users using one / a combination of the methods described above – if you don’t have much time, having discussions with PPI and other stakeholders is really important.
  2. Make notes during discussions and/or audio- or video- record interviews where possible.
  3. Use these notes and/or interview transcripts to draw out key positive and negative comments about specific elements / features/ sections of your intervention materials – record these in the first two columns of the table. Negative comments are very important for identifying things that may need changing - but recording positive comments allows the team to discuss whether or not to change items that some people like even if others do not.
  4. Discuss with members of your team (including PPI and stakeholders) the ways any identified problems might be solved – record these in the third column.
  5. The team can use the coding framework provided to help decide how important any proposed changes are and why they are important (recorded in the fourth column). It’s fine to use more than one code. Your team can adapt or replace this set of codes and/or the criteria for deciding how important a change is to reflect what you consider most important for your intervention.

Coding Framework

Code
Stands For
Means

IMP

Important
change

Important change. For example, it may be important because it is likely to impact engagement or behaviour change, or for practical, ethical or safety reasons.

EAS

Easy and uncontroversial

An easy and feasible change that doesn’t involve any major design changes. For example, a participant was unsure of a technical term, so you add a definition. 

REP

Repeatedly

This was said repeatedly, by more than one participant.

EXP

Experience  

This is supported by experience. Please specify what kind of experience, for example:

  1. PPIs agree this would be an appropriate change.
  2. Experts (e.g. clinicians on your development team) agree that this would be an appropriate change.
  3. Literature: This is supported by evidence in the literature.

NCON

Does not contradict

This does not contradict experience (e.g. evidence), or the Logic Model, or the Guiding Principles

NC

Not changed 

It was decided not to make this change. Please explain why (e.g. it would not be feasible). 

  1. Discuss with your team which of the agreed changes are essential and do-able within your resources, using the MoSCoW framework (Must do; Should do; Could do; Would Like to do, and record the final agreed changes in columns 5 and 6.
  2. Additional columns can be included depending on what your team needs to document or keep track of, e.g. the date/version number of changes made.