Product Playbooks

The empty-room problem starts before you open the doors

Plan early activity, member density and conversation prompts so new joiners do not arrive to silence.

The store.fan teamOctober 22, 20267 min read
The empty-room problem starts before you open the doors

You open your new community, check the member list and see three names. Nobody has posted since joining. You publish a welcome message, then wait. By the next morning, the room feels less like a gathering place and more like an empty venue with the lights left on. This is the empty-room problem, and it usually starts before the doors open: there is no planned reason to return, no expected rhythm and no first conversation that feels easy to enter.

Decide what the room is for

Before you invite anyone, write one sentence that describes the job members can return to. “A place to discuss marketing” is too broad: almost any question could fit, and no particular question has to be asked. “A fortnightly working room where freelance designers bring one offer, improve it and report back” gives the community a repeatable purpose. The job creates the agenda without requiring you to invent a new topic each day.

  1. 1Name the recurring problem members bring into the room. Use the words they already use when asking for help.
  2. 2Choose the action they will take together: review, practise, report back, plan, troubleshoot or make a decision.
  3. 3Set a visible rhythm. For example, Monday can be for intentions, Wednesday for questions and Friday for progress reports.
  4. 4Define what does not belong. A narrow boundary makes useful participation easier because members do not have to guess whether their post fits.

Plan density before you plan growth

A room with five people behaves differently from a room with fifty. With five, one missed prompt may leave the week silent. With fifty, a single question may produce more replies than you can reasonably moderate. You do not need a universal member target; you need enough likely participation for the promised rhythm. If you expect one in four members to respond to a weekly prompt, a group of eight gives you an expected two responses. That may be enough for a small working circle, but not enough for a lively general discussion.

If your promise is...Plan for...
Personal feedbackA small founding group, clear submission limits and dates when feedback happens
Peer discussionA shared topic, simple opening questions and enough members for different viewpoints
AccountabilityA recurring check-in and a way to report progress without writing an essay
Expert accessSpecific office-hour times, a question queue and boundaries around response time

Treat this as an operating decision, not a vanity metric. If the room needs several replies per post, do not open it to a scattered audience and hope activity appears. Invite people who share the same immediate problem, or begin with a smaller founding cohort. A paid community is easier to explain when the access, cadence and member job are concrete; you can also study the distinction between a paid community and a product with a chat tab in this playbook.

Give the first week a shape

New members should not have to search the history to discover how to participate. Prepare a short sequence that moves from orientation to contribution. The first action should be possible on the day they join. Asking for a detailed introduction or a complete business plan creates work before trust exists. Ask for something small and relevant instead.

  • Day 1: explain the community’s job, how to ask for help and what happens each week. Ask members to share one current goal or obstacle.
  • Day 2: post a useful example, template or short exercise connected to the community’s job. Make it possible to use without attending a live session.
  • Day 3: ask one narrow question with a choice, a number or a short sentence as the answer. Specific prompts lower the effort of replying.
  • Day 5: run a check-in. Ask what members tried, what changed and what they want to work on next.
  • Day 7: summarise patterns you noticed and point to the next recurring activity. A summary shows that participation is being read, not merely collected.

The point is not to fill every day with your content. It is to make the room familiar. Once members know where introductions, questions and progress reports belong, they can start conversations without waiting for you to perform. If you sell access through store.fan communities, pair the access page with this operating sequence so the purchase describes what happens after the transaction.

Write prompts that can survive silence

A prompt fails when it asks for a performance. “Tell us about your business” sounds welcoming, but it gives members too many possible answers and no clear reason to read one another’s replies. A better prompt contains a subject, a boundary and a response someone can build on.

  1. 1Start with a shared situation: “What are you trying to finish before Friday?”
  2. 2Limit the answer: “Reply with the task, the obstacle and the next 20-minute action.”
  3. 3Add a connection: “Read one other answer and suggest a smaller next step.”
  4. 4Close the loop: return later with a summary, a resource or a follow-up question based on the replies.

Prepare more prompts than you expect to use, but do not publish them all at once. Keep a bank organised by purpose: introductions, diagnosis, practice, feedback and reflection. When a member asks a question privately, remove identifying details and turn the underlying problem into a prompt only if it will help others. Do not turn every member message into content; people need to feel that the room is for them, not simply a research source.

Make the paid access match the promise

The checkout is part of the room design. If the page says “join a supportive community” but the actual offer is one monthly group call and an archive of resources, the silence may be a positioning problem rather than a participation problem. Describe what members receive, what they are expected to do and when you will be present. A creator storefront such as store.fan can put the offer, payment and access in one place; its paid plans start with a 14-day trial, and store.fan takes 0% of sales while Stripe’s processing fee still applies.

  • Name the live or recurring elements, including their frequency where you have decided it.
  • Say whether members can expect replies from you, peers or both.
  • Explain the response boundary. For example, questions may be answered during a weekly session rather than immediately.
  • Show the first month’s sequence so a prospective member can judge the commitment before buying.
  • Use an email welcome message to direct new joiners to the first action, rather than assuming they will explore on their own.

Choose a number based on the interaction your promise requires. If a weekly prompt needs three replies and you expect one in four members to respond, eight members is the arithmetic starting point. Adjust for your actual experience, the topic and how often you can participate.

Do not immediately post three more prompts. Give the question a smaller answer format, answer it yourself with a real example and invite one or two relevant members directly if that is appropriate. Then check whether the question belongs to the community’s stated job.

Not necessarily. You can charge for access to a defined process, regular sessions, feedback or a specific member outcome before the room is large. Be precise about what is already available and what is still being built; do not price imagined activity as if it already exists.

Plan the first month, describe the member job and set up your storefront when the experience is ready to explain.

Start with store.fan
#communities#memberships#creator-playbook#engagement

Turn your knowledge into income

Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.