The Work You're Proudest Of Is Rarely the Work That Wins

There's a project I was genuinely proud of. It was technically difficult, it solved a problem in a way I hadn't seen done before, and the execution was the cleanest work I'd produced. I put it front and centre everywhere. And it won me almost nothing — while a straightforward, unremarkable piece I'd nearly left out, the kind of work I could produce competently in my sleep, kept generating enquiries. For a while I found this genuinely irritating, as though the market had failed to appreciate the good stuff. It took longer than it should have to see that the market was assessing something I wasn't.

The gap is this: you judge your work by how hard it was and how well you solved it, and clients judge it by whether it looks like the thing they need. Those are different criteria and they diverge constantly. The difficulty of a project is almost entirely invisible in the finished result — a client can't see the constraint you worked around, the problem you solved elegantly, or the technical achievement embedded in something that looks simple. What they can see is whether the work resembles their situation. Craft pride is about the making; client assessment is about the match.

This isn't clients being philistines, and it isn't an argument that quality doesn't matter. It's a recognition that you and the client are looking at the same artefact and evaluating completely different things. You see the hard-won solution and the elegance of the execution. They see something that either does or doesn't look like the answer to the problem currently costing them money. When those coincide, your proudest work is also your best-performing work. Frequently they don't coincide, and then the pride and the results come apart.

The practical cost of not understanding this is that you present your work badly — leading with what impressed you rather than what would resonate with the person deciding, and quietly resenting an audience that was never assessing on your criteria. Recognising the difference doesn't require abandoning your standards. It requires understanding that pride and persuasion are separate systems, and presenting for the second while pursuing the first. Here's how they diverge.

Key Takeaways

• You judge difficulty; clients judge fit. The hard part of a project is invisible in the result. Clients assess whether the work resembles their problem, not how hard it was.
• Recognisable beats impressive. A client hires what looks like the answer to their situation, so relevance usually outperforms craft brilliance in unrelated work.
• Novel work is harder to buy. Unusual, boundary-pushing work is exciting to make and risky to hire, because it doesn't reassure a client that you'll solve their ordinary problem.
• Your pride is often about the constraint. Much craft satisfaction comes from what you overcame, which the client never sees and can't factor into their decision.
• Present for them, pursue for you. Keep making work you're proud of; just stop assuming pride predicts persuasion, and select what you show accordingly.

Difficulty Is Invisible in the Result

Start with the mechanical reason these diverge: nearly everything that makes work satisfying to produce is undetectable in the finished product. The impossible timeline, the client who changed direction three times, the technical constraint you engineered around, the elegant solution that replaced an ugly one — a viewer encountering the result sees none of it. They see an outcome, stripped of its history, and they judge that outcome on its own terms.

This means your internal ranking of your own work is calibrated on information nobody else has. You rate a piece highly partly because you know what it took, and that knowledge is unavailable to everyone else. Worse, the relationship often runs backwards: the most impressive technical achievements frequently look effortless, because making something difficult appear simple is precisely the skill. So the work you're proudest of can be the work that reads as least remarkable, exactly because you succeeded at hiding the difficulty.

There's a partial remedy, which is to make the invisible visible — explaining the constraint, the problem, and the reasoning alongside the work, so a viewer can see what was actually solved. Context genuinely changes how work reads, and it's why a piece with its problem and constraints explained lands so differently from the same piece shown bare. [BACKLINK PLACEHOLDER → suggestion: internal link to article #89, what to put in your portfolio / context turns an artefact into evidence of judgment] But this only goes so far. Explaining difficulty helps a client appreciate your capability; it doesn't make an unrelated project look like the answer to their problem, which is the more decisive factor.

Clients Are Matching, Not Ranking

The deeper reason the divergence exists is that clients aren't ranking your work by quality at all — they're pattern-matching against their own situation. Someone assessing whether to hire you isn't asking "what's the best thing here?" They're asking "has this person done something like what I need?" That's a matching operation, and it's dominated by resemblance rather than by excellence.

Which explains the frustrating result: an ordinary, competent piece that closely resembles a prospect's problem will outperform a brilliant piece that doesn't, nearly every time. The brilliant unrelated work requires the client to make an inferential leap — this person is clearly talented, so presumably they could also do my quite different thing — and inference is effortful and uncertain, so many won't make it. The ordinary similar work requires no leap at all: they can see the answer to their question directly.

This is also why the enquiries you receive track what you display rather than what you're best at, and why leading with your proudest work can actively misdirect the market about what you do. The signal a client takes from your work isn't "this person is excellent"; it's "this person does this." Being clearly, visibly the person for a specific kind of problem is what converts, which is the same reason a focused position beats an impressive but unfocused one. [BACKLINK PLACEHOLDER → suggestion: internal link to article #61, why niching down isn't risky / being recognisably for something beats being broadly impressive] Excellence is what keeps clients; recognisability is a large part of what gets them.

Novelty Is Exciting to Make and Risky to Buy

There's a specific version of this worth naming, because it catches ambitious people particularly hard: the work that's most creatively satisfying is often the most unusual, and unusual work is harder to hire. Pushing into new territory, doing something differently, solving a problem in a way you haven't seen before — these are precisely the projects that generate pride, and they're precisely the ones that give a cautious buyer less to hold on to.

From the client's side, hiring is a risk-management exercise as much as a quality judgment. They're spending money on an uncertain outcome, often with their own reputation attached to the decision, and what reduces that risk is evidence that you've reliably done this before. Novel work is weak evidence of reliability by definition — it's evidence you can do something new, which is a different and less reassuring proposition than evidence you can do their ordinary thing dependably. So the boundary-pushing piece impresses and doesn't reassure, and reassurance is often the deciding factor.

None of which means novel work is worthless. It builds your skill, it's frequently what makes the work worth doing at all, and it can attract exactly the small number of clients who want something unusual — which is a legitimate and sometimes excellent position to occupy. But it's worth being clear-eyed that pursuing novelty and pursuing broad hireability are somewhat different goals, and that the same client caution which makes impressive-but-unusual work hard to sell is the caution that makes clear, relevant, reliable-looking evidence so effective. The unglamorous, obviously-relevant piece isn't winning because clients have poor taste; it's winning because it answers the question they're actually asking.

What This Should and Shouldn't Change

The wrong conclusion here is to stop caring about the work — to conclude that since clients can't see craft, craft doesn't matter, and to optimise entirely for what's easy to sell. That's a route to work you don't want to do, for clients who don't value what you're good at, and it hollows out the thing that made you worth hiring in the first place. Quality still matters enormously; it's what makes clients stay, what generates referrals, and what makes the work sustainable to keep doing.

The right conclusion is narrower: separate what you make from what you lead with. Keep pursuing the difficult, satisfying work, because that's how you get better and it's frequently why you do this at all. But select what you present according to what the client you want is actually assessing — relevance to their problem, evidence of reliability, work that resembles what they need. Those two things can coexist perfectly well; the error is assuming that the ranking inside your head should determine the order things appear on your website.

There's an emotional adjustment in this too, and it's worth naming because the resentment is common. It's genuinely deflating when your best work goes unremarked while something routine keeps generating enquiries, and the instinct is to read that as the market failing to appreciate quality. It isn't; it's the market assessing a different question. Letting go of the expectation that pride should predict performance removes a persistent, pointless frustration — and it lets you make deliberate decisions about presentation rather than emotional ones. It's the same discipline as recognising that the thing you're best at can quietly become the lens that distorts your judgment. [BACKLINK PLACEHOLDER → suggestion: internal link to article #75, what made you successful will hold you back / your strengths become the lens that distorts what you see]