A marketing agency in London sent me a tagline last month. Four words in English, punchy, a little pun buried in it. They wanted it "adapted for the Turkmen market — make it sing." Fine. That's the job I like. I gave them a line that actually works in Turkmen, one a person in Ashgabat would repeat without wincing. Then came the email: "Can you provide a back-translation so the client can approve?"
And there it is. The moment where every good transcreation gets quietly strangled.
The autopsy problem
Here's what a back-translation does. You take the Turkmen line — which lives on rhythm, a vowel-harmony chime, maybe a proverb the reader half-recognizes — and you render it back into flat, literal English so someone who doesn't speak the language can "check" it. The pun dies on the table. The rhythm is gone. What's left is a corpse laid out for inspection, and the client reads the corpse and says, "Hmm, this doesn't really match the original. Can you make it closer?"
Closer to what? To the thing you paid me to move away from?
Transcreation is the one service where being faithful to the source is the failure. The brief said make it sing. Turkmen doesn't sing in the same key as English. It agglutinates. It stacks suffixes where English stacks adjectives. A three-syllable English brand promise might need a compound noun with four case endings to land the same emotional weight, and when I peel that back into English word by word, it reads like a customs declaration. That's not a mistranslation. That's the language doing its job.
I still write the back-translation, because refusing looks like hiding something. But I've learned to write two things next to it: the literal gloss, and a plain-English note explaining why the Turkmen goes where it goes. "This uses a proverb structure Turkmen speakers associate with reliability. Literally it says X, but the feeling is Y." Without that second column, the whole approval chain is people guessing at a language none of them read.
Nobody in the room speaks Turkmen
That's the real structural problem, and it's worse for me than for a French or Spanish transcreator. Somewhere in a Paris office there's usually a native French speaker who can sanity-check the transcreation directly. For Turkmen, there is no one. The PM doesn't read it. The client's regional lead — if they even have one — covers "Central Asia" as a bundle and probably leans on Russian or Turkish. So the only bridge back to the decision-maker is my back-translation. Which means the thing I write to explain my work becomes the thing they judge my work by. The map replaces the territory.
I've watched approvers reject a genuinely good line and approve a wooden, over-literal one — purely because the wooden one's back-translation matched the English better. The safe choice on paper is the dead choice in the wild. And the person who has to say the line out loud in a shop in Mary never gets a vote.
This is why I've started pushing back at the quoting stage, not the delivery stage. Before I take a transcreation job now, I ask: who signs off, and can they read Turkmen? If the answer is no — and it's almost always no — I tell them the back-translation is a courtesy, not a proof, and I bill for the rationale as part of the work. Writing a defensible "why" for each option takes real time. It's not a free footnote.
Give me options and a reason to exist
The agencies that get good work out of me do one thing differently: they let me deliver two or three versions with a short note on each, and a recommendation. Version A is safe and close to the source. Version B takes a risk with a local idiom. Version C is the one I'd actually put on a billboard. Then the approver isn't grading my Turkmen against English — they're choosing a strategy they can understand in English, and trusting me for the execution they can't.
That framing changes everything. It moves the conversation from "is this correct" to "which effect do we want," which is the only honest question in transcreation anyway. Correctness is table stakes. I'm not being paid to be correct. A machine is correct now, mostly, and correct is exactly why machine transcreation reads like a hostage statement.
And this bleeds straight into subtitling, by the way. Same trap, tighter box. When I compress a line of dialogue into 42 characters with a joke intact, and someone back-translates my subtitle to check it, they'll flag that I "dropped" half the sentence. Of course I dropped it. The viewer has 1.8 seconds and the joke has to land before the shot cuts. What looks like loss on a back-translation is the entire craft on screen.
So here's my ask to the PMs reading this: stop treating the back-translation as the verdict. It's a witness statement, not the trial. If the only Turkmen speaker on the project is the one you hired, then at some point you either trust the hire or you don't. Reading the autopsy report louder won't bring the line back to life.
Ask me why I made the choice. Don't ask me to unmake it in English.