Guide · teaching
How to Share Your Skills: Teach, Workshop, Community or Volunteer
If you want to share your skills effectively, the first problem is not confidence and it is not material. It is that you know the thing too well. Whatever you do daily has become invisible to you, so the parts a beginner will trip over are precisely the parts you will skip.
Everything below is about fixing that, and about the four routes people actually use to start: joining something that already exists, finding a community, starting one, and volunteering. Learning to share your skills is mostly learning to notice what you have stopped noticing.
Share Your Skills by Picking One Thing You Can Teach in Twenty Minutes
Scope is the whole game. The instinct is to cover a subject; the useful move is to cover one decision inside it. Not “typography” but how to pick a size relationship between a heading and body text. Not “JavaScript” but one API and what it replaces.
The archive on this site is a decent argument for narrowness. Across 47 talks the titles are almost all specific to the point of being odd out of context, and the abstracts are short. The shortest usable one runs to 11 words. People did not summarise a field; they described one thing they had done.
A practical test: can you say what the audience will be able to do afterwards, in one sentence, without the word “understand”? If not, it is still too big to teach well. To teach a skill properly you need a boundary around it, and to share your skills effectively you need that boundary to be visible to the room as well as to you.
Structure a Workshop Around the Thing Going Wrong
The most reliable workshop structure is not a tour of features. It is: here is the problem, here is the obvious approach, here is why it fails, here is what to do instead. That order works because it earns the answer before giving it, and because the failure is the part your audience recognises.
Compare it with the structure people reach for by default, which is chronological: this is what I set out to do, this is what I tried first, then this, then this, and here is where I got to. It feels honest and it is almost always worse, because the audience has no way to tell which of the twelve things you mention is the one that mattered. Problem-first tells them what to listen for in the first thirty seconds.
Cut ruthlessly to fit twenty minutes rather than talking faster. A workshop that covers three points properly is remembered; one that covers eight at speed is not remembered at all, and the speaker cannot tell the difference from the front of the room because both feel like they went fine.
Say the obvious thing out loud. In any workshop the step you consider too basic to mention is usually the one that loses half the room. If you catch yourself thinking “everyone knows that”, that is the sentence to say.
Finish early. A workshop that ends with ten minutes of questions is better received than one that runs over by five, and the questions are where you find out what you actually failed to explain.
Rehearse once, out loud, alone, with a timer. Not to memorise it — to find the two places where you cannot actually explain the thing you thought you understood. Everyone has them, they are invisible while reading through slides silently, and they are obvious the moment you have to produce a sentence. Fixing those two places is worth more than any amount of polishing the rest.
Show the real artefact. The actual file, the actual mess, the actual thing that broke. A cleaned up example teaches the cleaned up case, which is not the case anybody in the room is stuck on. This is the single largest difference between a peer teaching and a professional teaching: the professional has a prepared example and the peer has the real one, and the real one is worth more.
Take Part in a Skill Swap Programme
The lowest-risk way to start is inside something that already runs, because the audience, the room and the date are somebody else’s problem. In many places you can find groups committed to skill swapping: people who get together and share their time supporting each other, so that when somebody helps a neighbour with bookkeeping for an hour, they earn an hour’s credit toward something they need themselves.
That covers any sort of skill — how to bake a cake, how to put up a shelf, how to make handcrafted ornaments. If you live in a large city or metropolitan area you can use a dedicated website to help you find someone willing to exchange skills with you.
Programmes like that suit a one-to-one exchange, which is a different shape from an evening with an audience and worth knowing about separately. One-to-one is better for anything that needs hands on the work: you cannot teach somebody to wire a plug or lay out a page from a lectern. A room is better for anything where the argument is the value, because five people disagreeing about an approach produces something no pair of people reaches alone.
If you are choosing between them, choose by what the skill needs rather than by what you would find comfortable. Most people find the pair easier and pick it for that reason, then discover the skill wanted a room.
Join a Like-Minded Community, or Start One
Joining a community of people with similar interests opens a whole new set of doors, and these groups are not hard to find: search, social platforms, local mailing lists, a noticeboard in the right café. Initiative pays off here more than credentials do, and if nothing near you exists you can start the group yourself.
Starting one sounds like the harder option and is not, particularly. The Brighton archive documents ten years of a community that began as a handful of people in a room, and starting a group sets out what the record suggests actually matters.
Writing is the other route. A blog post about the same narrow thing you would teach in twenty minutes reaches people who will never be in your town, and it doubles as your notes when somebody eventually asks you to speak.
It is also the route with the best ratio of effort to reach, and the archive on this site is a demonstration of the limits of the alternative. Of 47 talks given to rooms of a dozen or two, the ones that reached anybody afterwards are the handful that were recorded. Everything else exists as a title and a paragraph. That is not an argument against speaking — the room got the value on the night — but if your aim is for the knowledge to travel, write it down as well.
Volunteer, Because Repetition Is the Only Fix
Nobody shares a skill well the first time. The people who do it well have done it fifteen times, and volunteering is the cheapest way to accumulate those repetitions: a school, a library, a community centre, a charity that needs somebody who can do the thing you can do.
Repetition changes something specific, and it is not confidence. It is that you accumulate a catalogue of the places people get stuck. The first time you explain something you know how you understand it; by the fifth you know the four points at which somebody else stops following, and you arrive at those points ready. That knowledge cannot be reasoned out in advance and it cannot be borrowed from anyone else’s material, because the sticking points depend on how you explain it, not on the subject.
You do not need permission to volunteer to teach a skill, which is the other reason it is the fastest route. Volunteer settings are also more forgiving than professional ones. The stakes are low, the audience is grateful, and you find out quickly which of your explanations work. Several speakers in this archive gave their first talk in a room of a dozen people, having attended two or three sessions first — which is to say they volunteered into an existing community rather than launching anything.
A last thing about nerves, since it is the reason most people never start. The fear is almost always that somebody in the room knows more than you do. Frequently somebody does. It does not matter, and the reason it does not matter is structural rather than reassuring: you are not there as the authority, you are there as the person who did this particular thing recently. The expert in the third row is a resource, not a threat, and the correct response to their better answer is to say so out loud. A room watching a speaker learn something is a room that will produce its next speaker.
What genuinely goes wrong is different and more mundane. Talks fail because they were too broad, because the speaker read from notes they had never said aloud, or because the interesting part was rushed at the end after fifteen minutes of preamble. All three are fixed before the night, none of them are about confidence, and all three are why the advice above spends most of its length on scope and structure rather than on delivery.