Before any feature, a product manager needs a sharp answer to one question: who are we serving, what change are we creating, and how will we know it worked? A vision one-pager forces that clarity onto a single page. GenAI tools like Claude and ChatGPT are excellent thinking partners here, because they pressure-test your logic and surface assumptions you cannot see yourself.

Why a one-pager beats a deck

A 30-slide strategy deck hides weak thinking behind animation. One page does not. The discipline of fitting vision, target user, the core problem (al-waga’a al-asasi / الوجع الأساسي), the wedge, and a single success metric onto one page is where strategy actually happens. In MENA product work this is doubly important: you often serve bilingual EN/AR users with very different expectations, and a fuzzy vision produces a product that serves neither well.

Step-by-step: draft your vision one-pager with Claude

  1. Write 3-4 messy paragraphs about your product idea or area in plain language. Do not polish.
  2. Paste them into Claude with the prompt below. Ask for a structured one-pager.
  3. Read the output critically. Where Claude guessed, correct it with real knowledge. Where it asked a sharp question, answer it.
  4. Iterate twice. The second pass is always tighter than the first.
You are a senior product strategy advisor. Here are my rough notes on a product
area: [PASTE NOTES].

Turn this into a one-page product vision with exactly these sections:
1. Vision statement (one sentence, present tense)
2. Target user and the job they are hiring us for
3. The core problem and why it is painful today
4. Our wedge: the smallest thing we can win on first
5. One north-star success metric, with a target
6. Three assumptions this vision depends on, ranked by risk

Keep it to one page. For each section, flag where my notes are too vague to be
credible, and ask me a sharp question to sharpen it.

A second prompt that works well for sharpening:

Act as a skeptical investor. Read this vision one-pager and give me the three
weakest claims, the one assumption that would kill the product if wrong, and the
single question you would ask in a pitch meeting that I cannot yet answer.

Try it

Take a product or feature area you actually work on. Write your messy notes, run the first prompt, then run the skeptical-investor prompt. Rewrite your vision statement until it survives both. Save the final one-pager — it becomes the anchor for your PRD later in this course.

Next