FIELD NOTES

Log

Observations from the practice. Translation, identity, and the gap between them.

01 Brief the Gap, Not the Aesthetic
arrow_forward
02 Why Translation Isn't Communication
arrow_forward
03 The Seam Nobody Talks About
arrow_forward

STRATEGY · 01

APRIL 2025

4 MIN READ

Brief the Gap,
Not the Aesthetic

The most expensive mistake in an agency brief is aesthetic displacement — asking for a look when you have a communication problem.

When an Osaka manufacturer says they want "a modern, international website," they are describing an aesthetic wish. Underneath it is a more precise problem: their current site fails to convince a German procurement manager that they are a credible long-term supplier. That is a content and information architecture problem, not a typography problem.

The aesthetic is downstream of the communication problem. Get the problem wrong and you will produce a site that looks different but fails identically.

What closes an information gap is not visual sophistication. It is the right information, in the right order, framed for the right decision-maker.

A Japanese B2B site that leads with the company's founding history is not making a mistake of taste. It is making a mistake of sequence. The international reader needs credibility signals earlier than the Japanese reader does. The content is often identical — the architecture is what changes.

This is the information gap: the distance between what a client needs to communicate and what their current materials actually transmit to a specific audience. It is not a creative problem. It is a diagnostic one. And the brief is where it should be surfaced.

The brief's job is to name the gap. Our job is to close it. The two become confused when clients — and agencies — treat aesthetics as the primary deliverable rather than the means to an end. We always start with the gap.

LANGUAGE · 02

MARCH 2025

3 MIN READ

Why Translation
Isn't Communication

A translated website is not a multilingual website. The distinction matters more than most clients realise.

Translation preserves content. It moves words across a language boundary at roughly the same level of abstraction at which they entered. What it does not do is reconstruct the argument. Japanese and English differ not just in vocabulary but in the fundamental logic of persuasion: Japanese business writing typically establishes context before making a claim; English business writing leads with the claim and follows with evidence.

When you translate the former into the latter, you preserve the words but invert the structure — and to the English reader, the text feels slow to arrive at its point. The translation is accurate. The communication still fails.

The more precise operation is localization — not of language, but of argument.

The claim goes first. The credentials follow. The category definition appears earlier. The competitive framing sharpens. This is not a translation task — it is a structural editorial task performed by someone who understands both the source logic and the target audience's decision-making sequence.

Most companies discover this after launching a translated site and finding it underperforms. The translation vendor delivered what was asked for. The brief asked for the wrong thing. Language is architecture. Brief it accordingly.

ENGINEERING · 03

FEBRUARY 2025

3 MIN READ

The Seam Nobody
Talks About

The creative industry has a structural blind spot: most agencies separate design from engineering, and their clients absorb the cost of the gap between them.

The typical engagement runs like this. A brand agency produces a visual identity — logotype, colour system, type hierarchy, usage guidelines. The client takes the guidebook to a development team, which builds a site from it. The development team was not in the room when the design decisions were made. They implement what they can, approximate what is unclear, and omit what is impractical. The result is a faithful interpretation of an interpretation.

What gets lost in that handoff is precision. The 4px rule mark beneath every section heading. The exact letter-spacing at label scale. The timing curve on hover transitions. These are not decorative preferences — they are the micro-decisions that determine whether a brand reads as engineered or merely assembled.

The solution is not better documentation. It is a practice that never separates design from engineering in the first place.

When the person who specifies a component is the same person who builds it — or is in direct conversation with the person who will — the handoff problem disappears. The gap between intent and execution closes not because the spec was more detailed, but because there was no seam for precision to fall through.

This is why Layer 03 exists as part of Communiqué's model rather than as a referral. Not because every client needs software engineering, but because the discipline of building changes how you design. It makes you honest about what is actually deliverable — and uncompromising about delivering it exactly.

START A PROJECT

Tell us what you're building. We'll tell you how to make it land.

GET IN TOUCH