Public speaking guidelines

This page contains guidelines for how to properly represent Fedora in public speaking engagements. Those engagements might include:


 * interviews with the press, in person, by email, on the telephone, or on film or video.
 * formal speaking engagements at a conference or other gathering
 * informal speaking to a group, whether organized or impromptu

Rationale
Being a leader in free software means spreading our message worldwide. To do this properly and scalably, we must have more than just one or two people able to speak on behalf of Fedora. Typically, the most important representation of Fedora comes from a small group:


 * the FPL
 * the Community Architecture team

We also have an ever-expanding group of Fedora Ambassadors who are responsible for grassroots spread of Fedora and our supporting message about the advancement of free software and community. It is vital that people who represent Fedora do so with a consistent message, and with an air of confidence, accountability, and positivity.

The guidelines on this page are designed to give you an idea of the knowledge, skills, and abilities you must possess to gain recognition as a spokesperson for Fedora. Being a good spokesperson requires a combination of talent, learning, and effort. Not everyone who is a great Fedora Project member is a great spokesperson as well.

General
These are guidelines everyone should observe, regardless of the venue.

Delivery

 * 1) Speak clearly and use direct language.
 * 2) * Enunciate clearly.
 * 3) * Speak slowly and with confidence, so you can be understood and heeded.
 * 4) Pay attention to questions.
 * 5) * Jot down notes if you find that helpful.
 * 6) * Give yourself time to formulate a response in your head before you open your mouth.
 * 7) * Break down the question as needed, and answer each part fully but without wandering too far off-topic.
 * 8) * Suggest separate follow-up if needed.
 * 9) Break down complex ideas into simple ones.
 * 10) * Software is complicated, and even tech journalists and target audience are not always aware of details.
 * 11) * Use analogies or examples to illustrate the idea.
 * 12) * Point to references only if required, because it is your job to explain, not the audience's job to do further research.
 * 13) Avoid jargon.
 * 14) * Jargon makes your message difficult to understand. If you use a term the average man on the street wouldn't understand, explain it before you use it. (Examples include: Spins, yum repo, RPM, PackageKit....)
 * 15) * If needed, use an analogy of a common-sense concept to explain.
 * 16) Make presentation slide decks simple, not text-heavy.
 * 17) * Slides full of text tend to be distracting and hard to read.
 * 18) * Short declaratives, or even names of concepts, cause people to focus on your words.
 * 19) * Photos or graphs are useful if they support your point.
 * 20) Know your material.
 * 21) * Do your research.
 * 22) * If you are giving a rehearsed speech, practice, practice, practice!
 * 23) * Give your talk to a test audience. Time it and solicit critiques afterward. Listen to the critique and use it to improve.
 * 24) * It's okay to re-use a talk from one venue to another. Re-use encourages familiarity, better speaking, and consistency of message.
 * 25) * Always include key messaging guidelines wherever possible.
 * 26) Know your audience.
 * 27) * Is the audience a journalist? Community members?  General computer users?
 * 28) * Make sure your message matches the informational purpose of the speaking engagement. Be relevant.
 * 29) * Avoid continually calling on the same audience member in speeches -- it discourages others.
 * 30) '''Know yourself.
 * 31) * Be willing to say "I don't know" if you truly don't. People respect honesty.
 * 32) * Avoid overuse of "I don't know." Are you sure the question is relevant to your topic? If not, take it offline. If you find yourself repeatedly in this situation, revisit the Know your material rule above.
 * 33) Anticipate questions.
 * 34) * Ask yourself tough questions about the material, and know how to answer. You have the ability to be much tougher on yourself than most audiences.
 * 35) * Have extra slides ready if helpful or needed.
 * 36) Keep talk on-target.
 * 37) * Recognize questions that are off topic. Invite the person asking the question to discuss afterward.
 * 38) * Avoid "woolgathering" or mental wandering while speaking.
 * 39) * In interviews, it is perfectly acceptable to invite later follow-up on a related subject.
 * 40) * Journalists are also susceptible to personal curiosity; help them stay on target if they are not using their time limit wisely. They will usually thank you, because their editor wants a specific story too.
 * 41) Be flexible.
 * 42) * Watch for signs of interest or boredom, and adjust as needed on the fly.
 * 43) * Always leave time for questions and answers in formal presentations wherever appropriate.

Content
These are guidelines that concern the messages you send as part of your engagement. Some are particular to canned presentations, others are particular to interviews or other impromptu speaking, and others are equally relevant across the board.


 * 1) Make your message positive, not negative.
 * 2) * Avoid criticizing other entities. This includes proprietary vendors and other distribution projects.
 * 3) * Indicate the Fedora philosophy or practice as a differentiating feature of the Fedora Project, and most importantly how exactly it helps advance free software.
 * 4) Turn competitive statements on their head.
 * 5) * Know our central messages like the back of your hand, and refer to them.
 * 6) * We showcase the work of upstream, and our community builds features that are adopted by other distros. (E.g. NetworkManager, virtualization, SELinux, PolicyKit, PackageKit....)
 * 7) * Our statistics are openly produced and we invite others to do the same thing.
 * 8) Invite technology comparisons based on current release.
 * 9) * Audiences often have not done this within the last few years.
 * 10) * Point out that Fedora ensures that free software rapidly advances, and thus a recent comparison is always needed to make a good judgment call. (This is often useful in addressing apt vs. yum questions.)
 * 11) Recognize apples vs. oranges comparisons.
 * 12) * Point out the fallacy politely: "I noticed you are comparing apt to rpm. Actually, rpm is a software library and packaging standard like dpkg. It sounds like you might be interested in hearing about yum, the program that actually manages the dependencies between software packages in Fedora, like apt does for Debian."
 * 13) Recognize hidden agendas.
 * 14) * Occasionally people ask questions to score points. You can defuse this kind of situation by acknowledging it up front, and emphasizing a positive message instead.
 * 15) * Recognize something good about whatever the audience member positions as a competitor, then recognize something equally good or better about Fedora's contribution.
 * 16) Find time to recognize individuals.
 * 17) * Talk about one or more persons working on a feature or team, and specifically what each did. Keep the list short, but be mindful of recognizing a larger group over time.
 * 18) * Thank sponsors, organizers, staff, and so forth.
 * 19) * Thank your interviewer for his or her time and offer to do it again any time, unless there is a really good reason against it.

Choosing opportunities
(This section concerns how to pick useful speaking engagements.