Chapter 3
Design a weekly growth rhythm
weekly audience-growth rhythm is the practical output of this chapter. Complete it in one focused work session so you can decide how to divide creation, publishing, distribution, conversation, and review time, without depending on daily inspiration and abandoning consistency after a busy week.
What you’ll get
- A completed weekly audience-growth rhythm you can use in the next chapter.
- A documented decision about how to divide creation, publishing, distribution, conversation, and review time.
- A pass or fail signal: the calendar is sustainable for four weeks and gives every strong idea more than one distribution moment.
- A concrete first action: Batch one core asset, repurpose it by channel, reserve conversation time, and schedule one weekly decision review.
Separate creation from distribution
A realistic weekly system includes:
- Research: collect questions and examples.
- Create: develop one substantial idea.
- Adapt: turn it into platform-native formats.
- Publish: distribute with a clear next step.
- Engage: answer relevant comments and participate in focused conversations.
- Capture: invite high-intent people to a free resource, email list, or store.
- Review: decide what to repeat, refine, or stop.
Apply this chapter to your store
Start with the evidence you already have: the current Tapmy setup, the exact customer path, the messages people see, and the records created after an action. Do not redesign the entire system while you are still trying to locate the constraint.
Implementation move: Batch one core asset, repurpose it by channel, reserve conversation time, and schedule one weekly decision review.
Write the decision beside the evidence that supports it. If a teammate cannot reproduce the conclusion from the same evidence, the work is not yet operational. The deliverable should be specific enough to hand to another person without a meeting.
Decision checkpoint
| Check | Pass condition | If it fails |
|---|---|---|
| Evidence | The current state is visible and reproducible | Capture the real route, screen, record, or message before changing it |
| Decision | how to divide creation, publishing, distribution, conversation, and review time is written in one sentence | Reduce the scope until one owner can choose |
| Execution | Batch one core asset, repurpose it by channel, reserve conversation time, and schedule one weekly decision review. | Assign a time and owner, then complete the smallest end-to-end version |
| Verification | the calendar is sustainable for four weeks and gives every strong idea more than one distribution moment | Return to the failed boundary and retest only after the cause is changed |
Common failure mode
Using the posting calendar as the whole growth system while ignoring distribution and replies. This hides the actual constraint and creates false confidence. Use the chapter output as a gate: do not move forward until the decision is explicit and the pass signal is visible.
20-minute implementation sprint
- Open the current Tapmy path and capture the starting state.
- Complete the smallest version of the weekly audience-growth rhythm.
- Record the decision, owner, and next review date.
- Test the pass signal once from the customer’s point of view.
- Save the evidence where the person running the next chapter can find it.