My two cents

When it comes to analysing user or experts interviews, I like these approaches

1. Line-by-line coding: in a sort of simplified Grounded Theory way, I analyse the text one line after the other and tag each part with the learnings that come out of it using a tool like Dovetail or Notion. That takes a shitload of time but also leads to the most in-depth learning. If you are interested in learning this approach in depth, the book Doing Qualitative Research by David Silverman is a gold mine.

2. Multiple summaries: Right after the interview, I summarise the top 3-5 elements that stick with me. After a few interviews, I summarise what sticks for me about these interviews. At the end of the process, I already have everything in the summaries, and if I have a doubt, I can go back to my notes. That's definitely quicker than the line-by-line coding approach.

3. Workshop format: the quickest way to do it, which I want to use more in the future, is to do the interviews in a workshop-like format with silence and solo work, and then group work where participants summarise the key topics they have in common. Basically, my role here is to create a set of exercises that make people do my analysis work together. That's the fastest way of doing it, but the danger of "groupthink" is higher, even if the process starts with solo work.

More Service Design questions and answers like this one

Check out all the questions about the field, user and desk research side of Service Design.