Nice article!
As most designers know, the more creative and forward-thinking the vision, the greater the chances of failing along the way. Thus, the really great designers not only accept, but celebrate failure as an essential part of the design process.
These lines really resonate. Embracing failure – and the uncomfortable – shifts us from a fixed mindset to a growth mindset.
I totally agree that great design depends on a growth mindset. It’s not about winning – it’s about learning and adapting. If we choose to focus only on what worked yesterday and what fits with our current way of thinking, we’re going to fall into the path fixation trap.
Individuals with a growth mindset tend to achieve more than those with a more fixed mindset because they worry less about looking smart and they put more energy into learning. They thrive on challenge and see failure as an opportunity for learning and stretching existing abilities, rather than evidence of unintelligence.
Absolutely this! That’s why research matters. We want to learn more about the environment in which our business and customers operate and how the conditions constantly change. I think this is where the term “validation” often misleads teams: it’s often treated as a checkbox exercise and even as a means to prove a pre-existing hypothesis or belief.
“We’ve tested with 5 users, job done. That will make Jakob happy. Awesome! Move on.”
“Outcomes X, Y, and Z validate our hypothesis, but let’s not review A, B, and C (because we don’t want to deviate from our current thinking).”
What we need to focus more on is invalidation, or a term that often sticks: falsification. Here, we don’t aim to verify hypotheses, but constantly seek evidence to prove a claim or idea wrong. And that happens by continuously exploring the terrain to find problems, which we can then turn into opportunities.
I think this is why AI technologies are causing so many issues for teams. It’s turned all the rituals upside down, and those who get it see the problems of using it and not using it.
Yep, we’re seeing lots of teams fall into AI-path fixation traps. When progress feels so good, they become too complacent in their abilities, and that’s when they forget, ignore, or overlook the opportunities to pause. In other words, vibe coding – vibe anything – needs some kind of pit stops.