article thumbnail

How to Conduct a Visual Design Audit (And Why You Should)

Design Shack

Improved usability: Visual inconsistencies in UI components (like buttons, forms, or spacing) can make products harder to use. A visual audit ensures your design patterns stay clean and functional. It’s also helpful to involve front-end developers, brand managers, marketing designers, and product managers.

article thumbnail

Stop wireframing (but still start low-fidelity)

UX Collective

Selecting a brand color for interactive patterns is no faster or slower as it is the default blue. Grey Blocking Sometimes, I need to get a WAG (wild-ass guess) on how much space I can / should allocate to patterns. This means that the tools we use to wireframe are *the exact tools we visually design with.*

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Design and Digital Interfaces: A Book About The Hidden Ethics Behind Your Screen

We And The Color

An interface that uses “dark patterns” to trick you into a subscription creates a feeling of distrust and manipulation. For Designers, Developers, and Product Managers: Ask the Hard Questions Early: Before a single line of code is written, ask: Who benefits from this product? Who might be harmed or excluded?

article thumbnail

AI-first?

UX Collective

My product manager has used AI to flesh out wireframes in order to get an idea across, but she’s already done the problem solving in her brain. You could possibly train it on specific company software to recognize patterns and replicate them but that’s very limiting and requires a lot of upfront work.

article thumbnail

The next era of design is intent-driven

UX Collective

Jack Menzel, former Product Management Director atGoogle. Visual hierarchies matching inquiry patterns. The Traditional WayA Maze of Clicks: Imagine youre a product manager trying to understand user behavior. Users werent just looking for links; they were looking for answers and understanding.

article thumbnail

Features shouldn’t feel like features

UX Collective

Both of these are features, of coursea product manager prioritized solving a pain point , a designer conceptualized the idea, an engineer built the functionality into thetool. Look for patterns in behavior that could theoretically be handled by the system, automatically. And both solve the need (to add images to atask).

article thumbnail

The politics of Design Systems

UX Collective

Everyone already has established working patterns and people aren’t usually inclined to change. Product managers have launch dates. But once your system meets the real world, things get complicated. Plus, designers have their opinions. Engineers have priorities. And everyone already has a “good-enough solution”.