Be nice. Or else.
Product Designer at Grubhub Joined over 4 years ago
Great breakdown. There's a case for more asynchronous communication when it comes to just about everything work-related – the hardest part is getting people to buy in and believe that real-time communication isn't the only kind.
100% - if tools that create new models that level up the speed and competency of UI and UX designers, we shouldn't be restricting ourselves to the current model of draw-vectors-on-a-screen.
Why? I'd rather have more badges – or like functionality – to be able to filter to content that I actually want to see.
This kind of whiteboarding exercise is definitely useful, but I'd also be concerned if it were the only – or even the main – determinant in a hiring decision. A discussion on a particular project in a portfolio, references, as well as the portfolio itself should all give some insight into how a designer thinks and communicates.
I say this because while whiteboarding is certainly a primary skill for a product designer, it also favors a very specific kind of design activity and skillset. Plenty of talented designers aren't going to be amazing at this exercise because they do more methodical research, or they prefer being heads-down for a while before collaborating with stakeholders.
UX StackExchange tends towards more objective, fine-grained design issues (typically UI design issues) —if you see the list of recent questions, you'll see things like "pencil icon for create vs. edit."
Playbook positions itself as "actionable career advice," which is not at all what StackExchange provides in my experience. The questions are much more about process, workflows, advice.
So I think the title of this post is a bit of a misnomer. I've found both sites useful, but they're quite different in terms of subject matter.
Super exciting to see tools like this—will check this out ASAP.
Are you aiming for feature parity with Lottie?
I'd recommend Mural for sticky notes and 'whiteboarding lite.' It's super smooth and easy to learn.
I'd also recommend emphasizing the need for advance preparation (honestly, this should be important for any meeting but becomes glaringly obvious with remote teams) and asynchronous updates (not everything has to be done at the same time in the same room—figure out what does and doesn't need real-time collaboration).
Agreed. Thanks for this!
Has there been thought in Framer Studio around statefulness and component libraries? I feel like Figma and Subform are innovating in these areas.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.