Breaking News
Comments
Sanjib.A
User Rank
CEO
training vs documention
Sanjib.A   4/25/2014 12:41:50 PM
NO RATINGS
First of all...a very nice article!! I am a user of EDA tools. I have not spent much time in reading the manual, but while reading through this article I realized that I might not be using the tool most efficiently. I think training is absolutely needed to start with. If the user works with an EDA tool frequently, training should be enough to start with. When ever I get stuck, I ask some expert users in my organization. That is quick...but if nobody is around to help, the manuals get handy then...only wish that the manuals are presented in a way which does not bore the user. :-)

junko.yoshida
User Rank
Blogger
Re: training vs documention
junko.yoshida   4/25/2014 6:29:08 PM
NO RATINGS
I agree, Sanjib. This article illustrates the crux of the issue -- documentaions? training? or both? -- rather eloquantly. 

I guess the fundamental human behavior isn't that much different -- whether one embarks of using a brand new flash light or a new EDA tool. 

AZskibum
User Rank
CEO
Re: training vs documention
AZskibum   4/27/2014 8:07:34 AM
NO RATINGS
Training and documentation serve different purposes and both are needed, especially for new users or even for experienced users who are being introduced to a methodology or major tool feature that is new to them.

Those multi-day offsite training courses in a room full of workstations are expensive, but can be incredibly valuable. The knowledge & experience gained by using the tool in such a focused environment with an expert instructor cannot always be duplicated by simply reading the documentation and trying things on your own.

_hm
User Rank
CEO
I read specifications
_hm   4/26/2014 4:33:15 PM
NO RATINGS
I first like to read specifications  of every new tool or device I encounter. So this way, I know the most capabilites. Reading documentation is sometime time demanding and not many family member have patience. So manual I read as need basis.

 

dfarbey
User Rank
Rookie
Re: Is it training or documentation
dfarbey   5/1/2014 6:07:03 AM
NO RATINGS
You highlight several important issues around documentation and training, and as someone who is responsible for providing information I recognise the problems you describe only too well. People with jobs like mine - often known as technical communicators, or technical writers, or technical authors - would love to provide information that supports user tasks, rather than information that just describes the product, but there are often obstacles that stop that from happening. For example:

1. Some companies see technical communication as a necessary evil, and teams are under-resourced in terms of staff, tools, and access to information

2. Some companies see technical communication as a cost centre, part of product development, and so it's kept separate from Training, which is seen as a revenue source. The result is often that there are two teams trying to provide parrallel information to customers, duplicating efforts and wasting resources.

3. The best sources for understanding user expectations and therefore producing documentation that supports users are from user research. This research is often undertaken and owned by a marketing department that doesn't see the need to share. Data about what features are least well understood - the features that need to be explained more fully in training or documentation - could be gathered by reviewing calls to Customer Service, but once again, it is rare for this information to be shared.



Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Feast Your Orbs on My Jiggly Exercise Machine
Max Maxfield
52 comments
Last weekend, I was chatting with my mother on the phone. She's all excited that I'm coming over to visit for a week in November. "I'll be seeing you in only seven weeks," she trilled ...

Glen Chenier

Missing Datasheet Details Can Cause Problems
Glen Chenier
3 comments
It is often said that "the devil is in the details." All too often those details are hidden deep within a datasheet, where you can easily overlook them. When a datasheet reference circuit ...

David Blaza

RadioShack: The End Is Nigh!
David Blaza
123 comments
I'm feeling a little nostalgic today as I read about what looks like the imminent demise of RadioShack, at least as we currently know it. An old ubiquitous cartoon image popped into my ...

Larry Desjardin

Engineers Should Study Finance: 5 Reasons Why
Larry Desjardin
47 comments
I'm a big proponent of engineers learning financial basics. Why? Because engineers are making decisions all the time, in multiple ways. Having a good financial understanding guides these ...