Session Kit: Module 23: Posters, Abstracts, and Conferences
Everything needed to run Module 23 as a taught session: prep, timing, materials, misconceptions, rubric.
Generated from modules/module23.md. Edit the module page, not this file.
At a glance
| Duration | 4 hours |
| Capability target | Submit a conference-ready abstract, produce a coherent poster draft, and deliver a defensible 90-second pitch with clear claim boundaries. Operationally: your abstract spends its word budget on evidence rather than motivation, a stranger can find your core result on the poster within ten seconds from two meters away, and you leave the session with at least two named follow-ups you initiated yourself. |
| Learners leave with | Abstract draft |
Before you walk in
- You can state the capability target in one sentence without reading it.
- You have one worked example you will narrate, including where you are unsure.
- Data access works — accounts, viewer, notebook — verified today, not last week.
- The rubric is visible to learners before they start, not after.
- You have decided what “uncertain” earns, and you will say so out loud.
Learners should arrive having covered:
- At least one completed analysis or mini-project
- Basic scientific writing experience
Materials
Run of show
| Time | Segment | Your note |
|---|---|---|
| 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 |
The activity
Scenario: You have one accepted poster slot and must communicate your connectomics result to mixed audience members. Two of the people who stop are specialists who will ask about segmentation quality; one is a program director who will ask what it means; one is a peer at your own stage who wants your code.
- Produce one abstract against the sentence budget and one poster wireframe tested at two meters.
- Deliver a 90-second pitch to a timer, twice, cutting on the second pass.
- Respond to two audience questions, including one about reconstruction quality.
- Draft one follow-up outreach message that sends something rather than asking for something.
What learners hand in
- Abstract draft
- Poster wireframe
- Pitch script
- Follow-up message template
- A named target list of five people and one question for each
Misconceptions to target
These are the errors this session exists to prevent. Surface them in the debrief rather than pre-empting them in the lecture — a misconception a learner has voiced is far easier to correct than one they are holding silently.
- They may believe: A strong motivating paragraph can compensate for thin results.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: Dense text signals that the work is thorough.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: Good science speaks for itself and networking is optional decoration.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: If the conversation went well, the other person will follow up.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
Naming the norm
Every session is a chance to make one piece of the hidden curriculum explicit. Pick a moment where you would normally just do the professional thing, and say out loud why you are doing it — then ask whether anyone was taught that.
For this session, the candidate is whichever norm the activity most depends on: stating an assumption in the same sentence as the claim, recording the version a number came from, or saying “uncertain” and having it count as a real answer. See the hidden curriculum for the collected set and why naming them is a fairness intervention rather than etiquette.
Assessment
- Minimum pass: abstract claims are evidence-grounded and name dataset, version, and n; poster layout surfaces core result and limitation; the pitch communicates method, result, and limit within time.
- Strong performance: handles Q&A with precise uncertainty language, adapts to the audience in front of them without changing the evidentiary standard, and produces follow-ups that are specific, sent within days, and initiated rather than inherited from a supervisor.
- Common failure to flag: overstuffed abstracts with missing quantitative anchors, posters organized by chronology instead of argument, and overconfident responses to unresolved technical questions. Also flag a learner whose entire target list consists of people their supervisor already knows.
Grade the reasoning, not the answer. A correct call with no evidence chain should not outscore a well-reasoned incorrect one — and saying so publicly changes behaviour within one session.
Exit prompt
Write a 5-sentence mini-abstract including question, method with dataset version, result with one number, limitation, and implication. Then count how many words went to the field and how many to your result; if the first number is larger, rewrite the opening sentence.
If this session goes wrong
- Nobody talks in the debrief. You asked “any questions?” Ask instead: “Which cue would you drop first if the data got worse?”
- Everyone finishes early. They are pattern-matching, not judging. Give an ambiguous case where the answer is “uncertain” and see what happens.
- Nobody finishes. The scaffolding came off too fast. Work the next case together rather than pressing on.
- A learner is silently lost. The most likely cause is unstated vocabulary. Point them at the dictionary and check back.