Skip to content

fixed unclear text #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fixed unclear text #256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion DISCOVER/09_participant_selection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
- Keep and maintain a list of possible speakers with expertise and their contact info
- Research and follow speaker lists compiled by other organizations and communities
- When querying your network for speaker ideas, specifically ask for suggestions of speakers who could contribute to the diversity of the speaker line-up
- If your system is to have speakers come to you & ask, but research shows they tend not to do so, they won't come.
- Researchers have found that speakers don't usually ask to be invited, so if you wait for them to do so, you might not get many applications from speakers.
- 🍎 Consider the specific wording of how you solicit talks (subtlety can make a big difference)
- E.g. "Experts in best practices" may turn away people who don't self-identify as "expert" or who have impostor syndrome.
- "Speakers who have advice or expertise to share" > Everyone has some level of expertise or knowledge to share about what they work on, so this phrasing is more inclusive and inviting.
Expand Down