Frequently assumed questions

If you’re launching a product or service and you’re tempted to write an FAQ, stop.

At this stage, you don’t know what your users will struggle with, so your FAQ would be a list of assumed questions. This is the curse of knowledge in action.

Even if you could predict the questions, wouldn’t it be better to improve the user interface or manual, so the user is no longer confused?

An FAQ should be a last resort. Write one when real users keep struggling with something. And view it as a temporary stopgap while you redesign those problems away.