---
name: map-out-one-minute-video-topics-using-topic-wheel
description: "Pick what to film next. Use your offer, key topics, and true stories to make a short list."
category: Content Factory — Produce
stage: Produce
definitive_article: /topic-wheel
status: complete
---

# Map out one-minute video topics using Topic Wheel

It is hard to film when you do not know what to say. This guide helps an owner turn real questions and stories into a short video list. Start with what you sell and who it helps, then choose useful topics.

**The path:** Clear offer → Useful topics → True stories and questions → Video queue.

**Use this when:** The recording queue is empty, off-topic, or hard to link to the business offer.

## Inputs
- The current offer, intended customer, and owner’s real purpose and goals.
- Real source material: customer questions, call notes, comments, FAQs, allowed event questions, and true owner or partner stories.
- The current [SEO Tree](https://blitzmetrics.com/seo-tree/) map of owned topic pages, or a record that the page map is still missing.
- A sheet or drawing tool and edit access to the content tracker. Name the person who can approve the plan and the person who will record.

## First-run prompt

> Use my current offer, true stories, customer questions, and page map to build a Topic Wheel and recording queue. Put WHAT at the center, HOW topics in the middle, and WHY stories outside. Keep sources and permission notes. Do not invent people, relationships, demand counts, or page links.

## Steps
1. Use the current [Topic Wheel](https://blitzmetrics.com/topic-wheel/) definitions: WHAT is the product or service at the center; HOW is the middle ring of topics and expertise; WHY is the outer ring of people and true stories. The audience moves from stories toward the offer, but planning starts with the offer.
2. Write one clear sentence for WHAT. State the actual product or service and who it is for. Do not replace the offer with a vague mission line.
3. List about three to seven HOW topics that support the offer and match real expertise. Merge duplicates. Keep the owner’s plain words instead of invented framework names.
4. For each topic, collect real WHY stories, people, and allowed collaborations. Record the source and permission state. A wish to work with someone is not an existing relationship.
5. Add real customer questions under the matching topics. Preserve the question wording and source in the private tracker. Questions can produce teaching clips; they are not themselves the WHAT ring.
6. Match topics to the owned page map. Use the topic hub for the main explanation and specific stories as supporting pages when appropriate. Mark a missing page as a gap instead of linking an unrelated page.
7. Create one recording-queue row per useful prompt: question or story, source, topic, link to the offer, intended viewer, page home, speaker, and state. Rank by observed repeat questions and the agreed business need. If frequency was not measured, say so.
8. Review the queue with the plan owner. Hand accepted prompts to [Record one-minute videos](https://local-service-spotlight.github.io/task-library/?task=record-one-minute-videos#task-record-one-minute-videos) or an agreed [50-clip batch](https://local-service-spotlight.github.io/task-library/?task=batch-record-50-raw-clips-in-one-session#task-batch-record-50-raw-clips-in-one-session). Save the wheel, source list, and current queue together.
9. The source calls for a monthly refresh. Keep answered items linked to their clips; do not erase history. Add new questions and mark replaced or stale prompts. A calendar job needs an agreed owner, timezone, access, and trigger before it can run.

## Definition of done (QA checklist)

- [ ] The wheel uses WHAT center, HOW middle, and WHY outside, with the actual offer stated.
- [ ] Each selected topic relates to the offer; each story or question has a traceable source.
- [ ] The queue has a clear prompt, topic, speaker, and owned-page destination or named page gap.
- [ ] Priority is based on evidence or labeled judgment, with no fabricated demand counts.
- [ ] Accepted prompts and prior answers remain findable for recording and later review.

## Example(s)

**Fictional teaching example — not a real business plan or customer research.** Maple Cycle’s sample wheel has WHAT at the center: “Bike repair quotes and service for local riders.” Its HOW topics are repair quotes, planning a shop visit, and used-bike questions. An outside WHY story is Alex’s wish to make basic questions feel welcome.

| Prompt | Ring or topic use | Sample source | Recording choice |
| --- | --- | --- | --- |
| Why did Alex open the shop? | WHY story | Invented founder note | One origin story |
| Can I send a photo before a visit? | HOW: planning a visit | Invented customer email | One teaching answer |
| What does a quote visit include? | WHAT: current offer | Invented service sheet | One offer explanation |

The sample does not say “customers ask this 20 times a week,” because no real count exists. In a real queue, replace each invented source with the actual record and set the next speaker before filming.

## Handoff and Content Factory context

The named speaker receives accepted prompts through [Record one-minute videos](https://local-service-spotlight.github.io/task-library/?task=record-one-minute-videos#task-record-one-minute-videos). The editor receives the page map so later articles fit the [SEO Tree](https://blitzmetrics.com/seo-tree/). A missing page is planning work, not a reason to invent a page URL.

This task serves **Produce** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce makes or prepares source material. Process edits it, Post puts approved work on a channel, and Promote helps it reach people. Only the steps and handoff above are part of this task.

## When this runs

Create the first wheel once. The source proposes a monthly refresh and updates when new questions arrive. Treat monthly as a planned review until a real owner and schedule have been configured; no reminder is installed by this guide.

## Run with an agent

The agent can prepare the plan, organize allowed files, and check the evidence it can actually access. A person records real stories, supplies permission, or resolves an account step when needed. Save the current state in the project files and tracker. A model name does not create memory, access, a scheduler, or permission to act.

For all agent media checks, keep the player muted and its volume at zero before playback. If that cannot be checked, use captions, metadata, or still frames. Do not claim sound quality was heard when it was not.

## Write up the real run

For every actual attempt, [write the run’s meta article](https://blitzmetrics.com/meta-article-prompt/). Link this exact task and its source revision. State the start, work done, evidence, result, gaps, and next owner. Keep failed, partial, and blocked work visible. Writing the record does not authorize publishing it.

Use one stable execution ID for this task’s actual run. Internal retries, checks, and new versions do not add runs. A separately scoped child task may have its own ID linked to the parent. A teaching example has no real execution ID and must not enter the run count. Follow the [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) for that distinction.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Produce
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 3, gating 4 (runs every factory cycle or weekly; gates a phase)
- **Suggested previous station:** `create-clear-conversion-path`
- **Suggested next station:** `batch-record-50-raw-clips-in-one-session`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Raw files in Content Library `01-Raw/` plus a tracker row (question, date, speaker). Next skill never needs the chat — it needs the files.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/topic-wheel
- Exact task: [Map out one-minute video topics using Topic Wheel](https://local-service-spotlight.github.io/task-library/?task=map-out-one-minute-video-topics-using-topic-wheel#task-map-out-one-minute-video-topics-using-topic-wheel)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Topic Wheel: stories, topics, and offer](https://blitzmetrics.com/topic-wheel/)

## Review and evidence still needed

The contributor status in the source header is preserved. It is not a claim that this draft has been independently accepted or that a real run has passed. The worked example above is for teaching only.
- The public Topic Wheel page still embeds an older skill with reversed rings; parent needs to synchronize that embedded source.
- Real offer, story permission and question sources remain required for a real plan.