Product Management And User Experience Prompts

INPUTS
[problem]; [users]; [evidence]; [constraints]; [desired outcome]

PROMPT
Write a product requirements brief centered on the user's problem. Include context, evidence, goals, scope, non-goals, user scenarios, functional requirements, acceptance criteria, dependencies, and open questions. Separate user needs from proposed implementation choices. Define success measures and how they will be observed. Avoid adding features merely because they are common in similar products. End with the smallest coherent release and the questions that must be answered before design or development can proceed responsibly.

INPUTS
[interview notes]; [product]; [customer situations]; [source identifiers]

PROMPT
Analyze the supplied material for the progress customers are trying to make. Identify triggering situations, desired outcomes, current alternatives, anxieties, and forces supporting or resisting change. Ground each finding in a source identifier and label interpretations. Create concise job statements and explain where different customer situations imply different jobs. Avoid reducing the analysis to demographic personas. End with product and messaging implications, contradictory evidence, and interview questions that would test the most important inferred job.

INPUTS
[feature ideas]; [user evidence]; [business goals]; [effort estimates]; [capacity]

PROMPT
Prioritize the feature ideas using explicit criteria tied to user outcomes and business goals. Separate strong evidence from requests supported by one anecdote. Use supplied effort estimates and mark uncertainty. Compare impact, reach, confidence, dependencies, and opportunity cost without presenting speculative scores as objective truth. Recommend a focused sequence and identify items to test before building. Provide a decision table and rationale. End with assumptions that could change the ranking and a review point after the next release or research cycle.

INPUTS
[journey or screens]; [user goal]; [context]; [research]; [constraints]

PROMPT
Review the journey from the user's perspective. Identify where people may not understand the next step, lack needed information, face unnecessary effort, or lose confidence. Distinguish observed problems from design hypotheses. Recommend changes that support the goal and respect the constraints. Provide a stage-by-stage critique, revised flow, and sample interface copy for key moments. End with a usability test plan and the evidence needed to determine whether the proposed changes actually improve task completion.

INPUTS
[prototype]; [target users]; [key tasks]; [research questions]; [session length]

PROMPT
Create a usability test plan that observes behavior without coaching participants. Define recruiting criteria, realistic tasks, opening script, neutral prompts, and follow-up questions. Specify what to record: completion, errors, hesitation, comments, and context. Avoid task wording that reveals the intended solution. Provide a timing plan and observation template. End with a synthesis method that distinguishes usability issues from feature preferences and a clear explanation of what this small study can and cannot establish.

INPUTS
[screen context]; [user goal]; [state]; [constraints]; [brand voice]

PROMPT
Write interface copy for the supplied state, including labels, instructions, errors, empty states, or confirmations as relevant. Make the action and consequence clear using concise language. Explain how a user can recover from an error and preserve consistent terminology. Do not imply success when a process is still pending. Provide alternatives with character counts when limits matter. End with a rationale for the recommended wording and a checklist covering clarity, accessibility, accurate expectations, and consistency with the actual system behavior.

INPUTS
[interface]; [user tasks]; [technology]; [known issues]; [review scope]

PROMPT
Create an accessibility review plan for the interface. Cover keyboard operation, focus order, semantic structure, labels, contrast, zoom, error handling, and assistive-technology checks as relevant. Distinguish issues visible in supplied material from those requiring interactive testing. Provide a prioritized checklist with the affected task and verification method. Do not claim conformance from screenshots alone. End with the tools or expertise needed for unresolved checks and a practical sequence for fixing barriers that prevent essential user actions.

INPUTS
[hypothesis]; [user segment]; [feature]; [metrics]; [constraints]

PROMPT
Design a product experiment that tests the hypothesis with a clear primary outcome. Define eligibility, assignment where feasible, exposure, observation window, guardrail measures, and decision rules. Explain risks from small samples, novelty, tracking gaps, or overlapping changes. Include a fallback research method if a controlled experiment is impractical. Provide an experiment brief and a results template. End with the evidence needed for rollout and a check that the experiment measures user value rather than superficial interaction alone.

INPUTS
[changes]; [audience]; [known limitations]; [required actions]; [version or date]

PROMPT
Write release notes that explain what changed and why it matters to users. Group updates by user task and distinguish new capabilities, improvements, fixes, and known limitations only where those categories help. Use clear language and avoid internal implementation detail that does not affect users. Include required actions, compatibility changes, and support information from the supplied facts. Provide a concise announcement and a fuller version. End with a verification checklist ensuring no feature, availability claim, or resolved issue is overstated.

INPUTS
[feedback]; [usage evidence]; [product strategy]; [capacity]; [decision]

PROMPT
Prepare a product decision brief from the supplied feedback. Group requests by underlying problem and distinguish desired outcomes from customers' proposed solutions. Compare evidence across segments and note whose voices are missing. Recommend building, testing, documenting, or declining each priority item with a reason. Provide a concise decision table and a customer-facing explanation for one declined request. End with research needed to resolve uncertainty and a check that the decision remains aligned with the product's intended users and scope.