Journal

November 15, 2026

Judging design work: Outcomes over Outputs

💡 Note: this is adapted from a post I made on LinkedIn on November 15. As of this writing, that post has 90 reactions and 17 comments! Wasn’t expecting it to spark so many feelings.

Last week, I had a conversation with one of my former colleagues that turned spicier than I intended. The conflict? This statement:

"As a hiring manager, I want to see evidence of what you shipped."

There's nothing inherently wrong with this statement, and it's certainly something that I've seen in comments from hiring managers and recruiters on platforms like LinkedIn. But I found myself frustrated because this mindset speaks to a specific time in a designer's career that doesn't fit where many of us who have been around several blocks actually are. And there are three reasons for that:

  1. The fact that you “shipped” something doesn’t inherently mean that what you shipped had a positive impact on the problem you were trying to address.
  2. At a certain point in your career, you move away from shipping individual features, and towards larger, more complex projects that usually involve a full roadmap of features.
  3. As designers and researchers, we do not build the things we design. And no matter how much we get pressured to get into the code, meaningful work requires collaboration.

Over the past 8 years at athenahealth, I can not point to a single feature that I shipped directly. That wasn’t my role. What I can point to is COUNTLESS corporate initiatives that were funded, product launches that succeeded, and cross-division initiatives that got back on track. Just a few examples:

I am hardly the first super-senior designer/researcher who has done work like this. We aren’t the ones who pull JIRA tickets, or execute on an enhancement. Who we are is the one who is going to help the teams make sure that what they execute on is something people actually WANT. Recruiter Cheryl Dean’s comment on my LinkedIn post says this nicely:

When I'm assessing senior candidates, I'm far more interested in what changed because of their leadership. What decisions did they influence? What teams did they build? What commercial impact did they have?

Despite this, my main issue with the focus on "what did you ship?" is that it reflects an oddly individualistic view of how work actually happens when you're working on complex things. So many people forget that as designers, we rarely build the things we design—no matter how many times we get pressured to write code or prototype in Claude. But that's a good thing. Because our superpower isn't pixels, it's people. When we're able to collaborate, respect each others' strengths, and do the work together, that's when the really powerful stuff happens.

I would really love this industry to start remembering that again.