The Portfolio Piece That Ends With 'I Quit' Is the One Clients Remember

I have a portfolio full of projects that worked. There’s the rebrand that shipped, the campaign that hit its numbers, the essay collection that actually got bound. And yet the page clients mention most is a case study about a video series I killed after two episodes.

I didn’t publish it to be brave. I published it because I was tired of pretending the only work worth showing was the work that ended with a bow. So I picked a project that had genuinely fallen apart, wrote it up the way I’d write up a success, and put it on my site with the same real estate as everything else.

The Project I Chose to Bury in Public

The project was called Kitchen Table Interviews: a short video series where I’d sit down with makers, cooks, and small-business owners in my corner of Ohio and ask them how they actually spend their days. The pitch was simple—three questions, one table, no glossy b-roll. I shot two episodes. I edited one. I never published the second. The whole thing stalled somewhere between “this is charming” and “why does this feel like homework?”

For the case study, I didn’t summarize it as “a video series that didn’t move forward.” I treated it like a real project: what I was trying to do, who it was for, what I decided, where it broke, and what I’d do differently. That last part turned out to be the whole point.

Writing the Brief I Wish I’d Written

The original brief was three sentences in a notes app. For the case study, I wrote a fuller version—not the brief I actually had, but the one I should have had. It included the audience (local small-business owners who were tired of being interviewed like case studies themselves), the constraint (I had four hours a week and no budget for a second camera), and the definition of done (six episodes, published monthly, each under seven minutes).

Writing that down was uncomfortable. It made the project look less like a vague creative experiment and more like a plan I had abandoned. But that discomfort was useful. It gave the case study a spine.

The Decisions (Including the Bad Ones)

I listed five decisions and what I was optimizing for at the time. Two were good. Three were not.

The good ones: I kept the setup minimal, and I chose subjects who were comfortable talking while doing something with their hands—making coffee, folding dough, sorting mail. The bad ones: I over-edited the first episode until it felt like a brand video instead of a conversation. I scheduled shoots too far apart, which made momentum impossible. And I kept telling myself I needed a “season” before I needed a habit.

In a success story, those decisions would get smoothed into a neat narrative about learning. In the case study, they just sit there. That’s what makes them useful.

Where It Stalled

The stall wasn’t dramatic. No client pulled out. No hard drive died. I just stopped opening the project file. I wrote in the case study that the real symptom was “a growing gap between the effort of scheduling and the reward of publishing.” That sentence took me an hour to write, mostly because it was true.

I also included the artifacts: the shot list with three unchecked boxes, the color-correction notes I never used, the email draft asking a third subject if we could reschedule “after the holidays.” Publishing those felt like leaving the garage door open. But they’re the most concrete part of the whole piece. They show the exact texture of a project that didn’t die—it just stopped getting fed.

What the Client Said

A prospective client—a small branding studio in Chicago—read the case study and sent me a note that said, “This is the first portfolio piece I’ve read where I believed the person had actually done the work.” She wasn’t being mean about the rest of my site. She was saying that the failure case study gave her something the polished ones couldn’t: evidence of judgment.

We ended up working together on a content strategy project. During our first call, she referenced the “scheduling gap” line from the case study and asked how I’d avoid the same trap on her project. That’s not a question I get from a page full of wins.

Why Failure Reads as Credible

A polished case study says: look at this thing I made. A failed case study says: look at how I think when the thing isn’t working. For clients, that’s often more relevant. They don’t need to know I can succeed when everything goes right. They need to know I can notice when something is going wrong and say so out loud.

There’s also a practical benefit. Success stories tend to flatten into the same shape: problem, solution, result. Failure case studies have more oxygen. They can hold ambiguity, partial credit, and the weird little decisions that don’t fit into a testimonial. Readers linger on them because they’re not being sold a lesson. They’re being shown a process.

A Template You Can Steal

Here’s the structure I used. It took about two hours to fill in, and most of that was arguing with myself.

1. One-line premise. What was this project, in plain language? No mission statements.
2. The brief as you understood it. Audience, constraints, definition of done.
3. Three decisions and what you were optimizing for. Include at least one you’d reverse.
4. The stall. What were the symptoms? When did you know? What did you tell yourself?
5. What you’d do differently. Be specific enough that someone could copy it.
6. Artifacts. A sketch, a shot list, a note, a red-lined draft. Proof of life.
7. One thing that worked. This keeps the piece from turning into a confession.

The Case Study Is Not a Confession

I want to be clear about something: this isn’t about romanticizing failure or turning every dead project into content. Some things should just stay in the drawer. The case study works because it’s structured like work, not like a diary entry. It has a brief, decisions, and a post-mortem. It treats the failure as material.

That’s the difference between “I quit this” and “here’s what I learned from quitting this in a way you can use.” The first is a feeling. The second is a portfolio piece.

I still haven’t revived Kitchen Table Interviews. I’m not sure I will. But the case study about it has done more for my site than the three success stories sitting next to it. It turns out clients don’t just want to see what you finished. They want to see how you think when you don’t.