Narrative Writing Through engineering

How I Use Build · Think · Create Task Cards to Teach Standards

In my 2nd grade classroom in Florida, some of our best narrative writing starts with a pile of bricks and a big engineering problem. When I pair building challenges with my Build · Think · Create task cards, students who usually freeze at a blank page suddenly have something they can’t wait to write about—and it still directly hits our Florida B.E.S.T. standards for narrative writing.[1][2]

Why I Start Writing With Engineering

Most of my students are strong problem solvers but hesitant writers. They’ll think through a challenge, build something clever, and talk endlessly about what it does—but the moment I say “Now write a story,” many shut down.

Florida’s ELA.2.C.1.2 standard asks second graders to “write personal or fictional narratives using a logical sequence of events, transitions, and an ending.” I found that if we start with engineering—asking “What’s the problem?” and “What could we build?”—students are naturally generating the story elements that standard requires: setting, characters, problem, solution, and sequence.

Instead of “Write a narrative,” my prompt becomes, “Tell the story of what you engineered and how it solved the problem.” That shift alone has unlocked writing for many of my low-to-mid students, especially those with attention and executive functioning challenges.

The Design Process as a Story Skeleton

I lean on a simple engineering design process: Ask, Imagine, Plan, Create, Improve. In my room, that’s not just STEM vocabulary—it’s the skeleton of our stories.

Here’s how we use it:

  • Ask – Beginning: What went wrong? Where are we? Who is involved?
  • Imagine/Plan – Middle: What solution will we try? What will we build?
  • Create/Test – Middle/climax: What happens when we try it? Does something break, change, or surprise us?
  • Improve – Ending: How do we fix or improve the design? How does the situation end?

Because my students hear this cycle over and over, it becomes a natural way to organize a narrative: “First we had a problem… Next we tried something… Then something happened… Finally we fixed it.” They’re meeting the standard, but they experience it as solving a challenge, not filling in a graphic organizer.

How I Use Build · Think · Create Cards in the Day

I design my Build · Think · Create Space Builders task cards to be flexible enough for classroom centers, morning tubs, or science/ELA crossover blocks. A typical 20-minute routine looks like this:[1]

  • 10 minutes – Build
  • 3 minutes – Oral story rehearsal
  • 7 minutes – Quick write

Here’s where it usually lives in our schedule:

  • ELA block: During narrative units, I use the cards as a writing center that directly targets ELA.2.C.1.2—fictional narratives with a clear sequence and ending.
  • Science/engineering: During STEM or science time, we treat it as an engineering challenge first, then capture the “story of the design” in writing.
  • Morning tubs: On soft-start days (buses late, kids arriving at different times), students build from a card and share quick oral stories as a warm-up, sometimes jotting one or two sentences.

Grouping and materials

  • Grouping: I usually put students in pairs or triads. They share materials, co-design, and then each writes their own version of the story.
  • Materials: Any basic building bricks, blocks, or STEM bins work; the cards are written so you don’t need a specific set.
  • Card organization: I keep 4 cards per tub (for example, four “Build the Rocket” cards in one bin, four “Build the Space Station” in another) so rotation is easy.

Clear routines—“Read, Build, Tell, Write”—are especially important for my students with executive functioning challenges. Once they know the pattern, the transitions get smoother and the focus lasts longer.[3][4]

A Concrete Example: Crash Landing

One of my favorite cards is: “Crash Landing – Build a rocket that has crash landed on a mystery planet. What happened?”

Here’s what this looks like in my room:

  1. Read and discuss the card
    I read the prompt aloud to the group and ask, “What problem do we think happened when the rocket crashed?” We brainstorm: broken engine, no fuel, strange weather, scary creatures, missing tools.
  2. Build the crash and the solution (10 minutes)
    Students build the crash scene and whatever they think will solve the problem—a repair robot, a shelter, a fuel machine, or a rescue vehicle. They’re using the Imagine/Plan/Create steps without realizing they’re planning a narrative.
  3. Oral story rehearsal (3 minutes)
    Before they pick up a pencil, I have them “tell the story of their build” out loud using transitions:
  • “First, my rocket crashed on a planet with…”
  • “Next, the astronauts built…”
  • “Then, something happened when they tried it…”
  • “Finally, they…”

We keep it short but focused. This oral step has been huge for students who usually struggle to organize ideas before writing.

  1. Quick write (7 minutes)
    Students write a 5–8 sentence fictional narrative. I remind them that the Florida standard wants a logical sequence, transitions, and a clear ending, and we point back to our engineering steps to make sure they’ve got each part.

What I love is that the writing feels like a natural extension of their play. They’re documenting the “adventure” of the rocket and the problem-solving that followed, not doing a random assignment.

Differentiation That Works in Real Classrooms

Because my community is mixed-level, I build differentiation into the routine instead of layering it on top. Some simple tweaks that have worked:

  • Read-aloud prompts
    I always read the card aloud first. Struggling readers aren’t blocked by decoding; they can jump straight into thinking and building.[1]
  • Visual anchors
    The build itself becomes the prewriting organizer. Students who need concrete visuals can literally point to parts of their structure as they tell the story.
  • Sentence stems and checklists
    On recording sheets, I often include stems like “First… Next… Then… Finally…” and a beginning/middle/end checklist that mirrors ELA.2.C.1.2 expectations.
  • Choice of cards
    Some cards are simpler (e.g., “My Rocket Ship,” “My Planet”), while others are more complex (“Emergency Alert,” “Alien Invention”). I can quietly steer groups toward prompts that match their current level.[1]

These small moves help students who might otherwise opt out of writing feel successful, and they keep the center doable for a busy teacher with limited time.

FAQ: For Teachers and Families

“Can I use this routine if I don’t have fancy STEM kits?”
Yes. I’ve used basic building bricks, generic STEM tubs, blocks, and even paper shapes. The key is the problem on the card and the story of how students solve it, not the specific materials.

“How does this support Florida’s narrative writing standards?”
Every card is a built-in plot: there’s a situation (often a problem), a response, and a resolution. When students write the story of their build with transitions like “first, next, then, finally,” they are meeting ELA.2.C.1.2’s requirement for fictional narratives with logical sequence, transitions, and an ending.

“Can families use this at home?”
Absolutely. Parents can follow the same pattern—read the card, build together, tell the story out loud, then capture a few sentences. It keeps writing connected to something tangible and fun.[9][10][1]


About me: I’m Lisa Decker, a 2nd grade teacher in Florida and a constructivist at heart. I create standards-based centers that let students build, think, and create their way into deeper reading and writing—not just memorize. If you try a narrative-through-engineering routine in your classroom or home, I’d love to hear how your students’ stories grow.

Leave a comment