# Great quote that I found reading an article around product biases and laziness **URL:** \ **Category:** Open topics\ **Tags:** quotes, ai, product\ **Created:** [July 31, 2025, 5:45pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146 "2025-07-31T17:45:04Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![ben](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/ben/32/442_2.png) [@ben](https://forum.zurb.com/u/ben)\ **Post date:** [July 31, 2025, 5:45pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/1 "2025-07-31T17:45:04Z")
“Our brain is lazy by nature, and if your product offers several ways to achieve the same goal, people will use the shorter and simpler one. Don’t make it hard for your users with complicated flows, long forms, and exhausting interfaces. They use your product to get a job done, help them do it seamlessly and don’t make them think too much. Don’t be afraid of adding “additional clicks” — sometimes it’s better to break a long flow to bite sized, scannable chunks of information.” - [Katrin Zotchev](https://medium.com/@katrinzot) Her article is here: [10 biases to be aware of when building products | by Katrin Zotchev | UX Collective](https://uxdesign.cc/10-biases-to-be-aware-of-when-building-products-cb5245fb7776) It seems that in a B2B sense, converting features to be this simple is quite tricky 90% of the time. I’m also starting to sense how AI tools can actually start to fill this gap. Does anyone else feel the same way? ---
**Author:** ![nathaliesmith](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/nathaliesmith/32/443_2.png) [@nathaliesmith](https://forum.zurb.com/u/nathaliesmith)\ **Post date:** [July 31, 2025, 6:08pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/2 "2025-07-31T18:08:24Z")
> [@ben](#): > > “Our brain is lazy by nature, and if your product offers several ways to achieve the same goal, people will use the shorter and simpler one. Don’t make it hard for your users with complicated flows, long forms, and exhausting interfaces. They use your product to get a job done, help them do it seamlessly and don’t make them think too much. Don’t be afraid of adding “additional clicks” — sometimes it’s better to break a long flow to bite sized, scannable chunks of information.” > > It seems that in a B2B sense, converting features to be this simple is quite tricky 90% of the time. I’m also starting to sense how AI tools can actually start to fill this gap. Totally agree with this. People just want to get stuff done. But I’m starting to notice how AI might actually help here. Instead of users clicking through 10 steps, we can start building smarter experiences that handle the messy parts behind the scenes. It’s not about fewer clicks, it’s about fewer decisions. Kinda exciting to think about where that could go. ---
**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\ **Post date:** [August 1, 2025, 1:17am UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/3 "2025-08-01T01:17:04Z")
I’ve found that concept testing with interfaces can be super valuable in arriving at a more straightforward answer. We’re wired to react to things using our immediate feelings, then our memory. I wrote about this a while ago. This is science! > **[Concept testing reveals patterns that make a product feel intuitive. | Bryan...](https://www.linkedin.com/posts/bryanzmijewski_productdesign-productmanagement-productdiscovery-activity-7153450668769333250-d7qd)** > > Concept testing reveals patterns that make a product feel intuitive. > > I've been keeping up with Rebecca Grier, Ph.D.'s posts, and trying to understand how they apply to high-volume concept testing during customer discovery. It's fascinating material.... ![concept-testing-and-human-cognition](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/3a557e7b37b73594563df895324c311477d8b735.png) ---
**Author:** ![Doug\_Curtis](https://avatars.discourse-cdn.com/v4/letter/d/e47c2d/32.png) [@Doug\_Curtis](https://forum.zurb.com/u/Doug_Curtis)\ **Post date:** [August 8, 2025, 6:45pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/4 "2025-08-08T18:45:54Z")
This is a really great article! AI feels like gasoline on a fire here. On one hand it could be super powerful, your prompting and configuration of Claude or ChatGPT could be programmed to always look for this in your planning docs (like a personal blindspot detector). On the other hand, features can be built super fast now. But if you didn’t do your homework on the users problem all of these could be amplified in the finished product. One example is “vibe coding”, the anchoring effect comes in right off the bat if you show a half baked idea to other stakeholders on your team. The conversation gravitates to nitpicking the details rather than zooming out on the user’s problem (been there done that 😉 ) ---
**Author:** ![ben](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/ben/32/442_2.png) [@ben](https://forum.zurb.com/u/ben)\ **Post date:** [August 9, 2025, 8:29pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/5 "2025-08-09T20:29:14Z")
That’s what I’ve been hearing as well. It seems that it all falls back down to “solving the right problems in the right way”. > [@Doug\_Curtis](#): > > the anchoring effect comes in right off the bat if you show a half baked idea to other stakeholders on your team. The conversation gravitates to nitpicking the details rather than zooming out on the user’s problem This is a super important detail that I forget frequently- a very good callout that the vide-coded prototypes could actually lead us in the wrong direction! Knowing what to truly do and why feels insurmountable. ---
**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\ **Post date:** [August 10, 2025, 8:20pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/6 "2025-08-10T20:20:16Z")
> [@Doug\_Curtis](#): > > On the other hand, features can be built super fast now. But if you didn’t do your homework on the users problem all of these could be amplified in the finished product. Absolutely Doug. This is where UX metrics can work at the speed of the build, giving stronger signals on those needs. > **[You don’t need more research. | Bryan Zmijewski](https://www.linkedin.com/feed/update/urn:li:activity:7360337430584942594/)** > > You don’t need more research. > > It might sound counterintuitive, but the real win is turning scattered insights into decisions that move things forward. > > UX metrics drive decisions when it counts. > > You’ve probably heard of lean (move fast with less... ![stronger-design-decisions](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/84a6b1b4dc7960df5f56cfd2a0834efb83249711.png) ---
**Author:** ![Doug\_Curtis](https://avatars.discourse-cdn.com/v4/letter/d/e47c2d/32.png) [@Doug\_Curtis](https://forum.zurb.com/u/Doug_Curtis)\ **Post date:** [August 11, 2025, 2:09am UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/7 "2025-08-11T02:09:12Z")
> [@ben](#): > > Knowing what to truly do and why feels insurmountable. 100% that solving the right problem is critical, IMO that rests squarely on the product manager’s shoulders. But once you identify it, the rest of the implementation details sort of fall into place a lot easier if it really is the right problem. Looking back on my own experience where projects excelled and when they floundered, it really all came down to the problem. User feedback signal is clear, team is aligned, it’s great! > [@Bryan](#): > > Absolutely Doug. This is where UX metrics can work at the speed of the build, giving stronger signals on those needs. I’m curious how you think of UX metrics and any causation/correlation between the quality of the problem statement (confidence the target user actually has the problem) ---
**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\ **Post date:** [August 11, 2025, 2:46pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/8 "2025-08-11T14:46:36Z")
> [@Doug\_Curtis](#): > > I’m curious how you think of UX metrics and any causation/correlation between the quality of the problem statement (confidence the target user actually has the problem) If you start with a well-defined problem statement, UX metrics will likely show strong, consistent signals that users value the change. - **If that statement is weak or wrong** → UX metrics will show weak, inconsistent, or no improvement, signaling that the problem might not exist or isn’t worth solving. - **Feedback loop** → Metrics confirm or challenge the problem statement, helping you refine it before you waste time building the wrong thing. So, in a design stack, UX metrics can reveal a new problem or indicate where the problem isn’t well-defined. ![kleen-kanteen-competitive-review](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/f87d94994632b69dc22cfb2d9454e9db667047bc.png) In this example, there were two areas that showed specific problems with Kleen’s website. ---
**Author:** ![Doug\_Curtis](https://avatars.discourse-cdn.com/v4/letter/d/e47c2d/32.png) [@Doug\_Curtis](https://forum.zurb.com/u/Doug_Curtis)\ **Post date:** [August 11, 2025, 8:50pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/9 "2025-08-11T20:50:59Z")
yes! love that! When you are doing UX testing on a design do you separate the cohorts of users as “test users” and “production users”? If so, I would imagine the “test users” would be directed to accomplish something and the “production users” are not. Sorry if these are noob questions 🙂 I don’t have any experience in UX testing specifically. My background is more from the PM view tracking product analytics with production users. I find it really interesting how these two sets of metrics are interrelated. ---
**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\ **Post date:** [August 11, 2025, 9:06pm UTC](https://forum.zurb.com/t/great-quote-that-i-found-reading-an-article-around-product-biases-and-laziness/146/10 "2025-08-11T21:06:33Z")
We mostly use test users as a proxy, as they tend to be great for finding problems the fastest. ![image](https://canada1.discourse-cdn.com/flex034/uploads/helio/original/1X/41525588e7d664f555c91063a6c1d31a581caddc.png) Ultimately we’re aligning the product analytics (product outcomes) with the user outcomes to create better business outcomes.