The case for keeping the messy middle

A case study that is too clean makes me suspicious. Real product work rarely moves from problem to insight to perfect solution in a straight line. There are false starts, awkward constraints, missing data, stakeholder reversals, technical limits, and at least one prototype that looked convincing until people used it.

I understand why designers polish the middle out. Portfolios are already hard to write. Nobody wants to look indecisive. Nobody wants to show work that was rejected. But the messy middle is often where judgment lives.

The final screen tells me what you shipped. The middle tells me how you think.

Polish can flatten the work

The standard case-study shape is familiar: problem, role, process, solution, impact. There is nothing wrong with that structure. The problem is what happens when every section is written like the outcome was inevitable.

If the first concept was obviously wrong, say why. If research changed the direction, show the before and after. If engineering constraints removed your favorite interaction, explain the tradeoff. If the metric moved because of a boring copy change instead of the hero redesign, that is useful.

The point is not confession. The point is credibility. A team hiring for product judgment wants to know whether you can update your opinion when reality pushes back.

Artifacts that carry useful mess

I do not need to see every sticky note. I do want to see artifacts that changed the work.

Good messy-middle artifacts include:

• A rejected flow with a short note about what failed.
• A decision table comparing two or three viable directions.
• A prototype clip that exposed a misunderstanding.
• A before-and-after IA sketch.
• A screenshot of the design-system gap you had to work around.
• A support-ticket pattern that changed the priority.
• A small metric table showing what improved and what did not.

The artifact should earn its space. If it only proves that a workshop happened, skip it. If it explains a decision that a polished final screen cannot explain, keep it.

Narrate false starts without rambling

The cleanest way to write a false start is three sentences:

1. What we tried.
2. Why it was plausible.
3. What made us change direction.

For example: "We first tried putting shipping estimates inside the cart drawer because it kept cost information close to the product decision. In testing, that looked helpful, but it pushed promotion codes and checkout below the fold on common mobile screens. We moved the estimate to a compact row and saved detailed delivery choice for checkout."

That is enough. It shows reasoning without turning the case study into a diary.

Show constraints as design material

Constraints are not excuses. They are part of the material. A strong case study explains which constraints shaped the solution and which constraints the team chose to challenge.

I want to know if the API could not support real-time quotes, if the design system lacked a compact table, if legal required specific language, or if the team had two weeks before peak season. Those details make the work more useful because they explain why the final design has the shape it has.

There is a difference between "we could not" and "we chose not to." The messy middle is where that difference becomes visible.

Protect the people, keep the lesson

Some mess should stay private. Do not turn stakeholders into villains. Do not expose sensitive business data. Do not publish customer quotes that should have stayed in a research room.

You can still keep the lesson. Replace names with roles. Round numbers. Recreate artifacts when the original cannot be shared. Describe the decision pressure without leaking the meeting.

The goal is to reveal your judgment, not somebody else's bad day.

The version I trust

A case study I trust usually has one or two moments where the author says, in plain language, "we thought this would work, then we learned something." That does not weaken the work. It makes the final solution feel earned.

The messy middle does not need to be long. It just needs to be present. Show me the fork in the road, the evidence that mattered, and the tradeoff you accepted. That is where craft shows up.