There is a couple, Stakeholder and Designer. Previously, they have a wonderful and lovely relationship. But recently, the Designer feels that their relationship isn’t going well anymore. She doesn’t happy about Stakeholder’s treatment to her.
Doesn’t want to lose her, Stakeholder makes a promise that he will change to a better person. Impressed with his gesture, the Designer forgave him.
Time passed, but he still repeating his mistake. Again, the woman still forgiving him, and keep swirling to the toxic relationship. She was blinded by deception.
That story may be a little bit exaggerated, but we can take a lesson from it. Don’t be a blinded designer. What is that?
Blinded designer from my perspective was,
a designer that blinded by their own designs and all its tricks.
They keep making design but they don’t know whether their design was worked or not, pretended to be okay. This is dangerous, it can make the product failure.
Design without guidance
Sometimes stakeholders want to create a feature/product without strengthened with good data, even though data is important as a reference to what we do next to solve the user’s pain. Not only that, after design execution, they also don’t provide the result metrics of our solution. Is it a success or a failure?
We don’t know the objectives or goals of the features
This related to the previous point, sometimes we don’t curious enough to ask about features that we design, we just received the request and done it. Without asking the purpose of the feature. Is it needed by the users? Is it impactful to them? No, we think ourselves as labor, do whatever was told by stakeholders.
Overconfidence
Although this is rarely happening, sometimes designers were overconfident about their design. It was implemented directly without testing it to users first, what happens next is users leave the application because it was hard to use.