◆ Figma

Gather stakeholder feedback

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCollect feedback on the new settings page from Priya in product, Alex in customer success, and…+
Collect feedback on the new settings page from Priya in product, Alex in customer success, and Omar in legal by Tuesday. Share the annotated prototype link, ask each to flag must-fix, nice-to-have, and blocked items, and tell them I will collate responses and propose a prioritized list on Wednesday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I send the prototype link, make it easy for stakeholders to respond: surface the three…+
Before I send the prototype link, make it easy for stakeholders to respond: surface the three biggest user risks at the top, include a one-sentence guideline for how to grade feedback (must-fix / nice-to-have / blocked), and add a suggested priority for each known issue so reviewers can agree or disagree instead of starting from scratch.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI sent the settings prototype two days ago and only vague comments returned from Priya and…+
Only vague comments came back from stakeholders
I sent the settings prototype two days ago and only vague comments returned from Priya and Alex. I am the designer; the stakeholders are busy. I don’t know if they skimmed, deferred, or don’t understand the proposal. What’s the most likely reason and the fastest way to get actionable input before Thursday?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternFeedback keeps arriving late and in long threads that bury priorities. I manage stakeholder…+
Feedback arrives late and undifferentiated
Feedback keeps arriving late and in long threads that bury priorities. I manage stakeholder reviews for product and CS. Which process or habit change will make reviewers give timely, graded feedback and how do I implement it so the team treats the reviews as decision points?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Figma's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.