2 Comments
author

You are completely right, which is why I hesitated to release this (as it's part of a larger series of posts around the topic). A way to have placeholder copy that is more useful than lorem ipsum exists and what I prefer: sketch copy. I wrote about this in an earlier post (https://uxdesign.cc/use-sketch-copy-instead-of-lorem-ipsum-to-save-yourself-some-headaches-773c62000c19), and how it has a number of key advantages: the primary one is that you can see how much space the placeholder sketch copy occupies, instead of a random amount of lorem ipsum.

I am in favor of using sketch copy until it's time to think about content, and then using ChatGPT from there (i.e. skipping lorem ipsum entirely).

Expand full comment
Mar 9, 2023·edited Mar 9, 2023

The benefit of using lorem ipsum in some cases is that it's universally understood placeholder copy. Let's say I need to share a design for a confirmation modal, but we don't have the language from legal for a standardized disclaimer yet. Putting in an AI generated one can be more confusing than helpful. It's less clear to the developers and BA's that the copy isn't final, and it's too easy to misinterpret as correct. AI generated copy is a great alternative for many use cases, but sometimes you need people to intuit very quickly what's done in a design and what's not. I do think your point about getting stakeholders talking is an interesting one, and so true. Still, for some things they'll have no influence over, it's just not worth going down a rabbit hole when we already have limited time with them. How would you go about flagging what copy is final in a mockup vs what is generated to keep the team on the same page?

Expand full comment