Mixed methods data analysis that is reproducible: analysis at collection on one record — where NVivo, MAXQDA, and Dedoose leave the join to you.
Mixed-methods data analysis triangulates the quantitative number and the qualitative narrative so each checks and explains the other. Sopact makes that possible on the Connected Record: the number and the open-text explaining it kept on one participant record under a persistent Contact ID, so triangulation is a query over one record rather than a reconciliation across two exports.
The discipline is well understood; the tooling fights it. Analysts pull numbers from a stats package and themes from a coding tool, then spend the analysis phase trying to line them up by ID, so triangulation becomes a manual merge that runs late and is hard to present as a defensible picture. The insight that a number and a narrative agree, or disagree, arrives after it could have mattered.
Key takeaways
Triangulation assumes you can hold the number and the narrative side by side, but most stacks capture them in separate systems with no shared key. The quantitative results live in a stats file and the coded themes in another, so lining them up by participant is an export-and-merge step that happens once, late, and rarely repeats as new data arrives.
Sopact is record-centric: the narrative is read on arrival against a codebook and tied to the same persistent ID as the numbers, so triangulation is a standing query over the Connected Record. Compare the two families on qualitative vs quantitative, or see scenarios on mixed-methods research examples.
Mixed-methods work usually spans SPSS, Excel, or Qualtrics for the quantitative side and NVivo, ATLAS.ti, MAXQDA, or Dedoose for the qualitative side. Each is strong on its half, and each stores its results separately, so the analyst is the triangulation engine, exporting from both and matching records by hand to see where the number and the narrative line up.
The one test that separates them: ask the stack to show where a score and the respondent’s own explanation disagree, with the sentence quoted, on one record. A two-tool setup answers by asking you to merge and eyeball. Sopact answers from the Connected Record, because the narrative was read on arrival and tied to the number.
The move that modernizes the discipline is reading the narrative against a codebook as it lands, so triangulation, contradiction analysis, and driver views are queries rather than a one-time merge. Sopact drafts the themes from the respondent’s words, quotes the sentence, and ties them to the numbers, so an analyst confirms a draft and keeps design control instead of merging exports by hand.
Kept on the Connected Record, mixed-methods analysis is longitudinal: number and narrative across every wave on one persistent ID. Sopact reads on arrival, so where a rising score meets a worried narrative shows up in time to look closer rather than in a report at the end.
A two-tool setup captures number and narrative apart and merges them once by hand; the Connected Record reads the narrative on arrival and triangulates as a standing query. The difference is whether triangulation is a query or a one-time merge.
| The question | Two-tool merge | Connected Record |
|---|---|---|
| Analyze the numbers? | Yes: the stats tool | Yes, on the participant record |
| Analyze the narrative? | Yes: the coding tool | Yes, against a codebook on arrival |
| Triangulate the two? | A manual merge | Yes: a query over one record |
| Catch a contradiction in time? | No: a late report | Yes: read as responses land |
See concrete scenarios on mixed-methods research examples, or the step-by-step on how to analyze survey data.
A dropping score is worth understanding while you can still respond to it, not in a report written after the program ends. The value of the open-text behind a number is highest the moment it lands, when the reason for a low rating can still change what happens next. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, with the number and the open-text explaining it on one participant record; analyze on arrival, reading each open-text answer against a codebook the moment it lands and tying it to the number; improve in time, so the reason behind a dropping score surfaces while you can still act.
The Loop is also what makes a mixed-methods finding defensible: every theme traces back to the exact sentence a respondent wrote and the number that respondent also gave, the standard detailed in Loop traceability, so a conclusion rests on the Connected Record rather than a hand-coded spreadsheet no one can re-check.
One method, three moves that never stop
Then the next wave reads a little sharper. Read the method: the Loop methodology →
The fastest way to see triangulation as a query is to run it on your own responses. Export your numbers and the open-text on the same IDs, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended responses
Here is a batch of open-ended survey responses with each respondent's ID and their rating: [ATTACH]. Read each open-text answer against our codebook as it lands, tag the themes, quote the exact sentence behind each theme, and keep every answer tied to the number the same respondent gave, so I can read the reason next to the score on one record instead of in two separate exports.
Academy walkthrough → Connect the number and the reason
Here is our quantitative data and the open-ended responses on the same participant IDs: [ATTACH]. For each rating, pull the open-text the same respondent wrote that explains it, quote the sentence, and show the number and the reason on one record, so a low score carries the reason a respondent gave rather than sitting in a column with no explanation.
Academy walkthrough → Clean open-ended responses
Here is a raw export of open-ended responses on their participant IDs: [ATTACH]. Flag blanks, duplicates, and off-topic answers, normalize the text so it is analyzable, and keep each cleaned answer tied to its ID and the number that respondent gave, so the open-text is ready to read against a codebook on arrival rather than after a month of hand-cleaning.
Academy walkthrough → Find the drivers behind a score
Here are ratings and the open-ended responses on the same IDs: [ATTACH]. Read the sentiment in each answer, identify the drivers behind the rating with the sentence quoted, and tie each driver to the number, so I can see what is pushing a score up or down from the respondent's own words rather than guessing behind the average.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading open-text against a codebook on arrival and keeping every answer tied to the number on one Connected Record.
It triangulates the quantitative number and the qualitative narrative so each explains and checks the other. Sopact makes it a query over the Connected Record — the number and the open-text explaining it on one participant record under a persistent Contact ID — rather than a merge across two exports.
Because most stacks capture the number and the narrative in separate systems with no shared key, so lining them up is an export-and-merge step. Sopact is record-centric and ties the narrative to the same persistent ID as the numbers on the Connected Record.
Those tools store the quantitative and qualitative results separately, so the analyst does the triangulation by hand. Sopact reads the narrative on arrival and keeps number and narrative on one Connected Record, so triangulation is a standing query.
Yes. Because the number and the respondent’s explanation sit on one Connected Record, a contradiction between a rating and its narrative is a query with the sentence quoted, rather than something you eyeball after a merge.
Yes. Sopact reads each narrative against the codebook the moment it lands, so triangulation and driver views update as responses land on the Connected Record rather than in a one-time merge.
Yes. Sopact drafts themes from the respondent’s words with the sentence quoted; an analyst confirms or overrides them, human-in-the-loop. The Connected Record records what was read and from which answer, so design control stays with the researcher.
Yes. Every theme traces to a sentence and stays tied to the number, so a reviewer can re-check a triangulated finding against the respondent’s own words on the Connected Record.
Sopact keeps number and narrative on one persistent ID, so triangulation across waves is read as a trajectory. The Connected Record survives each cycle, which is what makes a longitudinal mixed-methods view possible.
Next: see concrete scenarios on mixed-methods research examples, or compare the two families on qualitative vs quantitative.
