Perseverance and Problem Solving

Makey Makey, Raspberry Pi

What a lucky kid. Seventh grader C is an active participant in our library’s summer reading club. Last year, his first year participating in the teen program, he won the big tech-focused prize: a Raspberry Pi setup. This year, he was one of the random drawing winners again, and selected the MakeyMakey*.

excited price is right prize winner

When he and his mom stopped by the library’s table at the Junior High’s registration night to tell me what he’d been up to with all of this tech, he was glowing, and his mom was excited too. And just what had he been up to? Building a media server for his house. With the prize he won from the library for reading books.

I asked him to come over to the library some time and chat about what he’d learned, and hoped he’d share his ideas on technology in the library. We had a really interesting conversation. I showed him the pieces that I’ve been collecting for our circulating technology collection, and he had some great ideas on how to promote the collection. There was definitely more than a spark of curiosity and hunger when I asked if he would help me figure out how to use the tools.

When I asked what he had learned while working with these tools, I expected to hear about how he’d learned a lot about programming in Linux. Or how he’d discovered some fun vintage games online while looking for ways to play with the Makey Makey. What I didn’t expect was an answer that we can all learn so much from.

“I would say, perseverance and problem solving. Definitely. Yeah.”

My librarian heart grew three sizes.

grinch heart growing

This is, of course, the “right” answer. It’s the one we hope for, and the one that here, at the Robot Test Kitchen, we believe in sincerely. But it’s not the answer we often hear the young people we work with repeat. We hear about the fun they had finding the vintage games. We hear about their new sills in Linux. And though we might see them persevering and problem solving, those aren’t the skills they can usually pull out as evidence of their learning. What made the difference here that allowed this teen to make and then verbalize that connection so unwaveringly? I think there are several elements at play here.

First, he has ready access to the tools he used. He had them in his home, and he had time to use them.The ability to approach the technology on his own terms, when he’s in the frame of mind to be open to trial and error is key. This is obviously not a possibility for a lot of teens. But an ongoing club setup or open Makerspace time at the library could provide similar access.

Second, he has a great support network at home. Both of his parents are involved in engineering, so he had people to bounce ideas around with, and more likely than not, he had someone to fish him out of the weeds if he got in too deep. Again, not all teens have this, but this is an area where that same club setup and the supportive co-learning environment of Makerspaces fills that need.

Third, he had open ended time and opportunity. There was no assignment and there was no deadline. Assignments and deadlines certainly have their place, but for this teen, the blank slate of opportunity allowed him to be creative, think about what he wanted and needed from the tech, play, revise, start over, settle in to the detailed work required, and finally triumph with a project that was meaningful.

I’ve been doing a lot of reading lately on the benefits of summer reading program for teens whose reading skills are more established and don’t slide over the summer like those still developing reading abilities. What I’ve learned is that more than minutes spent or pages read, the most significant impact for teens in developing a love of reading, or increasing the perceived value of reading, is engagement. It’s seeing that adults care that they are reading, want to hear about what they think of the books they find, and encourage and champion them to read more.

I believe that technology literacy is largely the same. If we can encourage engagement with the technology by providing time, access, and support, the minutes spent on tech and the lines of code created will likely increase. But more than those quantifiable results, the teens will want to come back to it because they will be developing those Assets that have proven to lead more teens into successful adulthood.  It’s not about the tech. It’s not about the library. It’s about the people.

*I’d like to point out here that the total cost of the prizes he won this year is far less than many of the big draw prizes that some libraries offer. Another prize option, the gift card to the local book store, had a higher dollar amount. Sometimes -maybe most of the time- the biggest splash doesn’t come from the most expensive, shiniest tech.

Meet us at Tech Soup’s Teens & Tech Webinar


Next Wednesday, May 20th, Tech Soup is hosing a free webinar on Teens & Tech: Creating Successful STEM Programs in Libraries. Robot Test Kitchen is one of the two projects that is going to be featured, and we would love for you to join us! If you’ve been reading along with the blog and can appreciate the TechSouplogoTrue Confessions and have been encouraged by watching us try things, stumble, and keep on going, we really think you’ll get a lot out of the webinar. We did a rehearsal the other day with the other presenter, Amanda Allpress of Shasta Public Libraries, and she’s got some great stories to tell as well about involving teens in graphic design and more! It’s a quick hour, and there will be lots of time to share ideas and ask questions. Join us!

Let’s explore support: know what you need

True Confessions

Next up in this exploration of support as an issue in and barrier to technology programming for teens and youth gets down to brass tacks. Get out your pencils!

making a list by zephra on morguefilePart of knowing what you need is acknowledging that you have, within your reach, certain types of support already. For some, this acknowledgement is a huge step. It means that one excuse for not proceeding – not having the support and resources you need – no longer exists.

“But wait!” you’re saying, “I don’t have support! I’ve got zero budget as it is, and they just thrust this on me with no more time off desk to plan, and it’s not like my program closet’s full of Minestorms or anything!” Ok, ok, that’s valid. Still, within that we start to see a structure emerge of what you currently have, as well as what you lack. Like, for starters, you’ve got a program closet!

In all seriousness though, it helps to make a list. Consider what you might add to the following categories:

Things I have:


  • Who in the building can help me? Who can I bounce ideas off of?
  • Who do I know nearby with skills I could draw on?
  • What kids do I know who would definitely be excited about STEM programs?
  • Who here in the building wants this effort to be successful?


  • What programs am I already doing that use STEM?
  • What programs am I already doing that could incorporate STEM?
  • What programs have I heard or read about that sound interesting?
  • What resources (books, websites, Pinterest boards) can I draw upon?

Time and Funds

  • When do I usually plan my programs? How much time do I spend planning programs now?
  • Will STEM programs supplement our current schedule or replace less successful offerings?
  • How can I streamline any planning processes (order kits instead of assembling piecemeal? use program plans that someone else has created? use a peer-leadership structure?)?
  • What additional time will I need to start doing STEM programs (consider workshop attendance, idea generation, practice time, shopping time, etc)?
  • What can I give up or delegate to make this time?
  • What is my budget for supplies and resources?

If you work through this thought exercise, you may realize that you already have more than you thought you did. You’ll probably also note some gaps. This is what you need. Knowing where these gaps are is going to help you narrow your focus when seeking support. If you can sit down with the powers that be and confidently say “In order to do three STEM programs a quarter, I’m going to need someone else to take half of my Tuesday afternoon desk shift this month. I’d like coworker X to be off desk one of those afternoons too because I could use her expertise to help plan more efficiently. Given the budget of $30, I can do programs 1 and 2, but if there’s another $20 somewhere, I could serve this many more kids or offer program 3 also.”

A lot of this ties back in to the advocacy pieces recently discussed but here, the need for STEM is more or less assumed and you’re advocating for support. Knowing and then articulating what you need demonstrates a few different things. It shows that you’ve put thought into the overall approach you’re going to take. It points out the time and budget realities of revamping your program plan or adding a whole new type of programming. And it clarifies for you what you are going to need in order to proceed toward success.