◆ Google Looker

Define product requirements based on market research

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 taskPull the sales data for our new 'Zenith' product line from the last quarter, broken down by…+
Pull the sales data for our new 'Zenith' product line from the last quarter, broken down by region and customer segment, so I can prepare the product requirements document for the next iteration by 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 finalize these product requirements for the 'Nova' speaker, analyze user feedback from…+
Before I finalize these product requirements for the 'Nova' speaker, analyze user feedback from the last six months, specifically looking for recurring complaints about battery life and connectivity, and suggest three actionable improvements that directly address those pain points.
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 engineering lead just pushed back on a key feature for the new app, citing technical…+
The engineering lead just pushed back on a key feature for the new app, citing technical complexity and resource constraints.
The engineering lead just pushed back on a key feature for the new app, citing technical complexity and resource constraints. I'm afraid if we cut it, we'll lose a critical competitive edge, but I also can't risk delaying the launch. What's the best way to quickly assess the market impact of dropping this feature versus the cost of delaying, and how should I present this to both engineering and product leadership?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle to get engineering buy-in for new product features, leading to delays…+
I consistently struggle to get engineering buy-in for new product features, leading to delays and rework.
I consistently struggle to get engineering buy-in for new product features, leading to delays and rework. I need to change how I define requirements. What's the most effective habit I can build to ensure my product requirements are always grounded in technical feasibility and resource availability, fostering better collaboration with the engineering team from the start?
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 Google Looker'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.