Voice And Tone

Raw
GuidancelatestRetrieved 2026-05-16

Carbon Design System — Voice and Tone

Context

Carbon's content guidelines are built on and informed by the IBM Style Guide and IBM Design Language. They are designed for IBM product interfaces — a context that skews technical, enterprise, and international. The guidelines reflect IBM's need for clarity, consistency, and global accessibility above personality.

Carbon does not define a standalone brand voice separate from IBM. All voice guidance defers to IBM Brand Center's verbal expression guidelines.

Voice

IBM's voice is defined by what IBM content looks like when it is at its best:

  • It has a clear point of view.
  • It's simple and logical.
  • It builds on solid research, data, and analysis.
  • It's intellectually ambitious, expressing a bigger idea.
  • It's persuasive, not poetic.
  • It's confident, but not boastful.
  • It only ever uses figurative language for emphasis.
  • It elevates facts and outcomes.
  • It engages the thinker by speaking like the thinker.

This is a functional, thought-leadership voice: authoritative without being ornate, direct without being cold.

Tone

Tone in Carbon adapts to the user's context within the product journey. The underlying voice stays consistent; word choices and sentence structure adjust.

Carbon frames tone adjustment along the product journey:

  • "Discover, try, buy" phases: More conversational, friendly, and engaging. Longer sentences and fuller explanations are appropriate.
  • Error messages: Economy of words is essential. Short phrases rather than sentences. No conversational warmth — clarity only.
  • Onboarding flows: More time is warranted. Full sentences, friendly explanations, human pacing.

The principle: "Whatever the conversational level, the writing should always be simple, clear, and easy to understand. And keep the tone friendly, human, and inviting."

Content quality standard

Carbon's overarching standard for all UI writing: "Well-designed content empowers people to use our offerings with ease. Words form the conversation a user has with a product, working with the visual elements and interactions to form a cohesive and tight experience."

Writing should:

  • Be simple, clear, and easy to understand
  • Use everyday language, not jargon
  • Choose short words over long, impressive-sounding words
  • Be succinct — keep sentences as short and simple as possible
  • Never be terse — brevity should not come at the expense of clarity