Learn it
Pick one skill or tool you already know a little: a spreadsheet, a design app, resume formatting, study systems, a lab technique, a language. Get past the point of guessing.
Teach It Back · Start Here
Use something you know to help someone else succeed.
Teach It Back is a Project Launcher. This guide explains what it is, why it matters, and the first action that gets the project moving. From there, recurring video meetups, community support, feedback, and accountability help you keep building momentum.
The short version
You learn something, you use it on something real, and then you lead another person through it. Teaching is the part that turns a skill you sort of have into a skill you can prove. Your project is one small, repeatable session you designed, run with a host who agreed to have you, for an audience you picked on purpose.
The three moves
Apply it
Use it on something real first. You need one story where the thing worked, and one where it didn't, or the session is just a tutorial anybody could read online.
Teach it back
Design a short session for a specific audience, run it with a host, and capture what happened. Then run it again with one thing changed.
Popular topics right now
AI for nonprofit volunteersAI for resume improvementAI for student organizationsAI for community groupsSpreadsheet basicsStudy systemsCommunication tools
You don't need to be an expert. You need enough real-world experience to help a beginner get to a useful result.
Your first step
- 1Write down the one skill you could get a beginner to a working result with in under an hour.
- 2Write down three hosts who serve people who need it, and pick the easiest one to reach.
- 3Send four sentences: who you are, what the session would do for their people, how long it takes, and one date.
- 4Save the reply, even if it's a no, and use what you learn to shape the session.
The whole project starts with one conversation, and the hardest part is starting it before you feel ready.
Need a starting point?
If you want help shaping the session before reaching out, the Project Brief and Asset Inventory can help. They're optional planning tools, not required first steps.
Why this matters
Learn something. Use it. Help someone else succeed with it. In a fast-changing world, communities need people who can do all three.
Communities get stronger when knowledge moves
Knowledge doesn't have to flow one direction, from a classroom down. You learned it, so you can pass it to a club, a nonprofit, or a neighbor who needs it. A community gets stronger when people share what they learn while it's still fresh.
You're probably the first to learn it
Students are often the first to pick up new tools, tech, and workflows — sometimes before the professionals around you do. That puts you in a useful spot: far enough ahead to help someone take the next step.
Teaching is the proof, not the extra credit
Explaining a thing to a beginner exposes every gap you papered over. If you can get someone else to a working result, you know it.
It starts from what you already have
No blank page, no waiting for permission. The raw material is a skill you picked up in a class, a job, a club, or on your own.
Somebody in your reach needs it right now
A club that can't build a budget, a first-year who can't format a resume, a nonprofit whose volunteers never learned the tool they're paying for.
It repeats without permission
Once the session exists, running it again costs you an email. Second and third runs are where the numbers, the references, and the improvement story come from.
Get the project moving
Start by answering these three questions. You don't need a plan yet, and you definitely don't need slides.
- Name one skill you could get a beginner to a working result with in under an hour.
- Name one time you actually used it, and one thing that went wrong while you did.
- Name three groups who'd want it: a club, a class, a nonprofit, a team, a residence hall.
At a meetup, we'll help you pressure-test the skill against the audience, cut the scope down to something you can finish, and rehearse the ask you send your host.
What you actually do
Pick one audience, not everyone
"First-year business students who've never built a budget" is a project. "Students" is not. The narrower the audience, the easier every other decision gets.
Interview two or three of them
Ten minutes each. Ask where they get stuck, what they already tried, and what a good outcome looks like to them. You'll change your session after this.
Find a host who owns the room
A club president, an advisor, a professor, a nonprofit volunteer coordinator, a residence hall director. They supply the audience and the date. You supply the session.
Design a session people can finish
Thirty to sixty minutes. One outcome, one worked example, and hands-on time. Everyone should leave with the thing built, not with notes about building it.
Run it and capture it
Count who came, keep the materials, and collect a three-question exit check: what they can now do, what confused them, what they want next.
Change one thing and run it again
One change per run, so you know what caused what. Two or three runs is where this stops being a favor and starts being a project.
The hidden benefit: relationships
You'll think you're just running a session. You're also doing something bigger: putting yourself in a room with the people who run things — a club president, an advisor, a nonprofit coordinator, a library manager.
- You meet community leaders as a peer, not an applicant.
- You build a real relationship with your host before you ever need anything from them.
- You earn references from people who watched you work.
- You get known as the person who helps — which opens more doors than any cold email.
None of this is networking in the awkward, self-promotional sense. It's just what happens when you help somebody succeed.
What employers see
- You can transfer knowledge. Every new hire is expected to get someone else up to speed within a year. You've already done it with a group that had no reason to listen to you.
- You designed for an audience. You picked the audience, checked what they needed, and built to that. That's the same instinct behind good client work, good documentation, and good product decisions.
- You improved something on purpose. Run one to run two, you changed a specific thing and can say why. Employers pay for people who close the loop instead of moving on.
- You led without a title. You held a room that didn't report to you and kept them working. That's the skill most entry-level hires are missing.
- It's easy to verify. The host confirms it in one sentence, and the materials exist. Nobody has to take your word for it.
The part people skip
You practice the frameworks, not just the session
These are the names for what you're already doing. They're what a hiring manager is listening for when they ask a behavioral question.
Design thinking
You interview a few people in your audience, define the one thing they're stuck on, prototype a session, and improve it the second time you run it.
Storytelling
The session opens with the time you used this and it went sideways. That's what makes a beginner believe they can do it too.
Audience analysis
Skill level, motivation, time, and what they already tried. Everything you teach gets cut or kept based on those four answers.
Continuous improvement
Each run is one cycle. Note what landed, change one thing, run it again. Small experiments beat one big launch.
Teaching and facilitation
Explain, demonstrate, then get out of the way while they try it. Managing questions and quiet rooms is a practiced skill, not a personality trait.
Leadership
You set the outcome, held the time, and got a group of people to finish something together. That's the job, at any level.
Proof artifacts to keep
- The session plan: audience, outcome, timing, and the worked example you used.
- The materials: handout, slide, template, or checklist people took with them.
- Attendance and reach numbers for each run, with dates.
- The exit check results, including the confusing parts you fixed.
- A short before-and-after note on what changed between run one and run two.
- One photo or screenshot of the session with your host's permission.
How you earn the reference
The host is your reference, and you earn it during the project rather than asking for it at the end.
- 1Tell the host up front that you'll ask for a short reference after the second run. Nobody likes a surprise ask.
- 2Send a two-line recap the day after each session: who came, what they left with, what you're changing.
- 3Leave the materials with them so they can run it again without you. That's the thing they'll remember.
- 4When you ask, hand them the specifics — dates, headcount, what changed — so writing it takes them five minutes.
- 5Ask for a LinkedIn recommendation and permission to list them as a reference. Two different things, ask for both.
Turn it into a STAR story
Teach It Back gives you a STAR answer for teamwork, leadership, communication, and initiative questions, all from one project. Write it while it's fresh.
Situation
Who was stuck, and how did you know? Name the group and the specific gap.
The student marketing club kept losing money on events because nobody could build an event budget.
Task
What did you take responsibility for, and with whose agreement?
I offered the advisor a 45-minute working session that would leave every officer with a real budget for their next event.
Action
What did you design, and what did you change after the first run?
I interviewed three officers, built a template around their actual event, and taught it hands-on. After run one, I cut the theory and doubled the build time.
Result
What did people leave with, and what did the host say?
Two runs, 19 officers, and every one left with a finished budget. The advisor now uses the template with new officers each fall.
What it looks like in practice
Spreadsheet basics for club officers
A student who'd used spreadsheets in one business course.
Built a budget template around one club's real event, taught it in 45 minutes, ran it twice, and the advisor kept the template for new officers.
Resume formatting for first-generation students
A junior who'd fixed her own resume the hard way.
Ran three sessions with the campus first-gen program. Everyone left with a formatted, saved file instead of a to-do list.
Photo and video basics for a nonprofit's volunteers
A communications student with a phone and some practice.
Taught volunteers to shoot and caption usable photos at events, so the nonprofit stopped depending on one person for its social feed.
Study systems for student athletes
A sophomore who'd nearly lost eligibility his first term.
Built a one-page weekly planning session around travel schedules, ran it with two teams, and the academic advisor asked for it again the next season.
These are illustrative examples of the shape a Teach It Back project takes, not member case studies.
Where to find a host
- A student club or organization that needs a skill its officers keep outsourcing.
- A course or program office that runs first-year or transfer orientation.
- A nonprofit whose volunteers were handed a tool nobody trained them on.
- A residence hall or student affairs office with programming slots to fill.
- A high school teacher, coach, or counselor from the school you came from.
- A library, community center, or senior center that runs open workshops.
- A campus office — writing center, career center, tutoring — that would host a peer-led session.
If you don't know who's out there yet, the Community Asset Map is the launcher that finds them, and the two work well back to back.