Product Designers —Delivery

Act as a senior product designer. From this design backlog: [insert]. Score each item on: User impact (1–5), Effort (1–5), Strategic fit (1–5), Risk if ignored (1–5). Recommend the top 3 to do this quarter. Present as a prioritisation matrix.

Act as a senior product designer. For [insert initiative], sequence the work across 3 phases: foundations (weeks 1–4), build (weeks 4–10), polish (weeks 10–14). For each phase: what we deliver, what unlocks the next phase, what risks emerge. Present as a phase-by-phase plan table.

Act as a design strategist. Based on this product strategy: [insert], propose 5 design bets for the next quarter. For each: the user problem, the design move, the success metric, the risk. Present as a bet sheet.

Act as a senior product designer writing a handoff doc for engineering. For [insert feature], cover: user goal, key flows (linked Figma frames), states (loading, empty, error, success), edge cases, copy, accessibility notes, dependencies. Present as a handoff spec.

Act as a senior product designer. For [insert feature], list the edge cases I'm probably forgetting: empty states, error states, race conditions, slow networks, zero-data scenarios, abuse cases, internationalisation. For each: what could go wrong, what to design. Present as a checklist grouped by category.

Act as a product designer working with a PM. For [insert feature], write acceptance criteria in 'Given/When/Then' format. Cover happy path, edge cases, error handling, and accessibility. Present as a list of criteria ready for the ticket.

Act as a design systems lead. Across [insert product], audit how core components are being used. For each: where it's used correctly, where it's been bent, where it's been recreated locally. Recommend: what to consolidate, what to fix in the system, what to deprecate. Present as an audit table: Component, Correct Use, Bent, Recreated, Action.

Act as a design systems designer. For [insert component], write the documentation: what it is, when to use it, when not to, props/variants, accessibility considerations, common mistakes, code reference. Present as a doc page.

Act as a design systems lead. For this recurring pattern: [insert]. Decide whether it should become a system component. Cover: how often it's used, the variations needed, the cost of building/maintaining, the cost of NOT having it. Present as: Recommendation + rationale.

Act as a growth designer. For this question: [insert]. Design an A/B test: hypothesis, control, variant, success metric, guardrail metrics, sample size or duration, decision rule. Present as a test plan.

Act as a growth analyst working with a designer. [Insert metric] is declining. Decompose: 1) break the metric into inputs, 2) identify which input is moving, 3) propose 5 plausible root causes, 4) suggest the cheapest test for each, 5) name the first thing to investigate.

Act as a senior product designer. Based on these A/B test results: [insert], write a decision memo: what we tested, what won, what surprised us, what changed in our thinking, the next move (ship, iterate, kill). Present as a 1-page memo.

Act as a senior product designer running a quality audit on [insert product area]. Identify: visual inconsistencies, broken interactions, accessibility issues, microcopy that needs work, missing states, performance issues. Severity-rank each. Present as an audit report.

Act as a designer doing a final polish on [insert flow]. Look for: spacing inconsistencies, typography drift, transitions that feel rough, copy that's noisy, friction that could be cut. List 10 specific polish items, ranked by how much they'd improve the feel.

Act as a senior product designer. For [insert team], write a 'Definition of Done' for design work. Cover: visual quality, accessibility, copy review, edge cases, system component usage, handoff completeness, post-launch monitoring. Present as a checklist.

Act as a designer running an accessibility audit on [insert product area]. Cover: keyboard navigation, screen reader support, colour contrast, focus indicators, motion/animation, form labels, error handling. For each issue: severity (A/AA/AAA), location, fix. Present as an audit report.

Act as an inclusive designer. For [insert product], identify 5 edge user groups currently underserved: users in financial difficulty, users in crisis, low-bandwidth users, low-literacy users, users with assistive tech. For each: where the product fails them, the fix. Present as a table: User Group, Where It Fails, Fix.

Act as an ethical product designer. Audit [insert product] for dark patterns or coercive design: forced continuity, hidden costs, friction on cancellation, default opt-ins, manipulative comms. For each: where it occurs, why it's there, the user harm, the fix. Present as an audit.

Act as a product designer working with an analyst. For [insert feature], define the metrics that matter: 2 outcome metrics, 3 input metrics, 1 guardrail. For each: what it measures, target, healthy range, review cadence. Present as a metrics doc.

Act as a UX strategist. Given these analytics: [insert] and these user quotes: [insert], synthesise: where they confirm each other, where they conflict, what the gap suggests. End with 3 design implications.

Act as a growth-minded designer. For [insert flow], set up a funnel diagnosis: every step from entry to outcome, expected drop-off at each, healthy vs concerning rates, what each drop-off would imply for design. Present as a funnel diagnostic.

Act as a senior product designer briefing your PM. For [insert design decision], cover: what we're proposing, what we considered, what we sacrificed, what we'd want to know to be more confident, what would change our minds. Make it short. Present as a Slack-shaped pre-read.

Act as a product designer working with an engineering tech lead. For [insert feature scope], propose 3 versions: full scope, half scope, smallest viable. For each: what's in, what's out, what's the impact on the user value, what we'd commit to ship. Present as 3 scope options.

Act as a senior designer. There's a disagreement on [insert decision] between [insert parties]. Help me: 1) name the underlying tension (interest vs position), 2) identify what data would resolve it, 3) propose a path forward that respects both sides. Present as a resolution memo.

Act as a senior product designer reviewing your own work. For this quarter: [insert key projects]. Cover: what you shipped, what you learned, what's getting easier, what's getting harder, where you're stuck, what to invest in next quarter. Present as a personal quarterly review.

Act as a design hiring manager reviewing this case study: [insert]. Identify: what's strong, what's weak, what's missing (context, decisions, trade-offs, results), what to cut. Give specific, actionable feedback. Present as a critique.

Act as a senior designer coaching yourself. Given these strengths: [insert] and these gaps: [insert], propose 3 skill investments for the next 6 months. For each: what to learn, how to learn it, how you'll know it's working. Present as a 6-month dev plan.

Act as a design lead. For [insert cross-team initiative], plan how to coordinate across [insert N] designers. Cover: shared definitions, design rituals, async vs sync moments, the artefact everyone aligns on, how decisions get made, when you escalate. Present as a coordination plan.

Act as a design manager. Set up a recurring design crit for [insert team, e.g. a 6-person product design team]. Cover: cadence, format, who presents, the rules of the room (no defending, build don't break, named feedback), how it stays useful, what to do when it goes flat. Present as a crit charter.

Act as a head of design for [insert product]. Draft 5–7 design principles that guide the team's decisions. For each: principle, what it's not, an example of it in action, what it lets us say no to. Make them sharp, specific, usable in arguments. Present as a principles doc.