Product AI Hub > Prompts
AI Prompts for Product Designers
A curated collection of practical AI prompts to support research, ideation, UX writing, documentation and more.
Designed to be used directly in your day-to-day product design work.
How to use these prompts
Prompts are starting points, not final answers.
This space provides templates and examples to help you integrate AI into your design process, always with a critical mindset and strong product criteria.
Research problem definition
Act as a Senior Product Designer specialized in product research.
Help me define a clear research problem and scope for a digital product.
Product context:
[Describe product, industry, users, maturity]
Business goals:
[What the business wants to achieve]
Signals or issues detected:
[Data, feedback, metrics, assumptions]
Define:
Research problem statement
Current assumptions
Risks of not doing research
What should NOT be researched now
Expected research outcomes for product design
Research plan
Act as a Product Design Lead and create an actionable Research Plan.
Context:
[Product, team, deadlines, constraints]
Include:
- Research objectives
- Research questions
- Recommended methods
- Method justification
- High-level timeline
- Risks and mitigations
- How insights will inform design decisions
Research method selection
Act as an expert in UX Research for Product Design.
Product context:
[Brief description]
Product stage:
[Discovery, MVP, Growth, Redesign]
Recommend:
- Most suitable research methods
- Questions each method answers
- Methods to avoid and why
- Expected reliability
- Bias risks and mitigation strategies
User interview guide
Act as a Senior Product Designer focused on qualitative research.
Context:
[Product, user profile, problem space]
Create a user interview guide including:
- Interview objectives
- Warm-up questions
- Behavioral questions
- Motivations and pain points
- Observation signals
- Questions to avoid
- How to connect insights to design decisions
Stakeholder research
Act as a Product Designer facilitating stakeholder research.
Organizational context:
[Team, roles, design maturity]
Provide:
- Stakeholder research objectives
- Key questions per role
- Common assumptions to validate
- How to turn inputs into research hypotheses
- Internal bias risks and how to manage them
Stakeholder research
Act as a Product Designer focused on hypothesis-driven design.
Product context:
[What we know so far]
Help me:
- Formulate clear, testable hypotheses
- Link hypotheses to product metrics
- Define validation criteria
- Prioritize hypotheses by risk and impact
- Prepare for future experimentation
Research synthesis
Act as a Senior Product Designer specialized in research synthesis.
Context:
[Methods used, type of data]
Structure:
- Insight clustering
- Behavioral patterns
- Unmet needs
- User–business tensions
- Actionable insights for design
- What is NOT an insight
Research synthesis
Act as a strategic Product Designer.
Research context:
[Key findings summary]
Help me:
- Translate insights into design opportunities
- Write opportunity statements
- Evaluate user vs business impact
- Identify quick wins vs strategic bets
- Prepare for ideation and concept design
Design Decision Log
Act as a Senior Product Designer responsible for design decision traceability.
Product context:
[Product, industry, team]
Decision:
[What was decided]
Alternatives considered:
[Real options evaluated]
Create a Design Decision document including:
- Context and problem
- Options and trade-offs
- Final decision and rationale
- UX, business and technical impact
- Risks assumed
- Signals to revisit the decision
- Date, owners and status
Reject design decision documentation
Act as a Senior Product Designer documenting rejected options.
Generate a document including:
- Rejected options
- Reasons for rejection
- Risks avoided
- Scenarios for future reconsideration
- Signals that would trigger review
Lightweight decision documentation for agile teams
Act as a Product Designer working in an agile environment.
Define a lightweight design decision format that:
- Is easy to maintain
- Prevents reopening past decisions
- Is understandable by non-designers
Include:
- Document structure
- Recommended level of detail
- When to document vs not
- How to link decisions to epics, tickets or releases
Design rationale document
Act as a Product Designer explaining complex decisions to stakeholders.
Create a Design Rationale document explaining:
- Problem being solved
- Supporting insights
- Applied design principles
- Accepted trade-offs
- Why this solution fits the current context
Design decision impact document
Act as a Product Designer focused on impact and metrics.
Document:
- Expected UX impact
- Business impact
- Technical impact
- Related metrics
- Linked hypotheses
- Success and failure criteria
Documentation for handoff and continuity
Act as a Product Designer ensuring long-term product continuity.
Create documentation that:
Explains past decisions without oral context
Reduces dependency on individuals
Include:
- Key decisions summary
- Underlying principles
- Known limitations
- Explicit design debt
- What should not be changed lightly
Design-Product-Tech alignment document
Act as a Product Designer facilitating cross-functional alignment.
Create a document that:
- Explains design decisions in shared language
- Connects design to product goals
- Clarifies technical implications
Include:
- Key decisions
- Shared assumptions
- Known risks
- Technical dependencies
- Open points for future iterations
Create a button component from scratch
Act as a Product Designer and Design System Manager.
Product context:
[Product, platform, maturity]
Design a button component considering:
- Action hierarchy
- Sizes
- States
- Variants
- Accessibility (WCAG, contrast, focus)
- Responsive behavior
- When NOT to use this button
Return it in a Design System–ready format.
Variants and states definition
Act as a Product Designer specialized in component systems.
Define:
- Functional and visual variants
- Mandatory and optional states
- Accessibility states
- Combination rules
- System consistency impact
Component documentation
Act as a Design System Manager documenting a component.
Include:
- Purpose
- Usage guidelines
- Do / Don’t
- Anatomy
- Variants and states
- Accessibility rules
- Tokens
- Developer notes
Accesibility for components
Act as an accessibility-focused Product Designer.
Define:
- Applicable WCAG requirements
- Contrast per state
- Touch target size
- Focus behavior
- Keyboard and screen reader support
- Common pitfalls
Tokens and component properties
Act as a token-driven Design System Manager.
Define:
- Color tokens
- Spacing tokens
- Typography tokens
- Motion tokens
- Locked tokens
- Scalability considerations
Design-to-development handoff
Act as a Product Designer supporting developer handoff.
Include:
- Props and variants
- Controlled vs uncontrolled states
- Behavior rules
- Edge cases
- Dependencies
- Non-negotiable decisions
Component QA checklist
Act as a Product Designer performing component QA.
Create a checklist covering:
- Visual accuracy
- States completeness
- Accessibility
- Responsiveness
- Design System consistency
- Edge cases
Component evaluation and versioning
Act as a Design System Manager managing component evolution.
Define:
- Changes in new version
- Impact analysis
- Backward compatibility strategy
- Communication plan
- Deprecation criteria
Advanced accesibility audit
Act as a Senior Product Designer specialized in WCAG 2.2 AA and AAA.
Conduct an advanced accessibility audit covering:
- Failed AA criteria
- Failed AAA criteria
- Impact by disability type
- Severity
- Actionable design recommendations
- Steps to move from AA to AAA
- Legal and reputational risks
Cognitive accesbility (AAA)
Act as a Product Designer focused on cognitive accessibility.
Evaluate:
- Cognitive load
- Pattern consistency
- Language clarity
- Error prevention and recovery
Propose AAA-aligned design improvements.
Color and contrast accesibility
Act as a color and accessibility expert.
Evaluate:
- Text contrast (AA / AAA)
- Component contrast
- Non-color alternatives
- Provide brand-compatible recommendations.
Deliver rules and validation checklist
Interactive component accesibility
Act as a Product Designer specializing in accessible components.
Evaluate:
- Keyboard navigation
- Focus management
- Accessible states
- Error messaging
Deliver rules and validation checklists.
Accesible forms in critical context
Act as a Product Designer specializing in accessible forms.
Design forms meeting:
- WCAG AA minimum
- WCAG AAA where feasible
Accesibility in Design System
Act as a Design System Manager focused on advanced accessibility.
Define:
- Accessibility principles
- AA requirements
- AAA recommendations
- Regression prevention strategies
Accesibility documentation
Act as a Product Designer documenting accessibility for teams.
Provide:
- What AA / AAA compliance means for the product
- Design decisions
- Known limitations
- Release checklist
What to keep exploring?
Discover other areas of the Product AI Hub and dive deeper into resources, guides and content designed to apply AI with strong product design criteria.
