Carr Kids HQ
Enter your PIN to continue
Unit 2 of 6 · 8th Grade Language Arts

The Build Log

Engineering and making as writing — document a build from first sketch to finished product.

Weeks
7–12 (October–November)
Anchor Text
The Boy Who Harnessed the Wind (Kamkwamba) + engineering articles
Writing Focus
Technical · Expository · Process Writing
Computer Tool
Google Docs (formatted technical doc) + camera/photos
Showcase
Illustrated Build Log with technical documentation
Standards
OR W.8.2 · W.8.4 · W.8.2d · RI.8.3 · SL.8.4
Key Vocabulary — 5 Words This Unit
technical writing — clear, precise writing that explains how something works or how to do something
iteration — the process of repeating and refining a design or process based on what you learn each time
documentation — a written record of a process, decision, or result
design brief — a planning document that states a project's goal, materials, constraints, and success criteria
expository writing — writing that explains or informs, organized to make the information easy to follow
W1Reading Technical Writing
Mon Intro to The Boy Who Harnessed the Wind ch. 1–3; what makes engineering writing compelling? Reading▾
  1. Get "The Boy Who Harnessed the Wind" and read chapters 1–3.
  2. As you read, notice: does the author explain HOW things work, or just that they work?
  3. Find one passage where he describes building or fixing something. Put your finger on it.
  4. Say out loud: "The most interesting part about how he describes building is…"
  5. Write one sentence in your journal about what makes this kind of writing interesting.
✓ Done when: chapters 1–3 read + one observation written in journal
Tue Read a real engineering field notebook page; analyze structure and purpose Reading▾
  1. Read through the engineering field notebook page without stopping to analyze — just take it in.
  2. Now look again: how is it organized? Lists? Sketches? Numbered steps? Dates?
  3. Say out loud: "The field notebook is organized by _____ because _____."
  4. Write 2 things you notice about its structure in your journal.
✓ Done when: notebook page read + two structural observations written
Wed Write a "day one" entry: describe how something you own works, step by step Writing▾
  1. Pick something you use every day — a controller, headphones, keyboard, or tool.
  2. Pick it up and examine it. Press the buttons or move the parts.
  3. Say out loud: "This works by…" Explain the whole thing out loud first.
  4. Write 5 numbered steps explaining how to use it or how it works.
💬 Sentence starter: "Step 1: First, you…" Each step = one action.
✓ Done when: 5 numbered steps written about one familiar object
Thu Type and format your entry with headings, numbered steps, and a diagram description Computer▾
  1. Open Google Docs and start a new document.
  2. Add a heading at the top: "Day One Log — [name of object]"
  3. Add a bold subheading: "How It Works"
  4. Type your 5 numbered steps from yesterday.
  5. Add one more section called "Diagram Description" and describe what a labeled drawing of this object would show.
✓ Done when: Google Doc created with heading, numbered steps, and diagram description section
Fri Write a project proposal — your first piece of technical writing for the unit Writing▾
  1. Read a short sample project proposal your teacher gives you — notice it has three parts: what the project is, what it will do or look like when finished, and what materials are needed.
  2. Decide on your build: a LEGO original design, a model from other materials, or a simple circuit. Talk it through out loud first: "I want to build _____ because _____."
  3. Open Google Docs and write a 3–4 sentence project proposal. Name your project, describe what it will be, and explain why you chose it.
  4. Add one final sentence: "The main challenge will be _____, and I'll handle it by _____." — this is called a risk acknowledgment, and real engineers write it too.
💬 Talk option: Pitch your project out loud to your teacher first — explain what you're building and why. Then write the 3–4 sentences from what you said.
✓ Done when: 3–4 sentence project proposal + risk sentence saved in Google Docs
✍️ Writing Prompt

Pick an everyday object (a zipper, a pencil, a door hinge). Describe how it works as if explaining to someone who's never seen one.

Starter: "This object has _____ parts. The way it works is…"

Write 4–6 sentences. Talk it out loud first, then write it. Use numbered steps if that helps.

✅ Weekly Checklist
W2Process & Documentation Basics
Mon Kamkwamba ch. 4–7; how does he describe failure and iteration? Reading▾
  1. Read chapters 4–7 of The Boy Who Harnessed the Wind.
  2. Find one place in the book where something breaks or doesn't work.
  3. Say out loud: "He failed because _____, then he fixed it by _____."
  4. Write that sentence in your journal.
✓ Done when: chapters 4–7 read + one failure-and-fix observation written
Tue What is iteration? Design thinking: problem → sketch → build → test → revise Reading▾
  1. Write these 5 words down with space between each: Problem → Sketch → Build → Test → Revise
  2. Write one sentence for each word saying what happens at that step.
  3. Then say out loud: "Design thinking is like a loop because…"
  4. Connect it to your build project: "My loop will work like…"
💬 Starter: "Problem means you figure out what you're trying to solve. Sketch means…"
✓ Done when: 5-step cycle written with one sentence each
Wed Write a design brief for your build: goal, materials, constraints, success criteria Writing▾
  1. At the top of a page write: "DESIGN BRIEF — [your project name]"
  2. Write 4 sections with space between each: Goal, Materials, Constraints, Done When.
  3. Fill in Goal: what you're building and why (1–2 sentences).
  4. Fill in Materials: list everything you'll need.
  5. Fill in Constraints: any limits (time, space, parts available).
  6. Fill in Done When: what your finished build will do or look like.
💬 Starter: "My goal is to build _____ so that _____."
✓ Done when: all 4 sections of design brief filled in
Thu Create your design brief in Google Docs with headings and formatting Computer▾
  1. Open Google Docs and start a new document.
  2. Title: "Design Brief — [your project]"
  3. Add each section from your handwritten brief as a bold heading: Goal, Materials, Constraints, Done When.
  4. Type the content under each heading.
  5. Make the 4 headings bold so they stand out visually.
✓ Done when: design brief fully typed and formatted in Google Docs with 4 bold headings
Fri Begin the physical build; photograph stage 1 Kinesthetic▾
  1. Gather all your materials and lay them out.
  2. Take a "before" photo — everything laid out before building starts.
  3. Begin building — just the first stage (base, foundation, or frame).
  4. When you finish stage 1, take another photo.
  5. Write one sentence: "Stage 1 is done — it looks like _____."
✓ Done when: building started + at least 2 photos taken + stage 1 described in one sentence
✍️ Writing Prompt

Write a design brief for your build. Include your goal, materials list, any limits (time, size, cost), and how you'll know when it's done.

Starter: "My goal is to build _____ so that _____. Materials I need: … I'll know I'm done when…"

Aim for complete sentences, but a bulleted materials list is fine. Talk it out first.

✅ Weekly Checklist
W3Step-by-Step Technical Writing
Mon Finish Kamkwamba; how does he mix storytelling with technical explanation? Reading▾
  1. Finish reading The Boy Who Harnessed the Wind.
  2. Find one place where he's being technical but it also feels like a story — not just a list of facts.
  3. Say out loud: "He made the technical part interesting by _____."
  4. Write one sentence in your journal about that technique.
✓ Done when: book finished + one observation about mixing storytelling and technical writing
Tue Writing workshop: clear step-by-step instructions using active verbs Writing▾
  1. Think of something simple you know how to do (make a snack, set up a game, connect a cable).
  2. Write 5 steps in imperative (command) form: "Open the bag." "Take out two pieces." Each step = one action.
  3. Read your steps to someone — can they follow them exactly without asking questions?
  4. If they got confused, fix that one step.
💬 Imperative means a command. Start each step with a strong action verb: "Connect," "Place," "Attach," "Insert."
✓ Done when: 5 imperative steps written + at least one person confirmed they could follow them
Wed Write steps 1–10 of your build process with technical precision Writing▾
  1. Look at what you've built so far.
  2. Write Step 1 as a clear command: "Get out _____ and lay it flat."
  3. Write steps 2–10 — each one is one specific action.
  4. After step 4, add a checkpoint note: "Your build should look like _____ at this point."
  5. After step 8, add another checkpoint note.
✓ Done when: steps 1–10 written with 2 checkpoint notes
Thu Continue building; photograph each major stage; upload photos to doc Kinesthetic▾
  1. Continue your build, following your written steps.
  2. Every time you complete 3–4 steps, stop and take a photo.
  3. Label each photo briefly — "Stage 2," "Stage 3," etc.
  4. At the end of the session, upload the photos to your Google Doc next to the relevant steps.
✓ Done when: build progressed + photos taken and placed in Google Doc
Fri Peer review: follow each other's written instructions — do they actually work? Kinesthetic▾
  1. Give your written instructions (steps 1–10) to someone else.
  2. Watch them try to follow the steps — don't explain anything, just observe.
  3. Note where they get stuck or confused.
  4. Go back and revise at least one step that was unclear.
✓ Done when: instructions tested by someone else + at least one step revised for clarity
✍️ Writing Prompt

Write the first 10 steps of your build process. Each step is one specific action. After step 4 and step 8, add a checkpoint describing what the build should look like.

Starter: "Step 1: [Start with a strong verb — Attach, Place, Connect…]"

Say each step out loud before you write it — if you can say it clearly, you can write it clearly.

✅ Weekly Checklist
W4Explaining Your Choices
Mon Read: design rationale examples — how engineers explain WHY, not just WHAT Reading▾
  1. Read the design rationale example (the Pixar article or engineering excerpt).
  2. Notice: does the writer explain WHY they made choices, not just WHAT they did?
  3. Find one sentence that explains a "why" decision.
  4. Write in your journal: "A good design rationale explains _____ because _____."
✓ Done when: reading done + one observation about explaining WHY written
Tue Writing workshop: expository rationale — cause and effect, explaining decisions Writing▾
  1. Think of one choice you've made in your build (a material, a shape, a connection method).
  2. Write a "Because Statement": "I chose _____ because _____, not _____ because _____."
  3. Practice the same format for 2 more choices in your build.
💬 Say it out loud first: "I used this piece instead of that piece because it's stronger / fits better / looks the way I wanted."
✓ Done when: 3 "Because Statements" written — one for each design choice
Wed Write your "Why I Made These Choices" section — 3 key design decisions Writing▾
  1. Open your Google Doc and add a new section: "Why I Made These Choices"
  2. Write a rationale for 3 key decisions in your build.
  3. For each: (1) what you chose, (2) why you chose it, (3) what you could have done instead.
  4. Aim for 2–4 sentences per decision.
💬 Starter: "For the _____, I chose _____ instead of _____ because _____."
✓ Done when: 3 design decisions documented with reasoning (2–4 sentences each)
Thu Continue build; document any setbacks and how you fixed them Kinesthetic▾
  1. Continue building.
  2. When something goes wrong — and it will — stop and write: "Problem: _____. Fix: _____."
  3. Document at least one setback today in writing.
  4. Take a photo of what the build looks like now.
✓ Done when: build continued + at least one problem/fix documented + photo taken
Fri Mid-project share: show your build and read your design rationale aloud Discussion▾
  1. Show your build (in person or via photos) to someone.
  2. Explain what you're building in 2 sentences.
  3. Read your "Why I Made These Choices" section out loud.
  4. Ask: "Does my reasoning make sense? Is anything confusing?"
✓ Done when: build shown + design rationale read aloud to someone
✍️ Writing Prompt

Pick 3 choices you made in your build. For each one, explain what you chose, why, and what the alternative was.

Starter: "For the _____, I chose _____ instead of _____ because _____."

2–4 sentences per choice. Say each one out loud first — you already know the reasons.

✅ Weekly Checklist
W5Troubleshooting & Failure Writing
Mon Read engineering post-mortems and failure analysis examples Reading▾
  1. Read the engineering post-mortem or failure analysis examples provided.
  2. Notice: does the writer blame people, or analyze what happened?
  3. Find one sentence that describes a failure honestly.
  4. Write in your journal: "Good failure writing is different from just complaining because _____."
✓ Done when: reading done + one observation about failure-writing style noted
Tue Writing about failure honestly — what went wrong, what did you learn? Writing▾
  1. Think about one thing that didn't work the way you planned in your build.
  2. Write these 4 things (one sentence each):
  3. What I expected to happen: ___
  4. What actually happened: ___
  5. Why I think it failed: ___
  6. What I changed: ___
💬 Say it out loud like you're explaining it to a friend: "So what happened was…"
✓ Done when: 4-part failure analysis written for one problem
Wed Write "Problems & Solutions" section — at least 2 failures and fixes Writing▾
  1. Open your Google Doc and add a new heading: "Problems & Solutions"
  2. Use the 4-part format from yesterday for at least 2 problems.
  3. Add one final sentence: "The most important thing I learned from these problems was _____."
✓ Done when: "Problems & Solutions" section written with at least 2 failures + a learning note
Thu Finalize the build; take final photos; compile full photo set Kinesthetic▾
  1. Complete the build — add any finishing touches.
  2. Take 3–5 final photos from different angles.
  3. Place your hand or a ruler next to the build in one photo to show scale.
  4. Take one "hero shot" — the best angle that shows your build at its best.
✓ Done when: build finished + final photos taken (including a hero shot)
Fri Full build log draft review — check clarity, completeness, and formatting Discussion▾
  1. Open your Google Doc build log and read it from beginning to end.
  2. Check: Is there a photo for each major stage?
  3. Check: Do the steps make sense in order?
  4. Check: Is there a "Why I Made These Choices" and a "Problems & Solutions" section?
  5. Write a list of 3 things that still need work before the final version.
✓ Done when: full draft read through + 3 improvement notes written
✍️ Writing Prompt

Document at least 2 things that went wrong during your build. Use this format for each:

"What I expected: ___ / What happened: ___ / Why it failed: ___ / What I changed: ___"

Then write one final sentence: "The most important thing I learned was…"

Good engineers write about failure — that's how knowledge actually gets shared.

✅ Weekly Checklist
W6Final Document & Showcase
Mon Final revision of full build log — intro, steps, rationale, failures, conclusion Computer▾
  1. Open your Google Doc.
  2. Work through the 3 improvement notes you wrote on Friday — fix each one.
  3. After fixing each one, re-read that section. Does it read clearly now?
  4. Make sure all major sections are present: Design Brief, Steps, Why I Made These Choices, Problems & Solutions.
✓ Done when: 3 improvements made and all major sections present
Tue Format the document professionally — headings, photos, page numbers Computer▾
  1. Check that every section has a bold heading.
  2. Make sure photos are placed next to the steps they go with.
  3. Add page numbers (Insert → Page Numbers in Google Docs).
  4. Read through one more time for any typos.
✓ Done when: document formatted with consistent headings, photos placed, and page numbers added
Wed Write the conclusion — what did you build, learn, and what would you improve? Writing▾
  1. Open your Google Doc and add a final section: "What I Learned"
  2. Answer these 4 questions in 1–2 sentences each:
  3. What did I build?
  4. Did it do what I planned?
  5. What was the most important thing I learned?
  6. If I had more time, what would I improve?
💬 Starters: "My goal was to build _____ and in the end _____." / "If I had more time, I would _____."
✓ Done when: conclusion written (at least 4 sentences answering all 4 questions)
Thu Prepare 4-minute presentation — walk the audience through your build log Kinesthetic▾
  1. Decide which sections of your build log you'll walk through — you don't have to read all of it.
  2. Write a 3-sentence opening: "I built _____. The hardest part was _____. The coolest thing I figured out was _____."
  3. Practice saying your opening out loud once.
  4. Decide which 2 photos you'll point to during your talk.
✓ Done when: opening written + practiced out loud once + 2 photos picked for the talk
Fri SHOWCASE: Present your build and build log documentation Showcase▾
  1. Bring your physical build.
  2. Open your Google Doc build log on screen.
  3. Give your presentation: opening, walk through the log, point to photos, share one problem you solved.
  4. Answer any questions about your choices.
✓ Done when: showcase presentation complete — you built something and documented it! 🎉
✍️ Writing Prompt

Write the conclusion for your build log. Answer 4 questions: What did you build? Did it do what you planned? What was the most important thing you learned? What would you improve?

Starters: "My goal was to build _____ and in the end…" / "The most important thing I learned was…"

4–6 sentences total. Say it out loud first, then write it.

✅ Weekly Checklist
Unit Showcase

Illustrated Build Log

A complete technical document in Google Docs: design brief, step-by-step instructions with photos, design rationale, failure log, and conclusion. The physical build is presented alongside in a 4-minute walk-through for family audience.