It is, precisely because you are busy: undocumented IT makes every future problem slower and every absence dangerous. The value shows up as continuity when the person who knew how everything works is off or gone, as speed when a documented fix means you solve a recurring issue in minutes instead of rediscovering it, as safe recovery when you can rebuild a system because its setup is written down, and as smoother onboarding for new staff. The trick is to make it cheap: document while you work rather than as a separate project, and cover the records you actually rely on rather than everything. A little current documentation repays the time many times over; its absence is only free until the day it isn't.

Good documentation is simple, current, accessible and concrete — and, above all, trustworthy. The worst outcome is not missing documentation but wrong documentation, because it actively misleads someone into a bad action during an incident. So favour a short, accurate note over a long, stale one; keep everything centralized so people can find it; write concretely enough that another person can follow it without you; and update it as reality changes, ideally at the moment of the change. Don't chase exhaustiveness or perfect formatting — chase usefulness and accuracy for the things your team truly depends on. Living, honest, findable documentation is what turns individual know-how into organizational resilience.