Learn
Goals and Concepts
Start with the capability target and concept set for this module.
Lesson Flow
Practice
Studio Activity
Apply the ideas in a guided activity tied to realistic outputs.
Check
Assessment Rubric
Use the rubric to verify competency and identify improvement targets.
Teach
Slides and Worksheets
Open the teaching deck, worksheet, and editable slide source.
Interactive Lab
Practice in short loops: checkpoint quiz, microtask decision, and competency progress tracking.
Checkpoint Quiz
Microtask Decision
Choose the action that best improves scientific reliability.
Progress Tracker
State is saved locally in your browser for this module.
0% complete
Annotation Challenge
Click the hotspot with the strongest evidence for the requested feature.
Selected hotspot: none
Capability target
Submit a conference-ready abstract, produce a coherent poster draft, and deliver a defensible 90-second pitch with clear claim boundaries.
Why this module matters
Conference communication is often the first high-stakes visibility point for trainees. Without explicit scaffolding, learners miss unwritten norms about clarity, scope, and professional interaction.
Concept set
1) Abstracts are claim filters
- Technical: every sentence should move from question to method to result to implication, with one explicit limitation.
- Plain language: include only what helps reviewers evaluate credibility and significance.
- Misconception guardrail: broad motivation cannot substitute for concrete results.
2) Posters are spatial arguments
- Technical: layout should mirror inferential flow (question -> method -> evidence -> limits).
- Plain language: if viewers cannot find your core result in 10 seconds, redesign.
- Misconception guardrail: visual density is not rigor.
3) Conference performance includes social protocol
- Technical: introductions, question handling, and follow-up contact are part of dissemination competency.
- Plain language: what you say and how you engage both matter.
- Misconception guardrail: “good science speaks for itself” without communication strategy.
Hidden curriculum scaffold
- Unspoken conference rules trainees often miss:
- Start conversations with one-line project framing, not full backstory.
- Answer questions to the level asked; escalate depth only if invited.
- End interactions with a concrete follow-up option.
- Inclusive support practices:
- Provide sample scripts for first-time networking.
- Normalize “I need to check that detail” responses.
- Debrief difficult interactions explicitly after sessions.
Core workflow: abstract-to-poster pipeline
- Distill project into one claim hierarchy.
- Draft 250-word abstract and remove unsupported claims.
- Build poster wireframe around three key evidence panels.
- Rehearse 90-second and 3-minute versions.
- Run critique for clarity, limitations, and professional interaction plan.
60-minute tutorial run-of-show
-
**00:00-08:00 Framing + exemplar abstract** -
**08:00-20:00 Abstract sprint (individual)** -
**20:00-32:00 Poster wireframe build (pairs)** -
**32:00-44:00 90-second pitch practice** -
**44:00-54:00 Q&A and networking simulation** -
**54:00-60:00 Revision checklist + submission plan**
Studio activity: conference simulation lab
Scenario: You have one accepted poster slot and must communicate your connectomics result to mixed audience members.
Tasks
- Produce one abstract and one poster wireframe.
- Deliver a 90-second pitch.
- Respond to two audience questions.
- Draft one follow-up outreach message.
Expected outputs
- Abstract draft.
- Poster wireframe.
- Pitch script.
- Follow-up message template.
Assessment rubric
- Minimum pass
- Abstract claims are evidence-grounded.
- Poster layout clearly surfaces core result and limitation.
- Pitch communicates method/result/limit within time.
- Strong performance
- Handles Q&A with precise uncertainty language.
- Demonstrates audience-adaptive communication.
- Uses networking follow-up strategically and professionally.
- Common failure modes
- Overstuffed abstracts with missing quantitative anchors.
- Posters organized by chronology instead of argument.
- Overconfident responses to unresolved technical questions.
Teaching resources
- Writing context: Module 17
- Presentation context: Module 22
- Evidence set: Technical Track Journal Club
- Mentorship support: Ask-an-Expert
Quick practice prompt
Write a 5-sentence mini-abstract including:
- question,
- method,
- result,
- limitation,
- implication.
Teaching Materials
Slide Deck
Classroom-ready deck links for teaching and delivery.
Activity Worksheet
Learner worksheet aligned to the studio activity and rubric.
Slide Source
Marp source file for editing and rendering.
course/decks/marp/modules/module23.marp.md