Keeping device UI and collateral in sync for a global hardware brand (anonymised)

Background

A global enterprise hardware manufacturer needed its device UI, drivers, and customer-facing collateral to move together in several languages without the last‑minute rebuilds that had become routine. The content spanned embedded UI strings, XML/DITA‑style docs, and InDesign marketing assets. Cadence was monthly with hotfixes.

Stakeholders included device firmware engineers and build/release, a localisation PM, vendor PMs, DTP specialists, and translators/reviewers for fr‑FR, de‑DE, it‑IT, es‑ES, nl‑NL, sv‑SE, pl‑PL, pt‑BR, zh‑CN, zh‑TW, ja‑JP and ko‑KR.

What I built

A split pipeline: (1) device/UI strings travelled as safe XLIFF with explicit placeholders and reversible mapping; (2) technical docs validated against XML rules (XSD + Schematron) before packaging; (3) InDesign jobs exported clean IDML with a manifest so assets round‑tripped intact.

Small helpers normalised language codes and filenames across teams; QA checks caught mismatched tags, placeholder drift and overset text before sign‑off.

How we ran it together

Engineering supplied labeled drops; PMs launched translation from templates; translators worked in CAT‑friendly packages; DTP rebuilt with the manifest; firmware and docs returned on predictable schedules. A tiny pilot round‑trip ran each cycle to catch regressions.

Outcome

Build failures tied to localisation disappeared, DTP cycles shortened, and adding a new locale became a repeatable step rather than a mini‑project. People focused on content and design instead of repairing structure.

What I’d keep today

The reversible mapping for UI strings, XML gates that speak the domain’s rules, and the manifest for IDML. They remove most of the avoidable friction in mixed hardware+docs environments.