"If you weren't here to walk me through it, I would have dropped off already."
Amanda Pun · Series A PM
"What I find a bit problematic is that it's very open-ended. It obviously cannot do everything. But I'm not sure what I can try, what I cannot try."
Pier · Software engineer, Google
"I'm taking it at face value so my expectations are super high. You need to make sure you don't disappoint me if you don't set expectations from the get go."
Jon Reynolds · co-founder, Swiftkey
"The prompt helper is genius."
Marie Brayer · semi-technical VC
"I did not modify the new prompt because I was scared to break anything."
Lucas · technical founder
"I didn't know what to do tbh, so I was just checking out the changelogs."
Adnann · designer
"The main goal is to get things done — we'll worry about the quality later."
Keshvi R. · Head of Product, Balderton
"I tried an example because I don't know what you can do."
Lucas · technical founder
"Oh I didn't know I could click on this node to see the code. That's pretty cool."
Justin · product analyst
"For the first time today, I did use CW and it saved me 30 minutes in my day."
anonymous
Each one designed to be wrong.
↑ 1 of 8
From the Product Design Hypotheses doc · authored by the Agemo team, structured by Joyus.
"The tool seems powerful but it is lacking the integration into the user's workflow. The recurring themes revolve around usability ('what can I do?') and guidance ('what should I do?')."