LLenny's Podcast
← All frameworks
Peak PerformanceGuillermo Rauch (founder and CEO of Vercel, creators of v0 a

Exposure Hours

Build taste as a trainable skill by quantifying time spent watching real people use products

Difficulty
Easy
Time to result
~ongoing to results
Steps
3
Confidence
92%

Rauch reframes taste from an innate gift into a muscle you develop by maximizing 'exposure hours' — deliberately tracking and increasing the time you spend watching people use your products and others'. The inertia is to stay inside your own head and assume everything works; exposure to the friction of real usage grounds and humbles you into better judgment.

Origin

Presented by Guillermo Rauch as one of Vercel's internal operating principles.

Core principles

  • 01Taste is a skill you can develop, not a trait you are born with
  • 02You systematically overrate how well your own products work
  • 03Watching real usage — yours and competitors' — trains the judgment muscle
  • 04Painful reality is more instructive than your assumptions

How to run it

  1. 1

    Quantify your exposure

    Track how many hours you actually spend watching people use your product and using rival products yourself, rather than assuming you already know.

    Pro tip Rauch colors his calendar so a set share of meetings are customer meetings — roughly a third in a given week.

  2. 2

    Put the product in front of a real person

    Hand your product to someone else and watch them interact with it instead of relying on 'it worked on my machine.'

    Pro tip Invite customers to demo live how they use the product to the exec team or whole company; you always discover an unknown pain point.

    Watch out You will feel the pain of seeing your baby break in front of everyone — that discomfort is the point, not a failure.

  3. 3

    Stay at (or define) the frontier

    Continuously try lots of products and study emerging trends so your reference set stays current and you can push design forward.

In the wild

Rauch's own weekly cadence

Rauch asks his team to color his calendar so he holds enough one-on-ones plus customer meetings; in customer meetings he tries to forget how features are built and just uses the products as a normal user, then works backwards from what he sees.

Roughly one-third of his meetings in the week were customer meetings, giving him a steady stream of grounded observations about real-world success and friction.

Common mistakes

Assuming it works because it works for you

Builders default to thinking everything is fine and fast because it ran on their machine; without watching others you never see where it actually breaks.

Treating taste as innate

Believing 'that person was born with taste' becomes an excuse not to do the reps of exposure that actually build the muscle.

Is it for you?

Best for

Founders, designers, and PMs who want to build product judgment and stop shipping based on internal assumptions

Not ideal for

Teams with no live users yet or those unwilling to sit through the discomfort of watching real usage

From the transcript

increasing exposure hours. Try to quantify how much time you expose yourself to watching how people use your products and you'll develop that muscle

01:00

taste sometimes I think we think of as like this inaccessible thing that oh that person was born with taste I see it as a…

1:08:30

Another aspect of exposure hours is that you tend to overrate how well your products work. It's very important to give your product to another…

1:11:00

From the episode

Everyone’s an engineer now: Inside v0’s mission to create a hundred million builders

Guillermo Rauch (founder and CEO of Vercel, creators of v0 a