01 Build an experiment backlog / Case 1
An experiment should answer a specific content question with a planned change and an observation window. Keep ideas in a backlog and choose those you can produce and evaluate. Use the result to decide the next action rather than declaring a permanent algorithm rule. Apply the lesson to the fictional account Mothlight Plant Club. Work within one phone, a window, and a single plant demonstration.
02 Build an experiment backlog / Case 2
An experiment should answer a specific content question with a planned change and an observation window. Keep ideas in a backlog and choose those you can produce and evaluate. Use the result to decide the next action rather than declaring a permanent algorithm rule. Apply the lesson to the fictional account Everyday Repair Desk. Work within a tabletop, labelled cups, and a non-powered practice object.
03 Build an experiment backlog / Case 3
An experiment should answer a specific content question with a planned change and an observation window. Keep ideas in a backlog and choose those you can produce and evaluate. Use the result to decide the next action rather than declaring a permanent algorithm rule. Apply the lesson to the fictional account Small Kitchen Notes. Work within a small counter, recipe card, and a short preparation demonstration.
04 Build an experiment backlog / Case 4
An experiment should answer a specific content question with a planned change and an observation window. Keep ideas in a backlog and choose those you can produce and evaluate. Use the result to decide the next action rather than declaring a permanent algorithm rule. Apply the lesson to the fictional account Plain Language Practice. Work within a quiet room, a phone, and a fictional role-play.
05 Create a repeatable production system / Case 1
A production system connects research, scripting, capture, editing, checking, publishing, and review. Give each stage a clear output and keep a simple status record. Batch compatible tasks when it helps, but leave room to respond to new information and correct mistakes. Apply the lesson to the fictional account Mothlight Plant Club. Work within one phone, a window, and a single plant demonstration.
06 Create a repeatable production system / Case 2
A production system connects research, scripting, capture, editing, checking, publishing, and review. Give each stage a clear output and keep a simple status record. Batch compatible tasks when it helps, but leave room to respond to new information and correct mistakes. Apply the lesson to the fictional account Everyday Repair Desk. Work within a tabletop, labelled cups, and a non-powered practice object.
07 Create a repeatable production system / Case 3
A production system connects research, scripting, capture, editing, checking, publishing, and review. Give each stage a clear output and keep a simple status record. Batch compatible tasks when it helps, but leave room to respond to new information and correct mistakes. Apply the lesson to the fictional account Small Kitchen Notes. Work within a small counter, recipe card, and a short preparation demonstration.
08 Create a repeatable production system / Case 4
A production system connects research, scripting, capture, editing, checking, publishing, and review. Give each stage a clear output and keep a simple status record. Batch compatible tasks when it helps, but leave room to respond to new information and correct mistakes. Apply the lesson to the fictional account Plain Language Practice. Work within a quiet room, a phone, and a fictional role-play.
09 Collaborate around shared value / Case 1
A collaboration needs a clear audience purpose, roles, permissions, and a usable deliverable. Confirm access to participation features before planning around them. Agree on credit, review, and reuse expectations in advance. Avoid treating another creator as merely a source of followers. Apply the lesson to the fictional account Mothlight Plant Club. Work within one phone, a window, and a single plant demonstration.
10 Collaborate around shared value / Case 2
A collaboration needs a clear audience purpose, roles, permissions, and a usable deliverable. Confirm access to participation features before planning around them. Agree on credit, review, and reuse expectations in advance. Avoid treating another creator as merely a source of followers. Apply the lesson to the fictional account Everyday Repair Desk. Work within a tabletop, labelled cups, and a non-powered practice object.
11 Collaborate around shared value / Case 3
A collaboration needs a clear audience purpose, roles, permissions, and a usable deliverable. Confirm access to participation features before planning around them. Agree on credit, review, and reuse expectations in advance. Avoid treating another creator as merely a source of followers. Apply the lesson to the fictional account Small Kitchen Notes. Work within a small counter, recipe card, and a short preparation demonstration.
12 Collaborate around shared value / Case 4
A collaboration needs a clear audience purpose, roles, permissions, and a usable deliverable. Confirm access to participation features before planning around them. Agree on credit, review, and reuse expectations in advance. Avoid treating another creator as merely a source of followers. Apply the lesson to the fictional account Plain Language Practice. Work within a quiet room, a phone, and a fictional role-play.
13 Evaluate promotion as a separate test / Case 1
Paid distribution and organic response answer different questions. If you choose to investigate promotion, check current eligibility and settings, define a budget before spending, and record the objective and audience. Read the result in its paid context and avoid presenting paid views as proof of organic growth. Apply the lesson to the fictional account Mothlight Plant Club. Work within one phone, a window, and a single plant demonstration.
14 Evaluate promotion as a separate test / Case 2
Paid distribution and organic response answer different questions. If you choose to investigate promotion, check current eligibility and settings, define a budget before spending, and record the objective and audience. Read the result in its paid context and avoid presenting paid views as proof of organic growth. Apply the lesson to the fictional account Everyday Repair Desk. Work within a tabletop, labelled cups, and a non-powered practice object.
15 Evaluate promotion as a separate test / Case 3
Paid distribution and organic response answer different questions. If you choose to investigate promotion, check current eligibility and settings, define a budget before spending, and record the objective and audience. Read the result in its paid context and avoid presenting paid views as proof of organic growth. Apply the lesson to the fictional account Small Kitchen Notes. Work within a small counter, recipe card, and a short preparation demonstration.
16 Evaluate promotion as a separate test / Case 4
Paid distribution and organic response answer different questions. If you choose to investigate promotion, check current eligibility and settings, define a budget before spending, and record the objective and audience. Read the result in its paid context and avoid presenting paid views as proof of organic growth. Apply the lesson to the fictional account Plain Language Practice. Work within a quiet room, a phone, and a fictional role-play.
17 Refresh a strategy with evidence / Case 1
A strategy review asks whether the audience, promise, topics, and workload still fit. Use several observations and preserve what remains useful. Make changes at a manageable scale and document why. Recheck current rules and tool availability when a plan depends on a specific feature. Apply the lesson to the fictional account Mothlight Plant Club. Work within one phone, a window, and a single plant demonstration.
18 Refresh a strategy with evidence / Case 2
A strategy review asks whether the audience, promise, topics, and workload still fit. Use several observations and preserve what remains useful. Make changes at a manageable scale and document why. Recheck current rules and tool availability when a plan depends on a specific feature. Apply the lesson to the fictional account Everyday Repair Desk. Work within a tabletop, labelled cups, and a non-powered practice object.
19 Refresh a strategy with evidence / Case 3
A strategy review asks whether the audience, promise, topics, and workload still fit. Use several observations and preserve what remains useful. Make changes at a manageable scale and document why. Recheck current rules and tool availability when a plan depends on a specific feature. Apply the lesson to the fictional account Small Kitchen Notes. Work within a small counter, recipe card, and a short preparation demonstration.
20 Refresh a strategy with evidence / Case 4
A strategy review asks whether the audience, promise, topics, and workload still fit. Use several observations and preserve what remains useful. Make changes at a manageable scale and document why. Recheck current rules and tool availability when a plan depends on a specific feature. Apply the lesson to the fictional account Plain Language Practice. Work within a quiet room, a phone, and a fictional role-play.
21 Plan the next ninety days / Case 1
Use a modest audience purpose, a sustainable production rhythm, a test backlog, and scheduled reviews to plan a longer cycle. Keep later details provisional and reserve capacity for correction and response. Growth outcomes vary, so judge the plan by useful output, evidence, and decisions as well as follower totals. Apply the lesson to the fictional account Mothlight Plant Club. Work within one phone, a window, and a single plant demonstration.
22 Plan the next ninety days / Case 2
Use a modest audience purpose, a sustainable production rhythm, a test backlog, and scheduled reviews to plan a longer cycle. Keep later details provisional and reserve capacity for correction and response. Growth outcomes vary, so judge the plan by useful output, evidence, and decisions as well as follower totals. Apply the lesson to the fictional account Everyday Repair Desk. Work within a tabletop, labelled cups, and a non-powered practice object.
23 Plan the next ninety days / Case 3
Use a modest audience purpose, a sustainable production rhythm, a test backlog, and scheduled reviews to plan a longer cycle. Keep later details provisional and reserve capacity for correction and response. Growth outcomes vary, so judge the plan by useful output, evidence, and decisions as well as follower totals. Apply the lesson to the fictional account Small Kitchen Notes. Work within a small counter, recipe card, and a short preparation demonstration.
24 Plan the next ninety days / Case 4
Use a modest audience purpose, a sustainable production rhythm, a test backlog, and scheduled reviews to plan a longer cycle. Keep later details provisional and reserve capacity for correction and response. Growth outcomes vary, so judge the plan by useful output, evidence, and decisions as well as follower totals. Apply the lesson to the fictional account Plain Language Practice. Work within a quiet room, a phone, and a fictional role-play.