Run Weekly Community Engagement Activities

[opengov-africa]

Create recurring engagement opportunities inside the community.

Tasks

• Create weekly discussion prompts
• Plan themed conversations
• Host informal community check-ins
• Encourage member-led discussions
• Track participation levels

@OpenGovAfrica/wg-community-managers

[Scholarpat]

Hi @opengov-africa can I be assigned this issue?

[opengov-africa]

Done @Scholarpat Cant wait to see the work you do with the community 🤗

[Scholarpat]

OpenGovAfrica Weekly Community Engagement Plan

Document Type: Community Management Framework
Version: 1.0 | Created: March 2026
Issue: Run Weekly Community Engagement Activities

---

Table of Contents

1. Overview
2. Weekly Engagement Structure
3. Weekly Discussion Prompts
4. Themed Community Conversations
5. Community Check-In Structure
6. Member-Led Discussions & Contributions
7. Participation Tracking System

---

1. Overview

This framework gives OpenGovAfrica Community Managers a simple, repeatable system for running weekly engagement activities that are realistic for an all-volunteer team to sustain. The goal is to create a consistent rhythm of connection, conversation, and contribution that helps both new and old members feel at home and stay engaged over time.

Core principles behind this plan:

• Low effort to run, high value to participate — each activity should take a community manager no more than 30–60 minutes to prepare.
• Member voices first — the best communities are driven by their members, not just their managers.
• Open governance in practice — our engagement style should model the transparency and collaboration we champion.
• Asynchronous-friendly — our members span multiple time zones and availability windows; activities should not require live presence to participate meaningfully.

---

2. Weekly Engagement Structure

Each week follows a four-beat rhythm. Community managers rotate responsibilities so no single person carries the full load.

🗓️ The Weekly Rhythm at a Glance

Day	Activity	Platform	Time Investment
Monday	Post Weekly Discussion Prompt	Discord #general + GitHub Discussion	~20 min
Wednesday	Mid-week Check-In & Pulse	Discord #check-in (or an existing Discord group can be used)	~15 min
Thursday	Spotlight, Resource Share, or Member Feature	Discord / GitHub	~30 min
Friday	Weekly Wrap-Up + End-of-week Check-In	Discord #general	~15 min

💡 Rotation: Each beat is to be assigned to a different community manager per week. A simple shared spreadsheet or project board can track who owns what.

---

Monday — Weekly Discussion Prompt

Start a conversation related to open governance, civic tech, or community development. Kick off the week with a single open question. Keep it short and thought-provoking.

How to run it:

• Post the prompt in Discord (#general or a dedicated #weekly-discussion channel).
• Cross-post to GitHub Discussions under a Weekly Prompt category.
• Pin the Discord message for visibility until Friday.
• Add a simple react or poll for low-effort participation (e.g., emoji vote).

---

Wednesday — Mid-Week Check-In

A lightweight pulse check to sustain momentum mid-week and surface anyone who needs support.

How to run it:

• Post a short, warm check-in message in #check-in (see templates in Section 5).
• Include one low-barrier prompt — something personal or light.
• Respond to at least 3 replies to model engagement.

---

Thursday — Community Spotlight

Recognition, resources, and amplification. This is the "give something back" moment of the week.

Rotating Thursday formats (pick one per week):

• 🌟 Member Spotlight — highlight a contributor's recent work or milestone.
• 📚 Resource of the Week — share an article, tool, dataset, or report relevant to open governance or civic tech.
• 🗣️ Upcoming Opportunity — flag an upcoming event, open issue, or call for contributions.
• 🧵 Thread Recap — summarize the week's best GitHub Discussion or Discord conversation for members who missed it.

---

Friday — Weekly Wrap-Up

Close the loop, celebrate participation, and create space for members to reflect on their week's work.

How to run it:

• Post a brief summary of the week's discussion highlights.
• Open an end-of-week check-in: invite members to share updates or progress on tasks they are working on, wins they want to celebrate, or challenges they have encountered.
• Explicitly ask if anyone needs help or support with their task — make it easy and safe to raise a hand.
• Thank contributors by name (or by handle) where possible.
• Tease the following week's theme or prompt.
• Include a "Join us next week" CTA.

Note: The end-of-week check-in doubles as a light accountability moment — members who share progress publicly are more likely to follow through. Keep the tone celebratory, not pressured.

---

3. Weekly Discussion Prompts

Discussion prompts are the heartbeat of the week. The best prompts are open-ended, relevant, and accessible to people with different levels of technical background.

Prompt Bank — Open Governance & Civic Tech

These prompts can be used on rotation, and/or adapted to the community's current focus:

Open Governance & Transparency

• "What does 'open government' mean to you personally? Has your definition changed since you joined this community?"
• "What open governance challenge do you think technology can solve in Africa?"
• "What's one piece of public data in Africa that you wish were easier to access — and why does it matter?"
• "Which African institution do you think is leading on transparency and accountability? What are they doing right?"
• "If you could open-source one government process, what would it be and what would change?"
• "What's the biggest barrier between citizens and the data that affects their lives?"

Civic Technology

• "What civic tech tool or project has impressed you recently — from anywhere in the world? What makes it work?"
• "What's a problem in your community that technology could help solve — but hasn't yet?"
• "How do we make sure civic tech actually reaches and serves people who are offline or digitally excluded?"
• "What's a lesson from a civic tech project that failed — and what can we learn from it?"

Open Source & Community

• "What made you first get involved in open source or open governance work? What keeps you coming back?"
• "What's one thing you've learned from this community that you've applied in your work or life?"
• "What does a healthy open-source community look like to you — and where does OpenGovAfrica shine or fall short?"
• "What kind of support do you wish you'd had when you first joined this community?"
• "What tools help you collaborate effectively in open-source projects?"

Seasonal / Timely Prompts

• Around elections: "What open data or civic tech tools do you think citizens need most during election season?"
• Around budget cycles: "Has your country published its national budget in an accessible format? What would you want to know?"
• Year-end: "What's your open governance highlight of the year — something that gave you hope?"

---

4. Themed Community Conversations

Once a month, a weekly prompt ties into a larger themed conversation that runs across platforms and formats. Themes give community managers a content focus and help members go deeper on topics they care about.

Suggested Monthly Themes

Month	Theme	Prompt Focus
January	New Year, New Contributions	Goal-setting, onboarding new members
February	Data for the People	Open data access, data literacy
March	Women in Civic Tech	Gender equity in open governance
April	Budget Transparency	Public finance, participatory budgeting
May	Open Source Sustainability	Volunteer burnout, funding models
June	Youth & Governance	Youth civic engagement, student contributors
July	Election Integrity	Electoral transparency, voter tech
August	Community Health Check	Retrospective, feedback gathering
September	Local Government	Municipal data, local accountability
October	Storytelling for Impact	Communicating civic tech work
November	Pan-African Collaboration	Cross-border projects and partnerships
December	Year in Review	Reflections, appreciation, looking ahead

How to Run a Theme Week

1. Announce the theme on Monday with a contextual prompt.
2. Source a relevant reading or resource for Thursday's Spotlight.
3. Consider inviting a guest contributor or member expert to share their perspective mid-week.
4. Close the theme on Friday with a summary and a "what we're doing about it" call to action.

---

5. Community Check-In Structure

Check-ins are short, human moments. They are not about updates or output — they are about reminding each other that there are real people behind the handles.

Wednesday Check-In Templates

Rotate through these or adapt them freely:

• "🌤️ Wednesday check-in! How's your week going — one word or one sentence welcome."
• "Mid-week pulse 👋 What's something you're curious about this week?"
• "Wednesday energy check ⚡ Are you feeling more like: 🔥 on fire | 🌊 going with the flow | 🐢 taking it slow? React or drop a note!"
• "Check-in time 🙋 What's one thing you've worked on this week — big or tiny — that you're glad you did?"
• "This week I am grateful for: ____________ . Fill in the blank 💛"

---

Friday End-of-Week Check-In Templates

Use these prompts alongside the weekly wrap-up post to invite members to reflect, share, and ask for help:

• "It's a wrap on another week! 🎉 Share your update — what did you work on, what went well, or what's been tough? Drop it below 👇"
• "Friday check-in ✅ What's one win — big or small — from your week? And is there anything you're stuck on where the community could help? 🤝"
• "Week in review 📋 Share your progress, a challenge you navigated, or something you're proud of. If you need support on anything, this is the place to ask 💬"
• "Closing out the week 🙌 What tasks are you wrapping up — and what's carrying over to next week? Anyone need a hand? 🙋"
• "End-of-week pulse 💚 Celebrate a win, flag a blocker, or just check in. We're here for all of it."

💡 Note: If a member flags that they need help, follow up directly or tag someone in the community who might be able to assist. Visible support builds trust and encourages others to ask.

---

Monthly Deeper Check-In (15–20 min async)

Once a month, post a slightly longer check-in prompt in GitHub Discussions or a dedicated Discord thread:

• "How are you feeling about your involvement in OpenGovAfrica right now? What's working for you — and what could be better?"
• "What would make this community 10% more useful or enjoyable for you?"
• "Is there something you want to contribute but haven't found the right way to do it yet?"

These deeper prompts serve double duty as lightweight feedback loops. Community managers should review responses and note recurring themes.

---

6. Member-Led Discussions & Contributions

The healthiest communities eventually run themselves. These practices help shift ownership from community managers to members over time.

Encouraging Member-Led Discussions

• Open the floor explicitly. End each weekly wrap-up with: "Have a topic you want the community to explore next week? Drop it below or DM a community manager."
• Create a #pitch-a-topic Discord channel where members can suggest discussion prompts or themes for upcoming weeks.
• Feature member-sourced prompts. When you use a member's idea, credit them by name in the post. Recognition reinforces the behaviour.
• Ask returning members to co-host a themed week or to write the Thursday Resource post.

Member-Led Discussion Programme

Invite members who are ready to take a lead role to host an informal "Contributor Corner" — a short async or live session on a topic they know well. Format options:

• A written post in GitHub Discussions sharing expertise or a case study.
• A 30-minute informal Discord AMA (async or live in a voice/stage channel).
• A short audio or video recording shared in Discord or the repo.

How to launch it:

• Create a member-talks or contributor-corner GitHub Discussion category.
• Put out an open call for the first 3 speakers via Discord and the weekly prompt.
• Publish a simple one-page guide: "How to Run Your Own Contributor Corner."

Recognizing Contributions

• Pin a monthly "Community Stars" post naming contributors who made a notable impact — through code, docs, discussions, or support.
• Add a community-contributor GitHub label that maintainers can apply to issues or PRs as a badge of recognition.
• Track streaks — members who engage for 4 consecutive weeks get a shout-out in the monthly wrap-up.

---

7. Participation Tracking System

Tracking doesn't need to be complicated. The goal is to spot trends, recognize active members, and identify when participation is dropping before it becomes a problem.

What to Track

Metric	How to Track	Frequency
Discussion prompt responses (Discord)	Count replies each Monday–Friday	Weekly
GitHub Discussion responses	Check thread reply counts	Weekly
Check-in engagement	Count emoji reacts + text replies	Weekly
New member introductions	Count posts in #introductions	Weekly
Member-led contributions	Log in tracking sheet	Monthly
Unique active participants	Count distinct handles engaging	Monthly

Simple Tracking Sheet

Maintain a shared Google Sheet with the following columns:

Week | Prompt Topic | Discord Replies | GitHub Replies | Check-in Reacts | New Members | Notes

Keep it lightweight. Five minutes of logging at the end of Friday is enough.

Monthly Review

At the end of each month, the community management team reviews the tracker together (async or in a short call) and asks:

• Which topics generated the most engagement?
• Are the same people engaging every week, or is participation broadening?
• Are there members who were active and have gone quiet? Should we reach out?
• What's one thing we'll try differently next month?

[Scholarpat]

Done @Scholarpat Cant wait to see the work you do with the community 🤗

Hi @opengov-africa Kindly review my submission to confirm that it aligns with the requirements of the issue, and please let me know where I can make any improvements. Thank you very much.

I’m also happy to convert this into a google doc file if that is preferred.