Discovery effort should match solution risk

Not all solutions need a lot of discovery. That's a common misunderstanding, I think.

"These" refers to open coding traces - analyzing AI conversation logs and writing notes about failures or issues observed.

We recommend doing at least 100 of these. Keep looking at traces until you feel like you're not learning anything new.

18 months ago, you would get a short story and it would say, 'Is this short story better than this short story?' And now you're at a point where one task is building an entire website by one of the world's best web developers, or it is explaining some very nuanced topic on cancer to a model. These tasks now take hours of time and they require PhDs and professionals.

Being inspired by some aspects of what your competition is doing in their experience is a wonderful place to originate an ideation or potentially try to implement into your product as well. But blatantly saying, 'Hey, we're going to copy all of these best tactics or all of these flows because, hey, they're doing better than us. Let's just rip them and do exactly the same' - that's where things really go wrong.