
Thinking in Slices
Right now, our 7th graders are working on a challenge that fits inside an envelope. Each student is designing a kit card: a flat frame, 3 by 5 inches and no more than a quarter inch thick, with pieces that snap out and assemble into something three-dimensional. When it's finished, they'll mail it to someone in their life. That person will open the envelope, pop out the pieces, and build something made just for them.
Before anyone touches a computer, students plan their designs on a 3-by-5 index card and, I’ll be honest, this part is frustrating for them. They have a clear picture in their heads of what they want to make, and an index card doesn't make it easy to get there. It's also exactly where the learning happens.
A few students want to build a game that needs a ball, which means they need a sphere. Their first designs were thoughtful and carefully drawn, and, it turns out, they were cylinders. A circle cut from a flat card gives you a disc, and a stack of identical discs gives you a cylinder no matter how many you add. A sphere works differently. Every slice is a slightly different size, growing toward the middle and shrinking again toward the edges. Walking through why their designs had turned into cylinders, and what a sphere actually requires, felt like an important learning moment. You could see students rethinking a shape they thought they already knew.
That kind of thinking is hard to rush. When students move into Tinkercad to build their frames, the software will make precise measurements and clean edges easy. What it can't do is realize for them that a sphere is a series of changing circles. Students need to work that out first, and paper is a good place to do it.
Our 6th graders are following a similar path. In a class I'm co-teaching with Mr. Twadell, students are designing personal logos. They start with sketches and go through several rounds of ideation and iteration before their designs become digital files and, eventually, physical objects made with our digital fabrication tools. By the time they reach the computer, they know what they're trying to say.
When we talk about technology earning its place at Brookwood, this is a lot of what we mean. The digital tools in these projects are powerful, and students will use them well, in part because they've already wrestled with the problem on paper. And when the 7th grade project is done, someone in your child's life will open an envelope with something inside that only your child could have made.
Nuts and Bolts: Owning Your Account
For students in grades 4 through 8, a Brookwood Google account is one of their first real digital responsibilities. A few habits make a big difference:
- Know your password. It's worth practicing until it's automatic. If your child forgets theirs, our tech team can help them reset it during the school day.
- Keep it private. A password isn't something to share with friends, even close ones.
- Sign out of shared devices. On a classroom MacBook, a library computer, or a friend's laptop, signing out keeps your work and your account your own.
What I'm Starting to Read
I just picked up The Great EdTech Pivot by Natalia Kucirkova, who leads the International Centre for EdTech Impact. I'm only a few pages in, but I was drawn to her central idea. She argues that for years, educational technology was built to scale first, reaching as many students as possible as quickly as possible. Now the field is starting to shift toward tools designed around how children actually learn. She also offers a framework for evaluating whether a tool is worth using, which feels close to the questions we ask at Brookwood. I'll share more as I read.
Need Tech Help? If you have questions about technology at home, email [email protected], and our team will get back to you during the school day. I'd also love to hear what would help: topics you'd like to see in this column, or ways Brookwood could better support families.
David Saunders
Director of Changemaking, Leadership & Technology












.png&command_2=resize&height_2=85)
.png&command_2=resize&height_2=85)







