1.2.1 - Can You Explain This in 30 Seconds?

30-second explanation

Can you explain this in 30 seconds before users ask?

The call

If the explanation takes longer than 30 seconds, the idea is still too loose. AI can rewrite it quickly, but only you can decide whether the boundaries are right.

Why it matters

A 30-second explanation reveals whether you actually understand what this product should do. If the explanation needs extra context to make sense, the idea is not ready. AI can compress language, but human judgement decides which version keeps boundaries clear for users.

Explainer

A short explanation is not about compression alone. It is a test of whether you actually understand the user, the problem and the outcome. If the explanation needs a follow-up paragraph to land, the idea is still too loose. AI can help rewrite the message, but it cannot create clarity that is not there.

Make the 30-second explanation concrete

Compare the broad version with a version you can actually test.

• Too vague: This is an AI search tool that helps people find better answers.
• Concrete enough to test: This helps a content creator find gaps in what they have already published so they can decide what to write next, using AI search shaped by their saved context.

The second version lets two people describe the same product from it.

Check the 30-second explanation

• Pass: You can explain who it is for, what problem it fixes and what useful result appears without adding a second paragraph.
• Fail: If the explanation depends on follow-up clarification to make sense, it is still too vague.

Do not move into messaging, review or build work until this passes.

How to use AI for the 30-second explanation

• AI chat: Rewrite the 30-second explanation until you can state all three parts clearly.
• vibeCoding: Build the thinnest flow that tests this 30-second explanation in practice before broader build work.
• AI-assisted coding: Carry the same 30-second explanation into implementation and review so the live system keeps the same decision.

Sharpen the 30-second explanation

Copy this prompt into AI chat, replace the bracketed lines with your real 30-second explanation and keep the instruction exactly as visible here.

You are checking whether this 30-second explanation is clear enough before you move forward.

Constraint:
The explanation must be specific enough that two people would describe the same product from it.

Working draft:
User: [who it is for]
Problem: [what problem it fixes]
Useful result: [what useful result appears]

Task:
Decide whether this 30-second explanation is specific enough to guide the next decision. If it is vague, rewrite it so two people would make the same decision from this 30-second explanation.

Check:
- Would two people interpret this the same way?
- Does it stay concrete enough to guide the next step?
- Does it meet this bar: You can explain who it is for, what problem it fixes and what useful result appears without adding a second paragraph.

Return:
- A corrected 30-second explanation
- A short explanation of what was vague

Evaluation

Before accepting the result, check whether two people would describe the same product from it.

Example

To help you work through this, here is a real example. StartWithYourContext is an AI search tool built as part of the vibe2value project. Here is how its 30-second explanation was written using the three parts:

• User: A content creator who manages a website and publishes regularly.
• Problem: They search for what to write next but get generic suggestions because the tool does not know their existing content.
• Useful result: A shortlist of new page ideas grounded in what already exists on the site, shaped by their saved context.

That explanation fits in 30 seconds and two people would describe the same product from it.

When there is more than one side

Not every product fits a single explanation. When a system serves more than one side, explaining it to one audience may completely miss what matters to the other.

Multi-sided worked example

For example, StartWithYourContext needs two different 30-second explanations:

• Content creator: It finds gaps in what you have published so you know what to write next.
• Developer: It is a working example of edge compute, a database, AI search and authentication wired together into one deployable project.

Both are true, but they describe different products. If you only have one explanation, one side is being described by accident.

Risk and mitigation

• Risk: Using a long explanation that sounds complete but means different things to different people, which causes decision drift and rework.
• Mitigation: Agree on one 30-second explanation and check every new request against it before adding scope.

Key takeaway

Do not move forward until you can explain who it is for, what problem it fixes and what useful result appears without adding a second paragraph.

Work through this in a workshop

If your 30-second explanation is still unclear, bring it to a free weekly workshop. Bring the messy part of your AI-assisted build and leave with a clearer next step. In some sessions, we walk through practical examples on the Cloudflare Workers stack to show how a rough idea turns into something that actually runs.

What do you think?

How are you testing whether you can explain this in 30 seconds and how is AI helping you keep that explanation clear?