From ab0915b3a50d6dbc0a9f60a0e6cc665eee17f007 Mon Sep 17 00:00:00 2001 From: Chris Kenst Date: Fri, 7 Aug 2026 19:17:24 -0700 Subject: [PATCH 1/4] Add conference speaking guide --- guides/speaking-at-technology-conferences.md | 381 +++++++++++++++++++ resources.md | 6 +- 2 files changed, 386 insertions(+), 1 deletion(-) create mode 100644 guides/speaking-at-technology-conferences.md diff --git a/guides/speaking-at-technology-conferences.md b/guides/speaking-at-technology-conferences.md new file mode 100644 index 00000000..1c7fc70e --- /dev/null +++ b/guides/speaking-at-technology-conferences.md @@ -0,0 +1,381 @@ +--- +layout: page +permalink: /guides/speaking-at-technology-conferences/ +title: A Guide to Speaking at Technology Conferences +--- + +Speaking at a conference can look mysterious from the audience. In practice, it is a series of learnable steps: find an event, shape an idea, submit it, prepare carefully, and help an audience understand something useful. + +This guide follows that journey from the first thought of speaking through the end of the presentation. It is especially written for software testers, quality engineers, and other technology practitioners, but most of the advice applies to any technical community. + +> This is an original adaptation inspired by Karl L. Hughes's eight-part CFP Land guide to speaking at technology conferences, which is preserved in the [Internet Archive](https://web.archive.org/web/20220701014119/https://www.cfpland.com/guides/speaking/introduction/). CFP Land is no longer online, so we rebuilt and updated its useful path for today's conference community. + +## The eight parts + +1. [Understand technology conferences](#part-1-understand-technology-conferences) +2. [Decide why you want to speak](#part-2-decide-why-you-want-to-speak) +3. [Find calls for proposals](#part-3-find-calls-for-proposals) +4. [Write and submit a proposal](#part-4-write-and-submit-a-proposal) +5. [Understand how conferences choose talks](#part-5-understand-how-conferences-choose-talks) +6. [Handle acceptance, waitlists, and rejection](#part-6-handle-acceptance-waitlists-and-rejection) +7. [Prepare before the conference](#part-7-prepare-before-the-conference) +8. [Give the presentation](#part-8-give-the-presentation) + +## Part 1: Understand technology conferences + +No two conferences are quite alike. Before deciding where to submit, learn what kind of event you are looking at and what its audience expects. + +### Topic and depth + +Some conferences focus tightly on one practice, tool, or community. A specialist testing event might spend an entire day on exploratory testing, performance engineering, accessibility, security, or test automation. These events let you go deep because much of the audience already shares the vocabulary and context. + +Broader technology conferences may cover development, operations, product, design, data, leadership, and quality. A talk at one of these events usually needs a little more context and a clear explanation of why the subject matters beyond your immediate specialty. + +### Tracks and formats + +A single-track conference puts every attendee in the same room. Your potential audience is larger, but not everyone will have chosen your subject. A multi-track conference lets attendees select the most relevant session, which can produce a smaller but more engaged room. + +Events may offer several formats: + +- Lightning talks of five to fifteen minutes +- Experience reports or case studies +- Standard sessions of thirty to sixty minutes +- Panels or facilitated discussions +- Hands-on workshops lasting several hours +- Keynotes intended for the whole conference + +Choose a format that fits both the idea and your experience. A focused lightning talk is often a better first step than stretching one lesson into a forty-five-minute session. A workshop needs exercises, facilitation, and enough time for attendees to practice; it is not simply a longer talk. + +### Audience and scale + +An event may be a local meetup with a few dozen people, a regional conference with several hundred, or an international gathering with thousands. Size affects the atmosphere, not necessarily the value. Small events can make conversation and connection easier. Large events may offer more topics and people but can feel less personal. + +Look beyond attendance numbers. Ask who comes to the event, what experience levels it serves, and whether attendees are mostly individual contributors, leaders, consultants, academics, tool builders, or a mixture. + +### Organizers and incentives + +Conferences can be community-run, nonprofit, commercial, or organized by a vendor. Each model can produce an excellent event, but its goals influence the program. A vendor event may favor its ecosystem. A volunteer event may have limited money and staff. A commercial conference may have stronger production support while expecting content that helps sell tickets. + +Read the code of conduct, speaker agreement, refund policy, and sponsor information. Find out whether speakers receive travel, lodging, an honorarium, a free ticket, or no financial support. None of these arrangements is automatically right or wrong, but you should understand the exchange before committing. + +### Why attend before speaking? + +Attending helps you learn how a community talks about its problems. You can discover techniques, meet collaborators, find future employers or employees, and see different presentation styles. You will also notice what makes an event welcoming—or difficult—to navigate. + +You do not have to attend conferences before you are qualified to speak. Your practical experience can be valuable now. Attending simply gives you more context for choosing the right event and designing a useful session. + +## Part 2: Decide why you want to speak + +Conference speaking takes time. A clear reason will help you choose opportunities, respond to setbacks, and decide when to say no. + +### Share a lesson + +You do not need to be the world's leading expert. You need a useful experience that you can explain honestly. A failed automation rewrite, an accessibility bug that changed your process, or a team experiment that improved feedback time may be exactly what another practitioner needs. + +The strongest experience reports include boundaries. Explain the context, what you tried, what happened, and where the lesson may not apply. Audiences usually trust a specific account more than a claim that one practice solves every problem. + +### Learn more deeply + +Preparing to teach exposes gaps in your understanding. Questions from reviewers, peers, and attendees force you to define terms, test assumptions, and support claims. Even when you already know the subject, turning experience into a coherent explanation can make you better at the work. + +### Build relationships + +Speaking gives people a reason to start a conversation with you. Those conversations can lead to collaborators, mentors, jobs, podcast invitations, open-source contributions, or friendships. Treat these as possible outcomes, not debts the audience owes you. + +### Represent a perspective + +Conference programs improve when they include people from different roles, regions, industries, career stages, and lived experiences. You may be able to describe constraints or communities that are rarely represented on stage. + +Do not wait until you feel like a universal authority. Be precise about what you know, credit the people who helped, and share the view you can responsibly offer. + +### Grow a career or business + +Speaking can demonstrate communication skills and subject knowledge. It may support consulting, training, developer relations, leadership, or a job search. If your employer benefits, discuss whether speaking preparation counts as work and whether the company will cover travel. + +Keep promotion proportional. A useful talk may mention a relevant product or service, but a disguised sales pitch breaks trust and is rejected by many conferences. + +### Make the commitment realistic + +Decide how much time and money you can spend, how far you can travel, and how public you want to be. Consider accessibility, caregiving, visas, health, and employer approval early. Virtual, local, and internal events are legitimate speaking opportunities and can fit constraints that destination conferences do not. + +Write down a modest first goal, such as giving one ten-minute talk, submitting to three well-matched events, or developing one session you can improve over a year. + +## Part 3: Find calls for proposals + +A call for proposals—often shortened to CFP—is the period when a conference invites people to suggest sessions. It may also be called a call for papers, call for participation, or call for speakers. + +### Start with conferences you understand + +Look at events you have attended, communities you participate in, and conferences listed on [TestingConferences.org](/). Follow organizers and local groups, subscribe to event newsletters, and watch the official event site for dates. + +Conference directories and CFP newsletters help with discovery, but always verify the details on the organizer's official page. Deadlines, formats, themes, and event dates change. + +### Read the whole call + +Before drafting, record: + +- The submission deadline and time zone +- Event dates and location +- Tracks, themes, and intended audience +- Accepted session formats and lengths +- Required proposal fields and word limits +- Whether review is anonymous +- Whether previously delivered or published material is allowed +- Speaker benefits and expected costs +- Code of conduct and speaker terms +- When decisions are expected + +Do not assume every CFP uses the same definition of beginner, workshop, case study, or keynote. Use the language in the call. + +### Check the fit + +Review the current theme, previous programs, and videos when available. This shows the level and style of content the event selects. It can also reveal that your idea was covered recently, giving you a chance to choose a different angle. + +Fit is not the same as imitation. The program needs sessions that belong at the event, but it also needs ideas it has not already presented repeatedly. + +### Track opportunities + +A small spreadsheet or task board is enough. Include the conference, proposal, deadline, status, decision date, event date, costs, and important links. Set reminders before the deadline so you have time for feedback and technical problems. + +Start selectively. Three thoughtful submissions to suitable events teach you more than twenty generic submissions sent everywhere. + +### Watch for warning signs + +Be cautious when an event hides fees until late, pressures speakers to buy tickets, lacks identifiable organizers, has no code of conduct, copies another conference's material, or sends unsolicited acceptance for a subject you never proposed. Ask organizers direct questions. Declining a questionable opportunity is part of managing a speaking career. + +## Part 4: Write and submit a proposal + +A proposal is not the talk itself. It is evidence that you understand the audience, have a focused idea, and can deliver the session described. + +### Begin with the audience outcome + +Complete this sentence: “After this session, attendees will be able to…” Use a concrete verb. Compare approaches, diagnose a problem, design an experiment, or apply a technique is clearer than understand or learn about. + +Then define the audience. A session for test automation beginners should not quietly require advanced knowledge of distributed systems. A leadership talk should explain why its lesson matters to people responsible for teams or strategy. + +### Narrow the idea + +A useful talk usually has one central promise supported by a few points. “Everything about software testing” is too broad. “Three ways our team made flaky end-to-end tests easier to diagnose” establishes a problem, scope, and likely outcome. + +Narrowing does not make an idea less impressive. It makes the proposal credible and the talk memorable. + +### Write a clear title + +The title should help reviewers and attendees predict the subject. Personality and wordplay can help, but clarity comes first. If a clever title could describe five unrelated talks, add a subtitle or rewrite it. + +Avoid claims the talk cannot support. Words such as always, never, perfect, and effortless invite skepticism and rarely reflect real engineering work. + +### Build the abstract + +Unless the CFP requests a different structure, a strong public abstract answers four questions: + +1. What problem or opportunity does this session address? +2. Why does it matter to this audience? +3. What will the speaker cover or demonstrate? +4. What can attendees take back to their work? + +Write for a person scanning many submissions. Open with the substance, use plain language, and remove background that does not help someone choose the session. + +### Give reviewers the detail they need + +Many systems include private notes, an outline, or a field for the program committee. Use it. Describe the session's progression, examples, evidence, demonstrations, exercises, and timing. Explain what is original about your perspective and disclose vendor relationships. + +If the talk relies on a case study, include enough context to evaluate it. If it makes an empirical claim, identify the evidence. If it is interactive, describe how the interaction will work for the expected room and time. + +### Write an appropriate biography + +Your biography should establish why you can give this particular session. Mention relevant work, community experience, or prior exploration without turning it into a complete career history. First-time speakers can demonstrate credibility through the work itself; prior conference appearances are not the only qualification. + +### Get feedback and revise + +Ask at least one person in the intended audience and one person unfamiliar with the topic to read the proposal. Useful questions include: + +- What do you think this talk will teach? +- Who is it for? +- Which sentence is confusing? +- What would make you attend—or skip—it? +- Does the promised outcome fit the session length? + +Read the abstract aloud, check every required field, preserve a copy, and submit before the last hour. Confirm that the system shows the proposal as received. + +## Part 5: Understand how conferences choose talks + +Selection is usually program design, not a ranking of speakers from best to worst. A strong proposal can be declined because it duplicates another session, misses the theme, targets the wrong level, or does not fit the available schedule. + +### Eligibility and initial review + +Organizers may first remove incomplete, late, commercial, off-topic, or code-of-conduct-incompatible submissions. Following the instructions is the easiest selection factor to control. + +Reviewers then assess some combination of relevance, clarity, usefulness, originality, evidence, audience fit, and feasibility. In anonymous review, they may not see your name or biography at this stage. + +### Program balance + +The committee has to assemble a whole program. It may need a mix of beginner and advanced sessions, technical and human topics, talk formats, industries, and perspectives. Ten excellent proposals about the same popular tool cannot all occupy one track. + +Organizers may also consider speaker availability, travel budget, room capacity, previous program repetition, and whether a session depends on equipment they cannot support. + +### What you can influence + +You cannot control the other submissions or the program's constraints. You can make the proposal easy to evaluate: + +- Match the stated audience and theme +- Describe a focused problem and outcome +- Show a realistic plan for the time available +- Support claims and avoid hype +- Explain what distinguishes the session +- Follow every submission instruction + +Do not try to reverse-engineer a secret formula. Review processes vary, and a technique that worked at one event may be irrelevant at another. + +### Improve through reviewing + +If a community offers open proposal mentoring or volunteer reviewing, participate when you are qualified and have the time. Reading proposals teaches you how quickly ambiguity, excessive scope, and missing outcomes become visible. Respect confidentiality and declare conflicts of interest. + +## Part 6: Handle acceptance, waitlists, and rejection + +Every submission ends in one of a few outcomes. Responding professionally protects both you and the organizers and makes the next step easier. + +### If the proposal is accepted + +Celebrate, then verify the commitment before accepting. Confirm: + +- The exact event date, session length, and format +- Whether the title or abstract may be edited +- Travel, lodging, visa, ticket, and payment arrangements +- Recording and licensing terms +- Accessibility or technical requirements +- Important rehearsal and material deadlines + +Tell the organizers quickly if you cannot meet a condition. It is better to decline promptly than to accept and hope a major conflict disappears. + +Once confirmed, block preparation and travel time. Save the organizer's contact details somewhere accessible without internet service. + +### If the proposal is waitlisted + +A waitlist is a real possibility, not a promise. Ask when a final decision is likely and whether you should reserve travel. Do not make nonrefundable purchases unless the organizers clearly agree to cover them. + +Keep preparing only to the degree that the likelihood and timing justify. If another commitment creates a conflict, update the organizers rather than silently remaining unavailable. + +### If the proposal is rejected + +Rejection is common, including for experienced speakers. It does not establish that the idea is bad or that you do not belong on stage. The program may have received hundreds of proposals for a few dozen spaces. + +If feedback is offered, look for specific, actionable themes. Reviewers can be wrong or disagree with one another, so use judgment rather than applying every comment mechanically. If no feedback is offered, do not demand private deliberations from volunteer organizers. + +Revisit four possibilities: + +1. **Fit:** Was this the right event, track, and audience? +2. **Clarity:** Could a reviewer identify the problem and outcome quickly? +3. **Scope:** Was the plan realistic for the session length? +4. **Evidence:** Did the proposal support its important claims? + +Revise the idea, try a shorter version at a meetup, or submit it to a better-matched event. Also allow yourself to retire a proposal. Persistence means learning and choosing again, not sending the same text forever. + +### If circumstances change + +Withdraw as soon as you know you cannot speak. Give a brief, honest explanation and help the organizer recover time. You do not owe private medical or family details. + +Organizers may also cancel or change an event. Keep receipts, understand refund terms, and avoid costs you cannot absorb until arrangements are clear. + +## Part 7: Prepare before the conference + +Preparation turns an accepted idea into an experience the audience can follow. Start with the promise in the proposal; attendees chose the session based on it. + +### Design the story before the slides + +Write the central message in one sentence. Choose the few supporting points the audience needs, arrange them in a logical order, and decide what to leave out. + +A practical structure is: + +1. Establish the situation and why it matters. +2. Show the difficulty, constraint, or failed approach. +3. Explain what changed and why. +4. Demonstrate the result and its limits. +5. Give the audience concrete next steps. + +Slides are visual support, not the structure itself. Outline on paper or in plain text first. + +### Make evidence understandable + +Define necessary terms. Use readable charts, cite sources, and distinguish measurements from opinions. Protect confidential information and remove identifying customer or employee details unless you have explicit permission. + +When presenting a success story, include tradeoffs and conditions. When presenting a failure, focus on decisions and learning rather than blaming individuals. + +### Plan demonstrations defensively + +Live demonstrations are engaging and fragile. Simplify the environment, disable unrelated notifications, enlarge important text, and rehearse the exact path. Prepare screenshots, a recording, or a completed state so the lesson survives if the network or tool fails. + +Never expose production credentials, customer data, private source code, or internal messages. Use purpose-built examples. + +### Rehearse for time and comprehension + +Practice aloud from beginning to end. Silent review does not reveal timing, pronunciation, breath, or awkward transitions. Record a run and watch it once. Ask a peer to identify the main message and any unexplained assumptions. + +Rehearse until you can finish comfortably under the limit, including pauses and audience interaction. Decide in advance which optional section to skip if time is short. Do not solve an overlong talk by speaking faster. + +### Make the session accessible + +Use large text, strong contrast, descriptive link text, and meaningful labels on diagrams. Do not rely on color alone. Describe important visuals aloud and caption prerecorded video. Provide materials in a format that works with assistive technology when possible. + +Ask the conference about microphones, ramps, seating, captioning, interpreters, quiet spaces, and other support you need. Accessibility includes the speaker as well as the audience. + +### Prepare the logistics + +Confirm the slide aspect ratio, connection types, operating system constraints, internet availability, and whether you must provide materials in advance. Bring local copies of slides, fonts, videos, and demo dependencies. Carry the adapters you need and a backup on a separate device or drive. + +Know when and where to meet the session chair. Plan travel with enough margin for delays, and keep essential presentation equipment in your carry-on luggage. + +## Part 8: Give the presentation + +On the day, your job is not to perform perfection. It is to guide the audience through the promised idea. + +### Before the session + +Arrive early enough to find the room and test the actual equipment. Check that slides, demos, audio, confidence monitor, clicker, and microphone work. Learn how the organizer will signal remaining time and whether questions happen during or after the talk. + +Drink water, eat something appropriate for you, and use the restroom. Silence notifications and close unrelated applications. Put a timer where you can see it without repeatedly checking the wall clock. + +### Start clearly + +Pause, look at the audience, and begin. Briefly establish what the session is about, who it is for, and what people will leave with. You do not need to apologize for being nervous or recite your full biography. + +Speak more slowly than nervousness suggests. Use the microphone even if you believe the room can hear you; it may feed recording, captioning, or assistive listening systems. + +### Work with the room + +Look across different parts of the audience without fixing on one person. Allow time for laughter, reflection, and note-taking. If people enter late or leave, continue; their movement may have nothing to do with your session. + +If a demo fails, move to the backup and explain the lesson it was meant to show. If you lose your place, pause, check your notes, and continue from the next point. The audience usually experiences a short pause as much shorter than the speaker does. + +### Manage questions + +Repeat or summarize an audience question before answering so everyone hears it. Answer the question you understood, and ask for clarification when needed. It is fine to say you do not know, distinguish a hypothesis from a fact, or offer to follow up. + +Keep answers useful to the room. If one question becomes a detailed consultation, suggest continuing after the session. Ask the moderator for help if a participant monopolizes time or behaves inappropriately. + +### Finish intentionally + +Do not race through the conclusion. Restate the central lesson, give the audience a small next action, and show where they can find accessible materials or contact you if you want follow-up. + +Thank the audience and organizers, then stop. A clear ending is stronger than adding a new idea after the conclusion. + +### After the talk + +Save useful questions and feedback while they are fresh. Share slides, code, references, or corrections when promised and when you have permission. Watch the recording if one is published, but review it for one or two improvements rather than cataloging every mannerism. + +Thank the people who helped you prepare. Update the talk based on what the audience needed, not only on how the performance felt. Then rest: preparing and delivering a session is real work. + +## A simple first-speaker checklist + +- Choose one lesson grounded in your experience. +- Identify a specific audience and useful outcome. +- Find a conference whose topic, format, and terms fit. +- Write a clear title, abstract, outline, and biography. +- Ask for feedback and submit before the deadline. +- Treat the decision as program fit, not a verdict on your worth. +- If accepted, confirm the terms and prepare to the proposal's promise. +- Rehearse aloud, make the material accessible, and build backups. +- On the day, help the audience follow one idea at a time. +- Record what you learned and make the next version better. + +The path to the stage is not reserved for people who already look like conference speakers. It is open to practitioners willing to share a specific experience with care, clarity, and respect for the audience. diff --git a/resources.md b/resources.md index d3fc30fd..0513e85b 100644 --- a/resources.md +++ b/resources.md @@ -6,4 +6,8 @@ title: Resources Resources to help you attend and eventually run your own workshop or conferences. -Coming soon. +## Guides + +### [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/) + +An eight-part path from understanding conference formats and finding calls for proposals to preparing and delivering a useful technical talk. Written for software testers, quality engineers, and other technology practitioners. From fbb331a75b12be4e13ea225a2b71f5a415c8dfb7 Mon Sep 17 00:00:00 2001 From: Chris Kenst Date: Fri, 7 Aug 2026 19:26:08 -0700 Subject: [PATCH 2/4] Split speaking guide into article series --- guides/speaking-at-technology-conferences.md | 380 +----------------- .../speaking/decide-why-you-want-to-speak.md | 48 +++ guides/speaking/find-calls-for-proposals.md | 55 +++ guides/speaking/give-the-presentation.md | 67 +++ ...ndle-acceptance-waitlists-and-rejection.md | 58 +++ .../speaking/prepare-before-the-conference.md | 60 +++ ...understand-how-conferences-choose-talks.md | 45 +++ .../understand-technology-conferences.md | 55 +++ .../speaking/write-and-submit-a-proposal.md | 67 +++ 9 files changed, 474 insertions(+), 361 deletions(-) create mode 100644 guides/speaking/decide-why-you-want-to-speak.md create mode 100644 guides/speaking/find-calls-for-proposals.md create mode 100644 guides/speaking/give-the-presentation.md create mode 100644 guides/speaking/handle-acceptance-waitlists-and-rejection.md create mode 100644 guides/speaking/prepare-before-the-conference.md create mode 100644 guides/speaking/understand-how-conferences-choose-talks.md create mode 100644 guides/speaking/understand-technology-conferences.md create mode 100644 guides/speaking/write-and-submit-a-proposal.md diff --git a/guides/speaking-at-technology-conferences.md b/guides/speaking-at-technology-conferences.md index 1c7fc70e..9f9e4fce 100644 --- a/guides/speaking-at-technology-conferences.md +++ b/guides/speaking-at-technology-conferences.md @@ -6,376 +6,34 @@ title: A Guide to Speaking at Technology Conferences Speaking at a conference can look mysterious from the audience. In practice, it is a series of learnable steps: find an event, shape an idea, submit it, prepare carefully, and help an audience understand something useful. -This guide follows that journey from the first thought of speaking through the end of the presentation. It is especially written for software testers, quality engineers, and other technology practitioners, but most of the advice applies to any technical community. +This eight-part guide follows that journey from the first thought of speaking through the end of the presentation. It is especially written for software testers, quality engineers, and other technology practitioners, but most of the advice applies to any technical community. > This is an original adaptation inspired by Karl L. Hughes's eight-part CFP Land guide to speaking at technology conferences, which is preserved in the [Internet Archive](https://web.archive.org/web/20220701014119/https://www.cfpland.com/guides/speaking/introduction/). CFP Land is no longer online, so we rebuilt and updated its useful path for today's conference community. -## The eight parts +## Start the guide -1. [Understand technology conferences](#part-1-understand-technology-conferences) -2. [Decide why you want to speak](#part-2-decide-why-you-want-to-speak) -3. [Find calls for proposals](#part-3-find-calls-for-proposals) -4. [Write and submit a proposal](#part-4-write-and-submit-a-proposal) -5. [Understand how conferences choose talks](#part-5-understand-how-conferences-choose-talks) -6. [Handle acceptance, waitlists, and rejection](#part-6-handle-acceptance-waitlists-and-rejection) -7. [Prepare before the conference](#part-7-prepare-before-the-conference) -8. [Give the presentation](#part-8-give-the-presentation) +1. [Understand Technology Conferences](/guides/speaking/understand-technology-conferences/) + Learn how events differ by topic, format, audience, size, and organizer model. -## Part 1: Understand technology conferences +2. [Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) + Identify what you want to share and make the commitment realistic. -No two conferences are quite alike. Before deciding where to submit, learn what kind of event you are looking at and what its audience expects. +3. [Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) + Discover suitable CFPs, evaluate event fit, and track opportunities. -### Topic and depth +4. [Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) + Turn an idea into a clear title, abstract, outline, and biography. -Some conferences focus tightly on one practice, tool, or community. A specialist testing event might spend an entire day on exploratory testing, performance engineering, accessibility, security, or test automation. These events let you go deep because much of the audience already shares the vocabulary and context. +5. [Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) + See how reviewers evaluate proposals and assemble a balanced program. -Broader technology conferences may cover development, operations, product, design, data, leadership, and quality. A talk at one of these events usually needs a little more context and a clear explanation of why the subject matters beyond your immediate specialty. +6. [Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) + Respond professionally to every possible submission outcome. -### Tracks and formats +7. [Prepare Before the Conference](/guides/speaking/prepare-before-the-conference/) + Design, rehearse, and make the session accessible and resilient. -A single-track conference puts every attendee in the same room. Your potential audience is larger, but not everyone will have chosen your subject. A multi-track conference lets attendees select the most relevant session, which can produce a smaller but more engaged room. +8. [Give the Presentation](/guides/speaking/give-the-presentation/) + Set up, deliver the talk, manage questions, and learn from the experience. -Events may offer several formats: - -- Lightning talks of five to fifteen minutes -- Experience reports or case studies -- Standard sessions of thirty to sixty minutes -- Panels or facilitated discussions -- Hands-on workshops lasting several hours -- Keynotes intended for the whole conference - -Choose a format that fits both the idea and your experience. A focused lightning talk is often a better first step than stretching one lesson into a forty-five-minute session. A workshop needs exercises, facilitation, and enough time for attendees to practice; it is not simply a longer talk. - -### Audience and scale - -An event may be a local meetup with a few dozen people, a regional conference with several hundred, or an international gathering with thousands. Size affects the atmosphere, not necessarily the value. Small events can make conversation and connection easier. Large events may offer more topics and people but can feel less personal. - -Look beyond attendance numbers. Ask who comes to the event, what experience levels it serves, and whether attendees are mostly individual contributors, leaders, consultants, academics, tool builders, or a mixture. - -### Organizers and incentives - -Conferences can be community-run, nonprofit, commercial, or organized by a vendor. Each model can produce an excellent event, but its goals influence the program. A vendor event may favor its ecosystem. A volunteer event may have limited money and staff. A commercial conference may have stronger production support while expecting content that helps sell tickets. - -Read the code of conduct, speaker agreement, refund policy, and sponsor information. Find out whether speakers receive travel, lodging, an honorarium, a free ticket, or no financial support. None of these arrangements is automatically right or wrong, but you should understand the exchange before committing. - -### Why attend before speaking? - -Attending helps you learn how a community talks about its problems. You can discover techniques, meet collaborators, find future employers or employees, and see different presentation styles. You will also notice what makes an event welcoming—or difficult—to navigate. - -You do not have to attend conferences before you are qualified to speak. Your practical experience can be valuable now. Attending simply gives you more context for choosing the right event and designing a useful session. - -## Part 2: Decide why you want to speak - -Conference speaking takes time. A clear reason will help you choose opportunities, respond to setbacks, and decide when to say no. - -### Share a lesson - -You do not need to be the world's leading expert. You need a useful experience that you can explain honestly. A failed automation rewrite, an accessibility bug that changed your process, or a team experiment that improved feedback time may be exactly what another practitioner needs. - -The strongest experience reports include boundaries. Explain the context, what you tried, what happened, and where the lesson may not apply. Audiences usually trust a specific account more than a claim that one practice solves every problem. - -### Learn more deeply - -Preparing to teach exposes gaps in your understanding. Questions from reviewers, peers, and attendees force you to define terms, test assumptions, and support claims. Even when you already know the subject, turning experience into a coherent explanation can make you better at the work. - -### Build relationships - -Speaking gives people a reason to start a conversation with you. Those conversations can lead to collaborators, mentors, jobs, podcast invitations, open-source contributions, or friendships. Treat these as possible outcomes, not debts the audience owes you. - -### Represent a perspective - -Conference programs improve when they include people from different roles, regions, industries, career stages, and lived experiences. You may be able to describe constraints or communities that are rarely represented on stage. - -Do not wait until you feel like a universal authority. Be precise about what you know, credit the people who helped, and share the view you can responsibly offer. - -### Grow a career or business - -Speaking can demonstrate communication skills and subject knowledge. It may support consulting, training, developer relations, leadership, or a job search. If your employer benefits, discuss whether speaking preparation counts as work and whether the company will cover travel. - -Keep promotion proportional. A useful talk may mention a relevant product or service, but a disguised sales pitch breaks trust and is rejected by many conferences. - -### Make the commitment realistic - -Decide how much time and money you can spend, how far you can travel, and how public you want to be. Consider accessibility, caregiving, visas, health, and employer approval early. Virtual, local, and internal events are legitimate speaking opportunities and can fit constraints that destination conferences do not. - -Write down a modest first goal, such as giving one ten-minute talk, submitting to three well-matched events, or developing one session you can improve over a year. - -## Part 3: Find calls for proposals - -A call for proposals—often shortened to CFP—is the period when a conference invites people to suggest sessions. It may also be called a call for papers, call for participation, or call for speakers. - -### Start with conferences you understand - -Look at events you have attended, communities you participate in, and conferences listed on [TestingConferences.org](/). Follow organizers and local groups, subscribe to event newsletters, and watch the official event site for dates. - -Conference directories and CFP newsletters help with discovery, but always verify the details on the organizer's official page. Deadlines, formats, themes, and event dates change. - -### Read the whole call - -Before drafting, record: - -- The submission deadline and time zone -- Event dates and location -- Tracks, themes, and intended audience -- Accepted session formats and lengths -- Required proposal fields and word limits -- Whether review is anonymous -- Whether previously delivered or published material is allowed -- Speaker benefits and expected costs -- Code of conduct and speaker terms -- When decisions are expected - -Do not assume every CFP uses the same definition of beginner, workshop, case study, or keynote. Use the language in the call. - -### Check the fit - -Review the current theme, previous programs, and videos when available. This shows the level and style of content the event selects. It can also reveal that your idea was covered recently, giving you a chance to choose a different angle. - -Fit is not the same as imitation. The program needs sessions that belong at the event, but it also needs ideas it has not already presented repeatedly. - -### Track opportunities - -A small spreadsheet or task board is enough. Include the conference, proposal, deadline, status, decision date, event date, costs, and important links. Set reminders before the deadline so you have time for feedback and technical problems. - -Start selectively. Three thoughtful submissions to suitable events teach you more than twenty generic submissions sent everywhere. - -### Watch for warning signs - -Be cautious when an event hides fees until late, pressures speakers to buy tickets, lacks identifiable organizers, has no code of conduct, copies another conference's material, or sends unsolicited acceptance for a subject you never proposed. Ask organizers direct questions. Declining a questionable opportunity is part of managing a speaking career. - -## Part 4: Write and submit a proposal - -A proposal is not the talk itself. It is evidence that you understand the audience, have a focused idea, and can deliver the session described. - -### Begin with the audience outcome - -Complete this sentence: “After this session, attendees will be able to…” Use a concrete verb. Compare approaches, diagnose a problem, design an experiment, or apply a technique is clearer than understand or learn about. - -Then define the audience. A session for test automation beginners should not quietly require advanced knowledge of distributed systems. A leadership talk should explain why its lesson matters to people responsible for teams or strategy. - -### Narrow the idea - -A useful talk usually has one central promise supported by a few points. “Everything about software testing” is too broad. “Three ways our team made flaky end-to-end tests easier to diagnose” establishes a problem, scope, and likely outcome. - -Narrowing does not make an idea less impressive. It makes the proposal credible and the talk memorable. - -### Write a clear title - -The title should help reviewers and attendees predict the subject. Personality and wordplay can help, but clarity comes first. If a clever title could describe five unrelated talks, add a subtitle or rewrite it. - -Avoid claims the talk cannot support. Words such as always, never, perfect, and effortless invite skepticism and rarely reflect real engineering work. - -### Build the abstract - -Unless the CFP requests a different structure, a strong public abstract answers four questions: - -1. What problem or opportunity does this session address? -2. Why does it matter to this audience? -3. What will the speaker cover or demonstrate? -4. What can attendees take back to their work? - -Write for a person scanning many submissions. Open with the substance, use plain language, and remove background that does not help someone choose the session. - -### Give reviewers the detail they need - -Many systems include private notes, an outline, or a field for the program committee. Use it. Describe the session's progression, examples, evidence, demonstrations, exercises, and timing. Explain what is original about your perspective and disclose vendor relationships. - -If the talk relies on a case study, include enough context to evaluate it. If it makes an empirical claim, identify the evidence. If it is interactive, describe how the interaction will work for the expected room and time. - -### Write an appropriate biography - -Your biography should establish why you can give this particular session. Mention relevant work, community experience, or prior exploration without turning it into a complete career history. First-time speakers can demonstrate credibility through the work itself; prior conference appearances are not the only qualification. - -### Get feedback and revise - -Ask at least one person in the intended audience and one person unfamiliar with the topic to read the proposal. Useful questions include: - -- What do you think this talk will teach? -- Who is it for? -- Which sentence is confusing? -- What would make you attend—or skip—it? -- Does the promised outcome fit the session length? - -Read the abstract aloud, check every required field, preserve a copy, and submit before the last hour. Confirm that the system shows the proposal as received. - -## Part 5: Understand how conferences choose talks - -Selection is usually program design, not a ranking of speakers from best to worst. A strong proposal can be declined because it duplicates another session, misses the theme, targets the wrong level, or does not fit the available schedule. - -### Eligibility and initial review - -Organizers may first remove incomplete, late, commercial, off-topic, or code-of-conduct-incompatible submissions. Following the instructions is the easiest selection factor to control. - -Reviewers then assess some combination of relevance, clarity, usefulness, originality, evidence, audience fit, and feasibility. In anonymous review, they may not see your name or biography at this stage. - -### Program balance - -The committee has to assemble a whole program. It may need a mix of beginner and advanced sessions, technical and human topics, talk formats, industries, and perspectives. Ten excellent proposals about the same popular tool cannot all occupy one track. - -Organizers may also consider speaker availability, travel budget, room capacity, previous program repetition, and whether a session depends on equipment they cannot support. - -### What you can influence - -You cannot control the other submissions or the program's constraints. You can make the proposal easy to evaluate: - -- Match the stated audience and theme -- Describe a focused problem and outcome -- Show a realistic plan for the time available -- Support claims and avoid hype -- Explain what distinguishes the session -- Follow every submission instruction - -Do not try to reverse-engineer a secret formula. Review processes vary, and a technique that worked at one event may be irrelevant at another. - -### Improve through reviewing - -If a community offers open proposal mentoring or volunteer reviewing, participate when you are qualified and have the time. Reading proposals teaches you how quickly ambiguity, excessive scope, and missing outcomes become visible. Respect confidentiality and declare conflicts of interest. - -## Part 6: Handle acceptance, waitlists, and rejection - -Every submission ends in one of a few outcomes. Responding professionally protects both you and the organizers and makes the next step easier. - -### If the proposal is accepted - -Celebrate, then verify the commitment before accepting. Confirm: - -- The exact event date, session length, and format -- Whether the title or abstract may be edited -- Travel, lodging, visa, ticket, and payment arrangements -- Recording and licensing terms -- Accessibility or technical requirements -- Important rehearsal and material deadlines - -Tell the organizers quickly if you cannot meet a condition. It is better to decline promptly than to accept and hope a major conflict disappears. - -Once confirmed, block preparation and travel time. Save the organizer's contact details somewhere accessible without internet service. - -### If the proposal is waitlisted - -A waitlist is a real possibility, not a promise. Ask when a final decision is likely and whether you should reserve travel. Do not make nonrefundable purchases unless the organizers clearly agree to cover them. - -Keep preparing only to the degree that the likelihood and timing justify. If another commitment creates a conflict, update the organizers rather than silently remaining unavailable. - -### If the proposal is rejected - -Rejection is common, including for experienced speakers. It does not establish that the idea is bad or that you do not belong on stage. The program may have received hundreds of proposals for a few dozen spaces. - -If feedback is offered, look for specific, actionable themes. Reviewers can be wrong or disagree with one another, so use judgment rather than applying every comment mechanically. If no feedback is offered, do not demand private deliberations from volunteer organizers. - -Revisit four possibilities: - -1. **Fit:** Was this the right event, track, and audience? -2. **Clarity:** Could a reviewer identify the problem and outcome quickly? -3. **Scope:** Was the plan realistic for the session length? -4. **Evidence:** Did the proposal support its important claims? - -Revise the idea, try a shorter version at a meetup, or submit it to a better-matched event. Also allow yourself to retire a proposal. Persistence means learning and choosing again, not sending the same text forever. - -### If circumstances change - -Withdraw as soon as you know you cannot speak. Give a brief, honest explanation and help the organizer recover time. You do not owe private medical or family details. - -Organizers may also cancel or change an event. Keep receipts, understand refund terms, and avoid costs you cannot absorb until arrangements are clear. - -## Part 7: Prepare before the conference - -Preparation turns an accepted idea into an experience the audience can follow. Start with the promise in the proposal; attendees chose the session based on it. - -### Design the story before the slides - -Write the central message in one sentence. Choose the few supporting points the audience needs, arrange them in a logical order, and decide what to leave out. - -A practical structure is: - -1. Establish the situation and why it matters. -2. Show the difficulty, constraint, or failed approach. -3. Explain what changed and why. -4. Demonstrate the result and its limits. -5. Give the audience concrete next steps. - -Slides are visual support, not the structure itself. Outline on paper or in plain text first. - -### Make evidence understandable - -Define necessary terms. Use readable charts, cite sources, and distinguish measurements from opinions. Protect confidential information and remove identifying customer or employee details unless you have explicit permission. - -When presenting a success story, include tradeoffs and conditions. When presenting a failure, focus on decisions and learning rather than blaming individuals. - -### Plan demonstrations defensively - -Live demonstrations are engaging and fragile. Simplify the environment, disable unrelated notifications, enlarge important text, and rehearse the exact path. Prepare screenshots, a recording, or a completed state so the lesson survives if the network or tool fails. - -Never expose production credentials, customer data, private source code, or internal messages. Use purpose-built examples. - -### Rehearse for time and comprehension - -Practice aloud from beginning to end. Silent review does not reveal timing, pronunciation, breath, or awkward transitions. Record a run and watch it once. Ask a peer to identify the main message and any unexplained assumptions. - -Rehearse until you can finish comfortably under the limit, including pauses and audience interaction. Decide in advance which optional section to skip if time is short. Do not solve an overlong talk by speaking faster. - -### Make the session accessible - -Use large text, strong contrast, descriptive link text, and meaningful labels on diagrams. Do not rely on color alone. Describe important visuals aloud and caption prerecorded video. Provide materials in a format that works with assistive technology when possible. - -Ask the conference about microphones, ramps, seating, captioning, interpreters, quiet spaces, and other support you need. Accessibility includes the speaker as well as the audience. - -### Prepare the logistics - -Confirm the slide aspect ratio, connection types, operating system constraints, internet availability, and whether you must provide materials in advance. Bring local copies of slides, fonts, videos, and demo dependencies. Carry the adapters you need and a backup on a separate device or drive. - -Know when and where to meet the session chair. Plan travel with enough margin for delays, and keep essential presentation equipment in your carry-on luggage. - -## Part 8: Give the presentation - -On the day, your job is not to perform perfection. It is to guide the audience through the promised idea. - -### Before the session - -Arrive early enough to find the room and test the actual equipment. Check that slides, demos, audio, confidence monitor, clicker, and microphone work. Learn how the organizer will signal remaining time and whether questions happen during or after the talk. - -Drink water, eat something appropriate for you, and use the restroom. Silence notifications and close unrelated applications. Put a timer where you can see it without repeatedly checking the wall clock. - -### Start clearly - -Pause, look at the audience, and begin. Briefly establish what the session is about, who it is for, and what people will leave with. You do not need to apologize for being nervous or recite your full biography. - -Speak more slowly than nervousness suggests. Use the microphone even if you believe the room can hear you; it may feed recording, captioning, or assistive listening systems. - -### Work with the room - -Look across different parts of the audience without fixing on one person. Allow time for laughter, reflection, and note-taking. If people enter late or leave, continue; their movement may have nothing to do with your session. - -If a demo fails, move to the backup and explain the lesson it was meant to show. If you lose your place, pause, check your notes, and continue from the next point. The audience usually experiences a short pause as much shorter than the speaker does. - -### Manage questions - -Repeat or summarize an audience question before answering so everyone hears it. Answer the question you understood, and ask for clarification when needed. It is fine to say you do not know, distinguish a hypothesis from a fact, or offer to follow up. - -Keep answers useful to the room. If one question becomes a detailed consultation, suggest continuing after the session. Ask the moderator for help if a participant monopolizes time or behaves inappropriately. - -### Finish intentionally - -Do not race through the conclusion. Restate the central lesson, give the audience a small next action, and show where they can find accessible materials or contact you if you want follow-up. - -Thank the audience and organizers, then stop. A clear ending is stronger than adding a new idea after the conclusion. - -### After the talk - -Save useful questions and feedback while they are fresh. Share slides, code, references, or corrections when promised and when you have permission. Watch the recording if one is published, but review it for one or two improvements rather than cataloging every mannerism. - -Thank the people who helped you prepare. Update the talk based on what the audience needed, not only on how the performance felt. Then rest: preparing and delivering a session is real work. - -## A simple first-speaker checklist - -- Choose one lesson grounded in your experience. -- Identify a specific audience and useful outcome. -- Find a conference whose topic, format, and terms fit. -- Write a clear title, abstract, outline, and biography. -- Ask for feedback and submit before the deadline. -- Treat the decision as program fit, not a verdict on your worth. -- If accepted, confirm the terms and prepare to the proposal's promise. -- Rehearse aloud, make the material accessible, and build backups. -- On the day, help the audience follow one idea at a time. -- Record what you learned and make the next version better. - -The path to the stage is not reserved for people who already look like conference speakers. It is open to practitioners willing to share a specific experience with care, clarity, and respect for the audience. +New to conference speaking? Begin with [Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/). diff --git a/guides/speaking/decide-why-you-want-to-speak.md b/guides/speaking/decide-why-you-want-to-speak.md new file mode 100644 index 00000000..a1ebb128 --- /dev/null +++ b/guides/speaking/decide-why-you-want-to-speak.md @@ -0,0 +1,48 @@ +--- +layout: page +permalink: /guides/speaking/decide-why-you-want-to-speak/ +title: "Part 2: Decide Why You Want to Speak" +--- + +[← Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/) + +*Part 2 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +Conference speaking takes time. A clear reason will help you choose opportunities, respond to setbacks, and decide when to say no. + +## Share a lesson + +You do not need to be the world's leading expert. You need a useful experience that you can explain honestly. A failed automation rewrite, an accessibility bug that changed your process, or a team experiment that improved feedback time may be exactly what another practitioner needs. + +The strongest experience reports include boundaries. Explain the context, what you tried, what happened, and where the lesson may not apply. Audiences usually trust a specific account more than a claim that one practice solves every problem. + +## Learn more deeply + +Preparing to teach exposes gaps in your understanding. Questions from reviewers, peers, and attendees force you to define terms, test assumptions, and support claims. Even when you already know the subject, turning experience into a coherent explanation can make you better at the work. + +## Build relationships + +Speaking gives people a reason to start a conversation with you. Those conversations can lead to collaborators, mentors, jobs, podcast invitations, open-source contributions, or friendships. Treat these as possible outcomes, not debts the audience owes you. + +## Represent a perspective + +Conference programs improve when they include people from different roles, regions, industries, career stages, and lived experiences. You may be able to describe constraints or communities that are rarely represented on stage. + +Do not wait until you feel like a universal authority. Be precise about what you know, credit the people who helped, and share the view you can responsibly offer. + +## Grow a career or business + +Speaking can demonstrate communication skills and subject knowledge. It may support consulting, training, developer relations, leadership, or a job search. If your employer benefits, discuss whether speaking preparation counts as work and whether the company will cover travel. + +Keep promotion proportional. A useful talk may mention a relevant product or service, but a disguised sales pitch breaks trust and is rejected by many conferences. + +## Make the commitment realistic + +Decide how much time and money you can spend, how far you can travel, and how public you want to be. Consider accessibility, caregiving, visas, health, and employer approval early. Virtual, local, and internal events are legitimate speaking opportunities and can fit constraints that destination conferences do not. + +Write down a modest first goal, such as giving one ten-minute talk, submitting to three well-matched events, or developing one session you can improve over a year. + +--- + +[← Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/) · [Part 3: Find Calls for Proposals →](/guides/speaking/find-calls-for-proposals/) + diff --git a/guides/speaking/find-calls-for-proposals.md b/guides/speaking/find-calls-for-proposals.md new file mode 100644 index 00000000..22452148 --- /dev/null +++ b/guides/speaking/find-calls-for-proposals.md @@ -0,0 +1,55 @@ +--- +layout: page +permalink: /guides/speaking/find-calls-for-proposals/ +title: "Part 3: Find Calls for Proposals" +--- + +[← Part 2: Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) + +*Part 3 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +A call for proposals—often shortened to CFP—is the period when a conference invites people to suggest sessions. It may also be called a call for papers, call for participation, or call for speakers. + +## Start with conferences you understand + +Look at events you have attended, communities you participate in, and conferences listed on [TestingConferences.org](/). Follow organizers and local groups, subscribe to event newsletters, and watch the official event site for dates. + +Conference directories and CFP newsletters help with discovery, but always verify the details on the organizer's official page. Deadlines, formats, themes, and event dates change. + +## Read the whole call + +Before drafting, record: + +- The submission deadline and time zone +- Event dates and location +- Tracks, themes, and intended audience +- Accepted session formats and lengths +- Required proposal fields and word limits +- Whether review is anonymous +- Whether previously delivered or published material is allowed +- Speaker benefits and expected costs +- Code of conduct and speaker terms +- When decisions are expected + +Do not assume every CFP uses the same definition of beginner, workshop, case study, or keynote. Use the language in the call. + +## Check the fit + +Review the current theme, previous programs, and videos when available. This shows the level and style of content the event selects. It can also reveal that your idea was covered recently, giving you a chance to choose a different angle. + +Fit is not the same as imitation. The program needs sessions that belong at the event, but it also needs ideas it has not already presented repeatedly. + +## Track opportunities + +A small spreadsheet or task board is enough. Include the conference, proposal, deadline, status, decision date, event date, costs, and important links. Set reminders before the deadline so you have time for feedback and technical problems. + +Start selectively. Three thoughtful submissions to suitable events teach you more than twenty generic submissions sent everywhere. + +## Watch for warning signs + +Be cautious when an event hides fees until late, pressures speakers to buy tickets, lacks identifiable organizers, has no code of conduct, copies another conference's material, or sends unsolicited acceptance for a subject you never proposed. Ask organizers direct questions. Declining a questionable opportunity is part of managing a speaking career. + +--- + +[← Part 2: Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) · [Part 4: Write and Submit a Proposal →](/guides/speaking/write-and-submit-a-proposal/) + diff --git a/guides/speaking/give-the-presentation.md b/guides/speaking/give-the-presentation.md new file mode 100644 index 00000000..a58fe4fa --- /dev/null +++ b/guides/speaking/give-the-presentation.md @@ -0,0 +1,67 @@ +--- +layout: page +permalink: /guides/speaking/give-the-presentation/ +title: "Part 8: Give the Presentation" +--- + +[← Part 7: Prepare Before the Conference](/guides/speaking/prepare-before-the-conference/) + +*Part 8 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +On the day, your job is not to perform perfection. It is to guide the audience through the promised idea. + +## Before the session + +Arrive early enough to find the room and test the actual equipment. Check that slides, demos, audio, confidence monitor, clicker, and microphone work. Learn how the organizer will signal remaining time and whether questions happen during or after the talk. + +Drink water, eat something appropriate for you, and use the restroom. Silence notifications and close unrelated applications. Put a timer where you can see it without repeatedly checking the wall clock. + +## Start clearly + +Pause, look at the audience, and begin. Briefly establish what the session is about, who it is for, and what people will leave with. You do not need to apologize for being nervous or recite your full biography. + +Speak more slowly than nervousness suggests. Use the microphone even if you believe the room can hear you; it may feed recording, captioning, or assistive listening systems. + +## Work with the room + +Look across different parts of the audience without fixing on one person. Allow time for laughter, reflection, and note-taking. If people enter late or leave, continue; their movement may have nothing to do with your session. + +If a demo fails, move to the backup and explain the lesson it was meant to show. If you lose your place, pause, check your notes, and continue from the next point. The audience usually experiences a short pause as much shorter than the speaker does. + +## Manage questions + +Repeat or summarize an audience question before answering so everyone hears it. Answer the question you understood, and ask for clarification when needed. It is fine to say you do not know, distinguish a hypothesis from a fact, or offer to follow up. + +Keep answers useful to the room. If one question becomes a detailed consultation, suggest continuing after the session. Ask the moderator for help if a participant monopolizes time or behaves inappropriately. + +## Finish intentionally + +Do not race through the conclusion. Restate the central lesson, give the audience a small next action, and show where they can find accessible materials or contact you if you want follow-up. + +Thank the audience and organizers, then stop. A clear ending is stronger than adding a new idea after the conclusion. + +## After the talk + +Save useful questions and feedback while they are fresh. Share slides, code, references, or corrections when promised and when you have permission. Watch the recording if one is published, but review it for one or two improvements rather than cataloging every mannerism. + +Thank the people who helped you prepare. Update the talk based on what the audience needed, not only on how the performance felt. Then rest: preparing and delivering a session is real work. + +## A simple first-speaker checklist + +- Choose one lesson grounded in your experience. +- Identify a specific audience and useful outcome. +- Find a conference whose topic, format, and terms fit. +- Write a clear title, abstract, outline, and biography. +- Ask for feedback and submit before the deadline. +- Treat the decision as program fit, not a verdict on your worth. +- If accepted, confirm the terms and prepare to the proposal's promise. +- Rehearse aloud, make the material accessible, and build backups. +- On the day, help the audience follow one idea at a time. +- Record what you learned and make the next version better. + +The path to the stage is not reserved for people who already look like conference speakers. It is open to practitioners willing to share a specific experience with care, clarity, and respect for the audience. + +--- + +[← Part 7: Prepare Before the Conference](/guides/speaking/prepare-before-the-conference/) · [Guide index](/guides/speaking-at-technology-conferences/) + diff --git a/guides/speaking/handle-acceptance-waitlists-and-rejection.md b/guides/speaking/handle-acceptance-waitlists-and-rejection.md new file mode 100644 index 00000000..8d1a1e19 --- /dev/null +++ b/guides/speaking/handle-acceptance-waitlists-and-rejection.md @@ -0,0 +1,58 @@ +--- +layout: page +permalink: /guides/speaking/handle-acceptance-waitlists-and-rejection/ +title: "Part 6: Handle Acceptance, Waitlists, and Rejection" +--- + +[← Part 5: Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) + +*Part 6 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +Every submission ends in one of a few outcomes. Responding professionally protects both you and the organizers and makes the next step easier. + +## If the proposal is accepted + +Celebrate, then verify the commitment before accepting. Confirm: + +- The exact event date, session length, and format +- Whether the title or abstract may be edited +- Travel, lodging, visa, ticket, and payment arrangements +- Recording and licensing terms +- Accessibility or technical requirements +- Important rehearsal and material deadlines + +Tell the organizers quickly if you cannot meet a condition. It is better to decline promptly than to accept and hope a major conflict disappears. + +Once confirmed, block preparation and travel time. Save the organizer's contact details somewhere accessible without internet service. + +## If the proposal is waitlisted + +A waitlist is a real possibility, not a promise. Ask when a final decision is likely and whether you should reserve travel. Do not make nonrefundable purchases unless the organizers clearly agree to cover them. + +Keep preparing only to the degree that the likelihood and timing justify. If another commitment creates a conflict, update the organizers rather than silently remaining unavailable. + +## If the proposal is rejected + +Rejection is common, including for experienced speakers. It does not establish that the idea is bad or that you do not belong on stage. The program may have received hundreds of proposals for a few dozen spaces. + +If feedback is offered, look for specific, actionable themes. Reviewers can be wrong or disagree with one another, so use judgment rather than applying every comment mechanically. If no feedback is offered, do not demand private deliberations from volunteer organizers. + +Revisit four possibilities: + +1. **Fit:** Was this the right event, track, and audience? +2. **Clarity:** Could a reviewer identify the problem and outcome quickly? +3. **Scope:** Was the plan realistic for the session length? +4. **Evidence:** Did the proposal support its important claims? + +Revise the idea, try a shorter version at a meetup, or submit it to a better-matched event. Also allow yourself to retire a proposal. Persistence means learning and choosing again, not sending the same text forever. + +## If circumstances change + +Withdraw as soon as you know you cannot speak. Give a brief, honest explanation and help the organizer recover time. You do not owe private medical or family details. + +Organizers may also cancel or change an event. Keep receipts, understand refund terms, and avoid costs you cannot absorb until arrangements are clear. + +--- + +[← Part 5: Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) · [Part 7: Prepare Before the Conference →](/guides/speaking/prepare-before-the-conference/) + diff --git a/guides/speaking/prepare-before-the-conference.md b/guides/speaking/prepare-before-the-conference.md new file mode 100644 index 00000000..9e25c6d7 --- /dev/null +++ b/guides/speaking/prepare-before-the-conference.md @@ -0,0 +1,60 @@ +--- +layout: page +permalink: /guides/speaking/prepare-before-the-conference/ +title: "Part 7: Prepare Before the Conference" +--- + +[← Part 6: Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) + +*Part 7 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +Preparation turns an accepted idea into an experience the audience can follow. Start with the promise in the proposal; attendees chose the session based on it. + +## Design the story before the slides + +Write the central message in one sentence. Choose the few supporting points the audience needs, arrange them in a logical order, and decide what to leave out. + +A practical structure is: + +1. Establish the situation and why it matters. +2. Show the difficulty, constraint, or failed approach. +3. Explain what changed and why. +4. Demonstrate the result and its limits. +5. Give the audience concrete next steps. + +Slides are visual support, not the structure itself. Outline on paper or in plain text first. + +## Make evidence understandable + +Define necessary terms. Use readable charts, cite sources, and distinguish measurements from opinions. Protect confidential information and remove identifying customer or employee details unless you have explicit permission. + +When presenting a success story, include tradeoffs and conditions. When presenting a failure, focus on decisions and learning rather than blaming individuals. + +## Plan demonstrations defensively + +Live demonstrations are engaging and fragile. Simplify the environment, disable unrelated notifications, enlarge important text, and rehearse the exact path. Prepare screenshots, a recording, or a completed state so the lesson survives if the network or tool fails. + +Never expose production credentials, customer data, private source code, or internal messages. Use purpose-built examples. + +## Rehearse for time and comprehension + +Practice aloud from beginning to end. Silent review does not reveal timing, pronunciation, breath, or awkward transitions. Record a run and watch it once. Ask a peer to identify the main message and any unexplained assumptions. + +Rehearse until you can finish comfortably under the limit, including pauses and audience interaction. Decide in advance which optional section to skip if time is short. Do not solve an overlong talk by speaking faster. + +## Make the session accessible + +Use large text, strong contrast, descriptive link text, and meaningful labels on diagrams. Do not rely on color alone. Describe important visuals aloud and caption prerecorded video. Provide materials in a format that works with assistive technology when possible. + +Ask the conference about microphones, ramps, seating, captioning, interpreters, quiet spaces, and other support you need. Accessibility includes the speaker as well as the audience. + +## Prepare the logistics + +Confirm the slide aspect ratio, connection types, operating system constraints, internet availability, and whether you must provide materials in advance. Bring local copies of slides, fonts, videos, and demo dependencies. Carry the adapters you need and a backup on a separate device or drive. + +Know when and where to meet the session chair. Plan travel with enough margin for delays, and keep essential presentation equipment in your carry-on luggage. + +--- + +[← Part 6: Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) · [Part 8: Give the Presentation →](/guides/speaking/give-the-presentation/) + diff --git a/guides/speaking/understand-how-conferences-choose-talks.md b/guides/speaking/understand-how-conferences-choose-talks.md new file mode 100644 index 00000000..ba74ba6d --- /dev/null +++ b/guides/speaking/understand-how-conferences-choose-talks.md @@ -0,0 +1,45 @@ +--- +layout: page +permalink: /guides/speaking/understand-how-conferences-choose-talks/ +title: "Part 5: Understand How Conferences Choose Talks" +--- + +[← Part 4: Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) + +*Part 5 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +Selection is usually program design, not a ranking of speakers from best to worst. A strong proposal can be declined because it duplicates another session, misses the theme, targets the wrong level, or does not fit the available schedule. + +## Eligibility and initial review + +Organizers may first remove incomplete, late, commercial, off-topic, or code-of-conduct-incompatible submissions. Following the instructions is the easiest selection factor to control. + +Reviewers then assess some combination of relevance, clarity, usefulness, originality, evidence, audience fit, and feasibility. In anonymous review, they may not see your name or biography at this stage. + +## Program balance + +The committee has to assemble a whole program. It may need a mix of beginner and advanced sessions, technical and human topics, talk formats, industries, and perspectives. Ten excellent proposals about the same popular tool cannot all occupy one track. + +Organizers may also consider speaker availability, travel budget, room capacity, previous program repetition, and whether a session depends on equipment they cannot support. + +## What you can influence + +You cannot control the other submissions or the program's constraints. You can make the proposal easy to evaluate: + +- Match the stated audience and theme +- Describe a focused problem and outcome +- Show a realistic plan for the time available +- Support claims and avoid hype +- Explain what distinguishes the session +- Follow every submission instruction + +Do not try to reverse-engineer a secret formula. Review processes vary, and a technique that worked at one event may be irrelevant at another. + +## Improve through reviewing + +If a community offers open proposal mentoring or volunteer reviewing, participate when you are qualified and have the time. Reading proposals teaches you how quickly ambiguity, excessive scope, and missing outcomes become visible. Respect confidentiality and declare conflicts of interest. + +--- + +[← Part 4: Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) · [Part 6: Handle Acceptance, Waitlists, and Rejection →](/guides/speaking/handle-acceptance-waitlists-and-rejection/) + diff --git a/guides/speaking/understand-technology-conferences.md b/guides/speaking/understand-technology-conferences.md new file mode 100644 index 00000000..50dead57 --- /dev/null +++ b/guides/speaking/understand-technology-conferences.md @@ -0,0 +1,55 @@ +--- +layout: page +permalink: /guides/speaking/understand-technology-conferences/ +title: "Part 1: Understand Technology Conferences" +--- + +[← Guide index](/guides/speaking-at-technology-conferences/) + +*Part 1 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +No two conferences are quite alike. Before deciding where to submit, learn what kind of event you are looking at and what its audience expects. + +## Topic and depth + +Some conferences focus tightly on one practice, tool, or community. A specialist testing event might spend an entire day on exploratory testing, performance engineering, accessibility, security, or test automation. These events let you go deep because much of the audience already shares the vocabulary and context. + +Broader technology conferences may cover development, operations, product, design, data, leadership, and quality. A talk at one of these events usually needs a little more context and a clear explanation of why the subject matters beyond your immediate specialty. + +## Tracks and formats + +A single-track conference puts every attendee in the same room. Your potential audience is larger, but not everyone will have chosen your subject. A multi-track conference lets attendees select the most relevant session, which can produce a smaller but more engaged room. + +Events may offer several formats: + +- Lightning talks of five to fifteen minutes +- Experience reports or case studies +- Standard sessions of thirty to sixty minutes +- Panels or facilitated discussions +- Hands-on workshops lasting several hours +- Keynotes intended for the whole conference + +Choose a format that fits both the idea and your experience. A focused lightning talk is often a better first step than stretching one lesson into a forty-five-minute session. A workshop needs exercises, facilitation, and enough time for attendees to practice; it is not simply a longer talk. + +## Audience and scale + +An event may be a local meetup with a few dozen people, a regional conference with several hundred, or an international gathering with thousands. Size affects the atmosphere, not necessarily the value. Small events can make conversation and connection easier. Large events may offer more topics and people but can feel less personal. + +Look beyond attendance numbers. Ask who comes to the event, what experience levels it serves, and whether attendees are mostly individual contributors, leaders, consultants, academics, tool builders, or a mixture. + +## Organizers and incentives + +Conferences can be community-run, nonprofit, commercial, or organized by a vendor. Each model can produce an excellent event, but its goals influence the program. A vendor event may favor its ecosystem. A volunteer event may have limited money and staff. A commercial conference may have stronger production support while expecting content that helps sell tickets. + +Read the code of conduct, speaker agreement, refund policy, and sponsor information. Find out whether speakers receive travel, lodging, an honorarium, a free ticket, or no financial support. None of these arrangements is automatically right or wrong, but you should understand the exchange before committing. + +## Why attend before speaking? + +Attending helps you learn how a community talks about its problems. You can discover techniques, meet collaborators, find future employers or employees, and see different presentation styles. You will also notice what makes an event welcoming—or difficult—to navigate. + +You do not have to attend conferences before you are qualified to speak. Your practical experience can be valuable now. Attending simply gives you more context for choosing the right event and designing a useful session. + +--- + +[← Guide index](/guides/speaking-at-technology-conferences/) · [Part 2: Decide Why You Want to Speak →](/guides/speaking/decide-why-you-want-to-speak/) + diff --git a/guides/speaking/write-and-submit-a-proposal.md b/guides/speaking/write-and-submit-a-proposal.md new file mode 100644 index 00000000..bda88707 --- /dev/null +++ b/guides/speaking/write-and-submit-a-proposal.md @@ -0,0 +1,67 @@ +--- +layout: page +permalink: /guides/speaking/write-and-submit-a-proposal/ +title: "Part 4: Write and Submit a Proposal" +--- + +[← Part 3: Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) + +*Part 4 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +A proposal is not the talk itself. It is evidence that you understand the audience, have a focused idea, and can deliver the session described. + +## Begin with the audience outcome + +Complete this sentence: “After this session, attendees will be able to…” Use a concrete verb. Compare approaches, diagnose a problem, design an experiment, or apply a technique is clearer than understand or learn about. + +Then define the audience. A session for test automation beginners should not quietly require advanced knowledge of distributed systems. A leadership talk should explain why its lesson matters to people responsible for teams or strategy. + +## Narrow the idea + +A useful talk usually has one central promise supported by a few points. “Everything about software testing” is too broad. “Three ways our team made flaky end-to-end tests easier to diagnose” establishes a problem, scope, and likely outcome. + +Narrowing does not make an idea less impressive. It makes the proposal credible and the talk memorable. + +## Write a clear title + +The title should help reviewers and attendees predict the subject. Personality and wordplay can help, but clarity comes first. If a clever title could describe five unrelated talks, add a subtitle or rewrite it. + +Avoid claims the talk cannot support. Words such as always, never, perfect, and effortless invite skepticism and rarely reflect real engineering work. + +## Build the abstract + +Unless the CFP requests a different structure, a strong public abstract answers four questions: + +1. What problem or opportunity does this session address? +2. Why does it matter to this audience? +3. What will the speaker cover or demonstrate? +4. What can attendees take back to their work? + +Write for a person scanning many submissions. Open with the substance, use plain language, and remove background that does not help someone choose the session. + +## Give reviewers the detail they need + +Many systems include private notes, an outline, or a field for the program committee. Use it. Describe the session's progression, examples, evidence, demonstrations, exercises, and timing. Explain what is original about your perspective and disclose vendor relationships. + +If the talk relies on a case study, include enough context to evaluate it. If it makes an empirical claim, identify the evidence. If it is interactive, describe how the interaction will work for the expected room and time. + +## Write an appropriate biography + +Your biography should establish why you can give this particular session. Mention relevant work, community experience, or prior exploration without turning it into a complete career history. First-time speakers can demonstrate credibility through the work itself; prior conference appearances are not the only qualification. + +## Get feedback and revise + +Ask at least one person in the intended audience and one person unfamiliar with the topic to read the proposal. Useful questions include: + +- What do you think this talk will teach? +- Who is it for? +- Which sentence is confusing? +- What would make you attend—or skip—it? +- Does the promised outcome fit the session length? + +Read the abstract aloud, check every required field, preserve a copy, and submit before the last hour. Confirm that the system shows the proposal as received. + +--- + +[← Part 3: Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) · [Part 5: Understand How Conferences Choose Talks →](/guides/speaking/understand-how-conferences-choose-talks/) + From 154ed7411b38bd76565ca90a5d75696abe27b989 Mon Sep 17 00:00:00 2001 From: Chris Kenst Date: Fri, 7 Aug 2026 19:31:45 -0700 Subject: [PATCH 3/4] Expand reasons to speak guide --- .../speaking/decide-why-you-want-to-speak.md | 101 ++++++++++++++---- 1 file changed, 83 insertions(+), 18 deletions(-) diff --git a/guides/speaking/decide-why-you-want-to-speak.md b/guides/speaking/decide-why-you-want-to-speak.md index a1ebb128..91421d8a 100644 --- a/guides/speaking/decide-why-you-want-to-speak.md +++ b/guides/speaking/decide-why-you-want-to-speak.md @@ -8,41 +8,106 @@ title: "Part 2: Decide Why You Want to Speak" *Part 2 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* -Conference speaking takes time. A clear reason will help you choose opportunities, respond to setbacks, and decide when to say no. +Conference speaking takes time. A clear reason will help you choose opportunities, respond to setbacks, and decide when to say no. You may recognize yourself in several of the motivations below, and your reasons may change as you gain experience. -## Share a lesson +This article expands on the themes in CFP Land's archived [“Why Speak? 11 Reasons People Get on Stage”](https://web.archive.org/web/20220701014119mp_/https://www.cfpland.com/guides/speaking/why-speak/), adapting them for today's software testing and quality communities. -You do not need to be the world's leading expert. You need a useful experience that you can explain honestly. A failed automation rewrite, an accessibility bug that changed your process, or a team experiment that improved feedback time may be exactly what another practitioner needs. +## 1. Make speaking part of a professional advocacy role -The strongest experience reports include boundaries. Explain the context, what you tried, what happened, and where the lesson may not apply. Audiences usually trust a specific account more than a claim that one practice solves every problem. +Some technology professionals are employed specifically to teach and support a technical community. Their titles include developer advocate, developer relations engineer, community advocate, product educator, or technical evangelist. Speaking may be one part of the job alongside writing examples, helping users, gathering product feedback, producing documentation, and supporting open-source projects. -## Learn more deeply +Testing and quality-tool companies have similar roles even when they use different titles. A person might demonstrate an automation framework, explain an observability technique, teach customers how to test an API, or bring practitioners' recurring problems back to a product team. -Preparing to teach exposes gaps in your understanding. Questions from reviewers, peers, and attendees force you to define terms, test assumptions, and support claims. Even when you already know the subject, turning experience into a coherent explanation can make you better at the work. +Conference experience can help you explore this career path, but prolific travel is not the only model. Advocacy can also happen through online events, workshops, local communities, documentation, livestreams, and recorded lessons. If the role interests you, pay attention to whether you enjoy the preparation and follow-up work as much as being on stage. -## Build relationships +## 2. Promote a business, service, or project -Speaking gives people a reason to start a conversation with you. Those conversations can lead to collaborators, mentors, jobs, podcast invitations, open-source contributions, or friendships. Treat these as possible outcomes, not debts the audience owes you. +Consultants, trainers, authors, and small-business owners often speak to demonstrate how they think. A useful session can help future clients understand the problems you solve without requiring a sales pitch. Maintainers may also speak to help an open-source project reach people who could use or contribute to it. -## Represent a perspective +Promotion works best when the audience receives value whether or not they ever hire you or adopt your tool. Teach the underlying problem, discuss alternatives, disclose your connection, and explain tradeoffs. A presentation built around exaggerated claims or a product demonstration disguised as education can damage trust and may violate the conference's rules. -Conference programs improve when they include people from different roles, regions, industries, career stages, and lived experiences. You may be able to describe constraints or communities that are rarely represented on stage. +Treat commercial outcomes as possible rather than guaranteed. Speaking may lead to a conversation months later, or it may lead nowhere measurable. Decide in advance whether the event is still worthwhile without an immediate sale. -Do not wait until you feel like a universal authority. Be precise about what you know, credit the people who helped, and share the view you can responsibly offer. +## 3. Help other practitioners -## Grow a career or business +You do not need to be the world's leading expert to help someone. You need a useful experience that you can explain honestly. A failed automation rewrite, an accessibility bug that changed your process, or a team experiment that improved feedback time may be exactly what another practitioner needs. -Speaking can demonstrate communication skills and subject knowledge. It may support consulting, training, developer relations, leadership, or a job search. If your employer benefits, discuss whether speaking preparation counts as work and whether the company will cover travel. +A familiar subject can still be valuable. New people continually enter the profession, and your explanation may connect with someone whom earlier explanations did not reach. Your particular industry, constraints, mistakes, or way of illustrating an idea can make an established lesson newly useful. -Keep promotion proportional. A useful talk may mention a relevant product or service, but a disguised sales pitch breaks trust and is rejected by many conferences. +The strongest experience reports include boundaries. Explain the context, what you tried, what happened, and where the lesson may not apply. Helping an audience includes protecting them from overgeneralizing your success. -## Make the commitment realistic +## 4. Meet people who share your interests -Decide how much time and money you can spend, how far you can travel, and how public you want to be. Consider accessibility, caregiving, visas, health, and employer approval early. Virtual, local, and internal events are legitimate speaking opportunities and can fit constraints that destination conferences do not. +Speaking gives attendees an easy reason to begin a conversation with you. They already know one subject you care about and can ask about a detail from the session. This can make a large event more approachable for people who dislike unstructured networking. -Write down a modest first goal, such as giving one ten-minute talk, submitting to three well-matched events, or developing one session you can improve over a year. +Those conversations can lead to collaborators, mentors, podcast invitations, open-source contributions, future speaking opportunities, or friendships. Conferences can also connect you with practitioners from industries and countries whose constraints are very different from yours. + +Leave time for those connections. When possible, attend other sessions, shared meals, or community activities instead of arriving immediately before your talk and leaving immediately afterward. At the same time, protect your energy: you are allowed to take breaks, decline a conversation, or choose a smaller social setting. + +## 5. Build professional recognition + +A clear, useful talk can make your work more visible. Attendees may remember your explanation, recommend a recording, follow your writing, or invite you to contribute elsewhere. Over time, a body of talks can demonstrate a recognizable area of expertise. + +Recognition is not the same as celebrity. View counts and follower totals are incomplete measures of impact, and conference selection is not a ranking of personal importance. Chasing attention can also encourage exaggerated titles, unnecessary controversy, or speaking far beyond your evidence. + +Aim to be known for helping people understand something, treating communities well, and representing your experience accurately. Recognition built on trust is slower but more useful than attention by itself. + +## 6. Travel to new places + +Conference speaking can make travel possible or more affordable. Some events pay for transportation and lodging; others offer a fixed stipend, an honorarium, a complimentary ticket, or no financial support at all. Never assume that acceptance includes expenses. + +Before accepting, ask what is covered, when reimbursement occurs, whether you must pay upfront, and what happens if the event is cancelled. Include ground transportation, meals, visas, insurance, taxes, accessibility needs, and extra nights in your calculation. A “free trip” can still be expensive and requires preparation time away from work or family. + +If you extend a trip for personal travel, clearly separate the costs the organizer approved from those you will pay. Travel can be a delightful benefit, but it should not pressure you into accepting financial risk you cannot carry. + +## 7. Develop confidence and communication skills + +Preparing and delivering talks gives you repeated practice explaining complex ideas to unfamiliar people. That practice can improve design reviews, stakeholder conversations, training, interviews, facilitation, and leadership—not only future conference appearances. + +Confidence usually grows through manageable repetitions rather than one dramatic leap. An internal lunch-and-learn, community meetup, panel, or lightning talk may be a better starting point than a large international stage. Record a rehearsal, ask for focused feedback, and choose one skill to improve at a time. + +Speaking does not affect everyone the same way. Anxiety may diminish with experience, remain present, or require accommodations and professional support. Success does not require becoming an extrovert or enjoying every moment in front of a crowd. + +## 8. Create career opportunities or find a job + +A conference talk can provide concrete evidence that you understand a subject and can communicate it. Recruiters or hiring managers may encounter your session, and people you meet may later tell you about a role. Talks can also lead to teaching, writing, workshops, community leadership, or other work you had not considered. + +Do not turn the session into a public résumé. Concentrate on the audience's problem and let your biography, profile, or conversations provide career context. If you are job seeking, make it easy to find accurate contact information and state the kinds of opportunities you are open to. + +Remember that public visibility has risks. Decide how much personal information to publish, separate professional contact channels when helpful, and ask organizers how recordings and attendee data are handled. + +## 9. Enjoy the energy of performing + +For some people, completing a talk brings a powerful burst of energy and satisfaction. The combination of preparation, nervous anticipation, focused delivery, and audience response can make speaking genuinely fun. That feeling alone can be a valid reason to return to the stage. + +Other speakers feel exhausted afterward and need quiet time. Many experience both reactions at different events. Plan around your own nervous system rather than imitating a speaker who thrives on a packed schedule. + +Enjoying the stage should not displace the audience's needs. The presentation is still an exchange of their time and attention for something useful. The best performance energy supports the lesson instead of becoming the lesson. + +## 10. Advocate for a cause or an overlooked perspective + +Technology decisions affect accessibility, privacy, safety, labor, sustainability, fairness, and people's ability to participate in society. A conference session can show practitioners how ordinary design, development, and testing choices contribute to those outcomes. + +Conference programs also improve when they include people from different roles, regions, industries, career stages, and lived experiences. You may be able to describe constraints or communities that are rarely represented on stage. + +Approach advocacy with care. Center affected people rather than using them as an abstract example, protect private information, cite their work, and do not claim to represent a whole community. Be precise about what you know and what action you are asking the audience to take. + +## 11. Learn through teaching + +Preparing to teach exposes gaps in your understanding. Questions from reviewers, peers, and attendees force you to define terms, test assumptions, build demonstrations, and support claims. Turning experience into a coherent explanation can make you better at the work even when the proposal is not accepted. + +Some speakers deliberately choose a subject they want to explore more deeply. That can work when the proposal honestly reflects their level of experience and they leave enough time for research and review. A conference deadline can provide useful motivation, but it should not become a reason to present speculation as expertise. + +Teaching is especially powerful when you build an example, compare approaches, or explain why a technique failed. The process makes hidden assumptions visible and often produces reusable notes, code, diagrams, or exercises. + +## Choose a reason that can sustain the work + +Your primary motivation affects which events make sense. Someone seeking community may favor a small participatory conference. A professional advocate may prioritize the right technical audience. A person developing confidence may choose a local lightning talk. Someone hoping to travel must look closely at expense policies. + +Decide how much time and money you can spend, how far you can travel, and how public you want to be. Consider accessibility, caregiving, visas, health, and employer approval early. If your employer benefits, discuss whether preparation counts as work and whether the company will cover costs. + +Write down a modest first goal, such as giving one ten-minute talk, submitting to three well-matched events, or developing one session you can improve over a year. A clear reason and a realistic goal make it easier to continue—and easier to decline opportunities that do not fit. --- [← Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/) · [Part 3: Find Calls for Proposals →](/guides/speaking/find-calls-for-proposals/) - From 0235711a8f1cf9553f953f3f3cdffde5d4163a63 Mon Sep 17 00:00:00 2001 From: Chris Kenst Date: Fri, 7 Aug 2026 19:39:58 -0700 Subject: [PATCH 4/4] Align speaking series with archived guide --- guides/speaking-at-technology-conferences.md | 18 ++--- .../speaking/decide-why-you-want-to-speak.md | 2 +- guides/speaking/find-calls-for-proposals.md | 32 +++++++-- guides/speaking/give-the-presentation.md | 67 ------------------ ...ndle-acceptance-waitlists-and-rejection.md | 15 +++- ...d => prepare-a-conference-presentation.md} | 28 ++++++-- guides/speaking/prepare-for-the-conference.md | 69 +++++++++++++++++++ ...understand-how-conferences-choose-talks.md | 27 ++++++-- .../speaking/write-and-submit-a-proposal.md | 39 +++++++++-- 9 files changed, 198 insertions(+), 99 deletions(-) delete mode 100644 guides/speaking/give-the-presentation.md rename guides/speaking/{prepare-before-the-conference.md => prepare-a-conference-presentation.md} (61%) create mode 100644 guides/speaking/prepare-for-the-conference.md diff --git a/guides/speaking-at-technology-conferences.md b/guides/speaking-at-technology-conferences.md index 9f9e4fce..5792f1cd 100644 --- a/guides/speaking-at-technology-conferences.md +++ b/guides/speaking-at-technology-conferences.md @@ -18,22 +18,22 @@ This eight-part guide follows that journey from the first thought of speaking th 2. [Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) Identify what you want to share and make the commitment realistic. -3. [Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) +3. [Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) + See how reviewers evaluate proposals and assemble a balanced program. + +4. [Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) Discover suitable CFPs, evaluate event fit, and track opportunities. -4. [Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) +5. [Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) Turn an idea into a clear title, abstract, outline, and biography. -5. [Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) - See how reviewers evaluate proposals and assemble a balanced program. - 6. [Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) Respond professionally to every possible submission outcome. -7. [Prepare Before the Conference](/guides/speaking/prepare-before-the-conference/) - Design, rehearse, and make the session accessible and resilient. +7. [Prepare a Conference Presentation](/guides/speaking/prepare-a-conference-presentation/) + Choose a format, design the material, rehearse, and build resilient demos. -8. [Give the Presentation](/guides/speaking/give-the-presentation/) - Set up, deliver the talk, manage questions, and learn from the experience. +8. [Prepare for the Conference](/guides/speaking/prepare-for-the-conference/) + Manage travel, equipment, on-site checks, and the hours before speaking. New to conference speaking? Begin with [Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/). diff --git a/guides/speaking/decide-why-you-want-to-speak.md b/guides/speaking/decide-why-you-want-to-speak.md index 91421d8a..c1a2f714 100644 --- a/guides/speaking/decide-why-you-want-to-speak.md +++ b/guides/speaking/decide-why-you-want-to-speak.md @@ -110,4 +110,4 @@ Write down a modest first goal, such as giving one ten-minute talk, submitting t --- -[← Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/) · [Part 3: Find Calls for Proposals →](/guides/speaking/find-calls-for-proposals/) +[← Part 1: Understand Technology Conferences](/guides/speaking/understand-technology-conferences/) · [Part 3: Understand How Conferences Choose Talks →](/guides/speaking/understand-how-conferences-choose-talks/) diff --git a/guides/speaking/find-calls-for-proposals.md b/guides/speaking/find-calls-for-proposals.md index 22452148..5a9010c1 100644 --- a/guides/speaking/find-calls-for-proposals.md +++ b/guides/speaking/find-calls-for-proposals.md @@ -1,15 +1,24 @@ --- layout: page permalink: /guides/speaking/find-calls-for-proposals/ -title: "Part 3: Find Calls for Proposals" +title: "Part 4: Find Calls for Proposals" --- -[← Part 2: Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) +[← Part 3: Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) -*Part 3 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* +*Part 4 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* A call for proposals—often shortened to CFP—is the period when a conference invites people to suggest sessions. It may also be called a call for papers, call for participation, or call for speakers. +This article expands on CFP Land's archived [“Finding and Selecting CFPs”](https://web.archive.org/web/20220701014120mp_/https://www.cfpland.com/guides/speaking/finding-cfps/). + +## Four ways to discover CFPs + +1. **Contact a conference directly.** This is useful when an event is invitation-only or has not announced whether it will run an open call. Avoid repeatedly chasing volunteer organizers when the information is already published. +2. **Subscribe to official updates.** Conference newsletters, blogs, and community mailing lists are the strongest sources when you care about a small set of events. +3. **Follow community channels.** Organizers and speakers share CFPs through social networks, forums, Slack or Discord groups, meetups, and professional associations. Platforms change, so follow the community rather than relying on one social network. +4. **Use directories and aggregators.** These make broad discovery efficient but are never complete. Verify every deadline and benefit on the official event page. + ## Start with conferences you understand Look at events you have attended, communities you participate in, and conferences listed on [TestingConferences.org](/). Follow organizers and local groups, subscribe to event newsletters, and watch the official event site for dates. @@ -39,6 +48,20 @@ Review the current theme, previous programs, and videos when available. This sho Fit is not the same as imitation. The program needs sessions that belong at the event, but it also needs ideas it has not already presented repeatedly. +Consider location and delivery format as well as topic. Time zones, flight duration, visas, accessibility, personal safety, and remote-production requirements can turn an attractive event into an unrealistic commitment. + +## Check financial viability + +Find out whether the event covers travel, lodging, local transportation, meals, visas, a speaker ticket, or an honorarium. Ask how booking and reimbursement work and whether you must carry costs for months. Employer professional-development funding may help, but obtain approval before treating it as available. + +Nonfinancial support matters too: speaker coaching, rehearsal sessions, accessibility support, childcare, a speaker dinner, or a private coordination channel can make an event much more workable. + +## Evaluate reputation and inclusion + +Review earlier programs, recordings, attendee accounts, and the people behind the event. A first-year conference is not automatically risky, but it gives you less history to assess. Ask how organizers handle cancellations, harassment reports, accessibility, and speaker communication. + +Look for an enforceable code of conduct and evidence that the program welcomes more than one narrow professional or demographic group. Consider whether you would be comfortable lending your name to the event even if your talk were the only session an attendee saw. + ## Track opportunities A small spreadsheet or task board is enough. Include the conference, proposal, deadline, status, decision date, event date, costs, and important links. Set reminders before the deadline so you have time for feedback and technical problems. @@ -51,5 +74,4 @@ Be cautious when an event hides fees until late, pressures speakers to buy ticke --- -[← Part 2: Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) · [Part 4: Write and Submit a Proposal →](/guides/speaking/write-and-submit-a-proposal/) - +[← Part 3: Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) · [Part 5: Write and Submit a Proposal →](/guides/speaking/write-and-submit-a-proposal/) diff --git a/guides/speaking/give-the-presentation.md b/guides/speaking/give-the-presentation.md deleted file mode 100644 index a58fe4fa..00000000 --- a/guides/speaking/give-the-presentation.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -layout: page -permalink: /guides/speaking/give-the-presentation/ -title: "Part 8: Give the Presentation" ---- - -[← Part 7: Prepare Before the Conference](/guides/speaking/prepare-before-the-conference/) - -*Part 8 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* - -On the day, your job is not to perform perfection. It is to guide the audience through the promised idea. - -## Before the session - -Arrive early enough to find the room and test the actual equipment. Check that slides, demos, audio, confidence monitor, clicker, and microphone work. Learn how the organizer will signal remaining time and whether questions happen during or after the talk. - -Drink water, eat something appropriate for you, and use the restroom. Silence notifications and close unrelated applications. Put a timer where you can see it without repeatedly checking the wall clock. - -## Start clearly - -Pause, look at the audience, and begin. Briefly establish what the session is about, who it is for, and what people will leave with. You do not need to apologize for being nervous or recite your full biography. - -Speak more slowly than nervousness suggests. Use the microphone even if you believe the room can hear you; it may feed recording, captioning, or assistive listening systems. - -## Work with the room - -Look across different parts of the audience without fixing on one person. Allow time for laughter, reflection, and note-taking. If people enter late or leave, continue; their movement may have nothing to do with your session. - -If a demo fails, move to the backup and explain the lesson it was meant to show. If you lose your place, pause, check your notes, and continue from the next point. The audience usually experiences a short pause as much shorter than the speaker does. - -## Manage questions - -Repeat or summarize an audience question before answering so everyone hears it. Answer the question you understood, and ask for clarification when needed. It is fine to say you do not know, distinguish a hypothesis from a fact, or offer to follow up. - -Keep answers useful to the room. If one question becomes a detailed consultation, suggest continuing after the session. Ask the moderator for help if a participant monopolizes time or behaves inappropriately. - -## Finish intentionally - -Do not race through the conclusion. Restate the central lesson, give the audience a small next action, and show where they can find accessible materials or contact you if you want follow-up. - -Thank the audience and organizers, then stop. A clear ending is stronger than adding a new idea after the conclusion. - -## After the talk - -Save useful questions and feedback while they are fresh. Share slides, code, references, or corrections when promised and when you have permission. Watch the recording if one is published, but review it for one or two improvements rather than cataloging every mannerism. - -Thank the people who helped you prepare. Update the talk based on what the audience needed, not only on how the performance felt. Then rest: preparing and delivering a session is real work. - -## A simple first-speaker checklist - -- Choose one lesson grounded in your experience. -- Identify a specific audience and useful outcome. -- Find a conference whose topic, format, and terms fit. -- Write a clear title, abstract, outline, and biography. -- Ask for feedback and submit before the deadline. -- Treat the decision as program fit, not a verdict on your worth. -- If accepted, confirm the terms and prepare to the proposal's promise. -- Rehearse aloud, make the material accessible, and build backups. -- On the day, help the audience follow one idea at a time. -- Record what you learned and make the next version better. - -The path to the stage is not reserved for people who already look like conference speakers. It is open to practitioners willing to share a specific experience with care, clarity, and respect for the audience. - ---- - -[← Part 7: Prepare Before the Conference](/guides/speaking/prepare-before-the-conference/) · [Guide index](/guides/speaking-at-technology-conferences/) - diff --git a/guides/speaking/handle-acceptance-waitlists-and-rejection.md b/guides/speaking/handle-acceptance-waitlists-and-rejection.md index 8d1a1e19..038f0a43 100644 --- a/guides/speaking/handle-acceptance-waitlists-and-rejection.md +++ b/guides/speaking/handle-acceptance-waitlists-and-rejection.md @@ -4,12 +4,14 @@ permalink: /guides/speaking/handle-acceptance-waitlists-and-rejection/ title: "Part 6: Handle Acceptance, Waitlists, and Rejection" --- -[← Part 5: Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) +[← Part 5: Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) *Part 6 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* Every submission ends in one of a few outcomes. Responding professionally protects both you and the organizers and makes the next step easier. +This article expands on CFP Land's archived [“What Comes Next? Dealing with Success or Rejection”](https://web.archive.org/web/20220701014118mp_/https://www.cfpland.com/guides/speaking/success-rejection/). + ## If the proposal is accepted Celebrate, then verify the commitment before accepting. Confirm: @@ -25,6 +27,10 @@ Tell the organizers quickly if you cannot meet a condition. It is better to decl Once confirmed, block preparation and travel time. Save the organizer's contact details somewhere accessible without internet service. +Acceptance can trigger doubt as well as excitement. Remember that the committee chose the proposal with more context than your anxious inner critic has. You do not need to know everything about the subject; you need to deliver the bounded session you promised. Seek a rehearsal partner or speaker mentor rather than withdrawing solely because you feel like an impostor. + +Keep expectations flexible. Events, formats, rooms, and schedules can change, and in rare cases the whole conference may be cancelled. Avoid tying your self-worth or unrecoverable expenses to plans that are not final. + ## If the proposal is waitlisted A waitlist is a real possibility, not a promise. Ask when a final decision is likely and whether you should reserve travel. Do not make nonrefundable purchases unless the organizers clearly agree to cover them. @@ -37,6 +43,8 @@ Rejection is common, including for experienced speakers. It does not establish t If feedback is offered, look for specific, actionable themes. Reviewers can be wrong or disagree with one another, so use judgment rather than applying every comment mechanically. If no feedback is offered, do not demand private deliberations from volunteer organizers. +Some events never send a rejection and simply publish the program. That is poor communication, but it is not an invitation to harass organizers. After the stated notification date, ask once, update your tracker, and make other plans. + Revisit four possibilities: 1. **Fit:** Was this the right event, track, and audience? @@ -46,6 +54,8 @@ Revisit four possibilities: Revise the idea, try a shorter version at a meetup, or submit it to a better-matched event. Also allow yourself to retire a proposal. Persistence means learning and choosing again, not sending the same text forever. +When asking for feedback, make the request easy to decline. You can also compare the accepted program with your proposal: look for topic overlap, missing levels, and differences in specificity without assuming you know the committee's private reasoning. Rejection happens to experienced speakers too and often reflects program constraints rather than proposal quality. + ## If circumstances change Withdraw as soon as you know you cannot speak. Give a brief, honest explanation and help the organizer recover time. You do not owe private medical or family details. @@ -54,5 +64,4 @@ Organizers may also cancel or change an event. Keep receipts, understand refund --- -[← Part 5: Understand How Conferences Choose Talks](/guides/speaking/understand-how-conferences-choose-talks/) · [Part 7: Prepare Before the Conference →](/guides/speaking/prepare-before-the-conference/) - +[← Part 5: Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) · [Part 7: Prepare a Conference Presentation →](/guides/speaking/prepare-a-conference-presentation/) diff --git a/guides/speaking/prepare-before-the-conference.md b/guides/speaking/prepare-a-conference-presentation.md similarity index 61% rename from guides/speaking/prepare-before-the-conference.md rename to guides/speaking/prepare-a-conference-presentation.md index 9e25c6d7..796d5fe1 100644 --- a/guides/speaking/prepare-before-the-conference.md +++ b/guides/speaking/prepare-a-conference-presentation.md @@ -1,7 +1,7 @@ --- layout: page -permalink: /guides/speaking/prepare-before-the-conference/ -title: "Part 7: Prepare Before the Conference" +permalink: /guides/speaking/prepare-a-conference-presentation/ +title: "Part 7: Prepare a Conference Presentation" --- [← Part 6: Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) @@ -10,6 +10,19 @@ title: "Part 7: Prepare Before the Conference" Preparation turns an accepted idea into an experience the audience can follow. Start with the promise in the proposal; attendees chose the session based on it. +This article expands on CFP Land's archived [“Preparing a Conference Presentation”](https://web.archive.org/web/20220701014119mp_/https://www.cfpland.com/guides/speaking/presentation/). + +## Choose a presentation shape + +Different ideas need different structures. Four useful starting points are: + +1. **A new solution to a familiar problem:** establish the problem, compare existing approaches, then demonstrate and qualify your approach. +2. **A change journey:** show the original situation, the disruption or failure, the difficult middle, and what you learned—not just a polished victory. +3. **A technical deep dive:** take the audience beneath a tool's normal interface and explain mechanisms, evidence, and consequences they rarely see. +4. **A live demonstration:** build or investigate something in real time while narrating the decisions. Rehearse heavily and prepare a recording, screenshots, or completed state for every fragile step. + +These are scaffolds, not rules. A testing experience report might combine a change story with a technical demonstration and finish with a decision framework. + ## Design the story before the slides Write the central message in one sentence. Choose the few supporting points the audience needs, arrange them in a logical order, and decide what to leave out. @@ -48,6 +61,14 @@ Use large text, strong contrast, descriptive link text, and meaningful labels on Ask the conference about microphones, ramps, seating, captioning, interpreters, quiet spaces, and other support you need. Accessibility includes the speaker as well as the audience. +## Choose familiar tools + +Slides are common, but they are not mandatory. Use a tool you can operate without spending attention on it. If you include video or audio, embed local copies, add captions, and test venue playback. Practice with the same laptop, slide remote, microphone style, and adapters you expect to use. + +Keep slides focused on illustration, evidence, and orientation. Dense paragraphs force people to choose between reading and listening. The opening slide should identify the session for people entering the room or watching a recording; the closing slide can hold accessible resources and contact details. + +Use humor only when it supports the audience's comfort and the lesson. Avoid making a person or community the target, and test uncertain material with someone who can challenge it honestly. + ## Prepare the logistics Confirm the slide aspect ratio, connection types, operating system constraints, internet availability, and whether you must provide materials in advance. Bring local copies of slides, fonts, videos, and demo dependencies. Carry the adapters you need and a backup on a separate device or drive. @@ -56,5 +77,4 @@ Know when and where to meet the session chair. Plan travel with enough margin fo --- -[← Part 6: Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) · [Part 8: Give the Presentation →](/guides/speaking/give-the-presentation/) - +[← Part 6: Handle Acceptance, Waitlists, and Rejection](/guides/speaking/handle-acceptance-waitlists-and-rejection/) · [Part 8: Prepare for the Conference →](/guides/speaking/prepare-for-the-conference/) diff --git a/guides/speaking/prepare-for-the-conference.md b/guides/speaking/prepare-for-the-conference.md new file mode 100644 index 00000000..4fa10857 --- /dev/null +++ b/guides/speaking/prepare-for-the-conference.md @@ -0,0 +1,69 @@ +--- +layout: page +permalink: /guides/speaking/prepare-for-the-conference/ +title: "Part 8: Prepare for the Conference" +--- + +[← Part 7: Prepare a Conference Presentation](/guides/speaking/prepare-a-conference-presentation/) + +*Part 8 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* + +Good preparation removes avoidable uncertainty so you can concentrate on the audience. This article expands on CFP Land's archived [“Preparing for the Conference”](https://web.archive.org/web/20220701014119mp_/https://www.cfpland.com/guides/speaking/pre-conference/). + +## One to three months before + +- **Get employer approval.** Confirm whether travel and preparation are work time, whether legal or communications review is required, and what information must remain confidential. +- **Reconfirm the event.** Verify dates, venue, session format, reimbursement rules, recording terms, and accessibility arrangements before spending money. +- **Book travel and lodging.** Establish who pays, which expenses qualify, how reimbursement works, and what happens after cancellation. Keep personal extensions separate from covered travel. +- **Prepare documents.** International events may require a passport, visa, invitation letter, insurance, or tax form. Begin early and do not rely on organizers for legal advice. +- **Join speaker communication.** Note briefings, rehearsals, dinners, private channels, and deadlines. These can be valuable places to meet other speakers and resolve common questions. +- **Keep rehearsing.** Lock the main structure early enough to practice the real session rather than endlessly redesigning slides. + +## One to two weeks before + +Reread the conference website, code of conduct, speaker handbook, and your accepted proposal. Confirm the audience, title, duration, room format, question policy, and material-delivery deadline. + +Plan the entire route: airport or station to lodging, lodging to venue, and late-night or accessible alternatives. Review the schedule so you know when to arrive, what overlaps with your talk, and which sessions or people you hope to encounter. + +Choose clothing that works for the venue, microphone, lighting, temperature, movement, and your own comfort. Avoid last-minute experiments. Ask what equipment is provided: laptop or bring-your-own device, display connection, aspect ratio, confidence monitor, microphone, remote, power, audio, internet, and dedicated demo network. + +Create offline backups of slides, fonts, videos, demos, notes, and contact information. Keep a copy on another device or drive. Disable notifications and ensure examples contain no credentials or private data. + +## When you arrive + +Find the room and view it from the audience. Locate the stage entrance, lectern, timer, screens, power, accessibility route, and technician. Learn whether the session is recorded and where the camera and captions appear. + +Test the actual media and equipment as early as the organizers allow. A successful test at home does not prove that venue audio, adapters, fonts, video, or network access will behave the same way. + +Join the event's official community channel if it is useful, but do not let a live social feed derail final preparation. Ask the session chair how you will be introduced, how time signals work, and how questions will be handled. + +## In the hours before speaking + +Develop a routine that steadies rather than exhausts you. Some speakers walk, stretch, talk with attendees, or listen to music; others need quiet. Eat and drink what works for you, use the restroom, and avoid changing caffeine or medication habits for the occasion. + +Arrive in the room before the previous session ends or at the time requested by the organizer. Check slides, demos, audio, clicker, microphone, and timer once more. Close unrelated applications and put devices into a focus mode. + +Your job is not to achieve perfection. It is to guide the audience through the useful idea you promised. Pause before beginning, speak more slowly than nerves suggest, and use the microphone because it may also feed recording, captioning, or assistive listening systems. + +If a demo fails, move to the backup. If you lose your place, pause and check your notes. During questions, repeat the question for the room and say when you do not know. Finish by restating the central lesson and giving the audience a practical next action. + +Afterward, save useful questions while they are fresh, share any materials you promised, thank the people who helped, and give yourself time to recover. + +## A simple first-speaker checklist + +- Choose one lesson grounded in your experience. +- Identify a specific audience and useful outcome. +- Find a conference whose topic, format, and terms fit. +- Write a clear title, abstract, outline, and biography. +- Ask for feedback and submit before the deadline. +- Treat the decision as program fit, not a verdict on your worth. +- If accepted, confirm the terms and prepare to the proposal's promise. +- Rehearse aloud, make the material accessible, and build backups. +- On the day, help the audience follow one idea at a time. +- Record what you learned and make the next version better. + +The path to the stage is not reserved for people who already look like conference speakers. It is open to practitioners willing to share a specific experience with care, clarity, and respect for the audience. + +--- + +[← Part 7: Prepare a Conference Presentation](/guides/speaking/prepare-a-conference-presentation/) · [Guide index](/guides/speaking-at-technology-conferences/) diff --git a/guides/speaking/understand-how-conferences-choose-talks.md b/guides/speaking/understand-how-conferences-choose-talks.md index ba74ba6d..3bcee11e 100644 --- a/guides/speaking/understand-how-conferences-choose-talks.md +++ b/guides/speaking/understand-how-conferences-choose-talks.md @@ -1,15 +1,23 @@ --- layout: page permalink: /guides/speaking/understand-how-conferences-choose-talks/ -title: "Part 5: Understand How Conferences Choose Talks" +title: "Part 3: Understand How Conferences Choose Talks" --- -[← Part 4: Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) +[← Part 2: Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) -*Part 5 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* +*Part 3 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* Selection is usually program design, not a ranking of speakers from best to worst. A strong proposal can be declined because it duplicates another session, misses the theme, targets the wrong level, or does not fit the available schedule. +This article expands on CFP Land's archived [“How Conferences Choose Their Speakers”](https://web.archive.org/web/20220701014121mp_/https://www.cfpland.com/guides/speaking/how-conferences-choose/). + +## How the CFP process works + +Most speakers enter through a public call for proposals rather than a personal invitation. Organizers publish the tracks, formats, deadlines, and submission form, often using a dedicated CFP platform. Invited speakers and keynotes may fill some places, but the open CFP supplies much of the program. + +Conferences commonly review proposals in one of three ways. **Rolling review** begins before the deadline and may reward an early submission. **Public voting** asks a community to express interest, usually with organizers retaining the final decision so popularity does not determine the whole program. **Post-deadline review** evaluates the complete pool together, making submission time irrelevant as long as the proposal is on time. Read the published process; if rolling review would change your timing and the page is unclear, ask the organizers. + ## Eligibility and initial review Organizers may first remove incomplete, late, commercial, off-topic, or code-of-conduct-incompatible submissions. Following the instructions is the easiest selection factor to control. @@ -22,6 +30,16 @@ The committee has to assemble a whole program. It may need a mix of beginner and Organizers may also consider speaker availability, travel budget, room capacity, previous program repetition, and whether a session depends on equipment they cannot support. +Reputation and qualifications can affect risk. An experienced speaker may have recordings that show reliable delivery, while a first-time speaker can establish credibility through practical experience, writing, teaching, open-source work, or a well-developed private outline. Some events deliberately reserve support or places for new voices. + +A thoughtful program also represents different identities, regions, company sizes, industries, educational paths, and career stages. Diversity is not a decorative final check: it changes which problems, assumptions, and solutions the audience encounters. + +Travel budgets may limit how many distant speakers an event can support. Sponsor sessions may be selected through a separate commercial process and should be labeled clearly rather than presented as ordinary peer-reviewed talks. + +## Notification and confirmation + +Selection can take weeks because organizers must contact accepted speakers, wait for confirmation, and use a waitlist when someone declines. A published lineup does not always mean every decision has been sent. Record the expected notification date and make a polite inquiry only after it passes. + ## What you can influence You cannot control the other submissions or the program's constraints. You can make the proposal easy to evaluate: @@ -41,5 +59,4 @@ If a community offers open proposal mentoring or volunteer reviewing, participat --- -[← Part 4: Write and Submit a Proposal](/guides/speaking/write-and-submit-a-proposal/) · [Part 6: Handle Acceptance, Waitlists, and Rejection →](/guides/speaking/handle-acceptance-waitlists-and-rejection/) - +[← Part 2: Decide Why You Want to Speak](/guides/speaking/decide-why-you-want-to-speak/) · [Part 4: Find Calls for Proposals →](/guides/speaking/find-calls-for-proposals/) diff --git a/guides/speaking/write-and-submit-a-proposal.md b/guides/speaking/write-and-submit-a-proposal.md index bda88707..0808e3de 100644 --- a/guides/speaking/write-and-submit-a-proposal.md +++ b/guides/speaking/write-and-submit-a-proposal.md @@ -1,15 +1,31 @@ --- layout: page permalink: /guides/speaking/write-and-submit-a-proposal/ -title: "Part 4: Write and Submit a Proposal" +title: "Part 5: Write and Submit a Proposal" --- -[← Part 3: Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) +[← Part 4: Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) -*Part 4 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* +*Part 5 of 8 in [A Guide to Speaking at Technology Conferences](/guides/speaking-at-technology-conferences/).* A proposal is not the talk itself. It is evidence that you understand the audience, have a focused idea, and can deliver the session described. +This article expands on CFP Land's archived [“Submitting Abstracts”](https://web.archive.org/web/20220701014119mp_/https://www.cfpland.com/guides/speaking/submitting/). + +## Choose a topic worth developing + +You do not need finished slides before submitting, but you do need a credible plan. Test the idea against seven questions: + +1. Does it fit the conference and one of its tracks? +2. Will you still care about it after months of preparation and questions? +3. Do you know it well enough, or have a realistic research plan? +4. Does your experience provide a distinct angle? +5. Will the lesson improve someone's work or wider community? +6. Is the story genuine, including its failures and limits? +7. Can attendees take a concrete action afterward? + +Introductory topics can be valuable when they serve the event's audience. Novelty does not require inventing a brand-new subject; it can come from a specific context, comparison, dataset, failure, or explanation. + ## Begin with the audience outcome Complete this sentence: “After this session, attendees will be able to…” Use a concrete verb. Compare approaches, diagnose a problem, design an experiment, or apply a technique is clearer than understand or learn about. @@ -28,6 +44,8 @@ The title should help reviewers and attendees predict the subject. Personality a Avoid claims the talk cannot support. Words such as always, never, perfect, and effortless invite skepticism and rarely reflect real engineering work. +Draft many titles, then return to the title after writing the abstract. Avoid clichés, unexplained acronyms, clickbait, and jokes that obscure the subject. Include the terms an attendee would use when searching the schedule. + ## Build the abstract Unless the CFP requests a different structure, a strong public abstract answers four questions: @@ -39,6 +57,10 @@ Unless the CFP requests a different structure, a strong public abstract answers Write for a person scanning many submissions. Open with the substance, use plain language, and remove background that does not help someone choose the session. +A dependable structure is: state the problem, preview the approach, and explain what the session will enable the audience to do. Two or three compact paragraphs are often easier to evaluate than one dense block. End with a specific outcome rather than a generic invitation to attend. + +Customize the framing for each conference, obey its word limits, and state the intended experience level. Use inclusive language and remove metaphors that depend on disability, violence, or stereotypes when plain language works better. + ## Give reviewers the detail they need Many systems include private notes, an outline, or a field for the program committee. Use it. Describe the session's progression, examples, evidence, demonstrations, exercises, and timing. Explain what is original about your perspective and disclose vendor relationships. @@ -61,7 +83,14 @@ Ask at least one person in the intended audience and one person unfamiliar with Read the abstract aloud, check every required field, preserve a copy, and submit before the last hour. Confirm that the system shows the proposal as received. ---- +## Choose the right submission strategy + +If the CFP permits multiple proposals, submit more than one only when each is genuinely developed and appropriate. This gives organizers options but does not make unfinished ideas stronger. -[← Part 3: Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) · [Part 5: Understand How Conferences Choose Talks →](/guides/speaking/understand-how-conferences-choose-talks/) +Consider a workshop only when the material benefits from practice and you can design exercises, pacing, support, and contingency plans. A workshop is not a talk made longer. + +Save every public and private field exactly as submitted. Note the promised format, length, and outcomes so an acceptance months later does not surprise you. Rejection is normal; improve the proposal and keep submitting to suitable events rather than measuring success by one decision. + +--- +[← Part 4: Find Calls for Proposals](/guides/speaking/find-calls-for-proposals/) · [Part 6: Handle Acceptance, Waitlists, and Rejection →](/guides/speaking/handle-acceptance-waitlists-and-rejection/)