◆ Figma

Create Impact Effort Matrix template

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 taskBuild an Impact Effort Matrix template with four quadrants: High Impact/Low Effort, High…+
Build an Impact Effort Matrix template with four quadrants: High Impact/Low Effort, High Impact/High Effort, Low Impact/Low Effort, and Low Impact/High Effort. Make sure it's easy to add sticky notes and move them between quadrants. Name it 'Q3 Feature Prioritization'.
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 share this Impact Effort Matrix with the product team, make it easier to use in our…+
Before I share this Impact Effort Matrix with the product team, make it easier to use in our weekly sync. Add a section for 'Assumptions' and 'Key Decisions' at the bottom, and ensure the quadrants are clearly labeled for presentation on a shared screen. Add a legend for different colored sticky notes.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe product owner just rejected the Q3 feature prioritization matrix, arguing it misses market…+
The product owner just pushed back hard on our Q3 feature prioritization, saying the matrix doesn't reflect the real market urgency.
The product owner just rejected the Q3 feature prioritization matrix, arguing it misses market urgency. I'm afraid to push back, but I also know the engineering team is already stretched thin. I can't tell him our current estimates are already optimistic. What's the likely diagnosis here, and what's my best next move to get this back on track without over-promising?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly losing an hour in prioritization meetings because the team can't agree on what…+
I keep losing time in prioritization meetings because the team can't agree on impact or effort scores.
I'm constantly losing an hour in prioritization meetings because the team can't agree on what 'high impact' or 'low effort' even means. Everyone's definition is different. What habit should I change in how I prepare or facilitate these sessions to get to consensus faster and make our matrices actually useful?
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.