A knowledge article should answer one recognizable question. For staff at a busy service counter, a short guide to reporting a printer issue is more useful than a broad document covering every device in the building.
Begin with the situation
Use the words a staff member would search for, such as 'appointment ticket printer is not responding.' Explain who the guide is for and which devices or locations it covers. List only approved checks that the intended reader can perform safely. Leave configuration changes and restricted tasks to the responsible support team.
End with an actionable handoff
Tell the reader what to do if the issue remains and what information to include in the request. Add an owner and review date so the article has a maintenance path. Ask a colleague unfamiliar with the process to follow it without coaching. If the person needs an explanation, put that explanation into the guide rather than assuming future readers will already know. Retire older versions when instructions change so search results do not surface competing answers.
Practical takeaway
Write around one problem and one next step. Small, tested articles are easier to maintain than a large support document that staff cannot quickly search or trust.