ClaudeEach audience, positioning update or new product explanation

Explain a software product from its positioning brief in Claude

Give Claude the audience, approved positioning and supported product facts. Review ngram’s plan, then create a concise explanation of how the product’s main concepts fit together.

See what you can make

A Blueprint explanation created through Claude from a positioning brief supported by Linear’s official product pages. Labeled diagrams explain issues, projects, initiatives, cycles and roadmaps.

Prompt

Use the connected ngram tools to explain Linear from this source-backed positioning brief. The audience is product managers and software teams who want a concise introduction to how the product organizes work. Positioning brief: Linear connects product planning with day-to-day execution. Projects bring related issues, documents and updates together. Initiatives organize larger product efforts, while cycles help teams plan time-boxed work. Roadmaps provide a visual view of the product plan. Explain these relationships without adding performance guarantees, customer results, pricing or endorsement claims. Sources: https://linear.app/features, https://linear.app/plan and https://linear.app/build. Use this narration: “Product plans and daily work need a shared structure. Linear brings issues, projects and larger initiatives into one product-development system. A project gathers related work and documents. Initiatives connect projects to bigger product efforts. Cycles help teams plan time-boxed work, while roadmaps show the plan visually. Start with the product work your team needs to organize, then explore how these pieces fit together.” Create a 40-second, 16:9 Blueprint video with clear English narration and quiet background music. Use labeled diagrams to introduce “Issues”, “Projects”, “Initiatives”, “Cycles” and “Roadmaps”, keeping the relationships consistent with the brief. Show a project containing issues and documents, an initiative grouping projects, and a separate cycle timeline. Treat these as explanatory diagrams. Use plain text “Linear” and do not simulate clicks or invent product interface screens. Finish on “Explore your product workflow” with “linear.app/features” held fully visible for at least five seconds after narration. Include readable source credit “linear.app/plan · linear.app/build”. Prepare the video for review and download. Show selected settings and the total estimate before creation. After I confirm, create the plan and return the narration and complete scene sequence for review. Wait for approval before production. Continue the same video when I ask for progress. Leave scheduled tasks off. Return the preview, ngram project and available MP4 export when ready. If the ngram connector is not connected, read https://www.ngram.com/markdown/docs/connect-ngram-to-claude.md?view=1 and help me connect ngram to Claude. Wait for me to complete sign-in and approve access, then resume this workflow.

Read the video transcript

Product plans and daily work need a shared structure. Linear brings issues, projects and larger initiatives into one product-development system. A project gathers related work and documents. Initiatives connect projects to bigger product efforts. Cycles help teams plan time-boxed work, while roadmaps show the plan visually. Start with the product work your team needs to organize, then explore how these pieces fit together.

How it works

One source. A repeatable workflow.

04 steps · Claude

Start with

An approved positioning brief and current product sources

ngram logo

Create in

Claude

Make

A source-backed software explanation with clear labeled visuals

  1. Supply the approved positioning

    Open Claude with ngram enabled. Provide the audience, product purpose, supported capabilities and current source pages.

  2. Review the concept relationships

    Confirm the selected settings and estimate with plan review. Check the narration, diagram labels and relationships against the approved brief.

  3. Watch the complete explanation

    Ask Claude for progress on the same video. Check that the visuals explain the intended concepts and that the source credit and next action remain readable.

  4. Place it beside the product information

    Choose appropriate viewing permissions or an available MP4 export. Include the current product destination where viewers can learn more.

Watch the workflow

Explain software positioning through Claude

Follow the product brief and sources in the actual Claude conversation. Review the diagram revision, approve the plan and download the MP4, then watch the complete software explanation.

Read the walkthrough transcript

The request supplies an audience, positioning brief, official source pages and narration. The plan is revised to keep cycles and roadmaps separate from the issue, project and initiative hierarchy. The revised plan is approved, and Claude returns the MP4 and ngram project. The complete explanation plays with this narration. Product plans and daily work need a shared structure. Linear brings issues, projects and larger initiatives into one product-development system. A project gathers related work and documents. Initiatives connect projects to bigger product efforts. Cycles help teams plan time-boxed work, while roadmaps show the plan visually. Start with the product work your team needs to organize, then explore how these pieces fit together.

Your starting point

Start with the prompt.

Prepare the audience and approved software brief in Claude, then review ngram’s explanation and concept diagrams.

Open Claude ↗

Connect ngram to Claude

Review. Then deliver.

Claude returns the software explanation and ngram project. Check the product facts and visual relationships before sharing.

While your video is being made

Ask Claude for the existing video’s status and review any pending plan or question.

Share a link

Choose the intended viewers and include the relevant product destination with the explanation.

Download the video

Ask Claude for an MP4 using an option available to the ngram account. Download in the ngram project requires an eligible paid plan. Review the saved explanation before placing it on the product page or presentation.

If the workflow needs attention

Ask Claude to inspect the existing attempt and identify the source or creation issue. Continue with the same video ID and project link.

The diagram implies an unsupported relationship
Identify the affected connection and provide the correct product description. Ask Claude to revise the diagram and matching narration.
The explanation adds a product claim
Quote the added line and supply the approved source wording. Review the full revision before sharing.
The positioning changes
Update the audience, product brief and closing action together. Ask Claude to revise the affected scenes and review the complete story.

Keep the workflow. Change the story.

  1. 01

    Explain the product to another audience

    Change the assumed knowledge, vocabulary and relevant capabilities while preserving supported product facts.

  2. 02

    Refresh the story when the product changes

    Provide the updated positioning and current source pages. Review the concept relationships and next action before replacing the video.

Turn your next source into a video.