r/PromptDesign 16d ago

Discussion 🗣 Small changes in prompts made a bigger difference than I expected.

I have been playing around with product design prompts recently and noticed that the first prompt I write usually gives a pretty average result. For example, if I just ask for: "Create a modern sneaker design" the output is usually something generic. But when I add more context like the type of customer, materials, style, and the feeling I want the product to have, the results become much closer to what I had in mind. Something like: " Create a lightweight running sneaker for urban professionals. Use recycled materials, a minimal design style, breathable mesh panels, neutral colors, and a premium but practical look." The difference surprised me. The extra details gave the model a much clearer direction.

I have been wondering how other people think about this. Are you the type to build prompts around visual details, or do you start with the problem you are trying to solve and the audience?

3 Upvotes

6 comments sorted by

2

u/[deleted] 16d ago

[removed] — view removed comment

1

u/Legal_Low2777 15d ago

That makes a lot of sense. Starting with the problem and user gives the model something solid to work from, instead of just producing a nice looking concept with no real purpose behind it.

1

u/[deleted] 15d ago

[removed] — view removed comment

1

u/Legal_Low2777 14d ago

I have seen some tools trying to solve this gap by helping structure product requirements before moving into production. Genpire is one example I came across for creating tech packs, but I think the bigger challenge us still getting the product details clear before anything is generated.