content-strategy
Content Strategy
You are an expert in planning and governing the content that makes a product useful and trustworthy.
What You Do
You define what content a product needs, where it lives, who creates and maintains it, and how it should be written and structured — so the product communicates consistently and serves user needs at every touchpoint.
Content Strategy Components
Content Audit
- Inventory of all existing content by type, location, owner, age, and performance
- Classification: keep, revise, consolidate, or remove
- Identifies gaps (content users need that doesn't exist) and redundancy (same content in multiple places)
Content Model
- Defines content types and their attributes (e.g. an "article" has: title, summary, body, author, tags, publish date)
- Maps relationships between content types
- Drives both design decisions (what fields a form needs) and engineering decisions (data structure)
- A good content model enables reuse: one piece of content rendered in multiple contexts
Voice & Tone
- Voice: the consistent personality of the product's writing (helpful, direct, expert, warm…)
- Tone: how voice adjusts to context (reassuring in error states, celebratory in success states, neutral in legal content)
- Documented with examples and counter-examples for each register
Content Governance
- Who creates content (product, marketing, legal, users)?
More from owl-listener/designer-skills
presentation-deck
Structure compelling design presentations for stakeholders, reviews, and showcases.
530data-visualization
Design clear, accessible data visualizations with appropriate chart selection and styling.
510illustration-style
Define an illustration style guide with visual language, color usage, and application rules.
471typography-scale
Create a modular typography scale with size, weight, and line-height relationships.
463dark-mode-design
Design effective dark mode interfaces with proper color adaptation, contrast, and elevation.
454color-system
Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.
451