◆ Figma

Share prototypes with stakeholders

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 taskSend the prototype link for the checkout flow to Priya in procurement and to Omar in customer…+
Send the prototype link for the checkout flow to Priya in procurement and to Omar in customer success for review. Give them view comments access, include a note asking them to review the payment UI and copy by Thursday, and ensure the link opens to the desktop breakpoint by default. Confirm they can see the micro‑interactions before Friday.
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 circulate this prototype to stakeholders, make it frictionless to approve. Put the…+
Before I circulate this prototype to stakeholders, make it frictionless to approve. Put the acceptance criteria at the top of the prototype, set the default open screen to the critical flow, enable comment highlights so reviewers can jump to unresolved notes, and include a short checklist that tells reviewers what to verify and how to mark approval.
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 shared the checkout prototype with procurement and got back a comment: 'looks odd' on the…+
Stakeholders left vague comments
I shared the checkout prototype with procurement and got back a comment: 'looks odd' on the promo step, which doesn’t tell me what to change. The deadline for a pilot is three days away and I can’t chase every vague reviewer. What’s the best way to get specific, actionable feedback quickly so I can ship the checkout without endless back‑and‑forth?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternPrototype reviews routinely take multiple rounds of vague feedback from stakeholders, delaying…+
Prototype reviews drag on and stall launches
Prototype reviews routinely take multiple rounds of vague feedback from stakeholders, delaying launches and making engineering wait. I need to shorten review cycles and get decisive approvals. What changes to how I share prototypes and to the review process will make stakeholder feedback specific and approvals timely?
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.