
Events and Peer Learning
Making community events useful for different experience levels
Design a community event where newer and experienced members can each contribute, question assumptions and leave with a useful next step.
Give newer and experienced members different ways to add value to the same event. Explain essential terms, ask for the circumstances behind advice and choose a task that neither group can finish merely by stating what it already knows. Everyone needs a reason to listen as well as speak.
Define the task before labelling the audience
“Beginner” and “advanced” are broad labels. A long-standing member may be new to this particular task; a recent member may bring deep experience from elsewhere. Describe the work instead: “for people setting up their first peer-support process” or “for people reviewing one they already run”.
If the two groups need fundamentally different answers, offer separate sessions or a common opening followed by task-specific discussions. If they share a decision, keep them together and make their different viewpoints useful. For example, newer members can identify where a process is confusing, while experienced members can explain which trade-offs appeared after they used it.
Build several entry points into one discussion
Send a short description of the problem and define terms that would otherwise be unexplained in the room. Invite a question beforehand. At the event, begin with a concrete situation rather than “Who has advice?” A case gives participants something to examine even if they have not handled that exact situation themselves.
- What would you need to know before acting?
- What would you try first, given these constraints?
- What changed when you faced a similar situation before?
- Which part of that account may not transfer to another setting?
This sequence invites observation, judgement and experience without requiring everyone to claim expertise. Allow thinking time or a brief written response before asking people to speak. If someone chooses to pass, leave that choice intact.
Designing Inclusive Community Events for All Experience Levels
- Share a concrete case studyPresent a real-world scenario relevant to the event topic, such as setting up a peer-support process in a community group.
- Define key terms upfrontExplain jargon like 'peer-support process', 'GST implications', or 'ABN requirements' to ensure clarity for all participants.
- Pose open-ended questionsAsk: 'What would you need to know before acting?', 'What would you try first?', and 'Which part may not transfer to another setting?'
- Invite diverse contributionsEncourage newer members to highlight confusion points and experienced members to explain trade-offs from past use.
Prevent experience from becoming authority by default
Ask experienced members to describe the conditions behind a recommendation: team size, available help, the type of customer problem or the point at which they changed course. Invite newer members to question a step that is easy to overlook. Neither group should be asked to represent everyone at its level.
If one person repeatedly answers first, the host can pause and ask for a different circumstance. When a specialist fact is needed, note it for verification by an appropriate owner. Peer experience should not quietly become official instruction.
Choose small groups deliberately. Similar-experience groups may let participants examine a concern in depth before sharing it. Mixed groups may help them compare assumptions.
Explain why a grouping was chosen and give each group a task. Change the grouping if the discussion leaves some people without a useful role.
Benefits of Mixed vs. Similar-Experience Groups
- Mixed-Experience GroupsHelp compare assumptions; newer members spot unclear steps; experienced members explain context behind decisions.
- Similar-Experience GroupsAllow deeper exploration of specific concerns; useful when discussing complex topics like ATO compliance or superannuation reporting.
Check whose needs the event met
At the end, ask what each participant can now do, what remains unclear and whether the event assumed knowledge they did not have. Review the contributions: were newer members able to ask without being dismissed, and did experienced members learn something beyond repeating familiar advice? Attendance alone cannot answer those questions.
Use the responses to adjust the next invitation, preparation material or grouping. If the same foundational explanation consumes every event, prepare a maintained resource for it. If experienced members need a deeper case, give that case its own session. Keep the event centred on a shared task.
Post-Event Reflection Questions for Facilitators
- Did newer members feel safe asking questions?
- Did experienced members share insights beyond repetition?
- Was foundational knowledge assumed that some lacked?
- Can the next event be improved based on feedback?



