Portfolio & Design Critique — March 2026

Why Read This from an HCI Perspective

This article is meaningful for HCI/UX practitioners because it asks for portfolio feedback not as a matter of taste, but as evidence-based critique. In particular, it makes clear the assumption that the more context you provide, the better the feedback you can get. This highlights that, more than the artifact itself, the evaluation is heavily influenced by how well the problem is defined, the logic behind decision-making, and the explainability of the collaboration process. It offers both practitioners and researchers a perspective on portfolios as ‘records of reasoning,’ not merely ‘deliverables.’

CIT's Commentary

From a CIT perspective, this piece is less about the act of showcasing a portfolio and more about designing the critique. In other words, the key is not what you show, but what questions you prompt and what rationale you use to elicit answers. This connects directly to how, in HCI, context design and information structure shape users’ judgments. Especially in the way it requests feedback on framing, narrative, and scope—like the top comments—it reads as a strategy to verify the readability of problem-solving ability rather than the portfolio’s ‘visual polish.’ That said, such requests can easily lead to fragmented opinions if evaluation criteria aren’t made explicit. Therefore, CIT argues that structured feedback with purpose-specific checkpoints presented in advance is more effective.

Questions to Consider While Reading

• Q.How should you balance the emphasis on visual polish and the problem-solving narrative in a portfolio?
• Q.To receive better feedback, how much of the case context and constraints should you disclose?
• Q.In UX portfolio evaluation, what signals do hiring managers and fellow researchers actually notice first?