Many companies right now not only have external websites but have internal websites, or documentation libraries, or both. And these libraries are typically organized and accessed around some sort of hierarchical index that you burrow down into or expand into lexia. They might allow plain-text or keyword searches. Or maybe both.
Looked at broadly, those libraries are hypertexts, and the readers of those hypertexts are very often coming in from some specialized angle that has nothing to do with the "official" hierarchy the index imposes. What is needed is specialized projections of that hypertext: indexes arranged along more of an FAQ model, or searches that give hierarchies and paths (structures) as a result. Multiple simultaneous hierarchies or paths. There's no reason not to except that the site designers aren't used to thinking of documentation as a hypertext like that, or not thinking about their site as a hypertext in the aggregate.
There's been some interesting thought about the role of narrative in business sites, and many good sites research the paths that visitors take through their sites, but few seem to be thinking (or talking) about giving readers structures for their personalized visits like customized site maps or multiple simultaneous indices.
The example we discussed was the documentation site for MySQL. What about a page that shows the site in terms of "how MySQL is SQL", or "trying to get MySQL to work with other platforms". These topics are worth more than a page, more than a lexia-- they've got their own hierarchies and paths of relevant information from sources all over the existing documentation.