Robots don’t listen to us yet.
Not in plain English, anyway. You still get joysticks, rigid scripts, or a mountain of documentation between you and telling a robot “grab that mug.” This Redditor, a researcher working with a team called Peppy, wants to close that gap. They’re asking the r/PromptEngineering crowd to help build it.
The post itself is simple: if you could hand a robot a task in plain English today, what’s the first thing you’d ask it to do? No demo video, no GitHub repo, no slick landing page. Just a question, posted straight to a community that already thinks in prompts for a living.
Plenty of teams are chasing this same problem now. Warehouse robots, humanoid prototypes, home assistants, all of them racing to turn natural language into motion. Most of those projects show up already finished, asking you to be impressed. This one showed up asking you to help decide what “finished” should even look like. That’s a meaningfully different pitch, and it’s worth paying attention to why.
The Twist
This isn’t a finished tool showcase at all. It’s the opposite: a company doing real user research before writing a line of the interface. Peppy is running a short 10-minute survey to map out how people actually picture talking to a robot. Anyone who finishes it gets a $20 Amazon gift card for their trouble. One commenter, u/acebase19, summed up the room’s reaction in a single word: “interested.” Honestly, same!
That matters more than it sounds. Most AI-robotics demos start with the robot and work backward to find a use case. This approach starts with your mental model, the actual commands you’d type or say, and lets that shape the product. If you’ve ever used a chatbot that clearly wasn’t built around how real people talk, you know why that order matters.
There’s a bigger lesson buried in here for anyone building AI products, not just robotics. Skip the survey and you end up guessing at prompts users will actually type. Run the survey first and you build the interface around real language instead of the language you assumed people would use.
How I’d Prompt That Robot
So let’s actually run the exercise. Here’s the mini-workflow I’d use if I were answering that survey myself:
- 🎯 Pick a task you do on autopilot. Something boring beats something flashy, “sort the mail” tells the platform more than “explore Mars.”
- Write the command exactly how you’d say it out loud. Don’t clean it up for a resume. “Grab the blue mug off the counter, not the chipped one” is more useful data than “retrieve beverage container.”
- ⚠️ Add the constraint that would actually break a dumb robot. Edge cases are where plain-English prompting earns its keep, so mention the thing that’s easy to get wrong.
- Describe what success looks like in one sentence. Not “task complete,” but what you’d actually check to know it worked.
- Note what you’d want it to ask you if it’s unsure. Good prompting isn’t one-shot, it’s a conversation, and a robot that asks a clarifying question beats one that guesses wrong.
Run through those five and you’ve basically written a mini prompt-engineering spec for a robot. That’s exactly the kind of raw material a team like Peppy needs before they lock in a design.
Pro Tips
Treat this survey the way you’d treat writing a system prompt. Specificity beats cleverness every time. “Water the plant on the left, skip if the soil’s still damp” gives a product team ten times more signal than “make it smart.” If you already write prompts for a living, you’re sitting on exactly the skill this research needs.
Keep a running note of tasks you wish a machine would just handle. Next time a survey like this lands in your feed, you won’t be starting from zero, you’ll have a backlog ready to go.
It costs you ten minutes, but it turns you from someone reacting to AI products into someone shaping them before launch.
One more thing worth noting: the original poster mentioned they’re happy to share more about the research, not just collect answers and vanish. That kind of back-and-forth is rare for an early-stage survey. It’s usually a sign the team is actually listening, not just checking a box for the roadmap.
If early access to robot control even mildly interests you, this is about as low-friction as it gets. Ten minutes, a gift card, and your actual voice baked into how the product turns out. Drop a comment on the original thread or DM the poster directly to get the survey. 🤖🎁 Worth it, honestly!
Building an AI platform that lets you prompt a robot in plain English. What would you have it do?
by u/HangingWithCyn in PromptEngineering