I guess one solution would be for programmers to write several versions of the same help files. This should satisfy the needs of those who think logically, those who do not think logically, and those who fall somewhere in between. Another solution would be for someone to invent a pill that folks can take that will result in everyone having the same thought patterns. Thus, when a programmer (regardless of the software) writes a help file, it will be understood by everyone. Those who think logically will be able to use the help file, those who don't think logically will also be able to use the help file, and those who fall in between will be able to use the help file - thus, no more complaints from people who can't figure out/follow the help files.
Of course, the downside of the pill version would be that we will all think alike and thus we become zombies. The advantage to the pill version is that software programmers wouldn't have struggle to try to satisfy everyone when they write the help files. Ron Bernier, Woonsocket, RI ------ Original Message ------ From: "Pat Hickin" <pph...@gmail.com> To: LegacyUserGroup@legacyusers.com Sent: 9/1/2012 8:33:09 AM Subject: Re: [LegacyUG] Legacy Help problems >Denise, >I agree that Legacy is complex, the staff no doubt small, and that the >Legacy staff does all sorts of wonderful things to assist its users, >who range from novice to expert. One of the things I especially like >about Legacy is the support staff, who often reply to emails posted by >LUG. I agree they deserve kudos. > >That being said, the problem remains that instructions are often >opaque and convoluted. In many instances,they could be dramatically >improved through reorganization. For example, after a brief >introductory paragraph, the instructions could tell us how to >accomplish a particular purpose by giving the instructions in the >order in which one does them. Beginning with the family view, simply >tell us what to click on in the order in which the clicking needs to >be done. When making reference, in a word or phrase, to something >explained, that word or phrase could be hyper-linked (I think that's >the term) to the explanation. More illustrations would also help to >clarify things. > >One section that is quite well done, I think, is the Legacy Tips and >Tricks set of instructions. Excellent illustrations help to make the >text in that section easily intelligible. > >Also in the Legacy Tip that shows when you first open Legacy (unless >you have that feature turned off) the instructions frequently tell >what to click on in the order in which the clicks need to be done. > >Pat > > > > >On Sat, Sep 1, 2012 at 3:59 AM, Larry Lee <ldlee...@gmail.com> wrote: > Absolutely correct! Very well said. > Can it be improved? Of course. > Will it be improved? Yes. > The developers have shown over time their desire to respond to user's > complaints and continually improve their product and deserve kudos > for all they do and have done. > Regards, > Larry Lee > On Aug 31, 2012 10:18 PM, "Denise Moss-Fritch" > <den...@newmoonalpacas.com> wrote: > Good Day All, > While I have read the comments to this topic with interest, my > response is not intended to replay to any one email. However, I am > hoping that perhaps I can provide a bit of perspective. > Before retiring three years ago, I was the lead technical writer to > a medical device company that provided equipment and software used > in the treatment of cancer (radiation and chemo). The multi-module > software recorded patient histories, treatments (planned and > actuals), control of the radiation generating machine during > treatment, through transfer of billing information to a hospital’s > accounting system. The database that recorded the whole process was > printed on a 4 x 5-feet poster with information describing the > database shown in 8 point type (10 or 12 point type is standard). > There are half a dozen development teams worldwide working on the > software, with no one developer understanding all the program’s > modules. Even the customers do not understand every element of every > module of the multi-million lines of code. > In comparison, I believe I heard during one webinar that Legacy has > 600,000 to 700,000 lines of code. Yet Legacy too is a complex > software application offering components (modules) that some, while > not all will use. For example, the Source Template Conversion Tool, > multiple recorded source clipboards, the picture gallery, or using > the Geo Location Database to search for surrounding cities are > probably not used by every Legacy user, every time, yet those > capabilities are available. > Just as the medical device software I described has multiple levels > of users, so does Legacy. Attempting to provide information, whether > details of how to use a feature or simple process flow (step-by-step > procedure information) can be complex when dealing with multiple > levels of users. Yet Legacy does offer a user guide, help system, > two add-on books, and multiple webinars. While I suspect the Legacy > staff is small, they do offer a variety of sources of information > describing how to use Legacy. Providing user information for a > complex software product, including information for multiple levels > of users, is not an easy task. > For that effort, I wish to commend the Legacy staff for what they > have accomplished to make their software understandable to so many > different levels of users. > Best, > Denise L. Moss-Fritch Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
