Skip to main contentSkip to navigation
Back to Best Practices

Tip: Check content BEFORE design, not after

by Team PaletteCheckBest PracticesNov 24, 2025 at 9:03 PM

Learned this the hard way and wanted to share!

Old workflow (expensive):
  1. Write copy
  2. Design the asset
  3. Check in PaletteCheck
  4. Find voice/messaging violations
  5. Revise copy
  6. Re-design the asset 馃槱
New workflow (much better):
  1. Write copy
  2. Check copy in PaletteCheck
  3. Fix voice/messaging issues
  4. Design the asset
  5. Final check (usually just visual stuff)

Catching voice and messaging issues at the copy stage saves expensive design revisions later. Your designers will thank you!

Anyone else have workflow tips to share?

0 Replies

You need to be logged in to reply to this topic.