Battle tested vs battle ready.

Early in my career, I built two websites for a guy at $100 each.

They were severely underpriced for the amount of work. I knew it. But I was desperate to build a portfolio, gain experience, and make money doing design.

And for what he was paying, I still made him happy with the work. That was the job. Do work good enough that the client is glad they hired you, hires you again, or refers you to someone else. Work good enough that you're proud to put it in your portfolio.

Around the same time, I entered more than 10 design contests. I lost every one of them.

Each brief had a specific goal and a hard deadline. I'd submit, wait, and lose. Then I'd study what the winning designers did with the exact same constraints I had. Same brief, same timeline, better decisions. Losing stung every time. But seeing those decisions side by side with mine taught me more than any tutorial ever did.

Targets that don't shoot back

A soldier can spend years training in the relative comfort of boot camp. Running drills, studying tactics, practicing on targets that don't shoot back. Then they step onto an actual battlefield, and everything changes. The stakes are real, the conditions are messy, and no drill fully prepared them for it.

I've never been to war, so I'll hold the comparison loosely. But design has its own version of this, and I know that one well.

Battle ready means you've trained. Courses, tutorials, polished Figma files. All good things. I had almost none of them when I started. My preparation was some Photoshop knowledge from a high school photo class and an art background from years of art classes. I got ready by getting tested.

Battle tested means you've done the work with real stakes. A client paying real money. A deadline someone's business depends on. A product shipped to customers who tell you exactly what they think of it.

The difference lives in small moments. Learning to give credit when it's due. Learning to push back in a meeting when staying silent would be easier. Learning to say the uncomfortable thing in a debrief. Pouring hours into something and hearing a client say "it's a good start."

That last one still stings when it happens. It also teaches you how to take a hit, ask better questions, and come back with stronger work. No tutorial covers that.

You can't practice those moments alone in Figma. You earn them.

The one-minute read

When I look at another designer's profile or portfolio, I can usually tell within a minute whether they've been through it.

It comes through in the details. How they present themselves. How they talk about past projects. What they choose to show and what they leave out. There's a refinement that only shows up after you've done the work for others, over and over, under real conditions.

Clients see the same thing. When they're deciding who to hire, they're looking for evidence that you've done this dance before. That you've worked inside the mess of teams, difficult personalities, and business demands, and still delivered. They want proof you didn't learn design only from books and YouTube.

My client work today isn't all that different from those $100 websites. The stakes are higher. So is my confidence. Because I've done this many times now, and I know what's required.

Tested, but invisible

If you've been designing for 8 or 15 years, you're already battle tested. That part is done.

The problem is that nobody can see it.

Your hardest projects live in old Slack threads and shipped products with no public story attached. A client considering you has no way to know about the deadline you saved or the feedback you survived. Your experience is real. It's just invisible.

So the question is how to make your experience visible to the people deciding whether to hire you.

If you have 15 minutes today

Make a list of the 3 projects you're most proud of. Pick ones that required real communication with a client or a team, where the outcome had real consequences.

Then write about what made you proud of each one. Where were things at when you started? What got hard? What did you do about it?

Odds are, those stories will show exactly how battle tested you are. Post one of them. Put one in your portfolio. Tell one on your next client call.

You already paid for these lessons with years of work. Telling the story costs you 15 minutes.

One question before you go

Which project proves you can deliver under real conditions, and could a potential client find that story anywhere right now?

If they can't, your experience isn't working for you yet. Every client I've worked with found me because something I shared made my experience visible before we ever talked. Clients hire the experience they can see.

Talk soon,
Trevor Nielsen

PS: If this edition helped, share it with a designer who's been doing great work for years without talking about it. They can get the full series at discoverabledesigner.com.