Why Some of the Most Valuable UX Work Isn't Particularly Pretty
UX portfolios tend to show the polished end of the process: refined interfaces, prototypes, and beautifully presented case studies. What they rarely show are the workshop notes, research synthesis, rough sketches, discarded flows, and decision logs that helped the team get there. These artifacts may never win any design awards, but they’re often where some of the most valuable product thinking happens.
If you only experienced UX through portfolios, you might assume the design process is remarkably tidy.
There are beautifully organized case studies, carefully selected wireframes, polished prototypes, and final interfaces presented in exactly the right order. Everything seems to move logically from problem to solution, with just enough process in between to show how the team arrived there. The reality is usually a little less photogenic.
Behind a polished product, there’s often a FigJam board covered in notes, research findings that took hours to organize, sketches nobody outside the team will ever see, flows that were explored and eventually abandoned, and conversations that changed the direction of the work entirely. There may even be a screenshot called “final-final-v3” somewhere in the process. We’re designers, not miracle workers.
Most of those artifacts never make the portfolio. They aren’t necessarily impressive to look at, and without context, some of them might not make much sense at all. But they often contain the thinking that made the polished work possible.
“Some of the most valuable UX work isn’t particularly pretty.”
Workshop Notes Capture the Conversations Behind the Product
A workshop board probably isn’t the first thing anyone wants to frame and hang on the office wall.
It can be messy. There are sticky notes everywhere, questions sitting beside half-formed ideas, observations grouped and regrouped, and sometimes a few thoughts that made perfect sense during the conversation but look slightly mysterious the next morning. That mess has value.
Workshop notes capture perspectives that might otherwise disappear as soon as a meeting ends. They show what stakeholders were concerned about, where people disagreed, which assumptions surfaced, and how the team’s understanding changed as the conversation progressed. They give everyone something tangible to return to instead of relying on slightly different memories of what was discussed. The board itself isn’t deliverable. The shared understanding it helps create is what matters.
Research Synthesis Turns Conversations Into Something We Can Use
User interviews can produce an enormous amount of information. One participant mentions a workaround. Another describes frustration. Someone uses a phrase that catches our attention, while another says something that contradicts what the team expected to hear. Individually, those observations are interesting. The real work begins when we start connecting them.
Research synthesis is where interview notes, observations, quotes, and behaviors are compared so we can identify patterns across the research. It may involve affinity mapping, spreadsheets, sticky notes, transcripts, or a FigJam board full of information that looks considerably less elegant than the final research summary.
This is where we begin separating isolated comments from recurring themes. A frustration mentioned once might be an individual preference. When the same problem appears repeatedly across interviews, it becomes something worth investigating more closely. Synthesis may not be particularly glamorous, but it’s what turns a collection of conversations into useful product direction.
Rough Sketches Give Ideas Somewhere to Go
There is something wonderfully freeing about a design that isn’t supposed to look good yet.
Early sketches and low-fidelity wireframes allow us to explore ideas without becoming too attached to them. We can move things around, try different workflows, simplify steps, and test several approaches before investing significant time in visual refinement.
These early artifacts are often where important structural decisions begin taking shape. We’re thinking about what information users need, what they should be able to do next, how a workflow should progress, and where complexity might be hiding.
A rough sketch doesn’t need to be portfolio-ready because that’s not its job. Its job is to help us think, communicate an idea, and give the team something concrete enough to question.
Sometimes the sketch survives and eventually becomes part of the finished experience. Sometimes it exists for twenty minutes and teaches us exactly why we should try something else. Both outcomes are useful.
Discarded Flows Aren't Wasted Work
One thing portfolios almost never show is how many ideas didn’t make it.
There are workflows that seemed promising until we mapped the edge cases. Features that became unnecessarily complicated once we understood the full user journey. Interactions that worked beautifully in one scenario but created problems somewhere else in the experience.
Those directions are usually removed from the final presentation because the finished product doesn’t need to explain every road the team chose not to take.
But discarded work still contributes to the outcome.
Exploring a direction helps us understand its limitations. It may expose an assumption, uncover a dependency, or clarify what the experience actually needs. Sometimes the fastest way to understand why one solution works is to spend a little time discovering why another one doesn’t.
The final design may look obvious in hindsight, but that’s often because the team already explored the alternatives.
Decision Logs Preserve the Why
One of the easiest things to lose during a long software project is the reasoning behind a decision.
A few months after something was agreed upon, someone inevitably asks, “Why did we decide to do it this way?” Without documentation, the answer can quickly become a mixture of memory, assumptions, and whatever everyone happens to remember from a meeting three sprints ago.
Decision logs help preserve that context. They don’t need to be elaborate. What matters is capturing the important choices, the reasoning behind them, the constraints that influenced them, and any assumptions the team was working with at the time. That information becomes especially useful as new people join the project or when a decision needs to be revisited later.
The artifact itself may never be seen by a user, but it can save a team from reopening conversations that have already been thoughtfully resolved.
Why the Messy Artifacts Can Matter More Than the Final Mockup
The final mockup is important. It’s what developers eventually need to implement, what stakeholders review, and what users ultimately experience. But the mockup doesn’t always tell you why the product works the way it does.
It doesn’t show the user frustration uncovered during research that caused a workflow to change. It doesn’t show the workshop conversation that aligned three stakeholders who had been imagining different solutions. It doesn’t show the early flow that revealed an edge case or the design critique that helped simplify an interaction. Those decisions live in the artifacts created along the way.
That’s why evaluating UX solely by the quality of the final screens misses a significant part of the work. The interface is the visible outcome, but much of the value comes from the process that gave the team enough clarity to make the right decisions before getting there.
What This Looks Like at Pepperplane
At Pepperplane, our projects naturally create plenty of artifacts that will probably never appear in a polished case study.
There are workshop boards filled with notes, research synthesis sessions, early wireframes, discarded concepts, comments in Figma, feedback from developers, and documentation that captures why particular decisions were made. Some are neat. Some are decidedly not.
We don’t create these things because a UX process is supposed to produce a certain number of artifacts. We use them when they help the team understand something, make a decision, communicate more clearly, or reduce uncertainty.
That’s an important distinction. More documentation doesn’t automatically mean better UX. A beautiful journey map nobody uses isn’t particularly valuable. A messy collection of notes that helps a team uncover the real problem might be. The artifact is only useful if it helps the work move forward.
Final Thought
There’s a reason UX portfolios tend to show polished work. It’s easier to understand, easier to present, and admittedly much nicer to look at. But if you want to understand how a product really came together, the messy work often tells the better story.
It’s in the workshop notes where assumptions first surfaced. The research synthesis where patterns became visible. The rough sketches where possibilities were explored. The discarded flows that showed us what wouldn’t work. The decision logs that kept the team aligned as the project evolved. None of those things may ever be seen by the people using the final product.They don’t need to be.
Their value is in helping the team arrive at something that feels clear, useful, and surprisingly simple when it finally reaches the user. The polished screen is what everyone sees. The invisible work is what helped us know what belonged on it.
Ready to Build Better Products Together?
Looking for a UX partner who can bring clarity to your next project? We’d love to chat.
Book a discovery call and let’s build something remarkable together.
