TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Pardon my frankness, but I think that last bit is nonsense.
It works the other way around.
You start out documenting your own product, and you document the ways that you think it can be used, in order to address the largest possible market. Actually, you might document fewer ways than you can imagine, since PLM has already decided which use-cases make economic sense to test - and therefore to officially support. You, and your customers, are better off if you don't document for public consumption until the use-case is tested and can be supported by Tech Support.
THEN, your customers start showing you uses of your own product that you never imagined anyone would do.
THEN, you document those, too.
And the cycle continues until your product ages out.
Your customers will already have imagined any use-case that is suggested or implied by the sales bumpf, your corporate web site, and their contact with Sales and Professional Services... in other words, any use-case that your company already officially knows about. (*)
So, in that context, the best thing a writer can do is to maintain contact with the [Pre-] Sales Engineers, the Tech Support people, and the Professional Services people, all of whom are exposed to customers finding novel uses for your product(s), and figuring out the details of making those use-cases a reality.
With respect to the OP's question... sorry... I'm not up to converting that into a pre-packaged vision thing, this morning. :-)
(*) We don't, but if you have a public user-to-user support forum, THAT venue might provide some novel suggestions and use cases.
From: jimmy -at- breck-mckye -dot- com
We want to help users unlock the full value of our products. We want to show our customers that we respect their investment by returning them a consummately high-quality product. We want to surprise and delight our users, showing them ways our product can help them they haven't even imagined.
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?