Hello. I'm Daniel Ritzenthaler. Most people call me Dan or Ritz. I've been a designer since 2002. Along the way I've explored several research and management roles.

Recently, I was with Iora Health for five years. Our web development group was small enough to require wearing several hats. I managed their design team. I designed interfaces and, for a short time, managed a development team. I started as the second designer with seven clinics in a handful of cities. I left when they had 49 clinics all over the country.

Previously, I was with HubSpot. I helped establish an early design system and build their original design and research teams. I started as the second designer and left a few months before the company went public.

The problem with problems

Don’t talk about problems (or solutions). Instead, talk about progress. Only then can we be precise without dictating implementation details.

Writing a good objective

Working with abstract concepts doesn’t make us more strategic. It doesn’t mean we understand the big picture. It doesn’t mean we’re doing something more valuable.

Interface design values

Clarity above all. Efficiency when interfaces are clear. Consistency when interfaces are efficient. Beauty when interfaces are consistent.

Is asking why always the best strategy?

There’s such a thing as getting down to the root problem too quickly, particularly when it comes to product design. The value in figuring out the “Why?” behind things isn’t quite as much about the destination as it is about the journey.