FilmotionOne good idea can support a week of content. But cropping one video three ways and rewriting its caption four times usually gives me seven versions of the same post.
I want each version to do a different job. Someone discovering a problem needs a different post from someone comparing solutions or trying to take action.
Here is how I would turn one practical idea into seven distinct posts, using a local plant shop as an example. The method works for tutorials, service businesses, product education and creator content.
Start with a claim, not a topic
“Houseplant care” is a topic. It is too broad to hold a week of connected content together.
A more useful starting point is: “Before watering a houseplant with yellow leaves, check the soil, because yellowing can have several causes.”
That claim gives me a problem, a common assumption and a useful action. It also has a boundary: checking soil is a starting point, not a complete diagnosis.
I write those elements into a small source note before drafting anything. For this example, I would include the plant species, its growing conditions and advice checked by someone qualified to provide it.
This matters because repurposing multiplies mistakes as easily as it multiplies useful information. I would rather verify one solid claim than clean up seven confident oversimplifications.
Find seven questions inside the idea
Instead of asking for seven captions, I ask what seven questions a customer might have about the claim.
For the plant shop, my question map looks like this:
- What might yellow leaves mean?
- What should I check first?
- What does that check look like?
- What mistake should I avoid?
- Does this advice apply to every plant?
- What information would help someone assess my plant?
- What should I remember next time?
Each answer becomes a separate post. The shared idea keeps the week coherent. The questions stop it from feeling repetitive.
I choose formats after this step. A demonstration benefits from video. A reference guide may work better as a carousel. A question that needs context can become a short written post.
Post one introduces the problem
My first post would challenge the assumption without pretending to diagnose every plant.
The opening could be: “Yellow leaves do not automatically mean your plant needs more water.”
I would show a yellowing leaf, explain that several causes are possible and introduce checking the soil as one useful first step. A short video of about 20 to 30 seconds should be enough for this narrow message.
The job is recognition. I am helping someone notice that their usual response might be worth reconsidering.
Posts two and three make the idea usable
For the second post, I would create a carousel explaining what to observe before reaching for the watering can. Each slide would cover one observation, such as soil moisture, drainage or recent changes in light.
I would keep species-specific advice clearly labelled rather than presenting one watering rule for every plant.
The third post would demonstrate the check on a real plant. I would film the pot, the soil and the observation being made, with the shop owner explaining what they can and cannot conclude.
These posts share a claim, but they are not duplicates. One is a reference someone can save. The other shows what the process looks like in practice.
Posts four and five add judgement
The fourth post would focus on one mistake: adding water without checking whether the soil is already wet.
I would explain the reasoning rather than simply telling people they are doing plant care wrong. A useful correction gives someone a better decision, not just a reason to feel embarrassed.
The fifth post would answer the boundary question: “Does this apply to every houseplant?”
This is where I would bring in a knowledgeable staff member to explain why species and growing conditions matter. If I did not have a checked answer, I would not generate a confident one to fill the slot.
A limitation can make a strong standalone post. It adds information that the introductory version deliberately left out.
Posts six and seven help people act
For the sixth post, I would show what information to gather before asking the shop for help: a photo of the whole plant, its location, recent watering and a view of the pot.
That turns a vague “What is wrong with it?” into a more useful conversation. It also gives the business a natural invitation to offer help without forcing a sales pitch into every post.
The seventh post would be a compact reminder card: “Yellow leaf? Pause, observe, then decide.” The accompanying caption would recap the first check and link back to the fuller explanation where the platform allows it.
This final version earns its place as a memory aid, not another introduction.
Use AI to separate angles, not invent evidence
I can use AI to turn my checked source note into drafts. My instruction would be: “Answer each question separately. Keep the central claim consistent. Do not add causes, statistics or customer stories that are not in the source.”
Then I compare the drafts side by side. If two posts teach the same thing, I combine them or find a genuinely different question.
I also check that every post makes sense alone. Nobody should need to have seen Tuesday's carousel to understand Thursday's video.
My final test is simple: can I name the new value in each post? Recognition, instruction, demonstration, correction, qualification, preparation and recall are seven different jobs. That is how I get a week from one idea without making the audience sit through the same lesson seven times.