strategy-micro-communities

name	strategy-micro-communities
description	Use when the main deliverable concerns niche WhatsApp, Facebook, LinkedIn, or private communities built around member value; use playbook-community-management when that neighbouring workflow owns the primary decision.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

Strategy: Micro-Communities

Use When

• Use this skill for niche WhatsApp, Facebook, LinkedIn, or private communities built around member value.
• Use it when the requested deliverable needs the domain decisions and acceptance checks below.

Do Not Use When

• Use playbook-community-management when that neighbouring workflow owns the main decision or deliverable.
• Do not proceed when required evidence, approval, or safety review is absent; return the missing-input path instead.

Required Inputs

Artefact	Source/provider	Required?	If absent
Objective, audience, market, and intended decision	Client or approved brief	yes	Ask for it or state a narrow working assumption
Existing channel, content, commercial, or performance evidence relevant to niche WhatsApp, Facebook, LinkedIn, or private communities built around member value	Client systems, supplied files, or verified research	conditional	Mark the check unassessed and avoid performance claims
Approval, policy, budget, access, or risk constraints	Accountable client owner	conditional	Stop before publishing, spending, collecting data, or making regulated claims

Workflow

1. Confirm the decision, consumer, market, and evidence boundary; distinguish the request from playbook-community-management.
2. Inspect supplied artefacts and record missing or unverified inputs before drafting.
3. Apply the domain framework in this skill and use the decision rule below at each branch.
4. Stop for approval before publishing, spending, contacting people, changing live systems, or making regulated claims.
5. Review the deliverable against the quality and anti-slop gates; if a check fails, correct it and rerun the affected check.
6. Hand off the artefacts, assumptions, evidence, and unresolved risks to the named consumer.

Outputs

Artefact	Consumer	Observable acceptance condition
Niche whatsapp, facebook, linkedin, or private communities built around member value deliverable	Client decision-maker or delivery team	Names the chosen route, owners, sequence, assumptions, and measurable acceptance checks
Decision and risk record	Reviewer or implementer	Links each recommendation to supplied evidence or labels it as an assumption

Evidence Produced

Evidence	Format	Acceptance condition
Input and assumption register	Table or annotated brief	Missing and unverified items are visible, not treated as passed
Release check	Completed quality checklist	All blocking findings are fixed or the deliverable is explicitly withheld

Capability and Permission Boundaries

Read and search are the minimum capabilities. Analysis and planning remain read-only. Edit only files placed in scope; publishing, outreach, spend, personal-data processing, production changes, and certification claims require explicit authority and evidence of success.

Degraded Mode

If files, tools, network, current evidence, rendering, or authorised access are unavailable, return the narrowest useful qualified deliverable. Mark each unavailable check not assessed; never convert it into a pass or invent market facts.

Decision Rules

Choice condition	Action	Failure or risk avoided
A specific member need and operating capacity exist	Define membership promise, moderation, and cadence before recruitment	An unmanaged broadcast group creates spam and trust loss
Evidence is contradictory or materially incomplete	Pause the affected recommendation and request the accountable source	Confident advice built on an unresolved premise
Authority is limited to analysis or planning	Deliver a read-only plan and approval checklist	Unauthorised publication, spend, outreach, or data use

Quality Standards

• Keep Uganda/East Africa, British English, EAT, UGX, and WhatsApp-first assumptions explicit where they apply.
• Tie recommendations to observed evidence, a named assumption, or a verification action.
• Give the next operator enough detail to execute without guessing ownership, sequence, or acceptance.
• Apply ai-marketing/anti-ai-slop during drafting and block release on an F from ai-marketing/ai-slop-audit.

Anti-Patterns

• Inventing a client metric, audience fact, price, partner, or platform rule. Fix: verify it or label the decision provisional.
• Treating a missing tool, source, render, or approval as a passed check. Fix: mark it not assessed and narrow the output.
• Producing channel tactics before defining the decision and consumer. Fix: state the required outcome and handoff first.
• Copying a global template without adapting Uganda/East Africa access, language, payment, or trust conditions. Fix: record which local assumptions apply.
• Recommending publication, outreach, spend, data collection, or a regulated claim without authority. Fix: stop at an approval-ready draft.
• Reporting activity as success without an acceptance condition. Fix: name the observable result and evidence source.

References

• AGENTS.md

Required Input

Ask for all of the following before generating any deliverable:

1. Client business name and industry — e.g., "Kampala Bakers Ltd — food and beverage"
2. Country/city — default Uganda/East Africa if not specified
3. Primary audience — who would join this community, and why would they join? Be specific about demographics, shared interests, and motivations
4. Business objective — what should the community achieve? (customer retention, lead generation, product feedback, brand advocacy, or a combination)
5. Moderation capacity — how many hours per week can the client or their team dedicate to moderating and posting in the community?
6. Existing community — does the client already have a Facebook Group, WhatsApp group, forum, or informal community? If yes, describe its current state (member count, activity level, problems)
7. Platform preference — Facebook Group, WhatsApp Community, LinkedIn Group, or private forum? If the client is unsure, apply the decision framework in Section 2

---

Section 1 — Community vs Audience

A brand audience receives content passively. Followers on a Facebook Page, subscribers to an email newsletter, viewers of a YouTube channel — the brand broadcasts and the audience consumes. The brand controls what is posted, when it is posted, and who sees it. Growth is measured in reach and impressions. The relationship is one-directional.

A community is a group of people with shared interests who interact with each other, not only with the brand. The brand facilitates; members generate value for one another. A question posted by one member is answered by five others before the brand responds. A success story shared in the group inspires three more members to try something new. The brand does not fully control the conversation — and that is precisely what makes the community credible. Growth is measured in engagement depth, member retention, and peer-to-peer interactions.

Why this distinction matters for East African clients: in Uganda and across East Africa, community is not a marketing tactic — it is the cultural norm. People trust networks, referrals, and shared group membership far more than brand advertising. A Ugandan consumer is more likely to act on a recommendation from someone in their WhatsApp group than on a sponsored post. A brand that builds a genuine community earns a level of trust that no advertising budget can replicate. The POEM model (Chaffey, 2024) classifies community as Owned media, but a thriving community generates Earned media — peer-to-peer advocacy — at scale.

---

Section 2 — Platform Selection

Apply this decision framework to select the right platform. If the client has expressed a preference, validate it against the criteria below before proceeding.

Platform	Best For	EA Suitability	Moderation Load	Monetisation Options
Facebook Group (public)	Discovery-led communities, broad topics	High — Facebook has the widest reach across all EA demographics	Medium	Facebook Stars, paid subgroups
Facebook Group (private)	High-trust communities, exclusive access	High	High	Paid membership
WhatsApp Community	Operational, high-engagement, mobile-first	Very high — WhatsApp is ubiquitous in Uganda and EA	Very high	Not native — link to external offer
WhatsApp Group (single)	Small, high-trust groups under 1,024 members	Very high	High	Not native
LinkedIn Group	Professional/B2B communities	Medium — LinkedIn penetration is lower in EA outside formal sector	Low–medium	Lead generation
Telegram	High-privacy, tech-savvy audiences	Low–medium in EA outside the tech sector	Low	Paid channels
Private forum (Circle, Mighty Networks)	Premium, paid communities	Low — requires strong existing brand equity to justify sign-up	Low	Subscription revenue

Selection rules:

• If the client's audience is broad, consumer-facing, and based in Uganda, default to Facebook Group (private) for trust or Facebook Group (public) for discovery
• If the client needs high-frequency, mobile-first communication with a small trusted group, use WhatsApp Community or a WhatsApp Group
• If the objective is B2B lead generation or professional credibility, use LinkedIn Group
• If the client has an existing loyal audience willing to pay for exclusive access, evaluate Circle or Mighty Networks
• Never recommend a platform the client cannot moderate at the required load — a dead community is worse than no community

---

Section 3 — Community Strategy Design

Produce all five elements below for the client. Each must be specific to their business, audience, and objective.

3.1 Community Purpose Statement

Write one sentence answering: "This community exists so that [audience] can [do/achieve/experience something specific]."

The purpose must be member-centric, not brand-centric. "This community exists to promote [Brand]" is an audience, not a community.

Example: "This community exists so that Ugandan women entrepreneurs can share practical advice on running a business while raising a family."

Test: Read the purpose statement aloud. If it could be replaced with "follow our page," reject it and rewrite.

3.2 Member Profile

Define the ideal member precisely. Vague member profiles produce communities that are useful to no one.

Include:

• Demographics (age range, location, gender if relevant)
• Professional or life stage context
• Shared problem, interest, or aspiration
• What would motivate them to join and stay active

Example: "Ugandan women aged 25–45 who own an SME with 1–5 employees, have been operating for at least one year, and are looking for peer support and practical business advice — not inspirational content."

3.3 Member Value Proposition

State three specific things a member gains from this community that they cannot get anywhere else. Generic answers ("connection," "support") are not acceptable.

Example:

1. Access to other vetted business owners in the same sector who share real numbers and real challenges — not curated highlight reels
2. First access to the client's new product launches, promotions, and free resources before the public
3. Monthly Q&A sessions with the brand founder or invited expert, exclusive to community members

3.4 House Rules

Every community must have written house rules published in the group description and pinned as the first post. Adapt the template below to the client's community:

1. Introduce yourself when you join — tell us who you are and what brought you here
2. Share your knowledge and experience freely — this is a giving community, not a selling community
3. No spam, unsolicited promotion, or advertising without prior admin approval
4. Treat every member with respect — no harassment, personal attacks, discrimination based on gender, religion, ethnicity, or any other characteristic
5. Do not share false or unverified claims, particularly regarding health, finance, or legal matters
6. Tag the admin if you see a post that violates these rules
7. Consequences: first offence → admin warning via private message; second offence → post removed; third offence → permanent removal from the group

3.5 Community Content Rhythm

Communities require consistent content from the admin, especially in the first three months. Apply this weekly rhythm:

Day	Post Type	Example
Monday	Opening question or weekly prompt	"What is your biggest challenge this week? Drop it below — let's help each other."
Wednesday	Educational post, how-to, or resource	A short tip, checklist, or article relevant to the community purpose
Friday	Celebration post	Member spotlight, wins of the week thread, or a success story submitted by a member
Daily	Active moderation	Respond to all member posts and comments within 24 hours; welcome every new member personally

In Month 2 and beyond, reduce admin posts to three per week minimum once member-generated content is sustaining the feed. Never drop below three admin posts per week in the first six months.

---

Section 4 — Community Launch Sequence

Follow this week-by-week launch guide. Adapt timelines only if the client has a compelling reason.

Week 0 — Pre-Launch Setup Set up the group with a complete description, cover image direction (brief for designer), and house rules. Write the welcome post before a single member joins. Identify the founding members — these are 10–20 people the client knows personally, respects, and trusts to set the culture. Founding members are not random followers; they are selected.

Week 1 — Soft Launch Invite founding members personally via direct message — not a mass broadcast. Post the welcome message. Publish five posts this week to fill the feed before other members see it. Ask founding members to introduce themselves. A community that launches to an empty feed dies immediately.

Week 2 — Activation Post one question designed to generate replies (not likes). Respond to every comment within 24 hours. Send a direct message to any member who joins but does not post: "Welcome! Tell us a little about yourself and what brought you here." This single action dramatically increases early engagement.

Week 3–4 — Growth Push Begin promoting the community externally: post about it on the brand's Facebook Page, send a WhatsApp broadcast to existing contacts, include a link in the email newsletter. Continue daily moderation without exception. Highlight founding member contributions publicly to set behavioural norms.

Month 2 Onwards Post a minimum of three times per week. Spotlight one member per week. Run one Q&A session or live discussion per month. Begin tracking member growth, post engagement rate, and the ratio of admin posts to member posts (the member-post ratio should increase steadily — aim for 60% member-generated content by Month 4).

---

Section 5 — Monetisation and Business Integration

Map how the community generates measurable business value. Apply the ROI formula — (TLV − COCA) ÷ COCA (Bodnar and Cohen, 2012) — when reporting community returns to the client.

Lead generation: Pin a post in the group header linking to a lead magnet, free consultation, or exclusive offer. Members who enquire via the community are warm leads — they have already demonstrated trust in the brand. Track these enquiries separately from cold inbound leads.

Product feedback: Use the community as a free research panel. Post a poll or open question when testing a new product idea, pricing model, or service change. Members who contribute feedback feel invested in the outcome and are more likely to purchase.

Brand advocacy: Active community members recommend the brand in other WhatsApp groups and Facebook Groups — the most high-value form of earned media in East African markets. Track referral source data on new enquiries and attribute community-sourced referrals explicitly.

Paid community tier: For clients with strong brand equity, introduce a paid members tier with exclusive benefits: early product access, private Q&A sessions, premium downloadable resources. Use Circle.so or Mighty Networks as the platform. Price in UGX at a level accessible to the target member — test at UGX 20,000–50,000 per month before scaling.

Community-to-sales funnel: Map the member journey explicitly:

New member → Engaged member (posts or comments within 30 days) → Warm enquiry → Customer → Advocate

Track how many sales per month originate from community membership. Report this figure to the client monthly. A community that cannot demonstrate a conversion pathway within six months needs a strategy review.

---

Section 6 — EA-Specific Considerations

Apply all of the following as defaults when working with Ugandan and East African clients.

Platform priority: Facebook Groups are the dominant community format for scale in Uganda. WhatsApp Groups and WhatsApp Communities are the preferred format for high-trust, high-frequency communication with smaller audiences. Do not default to LinkedIn unless the client's audience is explicitly professional and formally employed.

Language: Large EA communities naturally mix English and Luganda, or English and Swahili, in their posts and comments. Do not suppress this. Mixed-language posts signal authenticity and belonging; correcting members' language register damages trust. The brand's own posts should maintain the tone established in the community purpose, but member language is member-led.

Mobile-first design: The majority of community members in Uganda access Facebook and WhatsApp exclusively on mobile. Design all community content accordingly:

• No PDF attachments — use typed posts or images with embedded text
• Break long posts into short paragraphs with line breaks between each
• Keep videos under 60 seconds; subtitle all videos
• Use voice notes sparingly in WhatsApp communities — some members cannot play audio in public

Religious and cultural sensitivity: Uganda is a religiously diverse country. House rules must explicitly prohibit discrimination based on religion, ethnicity, and gender. Avoid scheduling major community events or promotions on Sundays (Christian observance) or Friday afternoons (Muslim Jumu'ah prayer). Acknowledge national holidays and mourning periods — posting promotional content during a national tragedy is a reputational risk.

WhatsApp administration: Appoint a minimum of two admins for any WhatsApp group or community — never rely on a single administrator. Define the admin response time commitment in writing before launch (e.g., "Admins respond within 4 hours between 7am and 9pm"). Admin burnout is the primary reason WhatsApp communities fail in EA markets.

---

Quality Criteria

Good output from this skill meets all seven of the following standards:

• The community purpose statement is member-centric, specific, and clearly distinguishable from a brand audience or broadcast channel
• The platform recommendation is justified against the decision framework in Section 2, with moderation load considered against the client's stated capacity
• All five community design elements (purpose statement, member profile, value proposition, house rules, content rhythm) are produced and tailored to the client
• The launch sequence is week-by-week, actionable, and accounts for the founding-member strategy
• Business value is mapped with at least three monetisation or integration pathways and a defined conversion funnel
• A complete house rules template is included, adapted to the client's community context
• EA platform defaults, language mixing, mobile-first design, and cultural sensitivity considerations are applied throughout

---

References

Consult these related skills when building or extending a community strategy:

Skill	When to Use
playbook-community-management/SKILL.md	Detailed day-to-day moderation playbook, escalation procedures, and community health metrics
platform-whatsapp/SKILL.md	WhatsApp-specific tactics, broadcast list strategy, and WhatsApp Community setup guidance
platform-facebook/SKILL.md	Facebook Group optimisation, algorithm considerations, and Facebook Page integration
meta-social-listening/SKILL.md	Monitoring community sentiment, tracking brand mentions, and identifying emerging issues before they escalate

Academic references:

• Bodnar, K. and Cohen, J. (2012) The B2B Social Media Book. Hoboken: Wiley
• Chaffey, D. (2024) Digital Marketing: Strategy, Implementation and Practice. 8th edn. Harlow: Pearson
• Kotler, P. et al. (2023) Marketing Management. 16th edn. Harlow: Pearson