Session 7: Leading reflection conversations

How will you lead reflection conversations? :thinking:

Share your list of 5–15 questions to ask learners during the workshop or during wrap up. Check out other responses below for inspiration. :bulb:

My questions for during the workshop:

  1. What are you making?
  2. What have you tried so far?
  3. (If they’re having trouble) Have you tried…?
  4. How did you come up with that? or How did you get to that result/conclusion?
  5. Can you walk me through your thought process?

Questions for after the workshop/wrap-up:

  1. What did you learn today?
  2. Where did you have trouble? What did you do to solve it?
  3. If you could do this over, what would you do differently?
  4. How would you explain this project to a friend?
  5. What is your advice for future participants doing this project?

In my job I’m always asking people what they’ve tried so far and suggest some solutions. Usually that’s enough to get them out of whatever wall they’ve found themselves in front of, and they say how “stupid” they were for not realizing that sooner. I always remind them that no one is born knowing this (including me!), that they’ve done a lot of things right (or that I would’ve done), and so long as they keep trying, they’re doing amazingly.

As for answering like a participant… The one thing I would suggest to others in this is to do two Paper Circuits: one to get the idea behind it, and the other to perfect it. At my program this past Saturday, I had one person make one that worked okay, but the second one she made worked flawlessly. This was actually my coworker’s suggestion and I’m pleased to say he was right! :slight_smile: The more often you do something, the better at it you become.

1 Like

I love your suggestion! The best part of working with inexpensive materials is that I don’t feel like I’m using up future opportunities to do other cooler projects. Creating a first version to make sure everything works is a learning experience.

In engineering, business, software, and even film-making, it’s called proof of concept, or proof of principle. So what you’ve facilitated is also a design and engineering practice! :partying_face:

1 Like

I too like the suggestion! Sometimes it isn’t about creating the best version of your product first, rather learning the fundamental skills and common areas where things might need improvement. That way you have a better idea at what needs to be done for the next time.:bulb:

2 Likes

@adodd I agree completely!

@ada I love “proof of concept”! That’s so true, I completely forgot. Though I did refer to my testing with my teams as “alpha” (my team members who will lead this at their branches) and “beta” (my two branches where I lead). The alpha phase showed me a lot of the bugs that needed to be worked out - both on the project’s end and on mine - while the beta allowed me to refine things even further and see how well a non-tech group could handle it.

1 Like

My reflection questsions are:

  1. Tell me about what you’re working on . . .
  2. What is your favorite part?
  3. What was the biggest challenge?
  4. How’d you decide on [insert design feature here]?
  5. If you hadn’t done [insert design feature here] how would it be different?
  6. What did you learn?

In the programs that I facilitate, I like to ask participants to tell me about what they’re working on as it’s open-ended. Sometimes I get really long, detailed responses and sometimes I get a few words. The question allows the participant to decide what to share and shows that I’m not trying to suggest what they should have done or what they do next.

3 Likes

These are great reflection questions, @Trisha! While sometimes it may be hard to get responses out of participants, it it important to include these reflections within the programs. Even though some people may not want to answer share out loud, asking them to reflect on their work might start the process of them internally reflecting and help improve their future work.

love these questions :heart: :pray:

2 Likes

Here are my reflection questions:
Were you able to get your project to work?
How many tries did it take to get it to work the way you wanted?
Were there any adjustments or changes you had to make?
Do you think you always have to have a project look exactly like an example?
How did you feel about this project?

1 Like

@michelleb Thank you for sharing these. I like how they refer to the challenges of doing the activity, as well as the process of iterating!

Be sure to celebrate the troubleshooting process as a form of investigative play, even if your patron doesn’t complete the project.

Instead of asking “how many tries did it take to get it to work the way you wanted?” which prompts people to mentally count the number of attempts, try to probe their creative troubleshooting. Asking questions like, “What are the different methods you tried?” and “How did your vision for your project change as you worked on it?” helps to signal your interest in their creative process and improvisation. Plus it puts less pressure on them to finish their project in a limited time period.