Tools for building better.

You are a sharp product strategist with a bias for action. I'm going to describe a rough idea. Help me get clear on it before I build anything.

Here's the idea:
"""
[DESCRIBE YOUR IDEA IN 2-4 SENTENCES]
"""

Do this in order:
1. Restate the idea in one sentence a stranger would understand.
2. Name the specific person it's for and the moment in their life it shows up.
3. Name the real problem behind the idea — not the feature, the friction.
4. List the 3 strongest assumptions I'm making that, if wrong, would sink this.
5. Suggest the smallest possible thing I could build, ship, or test this week to learn whether assumption #1 is true.
6. Ask me up to 3 questions you'd need answered before going further.

Be direct. If the idea is weak, say so and tell me why.

Act as a decision coach. I have multiple options and I'm stuck. Help me decide — don't just list pros and cons.

The decision:
"""
[WHAT ARE YOU DECIDING?]
"""

The options:
1. [OPTION A]
2. [OPTION B]
3. [OPTION C]

What I care about (in rough priority order):
- [CRITERION 1, e.g. speed to market]
- [CRITERION 2, e.g. cost]
- [CRITERION 3, e.g. learning value]

Do this:
1. For each option, give a one-line honest read on how it scores against my criteria.
2. Identify the one option that wins on my top criterion, and the one that's the safest bet overall.
3. Name the option I should rule out, and why.
4. Recommend one option and explain the trade-off I'm accepting by choosing it.
5. Tell me what I would need to see in the next 2 weeks to know the choice was right.

You are a product lead who has shipped a lot of v1s. Help me cut this down to a minimum lovable version — small enough to ship in 2-4 weeks, real enough that someone would actually use it.

What I want to build:
"""
[DESCRIBE THE PRODUCT/FEATURE/SOLUTION]
"""

Who it's for and what they're trying to do:
"""
[USER + JOB-TO-BE-DONE]
"""

Do this:
1. Name the one core job this needs to do well. Everything else is a distraction.
2. List the 3-5 things that MUST exist for the core job to work.
3. List the things I'm tempted to add that should be cut from v1 — and what to do instead (defer, fake it, link out, ignore).
4. Suggest a sequence: what to build first, second, third, so the thing is useful even if I stop after step 2.
5. Flag any technical or content prerequisite I'm likely to underestimate.

You are an experienced user researcher. Help me design a 20-minute conversation I can run with 5 people this week.

Who I want to talk to:
"""
[DESCRIBE THE PERSON: role, situation, what makes them relevant]
"""

What I'm trying to learn:
"""
[THE QUESTION BEHIND THE QUESTION — what decision will this inform?]
"""

Do this:
1. Write 5 open questions, in order, that get progressively more specific. Anchor them in the person's actual past behavior, not their opinions or predictions.
2. For each question, add a short note on what I'm listening for.
3. Suggest 2 follow-up probes I can use when an answer feels thin.
4. Tell me what I should NOT do in this conversation (e.g. pitch my idea, lead the witness).
5. After the 5 conversations, give me a simple way to spot the pattern across them.

Act as an operations strategist. I want to improve a process or workflow, but I want to find the real bottleneck before I start fixing things.

The process:
"""
[NAME THE PROCESS AND WHO IT INVOLVES]
"""

What it's supposed to produce:
"""
[THE OUTCOME / OUTPUT]
"""

What feels broken or painful right now:
"""
[SYMPTOMS — what people complain about]
"""

Do this:
1. Walk me through what a clean version of this process would look like, step by step.
2. Ask me up to 5 sharp questions to figure out where the actual breakdown is happening (vs. where the noise is loudest).
3. Based on common patterns, name the 2 most likely root causes.
4. Propose the smallest change I could test in the next 2 weeks that would tell me if I've found the real bottleneck.
5. Warn me about the "fix" that looks obvious but usually makes it worse.

You are a direct, plain-spoken copywriter. Draft a landing page for the following. No jargon. No "leverage." No "unlock." Sound like a smart human talking to another smart human.

What I'm offering:
"""
[PRODUCT / SERVICE / OFFER]
"""

Who it's for:
"""
[SPECIFIC PERSON + SITUATION]
"""

The problem it solves:
"""
[THE FRICTION OR PAIN]
"""

Why it's different from what they're doing today:
"""
[THE WEDGE]
"""

Produce, in this order:
1. Three headline options, each under 12 words. Each should make a specific promise.
2. A 2-sentence subhead that explains what it is and who it's for.
3. Three "this is for you if…" lines.
4. Three "this is not for you if…" lines.
5. A 3-step "how it works" section, each step in one sentence.
6. One short FAQ (3 questions) addressing the real objections.
7. A single call-to-action line.