Featured Paper · Version 2.0 — May 2026

Data Mise en Place

A framework for traceable AI synthesis in qualitative research — so findings can be defended, not just delivered.

Retrieval-Augmented SynthesisAI ArchitectureHuman-in-the-LoopTraceabilityAI-Assisted SynthesisPrompt Engineering
AuthorIgnacio Cánovas
StatusUnder review for publication
Developed2022 – 2026
AffiliationAccenture Song, Chicago
Abstract

The quality of AI synthesis is not determined by the model alone.

This paper proposes a structured framework for AI-assisted qualitative synthesis that maintains the traceability and rigor of grounded theory methodology while operating at the speed and scale that modern research practice demands.

The framework addresses a gap that current AI tools do not solve: the absence of a verifiable chain of custody from raw participant data to synthesized insight. It was developed from practice between 2022 and 2026.

The central argument is twofold. First, the quality of AI synthesis depends primarily on the structure of the data entering the system. Second, human presence is not optional in AI-assisted research — it is a foundational requirement. Without a researcher who has witnessed the data, there is no basis for validating what the AI produces.

"If you cannot trace it back to the source, it does not belong on the plate." — The mise en place principle, applied to research.
The Problem

AI tools appear trustworthy regardless of input quality.

AI language models are designed — at the interface level — to appear trustworthy. They deliver outputs with confidence and fluency regardless of the quality of the input. When researchers feed unstructured, noisy, or poorly organized data into these systems, the output can appear rigorous while being partially or wholly fabricated.

This is not a failure of the technology. It is a failure of the methodology surrounding it. Most practitioners have responded in one of two ways: accepting AI output without verification, or rejecting AI assistance entirely. Both responses are inadequate.

A third path exists: designing the data structure and human presence that makes AI synthesis verifiable. This is what the framework proposes.

The insight that drives the framework
AI tools constrained to a well-defined input produce more reliable output than AI tools given unconstrained access to raw data. The framework applies constraint through data architecture and structured prompting — making any AI tool more defensible.
Theoretical Grounding

Built from practice. Validated by theory.

This framework was developed independently through practice before its connections to existing methodology were recognized. In January 2026, the author encountered grounded theory methodology (Strauss & Corbin, 1998) for the first time and found that the pipeline built through trial and error over three years was structurally identical to what Strauss and Corbin had formalized decades earlier.

The parallel is significant. Grounded theory was developed precisely because researchers recognized that imposing analytical frameworks on qualitative data before the data had been examined produced findings that reflected the researcher's assumptions rather than participants' actual experiences. The same risk applies to AI-assisted synthesis.

The framework adapts principles from grounded theory for large language model-assisted synthesis — including bottom-up coding from data, researcher immersion, constant comparison, and data saturation.

Core Concept

An atomic observation is one value. One piece of data.

The unit of analysis in this framework is not the sentence. It is the value-bearing claim. A sentence can contain one value or many. The researcher's job — and the AI's job under constraint — is to decompose meaning until each unit is irreducible.

The decision rule: Can this observation be split further without losing a distinct piece of meaning? If yes — split it.

One observation = one value = one evidence quote = one evidence type.

Common observation types that emerge across research contexts: Preference, Emotional state, Behavioral pattern, Causal relationship, Contradiction, Social validation, Expectation. This is not a fixed taxonomy — different research contexts will surface different types.

The backlog principle
When a statement cannot be cleanly decomposed, it is not discarded — it is preserved with "ambiguity" as its evidence type. If the same unresolved signal appears across multiple participants, the pattern itself becomes attributable. The framework is not anti-ambiguity. It is pro-defensibility.
Path A — Generative Research

The data reveals the themes. You don't impose them.

For generative research (interviews, exploratory sessions), the pipeline follows an inductive path. Codes emerge bottom-up from atomic observations. The data generates the code.

Structured Transcript Clean Notes Anonymization Atomic Observations Evidence Type Inductive Codes Axial Codes Themes
01
Structured Transcript
Raw transcript + observation notes combined. Speaker labels added, metadata included, observation notes embedded at the exact moments they occurred.
02
Clean Notes / Reconciliation
AI removes filler, normalizes statements, replaces facilitator questions with neutral context lines. Researcher observation notes stay unchanged.
03
Anonymization
All names and sensitive content replaced based on pre-defined anonymization notes. Nothing disappears silently — redactions are flagged.
04
Atomic Observations
Each piece of clean data broken into atomic observations — one idea, one source, no interpretations. Each receives a unique code that travels unchanged through every subsequent stage.
05
Evidence Type / Taxonomy
Applied after all observations exist — never during extraction. The AI classifies against a taxonomy the researcher designed before the pipeline ran.
06
Inductive → Axial → Themes
Codes emerge bottom-up. Inductive codes cluster into axial codes — higher-order patterns visible across participants. Axial codes cluster into themes that name what the data has revealed.
Path B — Evaluative Research

The data measures against a known standard.

For evaluative research (user testing), deductive clusters are defined by the research design before the pipeline runs. The UX Area is the deductive code — brought in from outside, not discovered from the data.

Structured Transcript Clean Notes Anonymization Atomic Observations Evidence Type UX Area Cluster Description Findings Recommendations
The critical reconciliation step
In user testing, data cleaning is a genuine analytical task — not housekeeping. A participant who says "this is clear" while clicking the wrong button is telling us something important with their behavior that their words are not. The researcher makes that judgment call. The reconciled version becomes the clean note. The AI works from this truth.
What It Produces

A structured, queryable knowledge asset — not a deck.

The output of this pipeline — whether themes or findings — is defensible, filterable, and honest.

Defensible
Every conclusion traces to its source. No finding exists without attributed evidence. The chain from recommendation to participant quote is unbroken.
Filterable
Because observations are structured in a spreadsheet with coded columns, the data can be filtered by participant, session, topic, evidence type, UX area, or business risk.
Honest
Because the pipeline requires human presence at every validation gate, the output reflects what participants actually said and did — not what the model inferred they probably meant.
"Traceability creates auditability, not epistemic validity. What the pipeline guarantees is not that the output is correct — it is that the output is checkable."
Implications

The researcher role is not diminished. It is elevated.

Critical thinking moves upstream — into data architecture decisions — and downstream — into validation against lived experience. The researcher who develops these skills becomes more strategically valuable. The researcher who does not risks producing synthesis that looks rigorous and cannot be defended.

On hallucinations: this pipeline does not eliminate them. No methodology does. What it changes is detectability. Errors that previously passed unnoticed become visible at the validation gates, because the structured chain of custody gives the researcher something concrete to verify.

The pipeline does not prevent AI from making mistakes. It makes mistakes findable. That is the real reliability guarantee.

About the author
Ignacio Cánovas is a UX Researcher and AI Experience Designer at Accenture Song, where he developed and applied this framework across research projects spanning automotive, financial services, global search behavior, and enterprise AI agent development. Before technology, he spent nearly a decade in Michelin-starred kitchens across Europe and the Americas — where the standard was simple: if you cannot trace it back to the source, it does not belong on the plate.
Replay ✦
✉ Send Ignacio an email
📅 Book a call with Ignacio
🗓
Chat with Ignacio — 30 min
AI Experience Designer at Accenture Song. Happy to walk through my work, DMP, or just talk AI research, design, and adventures around the world.
Book a slot →
Opens Google Calendar · 30 min · Google Meet