Eleutherious: Start a Circle layout draft for the team to compare, text from the Start a Circle guide

2026-10-21T14:33:05Z

Start a Circle layout draft for the team to compare, text from the Start a Circle guide

New page

<div style="border:1px solid #c8ccd1;background:#fef6e7;padding:0.5em 1em;margin-bottom:1em;font-size:90%;">'''Layout 2 of 3''' for the team to compare: one page per part of the guide. Same text as [[Start a Circle]] on 21 October 2026. Compare [[Start a Circle 1|1. One page]] · [[Start a Circle 2|2. Part pages]] · [[Start a Circle 3|3. Chapters with a book box]].</div>
{{Start a Circle 2 parts}}
This section explains what to do after your first Circle has taken place. It covers how to follow up with attendees, maintain engagement, and keep momentum going between sessions. It also includes guidance for stewards on reviewing outcomes, identifying next steps, and turning initial conversations into ongoing participation and coordinated action.

== Post-event reporting ==
After your event, be sure to share an update on the [https://forum.logos.co/ '''Logos Forum'''] so the rest of the community can stay informed. Use the template below to help structure your feedback. Once your update is posted on the Forum, share the link in the Discord #circle-discussions channel so others can easily read it.

Post-event reporting is a core part of how Circles learn, improve, and coordinate across the network. It ensures that activity in local Circles translates into shared knowledge and measurable progress around winnable issues.

==== Why this matters ====
Without consistent reporting, it becomes difficult to:

* Track progress on winnable issues
* Understand what is working across Circles
* Justify ongoing funding and resourcing decisions

'''Please note!'''

If a Circle does not share their post-event updates, we will not be able to approve further funding for subsequent Circle activities in that location. This is not intended as a punitive measure, but as a requirement for maintaining transparency, accountability, and effective resource allocation across the network.

Funding should directly correlate with the visibility of outcomes.

'''Privacy Guidelines:'''

* Any photos of participants should have faces blurred or replaced with emojis before sharing, unless you have their express consent to share the photo.
* Avoid including full names in public notes; use first names only or initials.

----

=== Reporting template: ===
==== Logos Circle [location, month] ====
Date: <br />Location: <br />Registered on Luma: <br />Attended: [number of participants AND return attendees]<br />Languages:

==== Participants ====
'''Pointers to include:'''

* Number of attendees and countries represented
* Backgrounds: developers, startup founders, crypto enthusiasts, privacy advocates.
* Areas of interest or focus

==== Topics Discussed ====
'''For each topic, include:'''

* '''Topic Name / Theme'''
* '''Key Points & Insights:'''
** Challenges or open questions
** Solutions, ideas, or proposals
** Technologies or tools mentioned
* '''Action Items or Next Steps'''

==== Winnable issues update ====
'''Pointers to include:'''

* If a winnable issue has been defined, and what is it if so
* Any updates on the winnable issue that happened outside of the Circle meeting
* Any blockers faced
* Planned follow-up actions, including who is taking responsibility of what

==== What We Learned / To Improve / New Ideas ====
'''Pointers to include:'''

* Things that worked well
* Areas for improvement
* New ideas or experiments to try next time

== Feedback form ==
Feel free to use these questions for the Luma feedback form, or write your own. It's also a good idea to ask core circle members privately for feedback, and to check in with the wider group in the Discord channel about how things went and what could be improved.

* Star rating on Luma
* What part of the meetup stood out most to you?
* Is there anything you wish had been different or improved?
* Are you interested in helping with future events or actions?
* If yes, what would you like to contribute to?

== Checklist: Post Event ==
* ☐ Post an update on the Logos Forum about how your Circle went.
* ☐ Send a thank-you message in your group chat, including a link to your forum post for those who want to engage there.
* ☐ Reach out 1:1 to standout participants to discuss taking on a steward role in the Circle.
* ☐ Set up the Luma page for your next Circle as soon as possible, and share the link in your group chat so people know when and where the next meeting is.
* ☐ If a local topic had strong agreement, reach out to relevant people or organisations already working on that issue to explore collaboration, or invite them to the next Circle to discuss the topic in more depth.
* ☐ Join the Online Logos Circle X Space (Tuesdays, 7 PM UTC) to share updates with the broader Logos community and discuss what your Circle is working on.

<div style="display:flex;justify-content:space-between;border-top:1px solid #c8ccd1;margin-top:1.5em;padding-top:0.5em;font-size:90%;"><span>◄ [[Start a Circle 2/Section 3: Running the First Circle|Section 3: Running the First Circle]]</span><span>[[Start a Circle 2/Section 5. Stewarding a Circle|Section 5. Stewarding a Circle]] ►</span></div>
{{Start a Circle 2 parts}}

Start a Circle 2/Section 4: Post-Circle - Revision history

Eleutherious: Start a Circle layout draft for the team to compare, text from the Start a Circle guide