Greetings, Coderblog readers!
Reflecting on my extensive review of over a thousand design portfolios, a glaring issue stands out: a majority were rejected due to a reliance on a 'linear design process.' This term describes a standardized approach: identifying a problem, user interviews, persona creation, sketching, moving to mockups and wireframes, polishing with visual design, prototyping, testing with users, and wrapping up with a 'design system'—often, in reality, just a style guide mislabeled due to its current buzz.
This approach, while systematic, often lacks the authenticity and depth required by design-mature companies, leading to a staggering 90% rejection rate in my experience. The comparison to overly positive online product reviews is apt; perfection on paper often raises doubts about authenticity.
The discussions this topic sparked online, especially on LinkedIn, echo this sentiment. Many experienced designers highlight the disconnect between the linear, textbook approach taught in schools and the chaotic, iterative reality of actual design work. A design manager's frustration with repetitive, superficial case studies underscores the craving for depth and genuine problem-solving abilities.
The issue extends beyond the presentation of work; it reflects a broader misunderstanding of the design process itself. Some designers follow a truly linear path, possibly due to inexperience or misconceptions about what hiring managers seek. However, design is inherently non-linear, involving constant iteration, adaptation, and, often, revisiting previous stages.
For emerging designers, the challenge is to balance learned processes with the messiness of real-world design. This includes developing strong communication skills, fostering collaboration, and maintaining an open, flexible approach to problem-solving.
Design portfolios that stick too closely to a linear, 'clean' narrative risk not only failing to capture the complexity of the design process but also misrepresenting the designer's capabilities. The key lies in embracing and showcasing the messiness, the iterations, and the real challenges faced and overcome.
Monica's story, a mentee of mine, perfectly illustrates this point. Her initial case study presentation glossed over the complexities and learnings from the project, presenting a too-simple, linear narrative. Only by delving into the nuanced decision-making process, the setbacks, and eventual success did her case study gain the depth and authenticity needed to truly stand out.
The lesson here is clear: linear and perfect is not the goal. Design is about navigating challenges, leveraging creativity, and sometimes, embracing the mess to find innovative solutions. It's these stories of resilience, creativity, and real-world problem-solving that resonate with design-mature companies, not the sanitized narratives of flawless execution.
To all aspiring designers, let this be a call to action: showcase your design journey in all its complexity. It's not the neatness of the process but the depth of your problem-solving that will set you apart.
Warm regards,
Coderblog Team