10 questions before you help a community learn about IP

You might be planning a session for artists, running a business group, working in a library, or helping friends make sense of a shared project. The people in the room bring experience, hopes and ways of working that existed long before your session. Start your preparation with curiosity about those things.

Read all ten questions and answer each one for yourself before you look at the discussion. Your answers show you which parts of the session need the most preparation. Then read on.

The ten questions

1. Do you feel you need to know every answer before you can help people begin learning about IP?
2. When you picture the participants, what knowledge and experience do you expect them to bring?
3. Do you expect everyone to want the same thing from protecting or sharing their work?
4. What would count as a successful session in your mind: registrations, clearer questions, a useful conversation, or something else?
5. How much personal detail would you expect someone to share before the group could help them?
6. If an example feels obvious to you, how would you find out whether it makes sense to someone with a different background?
7. Do you think using simpler language means losing legal accuracy?
8. If someone brings a story, design, or practice connected to their community, whose interests would you expect to consider?
9. Would introducing a participant to a professional always feel helpful, or could it create pressure or reveal more than they intended?
10. At the end of the session, how would you distinguish feeling encouraged from understanding something more clearly?

Once you have answered the ten questions, continue below.

The answers

1. Do you feel you need to know every answer before you can help people begin learning about IP?

No. Your job is to help people read a reliable explanation, compare examples and name the question that needs specialist help. Tell the group at the start which role you are taking. When a participant asks what to do about their own dispute or agreement, acknowledge the question, say it needs someone who can look at the documents, and point them to support (finding the right IP support lists the options). Before the session, look up the national or regional IP office for your participants in WIPO's directory; that office is the place for official, country-specific information.1

2. When you picture the participants, what knowledge and experience do you expect them to bring?

More than you think. A craftsperson may already have thoughtful rules about sharing techniques. A musician may know how collaborators expect to be credited. A small business owner may know how customers recognize the work. Ask "How do you handle this now?" early. The answers give people a way into the subject and tell you which examples will mean something to them. Treat those habits as a starting point, not as the legal answer.

3. Do you expect everyone to want the same thing from protecting or sharing their work?

Expect the opposite. One person wants income, another wants credit, another wants a resource to stay free for teaching, and someone else needs to understand an accusation before doing anything at all. Plan the session so each of those purposes gets an answer. One useful exercise: take a single project and show how its questions change depending on what its makers want. Nobody needs a commercial goal to justify learning about IP.

4. What would count as a successful session in your mind: registrations, clearer questions, a useful conversation, or something else?

Pick one modest result and promise only that, for example "you will recognize which IP questions arise in a shared creative project." A participant who realizes an old agreement needs reading, learns where official guidance lives, or decides whom to ask before publishing has had a successful session, even if nobody files anything. A small promise is easier to teach well and easier to check afterwards.

5. How much personal detail would you expect someone to share before the group could help them?

None. Use invented or already public examples for group discussion, and give people a way to ask a general question without naming a client, retelling a live dispute or describing an unpublished invention. That last one matters most: patent novelty is judged against everything known or disclosed before the application's filing date, and that can include an oral disclosure.3 Anyone with an invention they have not filed for should speak to a registered patent attorney or agent before describing it anywhere public, your session included. If someone starts sharing more than they intended, stop them kindly and offer to continue privately.

6. If an example feels obvious to you, how would you find out whether it makes sense to someone with a different background?

Ask. A discussion about a software library may suit developers but leave a group of performers translating the setting before they can reach the IP question. Ask participants whether the example resembles something they deal with, and let them suggest a setting from their own work while keeping private details out. If you have to explain the example more than once, replace it. The example exists to make the subject clearer, not to be defended.

7. Do you think using simpler language means losing legal accuracy?

No. Put each term next to a concrete situation, then keep the limits that matter. "Permission to use this photograph on your website" is a better opening than a string of unexplained legal terms, and it still leads to a careful discussion of what that permission covers. W3C's accessibility guidance gives you a checklist for handouts and slides: headings that describe their sections, link text that says where the link goes, clear instructions, acronyms spelled out on first use, a glossary for unfamiliar terms, and no unnecessarily complex words.2 Plain wording makes the limits easier to see, not harder. Accessible IP learning goes further.

8. If someone brings a story, design, or practice connected to their community, whose interests would you expect to consider?

The community's, not only the person in front of you. Traditional cultural expressions are often collective and passed down through generations, so there may be no single identifiable author.3 WIPO's guide for Indigenous Peoples and local communities says plainly that IP law does not meet all of their needs, and that preservation and safeguarding of traditional knowledge are outside IP protection altogether.3 So do not assume one participant can speak for everyone connected to the knowledge. Ask who should shape the conversation, and keep secret or sacred material out of the room: some communities protect it as confidential information, and that protection depends on it staying confidential.3 Community knowledge and IP covers this in depth.

9. Would introducing a participant to a professional always feel helpful, or could it create pressure or reveal more than they intended?

It can do both, so let the participant decide. Tell them who the contact is, why they are relevant, and what fees or eligibility rules apply. For example, WIPO's Inventor Assistance Program matches eligible individual inventors and small businesses in participating countries with volunteer patent professionals who work for free, but applicants still pay official patent fees, translation and other costs.4 Give the participant the contact details first, before you offer to pass on any of their information. If they want an introduction, agree with them what it will say. Reading more, contacting the provider on their own, or doing nothing that day are all fine answers; make each one easy to choose. Making a consented introduction walks through it.

10. At the end of the session, how would you distinguish feeling encouraged from understanding something more clearly?

Test for understanding, not mood. Ask participants to explain a small example in their own words or to name one question they now know how to investigate. Ask what stayed confusing and which parts felt irrelevant. A session can be enjoyable and still leave an important misunderstanding in place; it can also leave someone less certain because they now see a distinction they had missed. Both answers tell you what to explain next time.