---
name: create-a-3x3-video-grid
description: "Plan nine videos across three topics. Give each one a clear purpose and a place in your content plan."
category: Content Factory — Produce
stage: Produce
definitive_article: /social-amplification
status: complete
---

# Create a 3×3 video grid

A list of random video ideas can leave gaps. This guide helps an owner plan nine clips on three useful topics. Start with what you sell, then choose stories, lessons, and offer answers that help the right people.

**The path:** Three topics → Nine clear prompts → Nine saved takes → Editor.

**Use this when:** The offer and purpose are clear and the team needs a planned set of nine source videos.

## Inputs
- The real offer, purpose, and existing WHY video or story notes. Use [the WHY-video task](https://local-service-spotlight.github.io/task-library/?task=create-a-3-minute-why-video#task-create-a-3-minute-why-video) if that source is missing.
- Three HOW topics from the [Topic Wheel](https://blitzmetrics.com/topic-wheel/) that support the actual offer, plus real questions, stories, and proof for those topics.
- The current [SEO Tree](https://blitzmetrics.com/seo-tree/) page map, so the editor knows which owned topic page each future piece should support.
- The speaker, phone, approved raw folder, tracker access, and a named editor. Allow enough filming time; a fixed half-day is a planning choice, not a promise.

## First-run prompt

> Build a three-topic by three-purpose video grid from my actual offer, stories, questions, and page map. Label story, teaching, and offer cells. Keep source links with each prompt and flag any invented or missing proof. After filming, count distinct usable cells and make the editor’s handoff.

## Steps
1. Select three related HOW topics where the business has real knowledge. Check how each supports the WHAT offer at the center of the Topic Wheel. Keep WHY stories on the outside.
2. Draw a table with three topic rows and three purpose columns: story/WHY, teaching/HOW, and offer or proof/WHAT. This is the purpose-based grid variant in this task source. The one-minute guide also describes concept/example/objection variations; label the chosen variant instead of mixing both systems mid-grid.
3. Write one prompt in every cell. Use a real story for the story cell, a useful question for teaching, and a true offer answer or supported result for the final cell. Link each prompt to its source. Do not fill a proof cell with a made-up win.
4. Give each cell a short ID such as A1. Add topic, purpose, question source, intended viewer, and the owned page that the later piece should support. Page-map neighbors are not automatic prerequisites.
5. Record one clear answer per cell using [one-minute video guide](https://blitzmetrics.com/one-minute-video-guide/). Aim for 45–90 seconds. Keep the person’s own words, and record a new take when facts, sound, or picture fail.
6. Save files as YYYY-MM-DD-topic-cellID-person. Use a take suffix for repeats. Upload into the existing raw folder and link the selected take for every cell in the tracker.
7. Review nine distinct purposes and nine usable takes. Count a repeated file once. If one cell has no real proof, mark the gap and agree on a truthful offer explanation or another supported prompt before filming it.
8. Hand the grid to [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). The editor decides which clips need articles or other formats. Publishing and paid sequencing are separate tasks with their own scope and evidence.

## Definition of done (QA checklist)

- [ ] Three topics and three clearly labeled purposes produce nine distinct cells.
- [ ] Each cell has a traceable prompt, a selected usable take, and rights notes.
- [ ] Topics connect to the real offer and a reviewed owned-page plan; no reversed Topic Wheel labels remain.
- [ ] All nine selected files open for the editor and match the tracker.
- [ ] Any missing cell is named; nine planned ideas are not nine completed videos.

## Example(s)

**Fictional teaching example — a planning grid, not nine recorded videos.** Maple Cycle uses this sample purpose-based grid:

| Topic | Story / WHY | Teaching / HOW | Offer / WHAT |
| --- | --- | --- | --- |
| Repair quotes | A1: Why Alex wants quotes to feel clear | A2: What information helps the shop prepare a quote | A3: What the shop’s quote visit includes |
| Shop visits | B1: A lesson from feeling lost in a new shop | B2: How to plan a drop-off | B3: How to book a visit with this shop |
| Used bikes | C1: Why the shop welcomes first-time riders | C2: What to ask a seller before a shop visit | C3: What a shop assessment does and does not include |

These sample prompts are invented. A real grid needs the owner’s actual stories, offer terms, and question sources. If only A1–C2 have usable takes, the measured result is 8 of 9. An unfilmed C3 remains open; it is not “covered” by a similar A3 clip.

## Handoff and Content Factory context

The editor receives the nine-cell map and source files via [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). The map may inform later distribution, but it does not choose ad audiences, spend, or prove a funnel result.

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

Run once for an agreed three-topic set. Expand or refresh when real questions, offers, or sources change. This guide creates no standing filming or ad schedule.

## 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:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** `create-a-3-minute-why-video`
- **Suggested next station:** `step-1-upload-video-to-google-drive-and-descript`
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/social-amplification
- Exact task: [Create a 3×3 video grid](https://local-service-spotlight.github.io/task-library/?task=create-a-3x3-video-grid#task-create-a-3x3-video-grid)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Topic Wheel: stories, topics, and offer](https://blitzmetrics.com/topic-wheel/)
- [One-minute video method](https://blitzmetrics.com/one-minute-video-guide/)
- [Social Amplification operating context](https://blitzmetrics.com/social-amplification/)

## 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.
- Independent editorial review should confirm the preferred grid variant across the task and one-minute public guide.
- Real source facts and nine reviewed takes are still execution requirements.