
Hey and welcome back to a new week!
The level of execution I see in portfolios keeps getting better. But the explanation of what the work was meant to achieve often gets much less attention.
Small PSA: Next week the newsletter will ship on Thursday due to travel earlier in the week.
This week, I am looking at how to connect design decisions to product outcomes and business value—including with a small side project you have built yourself.
In this issue:
Your Portfolio Looks Great. What Did Your Design Change? How to show impact alongside strong execution, even without impressive metrics.
Kinza’s Portfolio: A portfolio absolutely bursting with personality and one that puts the focus on the work as much as possible.
🏃 THE RIGHT PROMPTS MAKE THE DIFFERENCE
The AI Work Handbook That Cuts Your Workday in Half
The 8-hour workday is becoming a 4-hour workday for people who know how to use AI.
Everyone else is still catching up.
This AI work playbook shows you exactly how to cut your work hours in half using AI.
Sign up for Superhuman AI and get:
50+ step-by-step AI tutorials to cut your workload in half — covering every part of your workday, from emails to strategy, used by 1M+ professionals at Google, Microsoft, and NASA
Superhuman AI newsletter (4 min daily) so you keep discovering new AI tools and skills to stay ahead in your career — the playbook is just the start

Your Portfolio Looks Great. What Did Your Design Change? 📈
The level of execution I see in portfolios has gone up a lot. That includes junior designers. The interfaces are more polished, the interactions feel more considered, and more people are showing things they have actually built. AI has made it easier to get to something impressive, and plenty of designers are putting real care into what happens after that first version too.
But there is something I often struggle to find underneath all that polish: what was the work supposed to achieve? What became easier for the people using it? What improved for the product? And why would the organisation behind it care?
Those questions seem to have taken a backseat in many portfolios. They have not become less relevant to the businesses hiring designers.
A beautiful flow can still leave someone wondering why it needed to exist. And when the execution bar is this high, combining good design with a clear understanding of impact becomes a very valuable way to distinguish your work.
You don't need to understand the entire business
I have a background in product management, so thinking about goals, metrics and business outcomes has been part of how I approach design for a long time. It has helped me explain my work to people who care about it for very different reasons.
Not every designer needs that same depth of involvement. Expectations depend on your role, seniority and team. A design engineer working on interaction quality may sit further from commercial strategy than a product designer shaping an onboarding journey. You don't need to turn every project into a business-school assignment.
Still, a decent understanding of how your work influences the product, and how that product contributes to the business, is useful in pretty much any design role.
Your stakeholders will often include PMs, engineers and people in leadership. They may appreciate the craft, but they also need to understand what the investment is doing. Does it help customers get started? Reduce unnecessary support work? Make an important workflow more reliable? Give people a reason to stay?
My friend Ryan Scott works a lot on this topic. His article You’re not getting enough credit for your design work is a useful read on connecting design to the goals business teams already care about. He shares a DoorDash example where an initial photography test didn't improve overall conversion, but looking more closely revealed that photos helped people make decisions within the flow. It's a good reminder to understand what changed before deciding what the headline number means.
NN/g's article on reporting UX work through business outcomes is a useful deeper read on that translation. For your portfolio, I would start with a simpler habit: explain why the work mattered alongside how well you executed it.
Start with what you wanted to change
When I say impact, I don't mean every case study needs a revenue chart. Showing a meaningful improvement in the product experience is already valuable. You just need to explain why you chose that improvement and what it supports.
Imagine a booking product where people regularly select the wrong appointment type. You redesign the selection step so they understand the differences before confirming. Fewer incorrect bookings would be useful for customers. They could also mean less rescheduling work for staff and fewer appointment slots going to waste.
That gives you a chain worth explaining:
Design decision → change in the product experience → potential business value.
The middle matters. Jumping from “I redesigned the booking screen” to “I increased revenue” skips the part you need to understand and, ideally, investigate.
You might be able to measure incorrect bookings without having access to revenue. That is still useful evidence. Show the improvement you can support, then explain its likely relevance to the organisation. You don't need to claim you proved every link in the chain.
The same thinking applies to an internal tool. Helping a team complete a recurring task with fewer errors can have clear value even if the interface never sells anything directly.
Choose metrics that tell you something useful
Before adding a number to your case study, ask what it would actually tell you. More clicks could mean people are engaged. They could also mean people are lost. More time spent in a product might be desirable for one experience and a problem for another.
Start with the goal, then decide what evidence would indicate progress. Google's HEART framework provides a useful way to connect product goals with signals and metrics. You don't need to apply the entire framework to every project; the habit of choosing deliberately is the useful part.
For example:
People struggle to get started: look at whether they complete the first meaningful task, and where they stop.
A recurring workflow is difficult: look at successful completion, errors and time needed, alongside what people tell you.
A tool is meant to become part of someone's routine: look at whether people return to do that useful thing again.
Pick a small number that fit the problem. A case study with one well-explained result can tell me much more than a dashboard full of unexplained percentages. NN/g's guide to turning UX goals into an analytics measurement plan is helpful if you want to work through that choice in more detail.
When you do have results, give them context. What was measured, over what period, and with how many people? Is this a usability test or live product behaviour? Were other things changing at the same time? Explain your contribution to a team result without claiming the entire outcome as your own.
A launched side project is a particularly good opportunity
I have been encouraging designers to build something and put it into their portfolio. One reason is that a working product makes your capabilities much easier to see. Another is that launching gives you a chance to engage with questions that a fictional design brief can comfortably avoid.
Who will use this? How will they find it? What will make the first experience useful enough that they come back? Could it support a business, and what would need to be true for that to work?
It can be tiny. Imagine you build a tool that helps freelance designers prepare project estimates. The interface looks good, the interactions work, and someone can generate an estimate. That is already something you can show. But there is a much richer project available if you think beyond the build.
Your first useful goal might be getting a new visitor to create an estimate they can actually send. That could influence what you design: a realistic example before signup, a shorter setup, useful defaults, and a clear way to export the result.
You could then investigate where people stop. Are they leaving because they don't understand the tool, because the setup asks too much, or because the output isn't useful? The design changes depending on the answer.
If people use it successfully once, the next question might be whether they return for another project. If you want to explore charging for it, you could investigate which additional capability people would value enough to pay for. These are different questions, and they don't all need to be solved at launch.
The point is to show that your design decisions were connected to what you needed to learn or achieve. You designed the example because people needed to understand the value. You changed setup because it was getting in the way of the first useful result. You prioritised an export over another decorative feature because sending the estimate was the task that mattered.
If the project uses services that cost money each time someone generates a result, that can become part of the design problem too. How do you let someone try the tool meaningfully while keeping it viable to operate? You don't need a full financial model to recognise that constraint and explain how you responded.
A side project doesn't need impressive revenue or thousands of users to demonstrate this thinking. With a small audience, be straightforward about the scale and avoid turning a handful of observations into sweeping conclusions. If nobody comes back, that is something to investigate and reflect on. Launching gives you contact with reality; it doesn't guarantee a success story.
What if the project was never launched?
You can still apply the same thinking to fictional work. Start with a plausible product goal, explain the user problem connected to it, and show how that influenced your decisions. Then be clear about what you have actually checked.
You might test whether people can complete a task in a prototype, compare how clearly two versions explain an important choice, or investigate whether the problem appears in conversations with potential users. Those activities can give you evidence about specific questions. They don't establish retention, revenue or market demand for a product that doesn't exist.
Keep three things separate: what you intended, what you observed, and what you would measure next.
For an unlaunched booking concept, you could explain that you designed clearer appointment categories to reduce incorrect selections. If you tested the prototype, report what happened in that test. Then explain that a live version would need to track incorrect bookings and rescheduling requests to see whether the change helped in practice.
That is much stronger than attaching a made-up conversion improvement to the final screen. And reducing a flow from five steps to three is a description of your solution; you still need evidence before calling it faster or more successful.
Build the impact into the story
Please don't save all of this for a small “Business Impact” box at the bottom. If the goal influenced your design, it belongs in the explanation of the work itself.
A useful structure is:
Context: What did the product or organisation need to improve, and what was difficult for users?
Goal: What change were you aiming for, and why did it matter?
Decisions: Which choices did you make to support that change, including the trade-offs?
Solution: Show the work, ideally with a clear comparison or a short demonstration.
Evidence and reflection: What happened, what remains unknown, and what would you do next?
You don't need to make every section longer. Often, one clear sentence connecting a decision to its goal adds more than another page of process. If the project came from an internship or client engagement, ask what happened after you handed it over. You may have more evidence available than you think.
Keep pushing the quality of your execution. The care in the interface, the interaction and the delivery still matters. But help me understand what all that care was working toward.
When you can show strong craft and explain how it contributes to a useful product and a viable business, your portfolio gives people a much more complete picture of the designer they would be hiring.
💰 AI CHANGED THE GAME
200+ Proven Ways to Make Money With AI in 2026
The next wave of millionaires will be people who figured out how to make AI work for them.
The window to get ahead is still open. But not for long.
Here are 200+ proven ways to make money with AI in 2026.
Sign up for Superhuman AI, the free daily newsletter read by 1M+ professionals, and get instant access to all 200+ ways to profit from AI this year.
Portfolio Showcase: Kinza Ghanchi

Kinza Ghanchi brings product design, illustration, creative coding, and motion into a portfolio with a clear personality.
Her reworked site feels whimsical and welcoming, almost as though she is inviting you into her own space. Underneath that expressive surface is a simple structure that gives her work room to lead.
That character carries into the case studies too, from the Spotify project to newer pages that feel even more personal. Let’s look at what makes the approach compelling, and two improvements that could make the work easier to understand.
That’s it for this week—thanks so much for the support! ♥️
Do you want your own portfolio reviewed in-depth with a 30-minute advice-packed video portfolio review? Look no more. I do offer these as an async service you can book directly with me here.

Keep kicking doors open and see you next week!
- Florian




