Interesting question, I'd be interested in seeing the article once you're done.
The first challenge I'd say for many engineers is that they have Attention Deficit Disorder. I'd estimate that from 20 to 30% of the engineers I've worked with "exihibit symptoms similar to ADD" (since I'm not a Dr., I can't diagnose). I usually work with Mechanical, Electrical and Software engineers, other types may have different percentages. If you have any suggestions for organizing for the "organizationally challenged" I'd like to hear them. Oh, yah, I do have ADD and, although it's taking awhile to impliment, the GTD system and a Palm (nothing like an alarm to remind you of a meeting you forgot you had) are the only things keeping me from imploding.
Engineers who support production lines, whatever their title, have to deal with new issues dropping on them without a moments notice, so I'd suggest tracking all projects and prioritization.s Tracking the little issues is critical because if they aren't dealt with they usually become big issues.
While most companies have systems for tracking and storing important data (drawings, reports, etc). Learning to organizing data or papers for current projects is usually a problem, especially as companies start requiring all propriarity data be locked up at night. It took me a long time to file drawings instead of leaving them in a big pile on the desk. Although carefully folding 22" x 34" drawings is a pain, I've found it less painfull than anything else. David's suggestion of 1 A-Z filing system has helped since I used to stuff files where ever I could find space and, of course, it used to take longer to find what I needed.
As others have said, the standard ways of scheduling your day doesn't work. I like the GTD concept of having your 'punch lists' to look at when you get an odd moment of time. Dealing with the lists between the 'hard landscape' of meetings is the only way to go. Granted, if you'r designing something you're not going to create a punch list of each step you're going to take, but I'd suggest having a list of 'sub-projects', or things you don't want to forget, would be a good thing. If you need to remember something, figure out how to categorize it, write it down and track it, or you'll forget it until the most embarrasing part of the design review.
