Process in the Shallows of Pixels
Dissecting the gap between visual portfolios and a designer's actual capacity for systematic problem-solving.
Ecosystems of Professional Evaluation
Have you ever considered why programmers, unlike designers, do not primarily showcase the final appearance of their work for evaluation, but instead present the code itself?
The answer lies at the boundaries of expertise. Understanding code requires technical knowledge of the language in which it is written. A Java developer’s code can only be properly evaluated by experienced Java developers or technical leads. This is precisely why platforms such as GitHub and GitLab have become so widespread: environments where work is reviewed by specialists in the same field according to well-defined technical standards.
Web designers, however, lack an equivalent professional ecosystem.
Because design is inherently visual and intuitive, it is more accessible to a broader audience. As a result, platforms such as Dribbble and Behance have become the primary showcases for designers.
But do these showcases truly reflect the capabilities of a web designer?
The Gap Between Capability and Platform
Although web design often appears artistic on the surface, it is fundamentally driven by specific objectives and measurable outcomes.
Many respected voices in the field have emphasized that web design is not merely an artistic expression. It must solve problems, improve user experiences, and produce tangible results.
Yet on today’s platforms, designers are often forced to present themselves primarily through visual aesthetics. In such an environment, a static and decorative concept may receive more attention than a sophisticated UX solution—even when the latter demonstrates a much deeper level of expertise.
While developers on GitHub can demonstrate their capabilities through reviewable code, thorough documentation, and complex problem-solving, web designers on Dribbble are often limited to displaying “beautiful images.” They have little opportunity to present their design rationale, user-centered decisions, research findings, or usability testing results in a standardized and professional manner.
These platforms have effectively established the “static image” as the standard format for portfolios. Yet web design is inherently interactive and time-based.
We are expected to compress a complex user experience into a single flattened screenshot—as if photographing the exterior of a building without being able to show its architectural plans, structural systems, or internal functionality.
Do platforms such as Dribbble and Behance, with their strong emphasis on visual presentation, truly satisfy the needs of professional web designers who wish to demonstrate and evaluate their expertise?
Or do we need an environment where, much like GitHub for developers, the depth of design thinking and the effectiveness of solutions take precedence over aesthetics alone?
The Historical Roots of an Unlikely Coexistence
Dribbble was founded in 2009 by Dan Cederholm and Rich Thornett. Its original purpose was straightforward: to create a space where graphic designers, illustrators, typographers, and logo designers could share small samples of their work.
The original 400-by-300-pixel format was perfectly suited for showcasing icons, logos, and compact graphic compositions. It was never intended to explain information architecture, demonstrate responsive behavior, or document UX processes.
In the early 2010s, web design was still transitioning from static web pages to digital products. At that time, maintaining a personal portfolio website required either technical knowledge or a significant investment of time and money.
Dribbble offered something different. It was fast, social, accessible, and relatively easy to use.
As a result, many web designers—who at the time often worked more like digital graphic designers than product designers—migrated to the platform and gradually adopted it as their primary showcase.
Were there alternatives? Certainly.
However, none of them offered the same social infrastructure.
Behance functioned more as an archive than a conversation. Personal websites lacked network effects and community engagement.
Dribbble, on the other hand, promised visibility among employers and rapid feedback from peers. As the network grew, leaving it became increasingly difficult.
Why Do We Still Stay?
The issue is not merely historical.
We continue to rely on Dribbble because we still lack a widely adopted professional alternative.
While developers can use GitHub to demonstrate how they think—through code structure, repository organization, and approaches to problem-solving—web designers on Dribbble are often limited to demonstrating what they made.
The distinction is significant.
One reveals the process behind the work.
The other reveals only the outcome.
What We Need Today: A Shift Toward Process Documentation
The solution to this dilemma lies in moving from showcasing outcomes to documenting processes.
- Web designers need a platform where they can:
- Record and explain their decision-making process through design logs.
- Attach the results of usability studies and A/B tests.
- Demonstrate interactions and user flows in a live and interactive format.
- Most importantly, be evaluated by professionals within the same discipline according to criteria such as effectiveness, problem-solving ability, and the quality of design decisions—not merely visual harmony or adherence to design trends.
Perhaps the problem is not that Dribbble is a bad platform.
Perhaps it was simply built to solve a different problem.
Until a more suitable alternative emerges, Dribbble will remain for web designers what an art exhibition is for a structural engineer: a place that may be beautiful and inspiring, yet one that cannot accurately communicate the professional expertise involved in creating durable, effective, and problem-oriented solutions.
The challenge, therefore, is not a lack of talent among designers. It is the absence of a professional ecosystem capable of revealing the depth of that talent.