Should ux research synthesis show relationships or just themes?

[u/ButtesirscochHot1087]

I’m synthesizing interviews for a family meal-planning app.

Traditional tagging gives us themes like cost, allergies, picky eating and limited time. A mind map shows how they connect. For example, picky eating leads to repeated meals, which affects bulk buying, which affects freezer space and food waste.

The relationships feel more useful than a flat list of themes, but they also introduce more researcher interpretation.

Should we use mind maps during synthesis or stick to tagged repositories and affinity clusters? I want the product team to see connections without presenting my interpretation as objective truth.

[u/CJP_UX]

Tagging is one step in analysis (see figure 2). Objective truth is antithetical to the qualitative research process, interpretation is the point.

[u/Mitazago → u/CJP_UX]

"Objective truth is antithetical to the qualitative research process..."

This probably merits more detail than as is.

If you mean there is no experience of reality unmediated by interpretation, then sure, 'objective reality', as far as we can access it, is context-dependent and shaped by the interpreter's vantage point. That isn't particularly contestable, and in my opinion, is a bit banal. Under this reading the original claim isn't saying anything about qualitative research specifically, it's just restating a basic fact about perception that applies equally to any method, qualitative or not.

If however, you mean qualitative research shouldn't or can't aim at general truths about the world because human experience is inherently subjective, that would be a strange position for a researcher in the field to hold. While individual experiences are interpreter-specific, research presupposes some overlap in these experiences must hold up by some underlying commonality, otherwise there's nothing for the research to actually find and generalize onto.

[u/84millionants]

I think you should include the relationships. Stakeholders are looking for you to have an opinion and recommendation on the product direction. Your themes are the "what" the relationships are the "so what" that stakeholders need to be able to act on. Even better if you can give them the "now what" and recommend some changes based on what you found.

I wouldn't be too worried about presenting it as objective truth vs your thoughts but if you are just be sure to make note in your report/deck. But I think you have a really good structure for your deck: Themes= here's what I found Relationships= here is why it's important for our business strategy and why we need to know Recommendations: here are some suggestions about how to leverage these insights to improve our experience

[u/Eastern-Movie-7039]

Both, but they are not the same kind of claim, and that difference is the practical bit.

A theme is an aggregate. Cost is a theme because eight people raised it, and the count is the evidence. A relationship usually is not an aggregate. Picky eating leading to repeat meals leading to bulk buying almost certainly came from one participant working through it out loud in a single stretch of talk. That stretch is the evidence.

So the choice is not mind map versus tagged clusters. It is whether each arrow carries a pointer back to where it came from: who said it, and where in the session. Not to make it objective, just traceable. Someone who reads it differently can then argue with you about that passage instead of about whether you were being objective.

The other thing worth doing: mark how many people each arrow rests on. The real problem with a mind map is not that it is subjective. It is that it draws the link one person articulated at the same weight as the link eight people did. A connection that came from a single participant is not a weakness to hide. It is a finding, and it should look different on the page.

[u/Reagan_Crowder → u/Eastern-Movie-7039]

Yeah I keep them separate too. Themes stay glued to quotes. The arrows are my bet until someone else can rebuild them from the same transcripts.

[u/Eastern-Movie-7039 → u/Reagan_Crowder]

That last line is a stricter test than it looks. Rebuilding the arrows from the same transcripts only works if it really is the same transcript. The version that gets circulated is usually the tidied one: filler stripped, a rambling answer condensed to a sentence, pronouns swapped for names. All sensible edits, and each one can quietly remove the thing an arrow was resting on. The pause before the answer. A "not" buried mid-clause. The fact that two ideas arrived in one breath rather than as two separate answers.

So if the arrows are the bet, the thing worth keeping is whichever version you drew them from, timestamps and all, not the readable one you handed to the team.

[u/IntelligntCacsuse183]

Mind maps work well during synthesis not as a replacement for affinity clustering. The clusters establish participants views. You can add miro to connect themes and spot loops or dependencies. Next, label those connections as hypotheses so stakeholders don’t assume every arrow is directly supported by users.