Three worked mixed methods research examples — workforce training, DEI, and program outcomes — each connecting the number to the reason on one record.
Mixed-methods research pairs a number with the reason behind it: a rating plus the open-text that explains it, read together. Sopact keeps every example on the Connected Record, the score and its explanation on one participant record under a persistent Contact ID, so each scenario below shows the number and the reason as one record rather than two datasets a team joins by hand.
The scenarios here are illustrative, not case studies of named organizations, and they use no invented results. Each shows the same shape prospects describe wanting: a score that moved and the participant’s own words explaining why, available in time to act. The pattern breaks in most stacks because the number and the reason are captured in separate systems and reconciled late, if at all.
Key takeaways
A training program sees satisfaction scores dip mid-cohort; the open-ends on the same records read against a codebook show the reason is scheduling, not content, so the fix is a calendar change made while the cohort is still running. A service program watches an outcome rating rise while interview transcripts on the same IDs describe a lingering barrier, and the contradiction prompts a closer look before the final report.
In each scenario, Sopact keeps the number and the reason on the Connected Record, read against a codebook on arrival, so the example is a query over one record rather than two datasets joined by hand. See the discipline behind these on mixed-methods data analysis, or the two families on qualitative vs quantitative.
Reproducing a scenario like these normally takes two toolchains: SPSS, Excel, or Qualtrics for the ratings, and NVivo, MAXQDA, or Dedoose for the open-ends and transcripts. Each is capable on its half, and each keeps its output in a separate file, so building the example means an analyst exports both, matches IDs, and codes the text before the number and the reason can sit together.
The one test that shows the difference: ask the stack to reproduce any scenario above as a single view, a score with the exact sentence explaining it, on one record. A two-toolchain setup answers by making you assemble it. Sopact answers from the Connected Record, because the open-text was read on arrival and tied to the number.
The move that makes these scenarios useful is reading the open-text against a codebook as it lands, so the reason behind a score is part of the result rather than a write-up months later. Sopact drafts the themes from the participant’s words, quotes the sentence, and ties it to the number, so a team confirms a draft and sees the scenario form as responses arrive.
Kept on the Connected Record, each example is longitudinal: a participant’s score and reason across every wave on one persistent ID. Sopact reads on arrival, so a pattern like the ones above surfaces in time to act rather than in a retrospective.
A two-toolchain setup builds each example by exporting and merging two datasets; the Connected Record reads the open-text on arrival and keeps the number and the reason as one record. The difference is whether a scenario is a query or an assembly.
| The question | Two datasets | Connected Record |
|---|---|---|
| Show the score? | Yes: the stats tool | Yes, on the participant record |
| Show the reason? | The coding tool | Yes: against a codebook on arrival |
| Show them together? | A manual join | Yes: a query over one record |
| Reproduce it next wave? | Rebuilt by hand | One persistent record per participant |
See the discipline on mixed-methods data analysis, 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 these examples is to reproduce one on your own responses. Export a metric with 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.
A rating paired with the open-text explaining it, read together: a satisfaction score dipping while the open-ends show the reason is scheduling. Sopact keeps each example on the Connected Record, so the number and the reason are one record rather than two datasets joined by hand.
No. The scenarios are generic and illustrative, with no named organizations and no invented results. They show the shape prospects want: a score and the participant’s own words explaining it, kept on the Connected Record and read on arrival.
Because the ratings live in a stats or survey tool and the open-ends in a coding tool, so building the example means exporting both and matching IDs. Sopact is record-centric and keeps the number and the reason on one Connected Record.
It reads the open-text against a codebook on arrival and ties it to the number, so a score with the exact sentence explaining it is a query over the Connected Record rather than an assembly across two datasets.
Yes. Because the number and the narrative sit on one Connected Record, a rating that rises while the open-text describes a barrier is a query with the sentence quoted, surfaced in time to look closer.
No. Sopact drafts themes from the participant’s words with the sentence quoted; a human confirms or overrides them, human-in-the-loop. The Connected Record records what was read and from which answer, so nothing is fabricated.
Yes. Export a metric with the open-text on the same IDs and read it on the Connected Record, and any scenario above becomes a single view of the number and its reason.
Sopact keeps each score and reason on one persistent ID, so a scenario repeats across waves as a trajectory. The Connected Record survives each cycle, which is what makes a longitudinal example possible.
Next: see the discipline on mixed-methods data analysis, or capture both in one instrument on qualitative and quantitative survey.
