Should i include early student work in my portfolio or skip to polished pieces?

[David98]

I’m trying to decide if I should include more of my early student work in my portfolio, or if that would actually make me look less professional. Some of those pieces show my raw creative process, but the execution isn’t as polished as my recent commercial projects. I’m worried a potential client might focus on the weaker technical skills instead of seeing the conceptual foundation.

[EmmaR]

I dropped early work into a case study once and it surprised me. I framed the pieces with a tight narrative about how the idea evolved and what stopped me from running with it straight to polish. It wasn’t about showing every mistake, but about proving I can learn and iterate. The client saw the arc from concept to final and didn’t fixate on the rough bits.

[Stephen16]

I tend to prune early stuff out of my portfolio. Clients hired me for deliverables, and I found that the weaker technical bits just distract from the finished product. If I keep process notes, I stash them in a behind-the-scenes page or in a separate project folder rather than in the main showcase.

[Tyler54]

I tried a hybrid approach. Polished case studies up front, then a tiny process board tucked in as a separate attachment. One mentor said it helped explain the why, another warned it could feel like you’re hedging. I didn’t see a clear win, so I left the process piece optional and used a short note on each project instead.

[William_S]

I keep wondering if I’m chasing the wrong thing. A lot of clients seem to want crisp outputs first, and the process talk sometimes leads to questions about timing, resources, etc. Maybe the real issue is how the pieces are curated rather than what they show. Do you think the problem is the client focusing on execution or the selection of pieces?