Content design pass

Public

Words as an interface layer — a content designer plugging into a product team.

by BuildscapePublished Jul 25 2026, 02:02 · 43 views · 0 copies

How this workflow works

Audit

NotionNotion — Terminology audit

Every label, button, and error message in the product gets pulled into one doc to see just how many different words we're using for the same thing.

Standardize

NotionNotion — Term base

The single approved word list — which term wins when two teams have been calling the same thing two different names — kept internal so it can change fast.

Write

FigmaFigma — In-context UX writing

Copy gets written directly inside the real layout, not a separate spreadsheet — so tone and length get judged in the actual space they'll occupy.

Validate

MazeMaze — Comprehension test

A quick unmoderated comprehension check — can people paraphrase what a label or instruction means without help — before the copy locks.

Handoff

AirtableAirtable — Keyed string handoff

Final copy gets exported into keyed rows engineering can drop straight into the codebase, with the string key, English text, and character limit side by side.

Questions

Ask about the reasoning, not just the tools. Answers stay attached to this workflow.

Sign in to ask a question.

No questions yet.