Learning Targets
- Explain what strong engineering documentation looks like.
- Improve the Lesson 0.4 paper-airplane worksheet.
- Connect documentation quality to engineering decisions and communication.
IED Unit 0 • Lesson 0.5
Engineering Notebook & Documentation Basics
Focus Question: What makes engineering documentation useful?
Mission Briefing
Today’s Plan
Turn rough notes into clear, dated, labeled, evidence-based documentation.
Learning Targets
Success Looks Like…
Another person can understand your design, test, and revision without asking you to fill in missing details.
Core habit: Document enough information for someone else to follow the work later.
Opening prompt
Weak vs. strong
Documentation standard
Revision workshop
Peer check
File work
Exit
Opening Prompt
Could another person understand your work?
Good documentation is written for the future reader—not only for the person who completed the activity.
Quick class share: What information would be missing from the note “It worked”?
Reveal the documentation standard
Strong documentation makes engineering thinking visible.
It is clear, dated, labeled, evidence-based, and detailed enough to support a review or repeat the work.
Compare
Weak vs. Strong Documentation
More words do not automatically create better evidence.
Documentation Standard
Use five checks throughout the course
These checks apply to notebook pages, photos, screenshots, data tables, and design-review evidence.
Clear
Another person can understand what happened.
Dated
The work can be traced over time.
Labeled
Sketches, tables, and images have meaning.
Evidence-Based
Claims connect to data or observations.
Review-Ready
There is enough detail to explain a decision.
Revision Workshop
Improve the Lesson 0.4 artifact
Use the documentation standard to strengthen the paper-airplane worksheet.
Review the evidence
- Check the date and page number.
- Verify that sketches and versions are labeled.
- Confirm that both distances are recorded.
- Replace vague statements with specific observations.
- Explain why the revision was chosen.
Upgrade a weak note
Stronger: “Version 1 curved left. We corrected the uneven left-wing fold. Version 2 traveled 12 ft farther and followed a straighter path.”
Quick Check
Which note is review-ready?
Vote before opening the answer.
- 1“Changed it because it was bad.”
- 2“After Version 1 curved left, we leveled the wing tips. Version 2 traveled straighter.”
Reveal the stronger note
Best answer: 2
It identifies the observation, the change, and the result. The reader can follow the reasoning.
Mission Debrief
What You Submit
Improve the existing artifact rather than creating disconnected new work.
Revised Documentation Artifact
Lesson 0.6
Problem Definition, Criteria & Constraints
Open Lesson 0.6Resources
Lesson 0.5 Resources
Use only the files and references that support today’s work.
Lesson 0.5 Student Presentation
Google Slides-friendly 16:9 lesson deck with question slides followed by separate answer-reveal slides.
Engineering Notebook Entry Template
Use this optional structure when a project needs a more formal notebook entry.
Introduction to Engineering Design
Return to the IED course hub for units, resources, certifications, and current course information.