Patrick Navarro

Code, Design, Security

Quality


Quality is caring.

For me, quality is the lens through which I experience every product, digital or physical. It’s also the lens I use when building.

Below are the principles I hold myself to.

Quality is a filter for all output

Continuously ask:

  • Does this improve quality?
  • Does this feel right?
  • What would a customer think?
  • Is this as simple as it can be?
  • Is this intentional?

Every detail matters. If something doesn’t pass the filter, it doesn’t ship.

Data is useful, but intuition matters more

I often see teams stall because they feel they need data to justify every decision. In practice, this slows momentum and rarely leads to better outcomes.

Data can inform decisions, but it shouldn’t replace judgment. People can almost always find data to support the story they want to tell, so ask the right questions of it.

Trust your sense of what feels right. Listen deeply to users, not just dashboards.

Hire people who care about quality

Look for taste and attention to detail during interviews.

You can usually see it quickly, especially in portfolios. People who care show it in their work.

Don't overcomplicate it

When in doubt, choose simple. Prefer usefulness over novelty.

Reduce options and configuration. Have an opinion. Avoid building everything for everyone.

Reduce handoffs

Co-create as early as possible.

It’s unfair and inefficient to expect teammates to go from zero to one hundred in a few days when they weren’t part of the journey or the context-building along the way.

Better than what was there before

Don’t ship mediocre experiences. Customers feel the difference and quality compounds.