Hands-On Learning and Mentorship: Learning by Doing With Support

Hands-on learning and mentorship belong together because doing something yourself and having someone help you understand what happened are two halves of the same process. Practice gives you experience. Feedback tells you what that experience shows. Reflection is where you decide what to change. Leave out any one of those, and learning slows down.

This guide is for undergraduates and graduate students learning through projects, labs and placements, for the mentors who support them, and for educators running hands-on activities with younger learners. It explains how the three pieces fit, gives examples, and offers a reflection framework you can use straight away.

Practice, feedback and reflection

Each part does a different job.

• Practice is doing the real thing: running the experiment, writing the code, building the prototype, teaching the lesson. You learn things by doing that you can’t learn by watching.
• Feedback is information about how it went, from a mentor, a peer or the results themselves. Good feedback is specific and tied to what you were trying to do.
• Reflection is your own thinking about the experience and the feedback: what you noticed, what you make of it and what you’ll do next.

They work as a loop. Reflection shapes your next attempt, the next attempt produces new feedback, and so on.

A mentor strengthens every stage. They choose tasks that stretch you without overwhelming you. They notice things you’d miss. And they ask questions that prompt reflection rather than handing you answers.

Common formats

Formats for mentored, hands-on learning

Formats for mentored, hands-on learning

Format	What it looks like	Where feedback comes from
Apprenticeship-style	Working closely alongside an experienced person on their real work	Frequent, informal comments in the moment
Project-based	Taking a defined project from start to finish	Milestone reviews with a mentor or instructor
Lab or research placement	Joining an ongoing research project	Lab meetings, a supervisor and graduate students
Makerspace or studio	Building and testing physical or digital designs	Peer critique, staff guidance and testing results
Classroom or club activity	Structured activities for younger learners	The educator or mentor leading the session

How much guidance is right?

Too little guidance and a learner can flounder, repeating mistakes without knowing why. Too much and they never practice the thinking themselves. A useful approach is to match support to the learner’s current skill and reduce it gradually: show, then do it together, then let them lead while you watch, then check in less often.

A practical rule for mentors: before you explain, ask. “What do you think happened?” often reveals whether a learner needs a hint, a demonstration or just time.

Giving feedback on work in progress

Feedback is most useful when it’s:

• Timely, while the work is still fresh.
• Specific. “The labels on this graph are hard to read at this size” is more useful than “The figure needs work.”
• Focused. One or two points the learner can act on next time, not everything at once.
• Two-way. Ask what the learner thinks first, then add your perspective.

Learners can help by asking for the kind of feedback they need: “Could you look mainly at whether my method section is clear?”

A reflection framework you can use

This guide uses four short questions. Answering them takes five to ten minutes after a work session, lab, lesson or project milestone.

1. What did I try? Describe what you actually did, briefly and factually.
2. What happened, and what surprised me? Results, reactions, problems and anything unexpected.
3. What feedback did I get, and what do I make of it? From a mentor, peers or the results. Note where you agree and where you’re unsure.
4. What will I do differently next time, and how will I know it worked? One concrete change, and a way to check it.

Keep your answers in one running document so you can see patterns over weeks. The format is simple enough to share with a mentor before a meeting.

Reflection log template

Reflection log template

Question	Your notes
What did I try?
What happened, and what surprised me?
What feedback did I get, and what do I make of it?
What will I do differently, and how will I know it worked?

To connect reflections to longer-term aims, pair this log with the mentorship meeting and goals template and our guide to setting mentorship goals.

Examples

These examples are invented for teaching purposes. They don’t describe real people or programs.

An undergraduate in a lab. Example: a student’s first attempt at preparing samples gives inconsistent results. In their reflection, they note that they changed the timing between steps without meaning to. Their graduate student mentor confirms that timing matters and shows them how the lab records each step. Next time, the student uses a written checklist and compares the results.

A graduate student learning to teach. Example: after leading a discussion section, a graduate TA reflects that students went quiet when asked open questions. A faculty mentor suggests giving students a minute to discuss in pairs first. The TA tries it the following week and notes how many more students speak up.

An educator running a STEM activity. Example: a teacher runs a simple bridge-building challenge with paper and tape for a group of young learners, with adult supervision throughout. Several bridges collapse quickly. Instead of fixing them, the teacher asks each group what they noticed about the ones that held. The groups try again, and the teacher ends with a two-minute discussion about what changed. For more activity ideas, see STEM mentoring activities, and for broader guidance, our pillar on mentoring kids through STEM.

Running mentored projects with limited resources

Hands-on learning doesn’t require expensive equipment. A few approaches help:

• Use everyday materials for physical activities, and free software for digital ones.
• Mentor in small groups, so one mentor can support several learners, with peers giving each other feedback.
• Schedule short, regular check-ins instead of long, rare ones.
• Make reflection the routine. The four questions cost nothing and work in any setting.

Common pitfalls

• Doing it for the learner. It’s faster in the moment, but the learner misses the practice.
• Feedback without follow-up. If there’s no next attempt, feedback can’t be used.
• Reflection as a formality. Vague reflections (“it went fine”) don’t lead to change. Push for one concrete point.
• Too many goals at once. Focus on one or two skills at a time.

For more on building a mentoring relationship around this kind of learning, see our pillar on mentoring and mentorship.

Common questions

Do I need a formal mentor to learn this way?

No. Feedback can come from peers, instructors or the results themselves, and the reflection questions work on your own. A mentor makes the cycle faster and richer, but you can start without one.

How often should I reflect?

After any session where you tried something new, or at least weekly on an ongoing project. Short and regular beats long and rare.

What if the feedback I get is vague?

Ask a follow-up question that narrows it down, such as “What’s the one thing you’d change first?”

A practical next step

After your next lab session, class, project meeting or activity, set a timer for ten minutes and answer the four reflection questions. Bring your answers to your next conversation with a mentor or colleague.