Content Strategy · Interview Preparation · April 2026
A cross-brand audit of voice, terminology, UX writing patterns, and design system alignment — vetted against Spectrum 2 standards. Prepared by Josh for the Staff Content Strategist role on the Frame.io product team.
01 — Overview
This audit examines Adobe and Frame.io across six dimensions — voice/tone, terminology, UX writing patterns, accessibility, grammar/mechanics, and systems alignment — benchmarked against Spectrum 2. It surfaces gaps, names their priority, and proposes a structured plan to close them.
Enterprise-scale brand. Spectrum 2 is mid-rollout. Voice is aspirational, authoritative — "Creativity for All." Heavy use of product names as anchors. Marketing copy leans inspirational, often relying on passive constructions.
Pre-acquisition voice is still dominant: direct, practitioner-first, industry-fluent. Dark aesthetic roots. Uses film and production vernacular natively. Spectrum patterns are inconsistently applied; own brand DNA persists post-acquisition.
Single voice across products; tone shifts by context. Sentence case everywhere. Active voice preferred. Inclusive writing as a baseline. WCAG AA+ for accessibility. Component-level style defers to system, not product.
Frame.io was acquired for its differentiation — its community, culture, and direct voice are core product values. The content strategy job is to harmonize without homogenizing: bring Frame.io into alignment with Spectrum's system thinking while preserving the practitioner-first identity that makes it trusted by editors, DPs, and producers worldwide.
02 — Core principle
The most common failure mode in content strategy is treating an audit as a one-time deliverable. The goal here is different: build a process the team can run repeatedly, that surfaces new gaps as the product ships, and that doesn't require a single person to be the bottleneck.
A content audit isn't a deliverable — it's infrastructure. The output isn't a fixed document. It's a system: a shared rubric, a living glossary, a critique ritual, and a team that can make better content decisions independently. The goal is to raise the floor, not to be the sole ceiling-checker.
Before scoring anything, establish the rubric. For Frame.io, that means pulling Spectrum's voice principles, grammar rules, and inclusive writing guidance as the baseline — then documenting where Spectrum is silent on Frame.io-specific needs. Those gaps are yours to define.
Core UI, error states, empty states, onboarding, notifications, the embedded Premiere panel, help docs, and marketing site strings that set expectations before users enter the product. The map exists so you can prioritize intelligently — not to audit everything at once.
Score strings against the rubric collaboratively — involve two or three designers. This distributes the work and, more importantly, builds shared understanding of content standards across the team. The audit becomes a teaching artifact, not just a bug list.
Separate work into quick wins (sentence case fixes, passive-to-active rewrites), pattern decisions (things that need a defined standard before any string can be fixed), and product/strategy decisions (cross-functional terminology conflicts). Running these in parallel is what makes a team move fast.
New features don't ship without a content pass. A lightweight checklist in the design handoff template does the work without requiring a formal process. The goal is content-first thinking baked in, not bolted on.
A short weekly or bi-weekly session where the team reviews new strings against the guidelines. This is how you mentor designers and PMs on content standards without writing a document nobody reads. The guidelines doc is a living product — version it, update it, and assign ownership.
03 — Voice & tone
Comparing Adobe and Frame.io voice patterns against Spectrum 2's single-voice, variable-tone model. Each signal is rated: aligned, partially aligned, or a gap.
04 — Terminology
Frame.io and Adobe use overlapping but inconsistently defined terms across their products. These create cognitive dissonance for users who move between apps and signal a content systems gap that a shared glossary can address.
05 — UX writing patterns
An assessment of how Frame.io's most common UI writing patterns hold up against Spectrum 2 component-level guidance.
06 — Before / after rewrites
Every "before" string either drops the user from the sentence, leaves them with no path forward, or violates a Spectrum mechanic — usually sentence case. The "after" strings fix all three at once. That's the rubric applied to any string in the product.
07 — Terminology glossary
Spectrum-aligned definitions and usage rules for Frame.io's 10 most critical terms. Filter by category to isolate cross-Adobe conflicts or Frame.io-native vocabulary worth protecting.
version stack, not version history, revisions, or iterations. Always lowercase in body copy. Capitalize only when used as a proper UI label.C2C in user-facing copy. Pair with a brief description on first use per page.project consistently in Frame.io UI. Do not substitute folder, workspace, or library.workspace for the Frame.io account scope. Avoid using it as a synonym for "environment" or "interface."collection (lowercase) in body copy. Distinguish from static folders: "a collection automatically stays up to date."approval (a decision state) and feedback (the content of comments). Use: share for review, review link, send to review. Avoid: review cycle (jargon).timecode comment, not frame comment or annotation. In marketing, pair with the precision benefit: "leave feedback at the exact frame."approve, approved, request approval. Avoid conflating with review. In UI, approval status should be visually distinct from review status.asset in product UI and technical contexts. In user-facing marketing or onboarding, prefer plain language: file, footage, video depending on context. Don't use asset as a synonym for every noun in the system.footage or raw files in broader onboarding contexts for non-production users.08 — Gap analysis
Ranked by: user impact × frequency × strategic alignment with Spectrum integration. Gaps 1–2 are foundational blockers. Gaps 3–5 are high-frequency, high-visibility quick wins. Gaps 6–8 are important but non-blocking.
No voice principles, no product glossary, no UX writing guidelines. Everything is improvised or borrowed from Spectrum without Frame.io's practitioner context. This is the foundational blocker for all other gaps — fixing individual strings without a source of truth produces local improvements without systemic change.
At least 6 core terms are used inconsistently or conflict with Adobe ecosystem terminology. For users moving between Frame.io and Premiere, After Effects, or Creative Cloud, that's real friction. The cost is user confusion and increased support burden.
Frame.io V4 UI contains all three capitalization patterns in close proximity. Spectrum is unambiguous: sentence case. This is a high-visibility, high-frequency pattern that signals brand immaturity and creates scanning friction for users.
The Frame.io panel embedded in Premiere Pro shows error states that don't follow Spectrum's 3-part pattern (what happened, why, what to do). Users encountering errors at the creative tool / collaboration layer lose trust in both products simultaneously.
In-product status copy ("File is being processed," "Upload completed") uses passive constructions throughout. A systematic audit and rewrite of status strings is a discrete, high-impact project that can be batched into a single engineering sprint.
Spectrum has an explicit inclusive UX writing guide. Frame.io has legacy content with terms that don't meet current standards. No audit of Frame.io's inclusive language coverage has been completed or published.
Frame.io V4 represents a significant UX overhaul, but tooltip and contextual help copy from V3-era features persists throughout the product. These strings are verbose and don't reflect the V4 UX philosophy of fluid, minimal interruption.
"Smart folders" becomes "Collections" in product but remains "smart folders" in some marketing contexts. Users following marketing-to-product journeys encounter friction at the moment of entry — a trust-eroding inconsistency that's straightforward to fix once the terminology work is done.
09 — 30/60/90 day roadmap
A phased plan for the first 90 days — structured around the core principle: build the infrastructure first, then fix the strings. Each phase has a concrete deliverable and a connection back to Spectrum alignment.
The first 30 days aren't about rewriting copy. They're about building the shared understanding that makes every subsequent decision faster. The audit is the artifact. The rubric is the infrastructure. The team is the multiplier.
Before auditing anything, define "correct." Pull Spectrum's voice principles, grammar rules, and inclusive writing guidance as the baseline — then document where Spectrum is silent on Frame.io-specific needs. Create a lightweight scoring rubric: four criteria — voice/tone, capitalization/mechanics, terminology, and pattern compliance.
Draft and socialize Frame.io's first dedicated content principles document. Co-created with the team — not handed down. Covers: voice character, tone dial, core glossary (20 terms, Spectrum-compatible definitions), sentence case rule, active voice rule, and inclusive language baseline.
Now the infrastructure is in place. Run three parallel fix tracks: quick wins (sentence case, active voice rewrites — batch into engineering tickets), pattern decisions (error message structure, empty state model — content working sessions), and product decisions (terminology conflicts — already resolved in phase 2). Simultaneously, build the habit that keeps it going.