Advanced
meesh@meesh
3/16/2023

Have been meeting lots of product designers at highly funded + successful companies who don't do any (Figma) prototyping, but just create mocks 🤔 How the heck does this work? As product designers, it's our job to come up with solutions to problems + prototyping is key to defining the UX…

In reply to @meesh
meesh@meesh
3/16/2023

Curious about your thoughts on this, @nonlinear

In reply to @meesh
Mac Budkowski@macbudkowski
3/17/2023

Maybe they have a graphic design background (instead of UX/product) and that's why they start from the thing they feel the most comfortable with?

In reply to @meesh
3/17/2023

I remember in different banks I’d worked in, UX almost wasn’t a thing. Just a PM working with an engineer to get screen mock-ups Other places the UX team was had as many researchers as we had engineers Very polarizing cultures

In reply to @meesh
3/17/2023

You can “test” mocks even if they don’t make a standalone prototype. I personally wouldn’t skip it, but linking screens in Figma isn’t a necessary step

In reply to @meesh
Brent Fitzgerald@bf
3/17/2023

A lot of key stuff we use today got designed and built just fine before figma existed. Even paper prototypes can go a long way in user testing.

In reply to @meesh
welter.eth@fun
3/17/2023

it's low fidelity mockups on a whiteboard, detail should only come in for ui, not ux

In reply to @meesh
Brandon@saasdon
3/17/2023

Huge borders, two colours max, real content. Best way to make the most important design decisions imo

In reply to @meesh
veekay ⌐◨-◨@veekay
3/17/2023

a surprising number of teams get away with designing on the whim while coding 😭😭 mocks is still okay.

In reply to @meesh
Elie Munsi@mme
3/17/2023

Baffels me as well