Timeline for Which type of help system is best?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 6, 2016 at 13:02 | vote | accept | Matt Rockwell | ||
| Nov 4, 2014 at 9:47 | comment | added | Jason A. | We've advanced our in-application help and improved user satisfaction by tightly binding information to where people need it. The help is mostly around Domain complexity, not application behaviour as UX was improved. Pretty much ditched any semblance of "Read a book about an app" approach. Taking the example of Visual Studio, developers will read semantic behaviour of an API call (their Domain) very few will read "How to Drive Visual Studio" | |
| Jul 7, 2011 at 12:47 | comment | added | Matt Rockwell | +1 100% agreed that people don't read. We get tech support calls about things that are clearly explained in our help files. I would love to have no help, but the software is so powerful and capable of doing infinite amounts of operations, it needs a help file. We have done our best to simplify it, but it still needs the documentation (think Photoshop, Visual Studio, etc. Massive programs capable of a lot). | |
| Jul 6, 2011 at 20:58 | history | answered | DA01 | CC BY-SA 3.0 |