When the right answer is not a platform
Some things being run through an LMS should not be.
A short compliance briefing that everybody must acknowledge once a year does not need a course. A reference document that people consult occasionally does not need enrolment. A conversation between a supervisor and a learner does not need a forum. Each of these gets built as a course because the platform is where learning-shaped things go, and each of them fits badly.
The cost of the misfit is paid by the learner, who has to log in, navigate a structure designed for something else, and complete a completion mechanism that exists to produce a record rather than to help them. It is also paid by the administrator, in support tickets from people who cannot find the thing they were told to do.
The question worth asking early is what record actually needs to exist. If the answer is that somebody read something, an acknowledgement is enough and does not require a course. If the answer is that somebody demonstrated a skill, then the record needs the evidence, and a course is often the right container. The two get conflated constantly.
Saying no to a request to build something in the platform is unpopular and occasionally wrong. But an LMS filled with things that are not courses stops being navigable, and then the courses that matter get lost among them.
The related discipline is to notice when an LMS is being used as a document store because the organisation's actual document store is bad. That is a real problem and the platform is a poor solution to it: search is weaker, access control is coarser, and the material becomes invisible to everybody who is not enrolled. Naming the underlying problem rather than absorbing it is one of the more useful things an administrator can do, and it is usually unwelcome, because the underlying problem belongs to somebody with more authority than they have.