When a flow is hard to explain, the layout is usually not the only problem. The copy is often carrying more structure than the team realizes.

I like writing rough interface copy early because it exposes missing decisions. A vague button, a long helper text, or a confusing empty state usually points to a product question that is still unresolved.

This does not mean every screen needs more words. It means the words should clarify the relationship between user intent and system response.

Good interface copy is not decoration. It is part of the architecture of the experience.