My philosophy

Unless it can be built, the design is useless.

Users will only interact with what’s shipped. I have cold-heartedly ripped apart some very pretty designs for good reasons, mainly the nightmare it would cause developers. Quality product design understands development constraints including timelines, data, and how it affects the underlying app.

Know when to use intuition vs data.

Designers should use quantitative analytics to view history and user research to validate a hypothesis. But there is never a perfectly straight path to shipping, so it’s important to rely on judgment and experience to save time.

Find the sweet spot in shipping velocity.

Redesigns take time and the best ones will last. Businesses who have figured design out know when to invest deep into the full process and when to get something out the door to fix a problem. Sometimes shipping now is more valuable than what you could ship in months.

Enable the team over doing everything yourself.

I’m guilty of preferring to go heads down and not get the team involved. While sometimes it’s needed, the strength of a team will flourish when seniors get juniors involved, peer reviews happen, and knowledge gets documented. It's the teaching moments that will test your knowledge of something complex.

Design is only as good as the rest.

Good design goes hand-in-hand with good copy, engineering, and all other parts of the business that come together to solve user problems. Everyone is collectively responsible for the end-user experience, especially my former but not forgotten pastime of security and privacy.