The most valuable thing I ever learned as a designer had nothing to do with design.
When I put together my case for the UK Global Talent visa, I sat down expecting to talk about my craft. The tools I had mastered. The interfaces I had shipped. The years of learning how to make things work and look right.
Almost none of that turned out to matter.
What carried the case was not the software I used or the screens I designed. It was the impact. The growth I had helped create. The revenue that moved. The numbers that changed for the companies I worked with because of decisions I had made as a designer.
That was the moment something clicked that I wish someone had told me a decade earlier.
Most designers believe their value lives in their craft. In the quality of the work, the polish of the portfolio, the mastery of the tool. And craft matters, deeply. But craft is not what a business pays for, and it is not what makes design a force for innovation. Impact is.
Here is the uncomfortable truth I have watched play out on team after team. Most designers are not genuinely interested in what happens to their work after they hand it over. They care about the design being accepted. They care about the review going well. They care about the craft. But ask them what their last project did to the company’s numbers, and most cannot tell you. They were never in that conversation, and they never asked to be.
This is not laziness. It is how designers are trained. We are taught to make. We are rewarded for artefacts. The handoff feels like the finish line, so we stop watching right at the point where the only thing that matters is about to happen: contact with real users and real outcomes.
The data on this is blunt. When McKinsey studied the design practices of 300 public companies over five years, they found that just over half of them had no objective way to assess or set targets for the output of their design teams. Over 40 percent were not even talking to their users during development. Design was happening. Impact was not being measured, and often was not being created.
And yet the same study found that the companies scoring in the top quartile for design grew their revenues and their total returns to shareholders far faster than their industry rivals over that five-year period, by 32 and 56 percentage points respectively. Design, done as a discipline tied to outcomes, is one of the strongest growth engines a company has. Done as decoration, it is a cost.
The difference between the two is not talent. It is whether the designer connects the work to the number.
So how do you actually do that? For me the answer has been to design with data in mind from the very first decision, not to bolt it on at the end. I now work within the UK government, building services used by millions of citizens, and the way the system is built forces this discipline on you. The UK Service Manual sets out four measures that every public service is held to: cost per transaction, user satisfaction, completion rate, and how many people choose the digital route over the old one. You do not get to call a service good because it looks good. You have to show that people can actually complete what they came to do, that they are satisfied, and that it costs less to serve them well.
That reframes the entire job. You are no longer designing a screen. You are designing an outcome, and the screen is just one lever you pull to move it.
This is where design becomes a force for innovation rather than a paint job on someone else’s idea. When a designer walks into a team armed with a clear picture of the outcome the business needs, and a real understanding of the user standing in the way of it, they stop being the person who makes things pretty at the end. They become the person who reframes the problem at the start. And reframing the problem is where every real innovation begins.
The way you spark this on a team is not by declaring that design matters. Everyone says that and nothing changes. You do it by tying your work to a metric the team already cares about, out loud, before you design anything. You say, this is the number we are trying to move, here is what I have seen in the way real users behave, and here is the design bet I want to make against it. Suddenly you are not defending your craft in a review. You are leading a conversation about the business. Engineers lean in. Product leans in. That is the room where innovation happens, and design has earned a seat at the table by speaking the language of the table.
I will be honest about the cost of working this way. It is less comfortable. You have to learn the business, not just the tool. You have to sit with data that sometimes tells you your most beautiful work did not move anything. You have to let go of the idea that the artefact is the achievement. For a lot of designers, that is a hard trade, because the craft is where the identity is.
But here is the reframe I would leave every designer with. Your tools will change. The software you are proud of today will be obsolete in five years, and the next generation will master it in an afternoon. What will not go out of date is your ability to take a real user problem, connect it to a real business outcome, and move the number. That is not a threat to your craft. It is what finally makes your craft matter.
Stop showing people what you made. Start showing them what changed because you made it.
If ideas like this are worth sitting with, that is exactly what my newsletter is for.
Get next week’s idea in your inbox: Subscribe to Ideas Worth Sitting With.
https://samuels-newsletter-e55964.beehiiv.com/p/your-tools-are-not-your-value