TECHNICAL LOG BOOKS
by Jeffrey Leaf
Thomas Jefferson High School for Science and Technology
Technical log books play an important
role in the success of any problem-solving situation. Some of the uses
of the log book include:
-
Recording ideas and information for future
reference.
-
Recording design sketches and pieces of ideas
before the fragments are forgotten.
-
A legal record of ideas generated and the
time of the idea for possible support in patent infringement litigation.
Technical log books are to be bound. Pages
are not to be removed from the book for any reason. Pages should be used
in sequence. Do not skip pages. Technical log book entries are to be made
in ink and in chronological order. Every entry is to be dated. Entries
are to be completed during the same day as the work or brainstorming session
which generated the design. Memory fades quickly. Ideas must
be recorded as soon as possible, preferably at the time the idea arrives.
Include:
-
Brainstorming lists.
-
Sketches.
-
Dimensions.
-
Sources of information.
-
Problems that arise.
-
What worked, what didn't.
-
Parts lists.
-
Fabrication and/or operation instructions.
-
Test procedures, fixture designs and data.
-
Notes for future reference concerning any
aspect of the project.
Technical log book entries must be specific
and concise. There is no place in a technical log book for vague generalities.
The technical log book is also not a diary. "We made drawings today."
is not a valid entry. The technical log book is not the place to record
likes and dislikes about the project, team members or the teacher unless
the information directly applies to the project.
Entries must answer one or more of the
following questions:
-
What happened? Why did it happen?
-
What should have happened?
-
What problems occurred? Why?
-
How should it be done differently next time?
-
What work is to be performed next?
-
What problems do you foresee coming soon?
These questions can apply to the design, the
schedule, team interaction, or any aspect of every project. Be
factual, specific and detailed in all technical log book entries.
Created by Jeffrey Leaf
Last Update 12/9/98