Product Designers —0→1

Act as a senior product designer in a 0→1 product team. For this fuzzy area: [insert], help me write a sharp problem statement. Cover: who it affects, when it happens, why current solutions fail, and what 'good' would look like. Output as a 1-page problem brief.

Act as a product designer. For [insert audience], generate 8 user pain hypotheses across functional, emotional, and social dimensions. For each: hypothesis, why it might be true, how to test cheaply. Present as a hypothesis list.

Act as a product designer. For [insert competitor product], run a structured teardown. Cover: who it serves, what it does well, where it fails, what surface area is open. Present as: Strengths, Gaps, White space, Implication.

Act as a behaviour researcher. For [insert problem area], identify the 5 most common workarounds users have already invented (spreadsheets, Slack hacks, post-its, etc.). For each: what they do, what it tells us about the real job, the design implication. Present as a table: Workaround, What It Does, Real Job, Design Implication.

Act as a JTBD strategist. For [insert product area], write the core Job-to-Be-Done: 'When [situation], I want to [motivation], so I can [outcome]'. List 3 functional, 3 emotional, 3 social jobs. End with what users currently 'fire' to hire your solution.

Act as a product strategist. For [insert idea], identify the beachhead user — the smallest, sharpest segment to win first. Cover: who they are, where they congregate, why they'd pay, why they're easier to reach than the broader market. Present as a beachhead profile.

Act as a researcher. For [insert audience], write a persona including: demographics, behaviours, mental models, pain points, jobs, and one quote that captures their mindset. End with a 'how we help them' summary.

Act as a product strategist. For [insert product], define 3 anti-personas — users we will not optimise for, even if they show up. For each: who they are, why they're not the target, what we sacrifice if we serve them. Present as a non-target list.

Act as a B2B product designer. For [insert product] sold into [insert org type], map the decision-making unit: Buyer, Champion, User, Beneficiary, Blocker. For each: title, cares about, fears, unlocks. Present as a DMU table.

Act as a product designer. For this user job: [insert], generate 8 distinct concepts in Crazy 8s style. Range from safe to weird. For each: core mechanic, what user experiences, 1-line provocation. Present as 8 numbered concept cards.

Act as a senior product designer. For [insert opportunity], generate 3 distinct concept directions. For each: core idea, how user experiences it, what's distinctive, what it sacrifices. Make all three genuinely different. Present as 3 concept cards.

Act as a product designer. For [insert problem], generate 5 deliberately-bad concepts (anti-solutions). For each: how it would fail, what it tells us about real constraints. Use the inverted insights to refine our actual concept direction. Present as a table: Anti-Solution, How It Fails, What It Reveals — then the refined direction.

Act as a product designer. For [insert problem area], find 5 lightning demos — interesting solutions to similar-shaped problems from outside our category. For each: what they do, what mechanic to steal, how to adapt it. Present as a table: Demo, What They Do, Mechanic to Steal, How to Adapt.

Act as a product designer. For this concept: [insert], plan a clickable prototype that's 'realistic enough to test, not real to build'. Cover: which screens, what fidelity, what gets faked, what gets real. Present as a prototype plan.

Act as a product designer. Plan a Wizard of Oz prototype where [insert system or capability] is faked by a human. Cover: what the user sees, what the wizard does, the protocol, success criteria. Present as a WoZ test plan.

Act as a UX writer. For this prototype flow: [insert], draft the microcopy: empty states, error messages, confirmations, onboarding nudges, system messages. Use plain language, set expectations, don't apologise. Present as a copy doc.

Act as a senior product designer. For this prototype: [insert], stress-test it across: edge cases, slow connections, accessibility, multi-language, error states, abuse scenarios. Identify what breaks first. Present as a stress-test report.

Act as a researcher. Write a 5-act interview script for testing [insert prototype] with [insert audience]: friendly welcome, context questions, introduce prototype, tasks with think-aloud, debrief. 60 minutes total. Present as a script.

Act as a product designer running first-time user tests. For [insert prototype], plan 5 user tests covering: tasks, success criteria, observation guide, post-test questions, the patterns to watch for across all 5. Present as a test plan.

Act as a product designer. After 5 user tests on [insert prototype] with these notes: [insert]. Identify patterns (3+ users), partial patterns (2 users), and outliers. Map each pattern to: what the user did, what it means, what to change. Present as a pattern map.

Act as a senior product designer. Based on these test results: [insert], make the call: Build (pursue this direction), Iterate (test again with changes), Pivot (different solution to same problem), Park (problem isn't ready). Justify with evidence, not gut. Present as a decision memo.

Act as a strategist. For [insert concept] launching in 6 months, write 5 plausible reasons it could fail. For each: what specifically went wrong, what we should test or change today to prevent it. Present as a pre-mortem report.

Act as a product designer. For [insert concept], define V1 scope: what's in (the must-haves to deliver the core value), what's out (the nice-to-haves we will NOT build), what's deferred (V2 and beyond). For each, justify. Present as a V1 scope doc.

Act as a product designer. For V1 of [insert product], write a story map: user activities at the top, tasks below each, sub-tasks below those. Mark which sub-tasks are V1 release, V2, V3+. Present as a hierarchical story map.

Act as a senior product designer working with engineering. For [insert V1 scope], sequence the build into 4 sprints: what gets built first to de-risk, what unlocks user testing earliest, what can wait. Present as a 4-sprint sequence with rationale.

Act as a product marketing designer. For [insert product] V1 launch, draft the launch story: the hook (why now), the problem we solve, the moment of truth in the product, the call to action. Present as 4 short paragraphs.

Act as a product designer. For first-time users of [insert product], plan the onboarding: what they see in the first 30 seconds, the first action, the aha moment, the moment of habit. Avoid feature tours. Present as an onboarding flow doc.

Act as a UX writer. For [insert empty state — e.g. no projects yet], write 3 versions of the empty state copy: practical, motivating, witty. Each should have a heading, 1-line explainer, and a clear CTA. Present as 3 options.

Act as a product designer working with an analyst. For [insert product], identify the single 'aha metric' — the action that, when a user does it, predicts retention. Justify with reasoning, suggest how to instrument it, and define a healthy threshold. Present as an aha metric brief.

Act as a growth-minded designer. For [insert onboarding flow], plan how to track and report activation drop-off step by step. Cover: what to measure at each step, healthy vs concerning thresholds, where to focus design fixes first. Present as an activation tracking plan.

Act as a senior product designer running a critique on your own work. For [insert design], identify: 3 things that work, 3 things that don't, 3 things you're avoiding looking at. Be honest. Present as a self-crit doc.

Act as a senior product designer giving direct critique. For this flow: [insert], identify: where the user's effort outweighs the value, where the system asks them to do its job, where consistency breaks. Give specific, actionable feedback. Present as a critique doc.

Act as a product designer. For [insert stakeholder, e.g. the CFO], brief them on [insert design decision]. Cover: what we decided, why, what we tested, what we sacrificed, what risk we're carrying, what would change our mind. Be direct. Present as a 1-page brief.

Act as a senior product designer documenting a decision. For [insert design choice], write a rationale doc: what we considered, what we chose, why, what we rejected and why, what we'd watch for to know we got it wrong. Present as a structured doc.