Be nice. Or else.
UX Designer @ Bluebeam, Inc. Joined over 4 years ago
Direct access to users is so big. Makes user research such a breeze!
Exactly. Discussing a pain point is not the same as solving that problem. There's a million ways to solve that problem and in there are probably a few ways that people will legitimately pay to solve it.
Pitching and collaborating are not compatible.
This just isn't true. While bad pitching tries to sell a single solution to a perceived problem regardless of if that's actually a problem the client has, good pitching is flexible and has done the legwork to understand exactly what the client is looking for beforehand.
If a client brings up a concern about a design in a meeting you should be able to ask the questions necessary to get to the heart of the matter. If they are bringing up new information you should be able to pivot into a process for addressing a new found requirement and be able to give them a good idea of what addressing that concern might entail. If it's not new then you are failing to solve the clients problem.
The "pitch" is about gaining the trust of a client and the best way to get that is by understanding and addressing their concerns. A bad pitch will always alienate while a good pitch further builds a relationship, it's not at odds with collaboration.
Exactly. Designers tend to be hyper sensitive to these "Trends" because we are immersed in them all the time. Rule of thumb: whenever something has become so "trendy" that designers start to hate it is probably the point when it's starting to first be recognized by the general population.
where they see this fitting into current processes, where the biggest potential is for this, what problems they hope it will solve, etc.
I'd really like to see this automating Design System changes. Currently there's always a bit of a hurdle for designers to jump when handing off "simple" changes to Design Systems because development time for even small changes can be substantial.
I'd like to see control of Typography and Color handed back to UI designers. The devs often don't really care about that stuff and it feels like busy work whenever a change is requested. It'd be great if designers could push these types of things to a repo where a dev just looks over it and makes sure nothing broke.
Most people, unless their jobs are very production oriented, have some level of influence over design. If that's the company's primary product or a backend system, or simply an internal process. A lot don't internalize this as "design" though usually it's thought of as solving a specific problem, which is part of our job to get more people realizing that what they are doing is design.
The more I work in the industry the more I see my job as a "Design facilitator". I need to enable and guide people to make smarter design decisions rather than trying to control all aspects of design (because that's completely unsustainable).
Wow I wasn't expecting Fixed/scrollable objects to be a part of styles release. This is incredible.
Figma is built on the premise that as a designer, we want to work collaboratively. However, in my personal experience and preference (and, correct me if I am wrong here), I would like to complete the whole thing before involving others in the workflow.
That was their original messaging which I still feel was a bit flawed because I too reacted in a similar fashion until I actually tried it out.
I feel like the "multiplayer" aspect is less important as the "persistent single source of truth" aspect. I use it less as a tool to get together and create something but rather as a persistent status update. If stakeholders are curious about how a project is progressing after they've seen an initial draft they can check in whenever they want.
Part of the problem of "complete the whole thing before involving others"is it's anxiety inducing for stakeholders. Yes, I know the common thought is that "stakeholders should trust us to do our job well" but the fact is that it's often not the case. Having the ability to see progress (even if they don't use it) gives them a feeling of control that eases their anxiety and makes happier clients that more quickly trust you to do your job.
Just my thoughts :D.
Not yet. The best solution I've found for this is to make body text scalable with the parent component so that you can resize it if the text is too big.
This is highly requested on spectrum though so I wouldn't be surprised if it's something they are working on.
I've never gone "back" to Sketch, but do occasionally use it because co workers still use it.
I don't know how I'd survive without Figma's robust component/library system. I've amazed myself at how complex and creative I can get with "list" style content with a lot of child components. It feels as close to "atomic design" as it gets for design tools.
Not having to deal with actual files is a lifesaver as well. There's a huge amount of process discussion that happens around files within company servers and it's a pain point my entire team feels. Being able to send someone a single unchanging URL for an entire project is awesome. Cross platform compatibility is awesome as well. I can give someone on a Windows machine a URL and they can use that in another meeting without asking me for a bunch of jpgs for their presentation.
As you mentioned: the Figma team seems to be moving very quickly compared to other tools. They were one of the first to a holistic "team library", their latest API has had some very promising community projects and their upcoming Styles feature is looking good already.
For me it feels like a natural evolution. A while back we all switched from Photoshop/Illustrator mockups to Sketch and I feel strongly that Figma is going to be the next mass transition.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.