---
title: "The dribbblisation of design - The Intercom Blog"
description: "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 dribbblisation of design - The Intercom Blog

[Intercom](https://yomu.fyi/company/intercom) · Oct 8, 2026

**Type:** Problem & solution

## Summary

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.

## Context

The post is written against the backdrop of the rising popularity of Dribbble among designers in 2013, leading to a focus on aesthetic polish rather than problem-solving in portfolio work. The author draws on his experience reviewing hundreds of design job applications at Facebook and Intercom.

## Approach / What changed

Use a top-down design process: start with company mission and product architecture; design through four layers (outcome, system, interaction, visual) in order; apply the Jobs framework (When \_\_\_\_, I want \_\_\_\_, so I can \_\_\_\_) to frame problems; build prototypes and pattern libraries with real data instead of static mockups.

## Takeaways

- Dribbble’s community rewards superficial visual design, leading many designers to produce context-free PNGs that ignore business constraints and system interactions, effectively practicing digital art rather than product design.
- Effective product design begins with a clear mission, vision, and product architecture, then progresses through outcome, system, interaction, and visual layers, each dependent on the previous.
- Using the Jobs framework (When \_\_\_, I want \_\_\_, so I can \_\_\_) helps designers focus on triggering events and intended outcomes, ensuring designs are problem-driven and aligned with product architecture.

## FAQ

### Why does the author criticize Dribbble?

The author criticizes not Dribbble itself but the community's values, which reward superficial aesthetics and pixel-perfect visuals over solving real business problems, effectively moving product design backward.

### What is the recommended design process in the post?

The post recommends a top-down process: start with company mission and product architecture, then design through four layers (outcome, system, interaction, visual). Use the Jobs framework to frame problems and build prototypes with real data instead of static PNGs.

### How does the Jobs framework apply to product design?

The Jobs framework frames problems as 'When \_\_\_\_, I want \_\_\_\_, so I can \_\_\_\_,' specifying triggering event, motivation, and intended outcome. This ensures designers focus on real user goals and align with the product architecture.

**Tags:** [Dribbble](https://yomu.fyi/topic/dribbble), [Jobs-to-be-Done](https://yomu.fyi/topic/jobs-to-be-done), [Product Design](https://yomu.fyi/topic/product-design)

- Source: [Intercom](https://www.intercom.com/blog/the-dribbblisation-of-design)
- Source URL: https://www.intercom.com/blog/the-dribbblisation-of-design
- Ingested by Yomu: 2026-10-08T18:00:30.063Z

[Read original post](https://www.intercom.com/blog/the-dribbblisation-of-design)