Headshot photo of Andy Chung

Andy Chung

Andy is a Canadian designer based in Berkeley, California. I'm currently building a more thoughtful professional platform called Read.cv with my friends Joey and Mehdi.

Checklist Check-Ins is an ongoing series that asks designers about their best practices, and their experiences using checklists.

I came across Andy's work when he shared his current project Read.cv on Twitter. After securing the 'george' username, I took a look around and loved what I saw. It's execution is right up my alley β€” minimal, clever, with delightful interactions all round. I wanted to learn a little more about Andy's approach and practices, and here we are.

So Andy, how have you shaped your design thinking so far in your career?

My time at art school was more formative and impactful than I care to admit. Not so much the curriculum but the prolonged exposure to experimental design and form making.

I love products that can seamlessly combine that raw quality of something new with the pragmatism of product design.

This is a feeling we are constantly chasing with Read.cv β€” small things like the way photos open by expanding inline can make a typical interaction feel unexpectedly fresh and differentiated.

Andy's 3 best design practices

Prototype quickly

Try to validate or invalidate solutions as quickly as possible.

Design openly

Ideas aren't precious, share them early and often.

Don't be afraid to start over

Especially when something isn't working.

Outside of your work, what’s a personal best practice you try to employ?

I'm fortunate that the Berkeley hills are just a few miles from my place. As a cyclist I make sure to get out at least a few times a week and take a ride through the roads and trails.

Climbing the local hills is a great way to step away from the computer for a bit and come back to what you’re working on with a fresh perspective.

Another small thing β€” I keep a kendama at my desk to fidget with throughout the day. It’s a nice analog thing to practice while working on programming or design problems. Oddly enough everyone who works on the Read.cv team also plays kendama!

Let’s talk checklists. Has a project ever gone wrong because you forgot something important? Could a checklist have helped you out?

Every launch could be improved with a checklist β€” there’s always a million things to keep track of and inevitably stuff gets lost. However I also always make sure to iterate on checklist items. Projects can fall apart at the very end when out of date checklist items are enforced.

You're going into a new project, and you can only use one checklist from Checklist Design - which one is it, and why?

Probably the social media brand checklists - it takes me forever just to write a tweet!

Want to know more about Andy?