A research crit is a place for researchers to come together and provide each other advice and feedback on their work.
The benefits of a crit are they:
- encourage you to work collaboratively, in the open
- allow for rapid sharing of experience and knowledge
- are a place to get constructive feedback on early work
- encourage researchers to learn from each other
How they started
In the Children & Families Digital portfolio at DfE, we have a group of experienced user researchers working across several projects and policy areas. We wanted to find ways to share our knowledge and experience with each other to improve the quality of our work. We also wanted to share more about what we’re working on across the portfolio.
Crits are a well-established part of the UCD professions at DfE, but they’re often design focused. We wanted to see how well they could work for the research process. One of our researchers, James Bolchover, had run research crits in a previous role and suggested we trial them.
We came together to agree the terms for the crit. This written agreement for how the crits should run is recorded at the top of the Lucid board we use to run the session. The agreement outlines that we:
- should be present in the session
- respect and listen to everyone’s opinion – seniority isn’t a factor
- support each other
- inspire each other
How we run them
We already have a fortnightly meetup together on Mondays. We agreed that once a month, we’d repurpose this for a crit.
We started off by asking a week before over slack if anyone had things to bring to crit the following week. Uptake was low and we did have to skip a few crits to start with. When we investigated, we found that a week in advance was too far to wait to crit a problem. People needed feedback on things they were solving in the moment.
We changed the process and now put a message on Slack on a Monday morning asking what people want to discuss that day. Doing it this way means people bring things that are top of mind for them, and we can give them timely feedback.
We’ve found recently that researchers are wanting crits more frequently, so we’re doing them almost fortnightly now.
Things we crit
We’ve covered many topics in our crits so far. The only criteria is that we don’t review anything that’s finished; it must be a work in progress. Some things we’ve looked at include:
- A plan for a stakeholder workshop
- A blog about sample bias
- How to do roleplay as a research method
- Ways to present a journey map
- Versions of our insight libraries and how best to present them
- Consent forms for research with young people
- A survey plan
Tools we use
One of our principles is that crits shouldn’t take a lot of extra work. James created a Lucid board for us with the template below. This template covers:
- Background of the project and what stage the research is at
- What is being critted (links, screenshots etc)
- Why we want a crit, including what the researcher is unsure about
- Two scales to understand how sensitive the researcher is feeling about the feedback, and how far in the process they are / how able they are to make changes
- A space for feedback from others
- After session thoughts and updates
The researcher fills out the relevant sections before the session, and we use the meeting to provide feedback and discuss it.
We also have follow up sessions for researchers to share and reflect on what they eventually did with the work.

What we’ve learned
We’ve found research crits to be a great way to share what we’re working on without adding too much time and burden onto our researchers.
They’ve improved our practice as we’ve consistently made changes because of each other's feedback. To name a few examples, we’ve restructured our insight library to make it easier to read with labels and tags, we implemented pre-briefing for participants trying out a role play method for the first time, and we rewrote an information sheet to reduce the text for young people.
This year we’re looking for new ways to improve how we share our research and skills with each other. If you have any ideas to share, get in touch at ella.beaumont@education.gov.uk.
Leave a comment