Topic

Dribbble

2 posts about Dribbble. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Intercom
How to hire designers - The Intercom Blog
The post argues that design is fundamentally about how something works, not how it looks, and that hiring based on visual portfolios like Dribbble perpetuates a misunderstanding. The author presents a four-layer design framework: intended outcome, component design, detailed interactions, and visual layer. He asserts that these layers are interdependent and that the best designers excel at one or two while being very good at the others. He advises evaluating candidates against the specific layers needed for the role, noting that a popular Dribbble portfolio only proves graphics software skill and trend awareness, not design ability. The goal is to break the cycle of misunderstanding design education and ensure companies hire designers who can solve real problems.

Intercom
The dribbblisation of design - The Intercom Blog
Paul Adams argues that the Dribbble community rewards superficial aesthetics, moving product design backward. He observes that job applicants often submit pixel-perfect PNGs lacking context, business constraints, or problem definition, focusing on visual polish rather than solving real problems. Strong candidates instead present sketches, whiteboard diagrams, and prototypes that show interactions with real data, documenting pros, cons, and tradeoffs made during the process. True product design begins with company mission and a clear product architecture defining system components and their relationships, such as Facebook’s directory of people, friends, and interests with its relationship map, then progresses through outcome, system, interaction, and visual layers. The Jobs framework, structured as ‘When ____, I want ____, so I can ____,’ forces designers to specify triggering events and desired outcomes, ensuring designs are mapped to the company mission and product architecture.

The best engineering reads, once a week.

Topic

2 posts about Dribbble. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Intercom
How to hire designers - The Intercom Blog
The post argues that design is fundamentally about how something works, not how it looks, and that hiring based on visual portfolios like Dribbble perpetuates a misunderstanding. The author presents a four-layer design framework: intended outcome, component design, detailed interactions, and visual layer. He asserts that these layers are interdependent and that the best designers excel at one or two while being very good at the others. He advises evaluating candidates against the specific layers needed for the role, noting that a popular Dribbble portfolio only proves graphics software skill and trend awareness, not design ability. The goal is to break the cycle of misunderstanding design education and ensure companies hire designers who can solve real problems.

Intercom
The dribbblisation of design - The Intercom Blog
Paul Adams argues that the Dribbble community rewards superficial aesthetics, moving product design backward. He observes that job applicants often submit pixel-perfect PNGs lacking context, business constraints, or problem definition, focusing on visual polish rather than solving real problems. Strong candidates instead present sketches, whiteboard diagrams, and prototypes that show interactions with real data, documenting pros, cons, and tradeoffs made during the process. True product design begins with company mission and a clear product architecture defining system components and their relationships, such as Facebook’s directory of people, friends, and interests with its relationship map, then progresses through outcome, system, interaction, and visual layers. The Jobs framework, structured as ‘When ____, I want ____, so I can ____,’ forces designers to specify triggering events and desired outcomes, ensuring designs are mapped to the company mission and product architecture.

The best engineering reads, once a week.