Let's Chat
You're Not Designing, You're Solving Problems

You're Not Designing, You're Solving Problems

Peter Deltondo
Peter Deltondo·5 min read

Most people review design like art. Good. Bad. Pretty. Not my style.

Truth is, your website, product, or brand doesn’t operate like art in the real world.

The appropriate question is simple. Is it working? Does it achieve the outcome you desire?

The target is the job.

Every homepage has a job. Landing pages have jobs. Pricing pages have jobs.

If your job is “book a call” then good design looks one way. It consistently leads the right people to take that action. If your job is “reduce support tickets” then good design looks different. It makes the next step crystal clear and eliminates friction.

Taste is (somewhat) irrelevant. Results are not.

Where design-first falls short.

Agencies often jump straight into visuals, attempting to justify them later. And it feels productive! It feels like motion. It looks good on your portfolio.

But design-first leads to many problems:

  • You optimize for founder preference instead of customer need.
  • You commit to a direction before identifying what isn’t working.
  • You end up “polishing” something nobody can understand.

Strategy should establish the target. Design should focus on hitting it.

We treat design like a science.

  • Identify the target (what needs to change)
  • Define friction (what is preventing it from changing)
  • Create clarity (what needs to be clear within 5 seconds)
  • Validate with actual data (behavior, not opinions in a conference room)

Never once do we define the end goal as, “we need a good design.” The end goal is always the outcome.

Sometimes it’s something minor.

  • Removing a headline that directly conflicts with visitor intent
  • Crafting a CTA that removes any ambiguity
  • Changing a form field that asks 1 less question
  • Tweaking page layout to answer objections in the proper sequence

All of these increase conversion rates not because they’re trendy, but because they remove friction.

The “make it look better” trap.

Here’s a conversation that happens in conference rooms everywhere, every week:

“The site doesn’t feel right. Can we freshen it up?”

That request sounds reasonable. It even sounds strategic. But it’s not a target. It’s a vibe. And vibes don’t convert.

When a team starts a redesign because something “doesn’t feel right,” the project almost always drifts. Scope inflates. Timelines stretch. And six months later, you have a new site that looks different but performs the same, because nobody defined what “better” actually meant.

The alternative is to start with a question: what is the site supposed to do that it isn’t doing right now? Maybe qualified leads dropped 20% last quarter. Maybe visitors bounce from the pricing page at twice the industry average. Maybe demo requests come in, but they’re from the wrong audience entirely.

Those are real targets. And real targets produce focused work.

Design debt is real, and it compounds.

Most teams don’t think about design the way they think about technical debt. But the same principle applies.

Every shortcut you take in the interface, every “we’ll fix it later” compromise, every inconsistency between your marketing site and your product, it compounds. Users notice. They don’t always articulate it, but they feel it. And that feeling shows up in your metrics as lower trust, shorter sessions, and higher churn.

The tricky part is that design debt doesn’t announce itself. Your site doesn’t throw an error when your value proposition contradicts your hero image. Your app doesn’t crash when the onboarding flow creates more confusion than confidence. It just quietly underperforms, and you wonder why the numbers aren’t moving.

Treating design like a tool means auditing it the same way you’d audit your codebase. Where are the inconsistencies? Where is the friction hiding? What did we ship fast that we never came back to pressure-test?

“But our founder loves it.”

This is one of the most common and most expensive traps in design.

Founder taste is real. It matters. The people building the company should feel proud of what they put into the world. But founder preference is not a strategy. And when design decisions are driven by personal aesthetics instead of user behavior, you end up building for an audience of one.

The best design work we’ve done has always started with the same question: who is this actually for? Not who’s signing the check. Not who’s sitting in the review meeting. Who is the person landing on this page, and what do they need to understand in five seconds?

When the answer to that question drives the design, founders end up loving it anyway. Because it works. And working design feels great for everyone.

The five-second test.

We come back to this one constantly. If a first-time visitor lands on your page, can they answer three questions within five seconds?

  1. What does this company do?
  2. Why should I care?
  3. What do I do next?

If the answer to any of those is “not sure,” your design has a clarity problem. And clarity problems don’t get solved with a new color palette or a trendier typeface. They get solved by going back to the target and rebuilding from there.

This test sounds simple. It is simple. That’s why it works.

Run it on your homepage right now. Show it to someone who has never seen your product. Time them. If they can’t answer those three questions confidently, you don’t have a design problem. You have a communication problem. Design is just the delivery mechanism.

Validation is not a phase. It’s a habit.

Most teams treat validation like a milestone. Launch the site. Run a survey. Check the box. Move on.

But validation works best when it’s woven into the process, not bolted onto the end of it. We test assumptions before we open a design tool. We watch how real people interact with prototypes before we commit to a direction. We look at behavioral data after launch and treat it as the beginning of the next iteration, not the final grade.

This doesn’t mean every project needs a twelve-week research phase. It means asking the right questions at the right time. Before design: what do we know about what isn’t working? During design: does this solve that specific problem? After launch: did the numbers actually move?

The teams that treat validation as a habit consistently outperform the teams that treat it as a checkbox.

Stop reaching for the mascara brush.

If your product, brand, or website isn’t giving you the desired outcome, stop reaching for the mascara brush. Ask yourself: what is the target, and what is stopping you from achieving it?

Good design isn’t the one that wins awards. It’s the one that hits the target so consistently you forget it’s even doing a job. It fades into the background because everything just works.

That’s the standard. Not “does it look good?” but “does it perform?”

Want design that reaches a target? Start with the target.

More from Heyo