Why Every Tech Event Needs Pre-Conference Feedback Sessions
🔗 **Source:** [Why Every Tech Event Needs Pre-Conference Feedback Sessions](https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/)
> [!note]+ Document Notes
> tags: [event-organizing, public-speaking, feedback]
> author: Maciek Palmowski
> source: maciekpalmowski.dev
> reference: [https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/]
> date created: 2025-11-08 00:00
>
> # 🏷️ Title: Why Every Tech Event Needs Pre-Conference Feedback Sessions
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author adopted pre-conference feedback sessions (small-group dry runs) after seeing them at WebExpo and implemented them at WordCamp Gdynia.
- Why it matters: Reduces speaker stress, improves slide quality and timing, raises attendee satisfaction.
- Key stakeholders: Speakers, organizers, attendees, emcees/track hosts.
- Risks and tradeoffs: Time-intensive for facilitators; requires careful, empathic critique.
- Bottom line: Early, structured practice with peer feedback measurably improves talk quality and confidence.
## 📖 Main Content
- Core argument: Speakers often first “test” talks on stage; feedback sessions fix this by creating an early deadline and safe practice environment a week+ before the event.
- How it works: Groups of 3–5, each presents, then lists what worked and what to improve; prioritize concise slides, remove fluff, keep to time.
- Organizer notes: Sessions took ~40–45 min per speaker; scale by recruiting more facilitators; simple tooling (sheet + calendar + video call + recording) is sufficient.
- Uncertainties: Optimal group size/cadence and best facilitation format may vary by event scale.
### 🗒️ Notes
- “Speakers testing their presentations on stage for the first time” leads to “stressed speakers and disappointed attendees.”
- Format: 3–5 people, each presents; everyone (including speaker) lists likes and improvements; run at least a week before.
- Common fixes:
- Slide layout: remove most text; slides = roadmap, not script. “People are coming to your talk to listen to you, not to read slides.”
- Remove non-essentials for 20-min slots: no self-intro if host introduces; avoid deep dives, long videos.
- Ops tips: Public signup sheet → group, calendar invites, Meet/Zoom, record and share.
- Facilitation: Be empathic but honest; start with positives; still say what can be improved.
- Cost: ~40–45 min per speaker; tiring—spread load among more facilitators next time.
- Outcomes: Post-session survey showed 100% found sessions useful; speakers and attendees happy.
- Diffusion: Practice adopted at WordCamp Wrocław after success in Gdynia.
## 📚 References
- WebExpo Prague (speaker prep practice referenced): https://www.webexpo.net
- WordCamp Gdynia (context): https://central.wordcamp.org/
- WordCamp Wrocław (adoption): https://central.wordcamp.org/
- Google Calendar (scheduling): https://calendar.google.com
- Google Meet (remote sessions): https://meet.google.com
## 🗣️ Paraphrase
- A: Many speakers debut untested talks on stage, causing stress and weak sessions. Small-group feedback runs a week early create an enforced deadline and safe space to refine.
- B: Keep slides sparse, cut intros and long examples, and be candid yet kind. It takes time, so distribute facilitation. Surveys show universal usefulness and attendee uplift.
## 📰 Newsletter
- Want better WordCamp and tech-conf talks? Pre-event feedback sessions work. Small groups, early deadlines, and kind candor trim slide bloat, fix timing, and boost speaker confidence. Try a simple flow: signup sheet → group → calendar → Meet → record. After Gdynia’s success, Wrocław is adopting them too. Resources: WebExpo’s approach, Google Calendar/Meet, and community playbooks.
## ✅ Action Items
#### DevRel
- Stand up monthly feedback circles; set KPIs: NPS uplift, talk timing accuracy, slide-text density reduction.
- Offer office hours and dry-run clinics; publish quickstart slide templates.
- Build a sample repo of talk outlines and demo scripts.
#### OSPO
- Policy: encourage pre-conference reviews for sponsored speakers.
- Compliance/Security: add review checklists for demos (licenses, secrets).
- Inventory: maintain SBOMs for demo code; freshness SLOs.
#### Community
- Maintainers: “roadmap clinic” talks with timed rehearsals.
- Contributors: first-time speaker buddies; pairing rotations.
- Sponsors: sponsor session facilitation; publish impact reports.
#### WordPress
- Community: add feedback-session kit to WordCamp playbooks.
- Training: build a 60–90 min speaker rehearsal curriculum.
- Marketing: promote “Rehearsed Talks” badge; share before/after clips.
- Accessibility: add slide text-density and captioning checks.
- Documentation: one-pager on running sessions; templates and checklists.
#### The WPOCC
- Programs: microgrants for session facilitators.
- Projects: quarterly rehearsal sprints pre-major events.
- Funding experiments: milestone payouts tied to attendee NPS.
### FAIR
- Independence: store recordings with provenance metadata.
- Covenants: transparent facilitation; sunset/rotation for leads.
- Governance artifacts: facilitator charters and scorecards.
## 🧪 Hypotheses
- H1: Feedback sessions reduce average talk overrun by ≥30%.
- H2: Attendee session ratings increase by ≥0.3/5 after implementation.
- H3: Slide word count per slide decreases by ≥40% post-session.
- H4: First-time speaker reported stress decreases by ≥25%.
- H5: Adoption spreads to peer events within 1 cycle via organizer testimony.
### 📊 Methodology
- Pre/post metrics: timing accuracy, slide-text density, NPS, stress self-reports (Likert).
- Controls: similar tracks without sessions.
- Analysis: difference-in-differences; Mann–Whitney for non-normal data.
- Qual: coded feedback themes; facilitator workload logs.
### ❓ Questions
- Optimal group size and number of iterations?
- Does recording access improve revisions?
- What’s the minimal viable facilitator training?
### 🔮 Future Research
- Compare in-person vs remote sessions.
- Impact on underrepresented speakers’ retention.
- Long-term effect on CFP quality.
### 💡 Implications
- Practice: standardize rehearsal as a required step.
- Policy: add to event checklists; allocate budget/time.
- Education: integrate into speaker training tracks.
### 🧠 Learning Styles Assessment
- Reading level: ~8–9th grade (Flesch-Kincaid est.).
#### 👀 Visual learners
- Present: slide examples guidance.
- Improve: before/after slide visuals.
#### 🔊 Aural learners
- Improve: 3–5 min audio summary template.
#### 🗣️ Verbal learners
- Present: clear definitions and tips.
- Improve: analogy-driven examples.
#### 🧩 Kinesthetic learners
- Present: live dry runs.
- Improve: step-by-step rehearsal checklists.
#### 🧠 Logical learners
- Present: structured flow.
- Improve: decision trees for cut/keep.
#### 🧑🤝🧑 Social learners
- Present: group feedback.
- Improve: peer rubric.
#### 🧘♀️ Solitary learners
- Improve: self-review worksheet.
#### 🌿 Naturalistic learners
- Improve: lifecycle framing of talk prep.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Improve: ensure headings/landmarks in speaker guides.
#### Keyboard navigation
- Improve: template checklists with focus order guidance.
#### Contrast and readability
- Present: advice to reduce text; Improve: contrast checklist.
#### Text resizing and reflow
- Improve: slide templates tested at 200% zoom.
#### Media and captions
- Improve: require captions for embedded videos.
#### Forms and interactions
- Present: signup sheet; Improve: accessible labels and error states.
#### Standards reference
- Map to WCAG 2.2 AA: 1.4.3, 1.2.x, 2.4.x, 3.3.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Improve: multilingual options for rehearsals.
#### Inclusive language
- Present: gentle tone; Improve: jargon glossary.
#### Neurodiversity support
- Present: consistent structure; Improve: predictability and quiet channels.
#### Representation
- Improve: facilitator diversity targets.
#### Psychological safety
- Present: “start with positives”; Improve: explicit code of conduct for feedback.
### ✅ Logical Validity
#### Strong reasoning
- Inductive: observed success at WebExpo → applied at Gdynia with positive survey; plausible causal link via practice effect.
#### Fallacies
- Potential survivorship bias; fix with controlled comparisons and broader samples.
#### Tone of voice
- Supportive, practical, candid.
### 🛡️ DARVO Analysis
- No denial/attack/reversal patterns; constructive framing.
## 🎯 Conclusion
- Bottom line: Pre-event feedback sessions reliably improve talk quality and confidence with modest operational overhead.
- Next steps: Pilot with one track, recruit multiple facilitators, use a simple signup-to-recording workflow, and measure timing, slide density, stress, and NPS.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
<!--
Goal: Use Note Refactor’s built-ins to spawn Fleeting, Literature, and Atomic notes.
-->
```text
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] 5–10-word present-tense claim
> [!quote] [Why Every Tech Event Needs Pre-Conference Feedback Sessions](https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/) by [[Maciek Palmowski]] via [[maciekpalmowski.dev]]. Published 2025-11-06. Accessed 2025-11-08.
> “Feedback sessions give you an early deadline.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [Why Every Tech Event Needs Pre-Conference Feedback Sessions](https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/)
> “Slides should only be a roadmap of your talk.”
Two lines: context and use.
[view highlight](https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Early deadlines improve talk quality
- From pre-conference sessions; timing adherence improves post-rehearsal.
- Links: [[Talk-Preparation]] [[Speaker-Coaching]]
#### [Z2] Minimal slide text increases engagement
- Guidance from article; attendee satisfaction rises.
- Links: [[Slide-Design]] [[Audience-Engagement]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- [F1] Draft a facilitator script with “positives-first” prompts — context/https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/ #fleeting #inbox
- [F2] Build a 20-min talk trimming checklist — context/https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/ #fleeting #inbox
- [F3] Create a signup → calendar → Meet automation — context/https://maciekpalmowski.dev/blog/why-every-tech-event-needs-pre-conference-feedback-sessions/ #fleeting #inbox
---
<!-- deep-read:sections end -->