Quant translation-module UX walkthrough

Raw source preview

Raw, unprocessed file text shown below.

---
title: "Quant translation-module UX walkthrough"
status: processed
source_type: prototype walkthrough
session_date: 2026-02-03
duration: "51m 39s"
participants:
  - Leanne Willins
  - Desmond Leo
  - Fernando Guevara
product_area: "Quant Surveys / multilingual research"
tags: [quant-surveys, translation, multilingual, prototype-test, internal-practitioner]
---

# Quant translation-module UX walkthrough

## Source file

- [translation-module-ux-walkthrough.docx](./translation-module-ux-walkthrough.docx) — original Microsoft Teams transcript export.

## Evidence relevant to launch

- Leanne described a live need for seven or eight languages, including locale-specific variants.
- The current workflow exports the survey and manually marks what translators should change because filters and cells can become misaligned (8:01–9:41).
- Excluding non-translatable content would remove “grunt work” (17:19–17:45).
- Translation QA is manual and expensive; errors need to be obvious enough for a researcher to resolve (35:01–40:42).
- Leanne said she could use the proposed flow, found it familiar but nicer than the incumbent experience, and saw nothing that made it unusable (43:19–44:23).

## What this supports

Multilingual survey work has a specific, observed handoff and QA burden, and the proposed workflow was usable to an experienced practitioner.

## What this does not prove

This was an internal prototype review. It does not prove production readiness on the session date, measured time savings, or external willingness to pay.