> if you want to talk about something before it's covered in detail, you have to declare it first. For software, part of technical writing is providing the rea

> if you want to talk about something before it's covered in detail, you have to declare it first. For software, part of technical writing is providing the reader a conceptual model that they can work with in their mind. But another part of technical writing is discovering that the user interface does not consistently use that conceptual model, or any other conceptual model, and so it inevitably brings in suggestions for improvements to UI/UX.