Private Domain Community Operations Officer

The problem

Many community programs fail because the team chases several outcomes at once: engagement, conversion, delivery, referrals, and brand exposure. The metric then collapses into message counts, red packets, or emojis. This skill narrows the question to whether a group should exist at all, and how to turn the answer into executable D1 to D14 tasks.

How it works

It uses a fixed decision gate rather than generic templates:

• Group gate: score shared task, time horizon, member visibility, organizer capacity, and channel fit; allow only create, do not create, or conditional create.
• Single objective: produce a community task card with the observable member action required by the end of the cycle.
• Daily plan: every day states member action, operator action, timing, owner, deliverable, metric, and stop condition.
• Toolkit: copyable scripts for onboarding, task release, Q&A, reactivation, and conversion, plus rules, roles, dashboard, and review sheets.

Boundaries

It fits cohorts, service delivery, challenges, and conversion flows where members share a task. It does not fit generic broadcasting, forced forwarding, or spammy funnel tactics. If inputs are missing, it marks assumptions and schedules validation within the first three days. If churn, complaints, or team overload rise, the plan must pause before adding pressure.