Are design systems just a bandaid, Figma tips for UI3, building better logins
Briefly

A community, often an underserved one, is struggling with a problem. A designer sees this, observes them for a short period, comes up with an idea in the studio, and then comes back with a solution to the bewilderment and excitement of the community. The problem that no one has been able to figure out before now is solved! All thanks to the designer! Ok, this story might seem a little exaggerated, but it has long been a documented one... Projects like these often do little to help the communities they target, but instead raise the profile of the designer(s)/agency(ies) that made them. And years later, when the projects go inevitably wrong, the publicity has already been gained, and communities are left with little resources to hold them accountable.
It is not uncommon for someone to message, call, email, or carrier pigeon me to ask if something is accessible. They almost invariably want a 'yes' or 'no' However, I need to understand what the heck they mean and what the other-heck prompted them to ask... Before jumping to conclusions about the accessibility of a project or product, having a conversation about the specific context and needs can come about with far more meaningful insights.
Painful, Slow Research was passionate about slowing down product development, hiding in fragmented tools, hoarding knowledge in silos, and causing unnecessary friction for teams. They're survived by Dovetail, the leading AI-powered customer insights hub that gives everyone on the product team instant access to customer insights, at any time.
Read at Medium
[
|
]