User Researchers don’t need a full evals setup at the start of a project. 20 to 30 real real proof of concept is a good start. The goal is to check whether your definition of “good” matches what users actually care about. Build the harness once you trust the criteria.
so vision wears a suit and literally walks out of his make-believe house only to wake up in real life as a robot then appears at the location in a winter jacket.
A power user topping the leaderboard of an app that I built couldn’t find a feature I thought was obvious. The testers had sailed through it. He couldn’t. What happened to me is called The Illusion of Transparency.
I wrote about it; quadmor.design/articles/the-…
you built or designed the product, so you’d definitely have an obvious bias on the complexity of the product.
Shoe Dog by Phil Knight has been a very interesting read. the journey of every start up is always a wiggly line



