Document libraries are where good intentions go to become menu items. A partner wants clients to fetch drawings, policies, or packing specs without ringing the office. Someone uploads a few hundred files. Search is switched on. Six months later, the owner of the module cannot say whether a client has ever used it.
A feature adoption review of a library is mostly a distinction between two events: opened the library, and downloaded a file. If you only have a menu click, the reading will be thin, and we will say so in scoping. When the two events exist, the story is often this: staff use the library as a filing cabinet because it is easier than the shared drive. Clients almost never search. When a client needs a drawing, they ask a named person, who emails the PDF they already have on their laptop — which may be a different version from the one in the library.
That last point matters. A library that is out of date is worse than no library, because the few clients who do fetch a file may fetch the wrong one. In an engineering practice in Ipoh we watched internal users treat the library as canonical and clients treat email as canonical. The debrief did not recommend a bigger search box. It recommended labelling the library as staff storage and stopping the fiction that clients were self-serving.
If you are about to add another folder because a client asked for “everything in one place”, sit with the last quarter of downloads first. Everything in one place is how libraries die. A short list of the ten files clients actually request, sent the way they already request them, is usually closer to the work.
Utilitycorner reviews B2B client portal apps from Ipoh. If a similar question is sitting on your desk, write to us.