DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Conference Insights Engine

Signal Systems: connect event participation to useful follow-up

Design Slate events and portals around useful evidence, clear staff responses and maintainable follow-up, using the Event Signal Loop for one event.

Conference notes organized through brass dividers into a field guide.
Choose the signal. Plan the response. Review the loop.

THE IDEA, IN A MINUTE

Give each useful event signal an owner and a next step.

The fifth Conference Insights Engine episode connects event foundations, live attendance, personalized schedules, complexity and portals. Use its Event Signal Loop to decide what to capture, who acts and what to review afterward.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Plan the action before building the event

A full room tells an events team that people arrived. It leaves another useful question open: what should staff do next? Signal Systems follows the experience from registration through participation to the next appropriate action. Attendance is one part of that longer story.

David brings five conference sessions together around event foundations, live attendance, personalized schedules, operational simplicity and portal design. His Event Signal Loop gives those strands a shared planning question: what should the team learn before, during and after this event, and how will that learning change its work?

In the recording · 04:21 ↗

Capture evidence the team can actually use

Start with one event and a short list of useful observations. Registration choice, reliable attendance and a relevant next step may be enough. Define each before the build so the team knows what will be recorded and what the record means.

Keep registration, participation and inferred interest separate. Choosing a breakout does not establish that someone attended it, and a missing check-in can reflect incomplete recording. Clean guest handling matters too: a supporter's activity should remain distinguishable from the student's. Better structure makes later interpretation possible; it does not remove uncertainty.

In the recording · 06:31 ↗

Give live attendance a response plan

Live attendance earns its operational cost when staff can respond while help is still useful. Decide who watches the information, who follows up, who corrects the record and who handles exceptions. A dashboard without those responsibilities can leave the same problem unresolved, only more visible.

Walk through a missed check-in before event day. Ask how staff would verify what happened and when they would escalate it. Set expectations appropriate to the event. A small information session and a structured group program do not need identical tracking or response arrangements.

In the recording · 08:46 ↗

Personalize the schedule where choices matter

Schedule personalization is useful when the day contains meaningful differences: academic tracks, competing sessions, family options or required activities. Give students a clear route through those choices, then retain enough context to continue the conversation afterward.

Maintainability belongs in the design. The episode draws attention to a conference session on schedules without custom SQL, but it does not supply a universal implementation recipe. Review the local configuration and who can maintain it. When everyone follows the same agenda, a clear shared schedule may do the job with less work.

In the recording · 10:25 ↗

Make each additional feature justify its upkeep

A new branch brings testing, copy, training or data definitions with it. Before adding one, name its contribution: a clearer student experience, less staff effort, a usable signal or a better decision. Then name the person who will keep it working.

Apply that test to the whole event, including the busiest minutes of delivery. If capturing a detail makes check-in harder and changes no later action, remove it from the plan. Save staff attention for the observations and service problems that matter.

In the recording · 12:35 ↗

Keep the portal useful after the visit

An event portal can gather schedules, resources and next steps in one place. Its purpose should be specific enough to test. Can a registrant find the day's plan? Can an attendee find the promised resource after going home? Who updates that view when the event ends?

Portal activity can help the team notice questions or friction. Repeated visits do not explain themselves, though. Someone may be interested, confused or trying to recover a link. Review the surrounding experience before turning activity into a confident claim about readiness or preference.

In the recording · 14:47 ↗

Give different participation states different paths

The episode proposes attendees, no-shows and participants whose behavior warrants closer review as a useful starting point. An attendee needs an appropriate continuation. A no-show needs a respectful alternative, without a message falsely thanking them for attending. More specific outreach needs enough context to justify it.

Use the One Event Signal Worksheet to connect each path to an action, owner, timing and measure. Record signals that will remain unused because they lack an action plan or need more testing. That decision is part of responsible design, rather than unfinished automation.

In the recording · 18:19 ↗

Review the loop after follow-up happens

Choose three or four signals for the first trial. Agree on the next step each can support, assign the work and set a review date. The review should happen after follow-up has had time to produce something observable, rather than ending with the event's attendance report.

Check whether the planned actions happened, whether staff understood their roles and whether students could use the portal. Examine subsequent steps without assuming the event caused them. Finish by removing, combining or clarifying something before the next run. A smaller system that the team can explain and maintain is a practical starting point.

In the recording · 23:28 ↗

03 / A SMALL EXPERIMENT

Test three event handoffs

Use these fictional cases to test one event plan. For each, record the evidence, its limits, the next action, its owner and what would make you revise the decision.

The attendee with no check-in

A fictional registrant appears on a no-show list, but a staff member remembers helping them at the event. The recovery message is scheduled for tomorrow. What needs to happen first?

Compare your reasoning

Verify attendance and correct or flag the record before selecting follow-up. Name the person who resolves conflicting evidence and the fallback for unresolved records. A blank check-in alone is not a reliable account of what happened.

Revisit this moment · 08:46 ↗
A chosen session, an uncertain next step

A fictional student selects an academic breakout and later returns to the portal. Session attendance was not captured. A proposed counselor task says the student attended and is ready to commit. How would you revise it?

Compare your reasoning

Keep the known choices separate from attendance and readiness. Describe the selected session and portal return accurately, inspect whether the next step is clear, and choose a useful invitation or review rather than asserting intent.

Revisit this moment · 10:25 ↗
A new tab nobody maintains

A fictional event team proposes a personalized portal tab for every breakout. The same resources already live elsewhere, and nobody owns updates after event day. What should the team decide before building?

Compare your reasoning

Name the student problem, decide where the maintained information belongs and assign an update owner. Compare a simpler shared resource view. Keep additional tabs only where their usefulness and upkeep justify them.

Revisit this moment · 14:47 ↗
Build a test card to take with you

Notes stay in this tab. Reloading clears them.

04 / INSIDE THE STUDIO

The seams are part
of the story.

Behind the episode

David explicitly pairs five sessions because they span event fundamentals, live operations, schedule personalization, simplification and portal design. He later brings them together as an Event Signal Loop and describes the fields for a one-event worksheet.

Revisit the studio moment · 03:35 ↗

Closing song

Hear the closing song in the full episode.

Hear the song in the episode

Art from the workshop

Conference Insights Engine series artwork brings scattered observations into a structure for shared work.

Open the artwork ↗

KEEP THE IDEA MOVING

Where would you take it next?

CONTINUE EXPLORING