Be nice. Or else.
Denver, CO Independent designer, studiofellow.com Joined about 4 years ago
Design systems aren't replacing design jobs. They're actually causing a bubble of design jobs because they take more work to maintain.
Thanks! I think it’s important to share stories like this because we tend to assume it’s easy for everyone else.
Communicating the value of UX can be tricky for some clients, because they are suspicious the designer is just adding bloat to the project to raise fees. They want the final result, but don't understand that UX methods are key to getting there.
For them, I find the best way to teach this is to connect the process to the outcome. Doing user research will help you improve your conversion rate, or user testing will help you find which areas of the app need better onboarding to reduce your churn. Etc.
Other clients don't even care about metrics, as bizarre as that sounds. They're purely just trying to buy a nice design or hire a designer to bring their vision to life. In those cases, UX is a tougher sell but it's still doable if you don't call it UX—I just use these techniques as part of my process without adding extra phases or fees. It's just part of what I do. Avoiding that conversation can help with these kinds of clients.
This is great advice. The title is controversial, but he makes valid points.
How many times have we celebrated that story of Paula Scher scribbling the citi logo on a napkin? Even still it's pretty rare to find a designer who's so confident in an early concept. Instead we hang 100 sketches on a wall and show how many versions we produce before finding the final concept. It looks important, but it's not always necessary or even good work.
As a designer it's easy to miss the forest for the trees, and I appreciate being reminded. Thanks Pablo
This is really cool. Getting into web development is frighteningly complex, and we need more efforts like this to make it less intimidating.
Depending on how want to you do it, you might look up the design term "gradual engagement". (It applies to all kinds of use flows, not just signup, but I think the most common example is signups.) The idea is that you allow users to engage with the app and start using it before actually adding their account info and signing up. It works by essentially creating anonymous users, that then get populated with account data gradually as people use the app.
Here's an old example from Twitter, although it includes a password, the password could be moved later in the flow.
Obviously there's also Oauth (Sign in with your google account / twitter/ facebook / github / etc).
I've also seen developer docs about letting people sign in/up with just their phone number. I haven't found a good example of this yet, but Google's Firebase provides built in support for it.
Thanks for checking it out!
You're totally right. I removed the work "ugly", didn't intend it to be insulting. Edited article here.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.