The Engineering Design Notebook: Why Documentation Is Part of Making

Every engineer at Apple who worked on the original iPhone had a lab notebook. Every NASA engineer who designed the Mars rover had one. Every pharmaceutical researcher who wants their compound to eventually become a drug is required by law to have one, witnessed and dated.

This isn’t bureaucracy. It’s how good engineering works.

The notebook records decisions and their reasons. When something fails — and in engineering, things fail constantly — the notebook tells you what you tried, in what order, and what each iteration revealed. Without it, you’re rebuilding from memory. With it, you’re building on evidence.

Key Takeaways

• Professional engineering notebooks serve three functions that home notebooks can also serve: intellectual property documentation, iteration tracking, and knowledge transfer
• The critical habit isn’t writing everything down — it’s dating every entry and recording the reason for each decision, not just the decision itself
• NASA’s engineering documentation culture, developed after the Challenger disaster, established that undocumented decisions in engineering teams create catastrophic failure risk
• Kids who keep engineering notebooks iterate faster than kids who don’t, because they can see their previous reasoning and build on it rather than repeating it
• A basic engineering notebook setup for kids costs under $5 and requires no special materials — a composition book and a pen are sufficient

What Professional Engineers Actually Write Down

The engineering design notebook is not a journal. It is not a shopping list. It is a dated, sequential, unedited record of the engineering process — including things that didn’t work.

At NASA, Jet Propulsion Laboratory engineers follow formal notebook guidelines that include:

• Dated entries (never out of sequence)
• Numbered pages (never removed or redacted)
• Ink, not pencil (unalterable record)
• Signatures of the engineer and a witness for significant design decisions
• Explicit recording of what was observed, what was hypothesized, what was tested, and what was concluded

The witness signature matters for patents. Patent disputes often come down to priority — who had the idea first, and when. A properly kept engineering notebook, with dated entries and an independent witness, is admissible evidence in US patent proceedings.

A less obvious but more practically important function: the notebook records dead ends. When a project fails and restarts, the notebook tells the engineer what was already tried. Without this, teams often repeat failed experiments — an expensive and demoralizing pattern that is remarkably common in undocumented engineering.

Why Documentation Changes How Kids Think

A 2018 study in the Journal of Engineering Education found that students who used structured engineering notebooks during project-based learning produced more refined final designs and demonstrated higher scores on design process assessments than students who built without documentation. The effect was strongest in multi-week projects where early decisions had to be revisited.

The mechanism is straightforward: writing down a decision forces explicit reasoning. “I chose a wider base because I predicted the arm would tip over” is different from vaguely feeling that wider is better. The verbal articulation of the reason makes it available for later review — and revision.

A kid who can look back at a notebook entry from two weeks ago and say “that assumption was wrong” is doing the same cognitive process that experienced engineers describe when they reflect on failed projects. The notebook makes the process systematic rather than accidental.

Setting Up an Engineering Notebook for Kids

Materials: Composition book (sewn binding — pages can’t be removed without tearing), black or blue ink pen, tape or glue stick for attaching photos or printouts
Cost: Under $5

The five-element entry format:

1. Date — Always. Even if it’s the same day as the previous entry.
2. Problem — What specifically are you trying to do or figure out?
3. Design/Plan — What approach will you try, and why? Draw if helpful.
4. Test/Build — What actually happened?
5. Result/Next — What did you learn? What’s the next question?

That’s it. For kids starting out, even 5–10 lines per session is sufficient. The habit matters more than the volume.

The Patent Log Format (Ages 13+)

For older kids who want a more authentic engineering notebook experience, the patent log format adds two elements:

• Witness signature line: A parent or sibling signs and dates each significant entry as an independent witness. This mirrors the legal function of a professional engineering notebook.
• Prior art note: For each significant design decision, one line noting whether this approach was inspired by something existing (“adapted from hydraulic arm design in previous project”) or appears to be novel (“new approach — no prior reference”).

These additions sound overly formal, but they teach intellectual humility (knowing what you didn’t invent) and precision (knowing exactly what you did).

How to Use Photos in the Notebook

Smartphones make this much easier than it was for engineers even 20 years ago. The best practice for a home engineering notebook:

At each build session: Take 2–3 photos of the current state of the project. Print them (small, 3x4 inches works fine) and tape them into the notebook on the same day. Caption each photo with what it shows and why it was worth documenting.

When something fails: Photograph the failure. “This is what it looked like when the joint gave out” is more informative than any written description and takes five seconds.

For circuit projects: A photo of the breadboard layout at a point when the circuit is working is worth ten schematic diagrams, because it shows what was actually built, not what was planned.

Documentation element	Purpose	Frequency
Date	Establishes timeline, required for patents	Every entry
Problem statement	Clarifies what you’re solving before you start	Every session
Design sketch with labels	Records the plan and reasoning	Before major build steps
Results	Captures what happened vs. prediction	After every test
Photos	Visual record of build state	At key milestones and failures
Next steps	Preserves continuity between sessions	End of each session
Witness signature	Legal function; intellectual discipline	At major milestones

How to Teach Your Kid About Engineering Documentation

Ages 5–8: The Build Diary

At this age, the notebook is informal. After any building session — Lego, cardboard, play-dough — ask your kid to draw what they made and write (or dictate) one thing that worked and one thing they’d change next time. You’re not teaching documentation; you’re teaching reflection. That reflection habit is the precursor to engineering notebook thinking.

Ages 9–12: The Five-Element Entry

Introduce the five-element format above. Before the next project session, write the date and problem together. After the session, fill in results and next steps. Resist the urge to make it neat — the notebook should capture messy, real thinking. A crossed-out line with a note about why you changed your mind is more valuable than a tidy entry that obscures the reasoning.

Ages 13+: The Full Engineering Log

Use a sewn-composition book and the patent log format. Require your kid to write the problem statement before touching any materials. Require a photo per session, taped in with a date and caption. At the end of a project, spend 20 minutes reading back through the notebook together and identifying: what changed from the original design, and why?

The question to ask: “If someone else read only your notebook — without any explanation from you — could they figure out exactly what you were trying to do and why you made the choices you made?”

What to Watch For Over the Next 3 Months

Month 1: The documentation habit rarely sticks immediately. Most kids find it tedious at first. The trick is to make the notebook review ritual explicitly useful — start each session by reading the previous session’s “Next steps” entry together. When kids see the notebook save them from repeating a mistake, its value becomes concrete.

Month 2: Watch for whether the notebook is capturing design decisions or just build history. “I built the frame today” is build history. “I made the frame 15cm longer because the original was tipping forward under arm weight” is design decision — and it’s what engineers document. Help your kid identify which entries are which and upgrade the design-decision ones.

Month 3: At three months, a kid who has maintained the habit has a tangible artifact of their own engineering process. Reading back through a three-month notebook with them is a powerful exercise in recognizing growth. How did the quality of their reasoning change between the first entry and the most recent? This metacognitive reflection is itself a high-level learning skill. See engineering mindset research on how failure drives learning for the science behind why recorded iterations accelerate skill development.

Also see project-based learning for the research on why engineering design as a process — not just a product — is what produces durable skills.

Frequently Asked Questions

Does the notebook have to be physical, or can kids use a digital tool?

Both work, with trade-offs. Physical notebooks are better for drawing, can’t be accidentally deleted, and are legally stronger documents. Digital tools (Notion, Google Docs, OneNote) allow photo embedding and are easier to search later. For young kids: physical. For teens who are already comfortable in digital tools: digital with a consistent template is fine.

What if my kid doesn’t want to write — they just want to build?

Start by making the notebook faster to fill in: replace full sentences with bullet points, allow sketches instead of descriptions, make photos do most of the work. The minimum viable notebook entry is: date, one-sentence problem, one photo, one-sentence result. That’s 3 minutes and captures the essential record.

How is this different from a school lab report?

A lab report is written after the fact for an audience (the teacher). An engineering notebook is written during the process for yourself. Lab reports require clean prose and formal structure. Engineering notebooks allow any format that captures thinking accurately. The purpose difference matters: notebooks are tools for thinking, not performance.

At what age should kids start?

Any age is appropriate with the right format. Ages 5–7: picture-based diary after play. Ages 8–11: five-element simple format. Ages 12+: full engineering log with photos and reasoning. The habit of reflecting on what you built and why is developmentally appropriate at any age — the documentation format scales with the kid.

---

About the author Ricky Flores is the founder of HiWave Makers and an electrical engineer with 15+ years of experience building consumer technology at Apple, Samsung, and Texas Instruments. He writes about how kids learn to build, think, and create in a tech-saturated world. Read more at hiwavemakers.com.

---

Sources

1. Dym, C.L., et al. (2005). “Engineering Design Thinking, Teaching, and Learning.” Journal of Engineering Education, 94(1), 103–120. https://doi.org/10.1002/j.2168-9830.2005.tb00832.x
2. NASA. (2016). NASA Engineering and Safety Center: Documentation Standards. https://www.nasa.gov/offices/nesc/home/
3. United States Patent and Trademark Office. (2023). Keeping Records of Your Invention. https://www.uspto.gov/patents/basics/keeping-records
4. Cross, N. (2011). Design Thinking: Understanding How Designers Think and Work. Berg Publishers.
5. Atman, C.J., et al. (2007). “Enabling Engineering Student Success: The Final Report for the Center for the Advancement of Engineering Education.” American Society for Engineering Education.
6. Schön, D.A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.