Event owner lens
Use this record to benchmark whether a comparable event makes the work after the room visible. The score is 30/100, so the next move is to benchmark the weakest pillars before repeating the format.
lead or directory source agenda analysis
PyCon US - Posters (Sunday)
This lead or directory source in Technology / AI / Startup shows 18 visible agenda rows from pycon-archive.python.org and scores 30/100: a thin but inspectable design signal. The clearest public signals sit in Participation Architecture and Problem Specificity; the main limits are Follow Through and Evidence Maturity. Visible mechanisms include Participant work, Feedback, Network design, and Learning transfer. The public record does not show follow-up or tracking, so the score should be read as design intent... A practical reading: For a reader, this is mainly a warning or source-evidence record: it reads as a lead or directory source, with the strongest visible signal in participation architecture and problem specificity and the biggest open question around follow through and evidence maturity. The practical test is whether the published agenda connects the room to post-event continuation and evidence. This page is an original public-evidence analysis, not a copy of the source agenda or an endorsement of the event. The score places the visible agenda in the thin outcome architecture band. The strongest visible pillars are Participation Architecture, Problem Specificity, and Personalization; the thinnest visible pillars are Follow Through, Evidence Maturity, and Learning Transfer. Visible mechanisms include Participant work, Feedback, Network design, Learning transfer, and Personalization. The extracted agenda preview includes 30 visible rows. The most common formats are Poster Session, Presentation, and Training; the most common inferred purposes are Showcase, Knowledge Transfer, and Skill Building.
Eight-pillar fingerprint
Hover any pillar to see what it measures and, where it scored low, what the agenda is missing.
Participation Architecture?43
Participation Architecture - 43/100. Participant work, contribution, interaction, and alternatives to passive broadcast.
Follow Through?5
Follow Through - 5/100. Owners, dates, commitments, progress checks, and accountability after the room.Missing: Add named owners, dates, implementation checkpoints, and a visible post-event continuation path.
Problem Specificity?41
Problem Specificity - 41/100. A clear costly problem, objective, decision, or performance target.
Personalization?40
Personalization - 40/100. Role, path, goal, preparation, or connection tailoring for participants.
Network Design?40
Network Design - 40/100. Structured weak ties, bridge-building, mixers, and relationship persistence.
Learning Transfer?35
Learning Transfer - 35/100. Applied practice, feedback, workplace use, refreshers, and 30-90 day transfer.Missing: Build transfer into the agenda through practice, feedback, job aids, reflection, and 30-90 day use cases.
Evidence Maturity?31
Evidence Maturity - 31/100. Baseline, comparison, follow-up, isolation, and attribution confidence.Missing: Add baseline measurement, comparison logic, tracking, or post-event impact reporting so effectiveness is not inferred only from format.
Future-of-Work Fit?38
Future-of-Work Fit - 38/100. Value against time, hybrid reality, accessibility, AI, and meeting load.
Fix the gaps
Field-tested exercises matched to this agenda's weakest pillars, from the exercise library.
Follow Through (5/100)
Exercises that strengthen it: Mental Toughness Workshop • WorkshopBank · 15% Solutions • WorkshopBank · Network Patches
Learning Transfer (35/100)
Exercises that strengthen it: Team Challenge Activity for Group Problem-Solving: Don't... · Thrilling, Quick Elimination Game to Boost Energy - Match... · Creative Brain Teaser & Fun Geometric Team Puzzle - T-Puzzle
Personalization (40/100)
Exercises that strengthen it: Journey Mapping • WorkshopBank · Group Energiser & Perspective-Changing Exercise - Paradigm... · Photo Storytelling
Agenda Preview
The actual agenda we captured. Every block is classified by format and purpose. Open any block to see how we read it; the colored edge shows whether it is participant work, broadcast, logistics, or a showcase.
Room vs wrapper
10 percent of the 30 classified blocks put participants to work; the rest broadcast, show, or handle logistics. That mix is what drives the participation score.
Participant workBroadcastShowcaseLogistics
all eventTutorials (Wed. and Thurs.)TrainingSkill building+
Format · Participant workTrainingGuided skill building where participants practice. Counts as participant work and learning transfer.
Evidence basisParticipant work is implied by the formatInferred from format
all eventTalks (Friday - Sunday)PresentationKnowledge transfer+
Format · BroadcastPresentationSpeakers present, the audience receives. Awareness only unless paired with practice or follow-up.
Evidence basisNo participant output visible from this rowRead from source, no work signal
all eventPosters (Sunday)Poster sessionShowcase+
Format · ShowcasePoster sessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisOutcome inferred from formatInferred from format
all eventKeynote SpeakersKeynoteExpert framing+
Format · BroadcastKeynoteA featured talk from the stage. Builds awareness and energy, produces no participant output on its own.
Evidence basisNo participant output visible from this rowRead from source, no work signal
all eventOpening ReceptionReceptionRelationship building+
Format · LogisticsReceptionA social or hospitality block. Pacing and informal connection, not participant work.
Evidence basisOutcome inferred from formatInferred from format
all eventPyLadies LuncheonMealPacing+
Format · LogisticsMealA pacing block. Can carry unstructured networking, not scored as participant work.
Evidence basisOutcome inferred from formatInferred from format
all eventPostersPoster sessionShowcase+
Format · ShowcasePoster sessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisOutcome inferred from formatInferred from format
10 a.m. - 1 p.mSunday . in Hall APresentationKnowledge transfer+
Format · BroadcastPresentationSpeakers present, the audience receives. Awareness only unless paired with practice or follow-up.
Evidence basisNo participant output visible from this rowRead from source, no work signal
all eventThis poster intends to highlight ongoing experiments, existing challenges, and the packages used.Poster sessionShowcase+
Format · ShowcasePoster sessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisOutcome inferred from formatInferred from format
all eventThe poster will introduce Flet framework to the visitors.Poster sessionShowcase+
Format · ShowcasePoster sessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisOutcome inferred from formatInferred from format
all eventPainting with Python (poster)Poster sessionShowcase+
Format · ShowcasePoster sessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisOutcome inferred from formatInferred from format
all eventThis poster will explore how to use Python to: - Parse chess games using the python-chess library.Poster sessionShowcase+
Format · ShowcasePoster sessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisOutcome inferred from formatInferred from format
all eventTutorials (Wed. and Thurs.)TrainingSkill Building+
Format · Participant workTrainingGuided skill building where participants practice. Counts as participant work and learning transfer.
Evidence basisMediumRead from source
all eventTalks (Friday - Sunday)PresentationKnowledge Transfer+
Format · BroadcastPresentationSpeakers present, the audience receives. Awareness only unless paired with practice or follow-up.
Evidence basisMediumRead from source
all eventOpen Spaces (Friday-Sunday)UnknownUnknown+
Format · BroadcastUnknownFormat not classified from the source; treated as a broadcast block by default.
Evidence basisLowRead from source
all eventPosters (Sunday)Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventKeynote SpeakersKeynoteThought Leadership+
Format · BroadcastKeynoteA featured talk from the stage. Builds awareness and energy, produces no participant output on its own.
Evidence basisMediumRead from source
all eventOpening ReceptionReceptionRelationship Building+
Format · LogisticsReceptionA social or hospitality block. Pacing and informal connection, not participant work.
Evidence basisMediumRead from source
all eventPyLadies LuncheonMealWellbeing+
Format · LogisticsMealA pacing block. Can carry unstructured networking, not scored as participant work.
Evidence basisMediumRead from source
all eventPostersPoster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
10 a.m. - 1 p.mSunday . in Hall AUnknownUnknown+
Format · BroadcastUnknownFormat not classified from the source; treated as a broadcast block by default.
Evidence basisMediumRead from source
all eventThis poster intends to highlight ongoing experiments, existing challenges, and the packages used.Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventThis poster will show you how to use CrossHair's diffbehavior command, your secret weapon for confident refactoring. CrossHair uses a constraint solver to efficiently find inputs that reveal discrepancies between your original code and the refactored version.Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventLarge Language Models (LLMs) excel at tasks like filtering, summarization, and code generation, but their high computational requirements lead to steep costs and limited scalability. This poster proposes a novel approach that breaks from the constraints of monolithic LLMs, moving toward a lightweight ecosystem of open-source Small Language Models (SLMs) coordinated by a central Master Agent.Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventOur implementation, primarily in Python and supported by open-source frameworks like Langchain, Hugging Face LLMs, etc. to foster community-driven enhancements. The poster will showcase how this multi-agent framework optimizes resource utilization, simplifies maintenance through modular specialization, and ensures robust failover for uninterrupted performance. Attendees will learn how to integrate these components into their own projects, benefiting from a flexible, future-proof platform that’s both affordable and adaptable.Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventThe poster will introduce Flet framework to the visitors.Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventThe poster will include: - A visualization of how the same Python program can be packaged and deployed to iOS, Android, macOS, Windows, Linux and web. - Project statistics such as GitHub stars, Discord users, # of contributors, # of PyPI downloads. - Visualization of extensibility model and connection to Flutter/Dart ecosystem. - The cloud of available binary packages (wheels) for iOS and Android (NumPy, Pydantic, Pandas and others).Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventPainting with Python (poster)Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
all eventChess, one of the most iconic board games in history, has a global community nearing a billion players. With the help of powerful chess engines, computers have democratized access to advanced chess analysis tools - tools that even top grandmasters use to analyze and improve their games.DemoShowcase+
Format · Participant workDemoA hands-on or applied walkthrough that invites attendee questions and direct engagement.
Evidence basisMediumRead from source
all eventThis poster will explore how to use Python to: - Parse chess games using the python-chess library.Poster SessionShowcase+
Format · ShowcasePoster SessionPresenters display work; attendees browse and ask questions. Some interaction, not structured work.
Evidence basisMediumRead from source
The Full Reading
Why It Ranks This Way +
Calibrated from GES design 34/100 and verified 34/100, then capped for source appears to be a guide, directory, calendar, or ancillary page rather than a source agenda.
Reader Takeaway. For a reader, this is mainly a warning or source-evidence record: it reads as a lead or directory source, with the strongest visible signal in participation architecture and problem specificity and the biggest open question around follow through and evidence maturity. The practical test is whether the published agenda connects the room to post-event continuation and evidence.
Strongest signals: Participation Architecture, Problem Specificity, and Personalization. Weakest signals: Follow Through, Evidence Maturity, and Learning Transfer.
How This Agenda Could Improve +
- Add named owners, dates, implementation checkpoints, and a visible post-event continuation path.
- Add baseline measurement, comparison logic, tracking, or post-event impact reporting so effectiveness is not inferred only from format.
- Build transfer into the agenda through practice, feedback, job aids, reflection, and 30-90 day use cases.
Fastest next move: Add named owners, dated next steps, and a visible continuation path before treating the event as outcome-ready.
Role-Specific Reading +
Sponsor lens
Look beyond exposure. Strong sponsor value would show qualified interaction, problem work, buyer learning, customer evidence, or follow-up. The practical sponsor move is to look for structured introductions, buyer-seller fit, and relationship persistence.
Designer lens
The agenda is useful as a pattern sample from pycon-archive.python.org. Redesign attention should go first to the lowest-scoring pillars; in practice, turn the thinnest agenda blocks into participant work.
Executive lens
Treat the visible agenda as an operating plan. The executive move is to require owners, dates, and evidence before treating the event as strategic. If owners, proof, and follow-through are not visible, the public record does not yet prove strategic movement.
Aggregator lens
Treat the source URL as evidence, not decoration. The data-product move is to keep it as lead evidence unless a direct agenda source is also available before ranking or syndicating the record.
What GES Means Here +
The Gathering Effectiveness Score is a strict 0-100 public-evidence reading of the agenda across eight pillars. It rewards visible participant work, follow-through, transfer, network design, and proof mechanisms more than polish, speaker fame, attendance, or satisfaction.
Visible mechanisms: Participant work, Feedback, Network design, Learning transfer, Personalization.
Evidence boundary: Scores reflect visible agenda/source evidence and should not be read as proof of causal event impact.
Limitations, Score Caps, and Review Flags +
Limitations
- No visible follow-up, progress monitoring, or longitudinal tracking.
- Source shape weakens confidence in the agenda record.
- No baseline measurement is visible.
Score caps
- 28: Source appears to be a guide, directory, calendar, or ancillary page rather than a source agenda.
Review flags
- Fourth-loop score cap: Source appears to be a guide, directory, calendar, or ancillary page rather than a source agenda.
- URL path looks like an event calendar, directory, or list.
- Agenda is useful as a source record but weak as evidence of gathering effectiveness.
- No source-backed follow-up, validation, baseline, tracking, or impact evidence.
- Source URL looks like a single session/event detail page; many extracted items may be navigation or parent-schedule bleed-through.
- No tracking, validation, feedback, or impact measurement found in the visible source text.
- Original category was unknown; publication category is inferred.
Is this proof the event worked? +
No. This is a strict public-evidence reading of the agenda. Proof would require baseline, comparison, follow-up, attribution, and impact evidence beyond the listing.
What should a reader inspect first? +
Start with the source URL, then compare the eight pillar scores against the agenda rows. The biggest opportunities usually sit in follow-through, evidence maturity, and participant work.
Why publish weak records? +
Weak records are part of the map. They show where public agendas still describe sessions and speakers more often than outcomes, commitments, transfer, or proof.
How should I use the rows? +
Read the agenda rows as the visible design trace: formats, purposes, and evidence labels show what the public source made inspectable, not everything that happened in the room. This is a source-grounded interpretation of the public agenda record, not a copy of the source, and not an endorsement of the event.
Where To Go Next
Compare this agenda against other Technology / AI / Startup events scored on the same eight pillars.