logo
Hi there 👋

I'm slowly chipping away at this updated portfolio site in between work, helping my amazing wife raise our toddler, and otherwise trying to live a rich and full life not bound to my computer. In the meantime, please excuse the mess, and thanks for taking the time to give my site a look.
Done

about me

I’m a little odd. While I really enjoy designing software, outside of work, I actually try to use technology as little as possible. Don’t get me wrong, I’m glad to have my phone and my computer, and I use them every day, but I’d much rather leave them in the car and go on a hike or grab a beer with a friend.

When it comes to product design, I get a lot of satisfaction out of taking highly complex bundles of technical mess and finding ways to present them to users in clear and useful ways. I love digging into complex problem spaces for the purpose of understanding them well enough to design helpful shortcuts and abstractions for users. In my mind, that’s a great way to sum up what a product designer does: “I learn how all this actually works so you don’t have to.”

meditations

When do we move on?

As a designer, I’m often asking myself questions like, “Is this good enough for now? Can we start putting this in front of users to gather feedback? This whole solution is based on a single assumption... is that okay for now?” It can often be hard to answer questions like this when you’ve spent so much time with your head down in the weeds designing a solution. My design director and I took to a whiteboard one day in an attempt to create a simple framework our team could use to make go/no-go decisions throughout the design process.
We came up with this diagram. Here’s the gist. Generally, when our confidence in a solution or an assumption is higher than the risk of us getting it wrong, we move forward. However, if the risk outweighs our confidence, we determine what we need to learn in order to raise our confidence to a tolerable level, and we put together a research plan. I’ll admit this isn’t incredibly precise and ‘Low’ and ‘High’ on either axis are subjective, but we’ve found it incredibly useful for facilitating meaningful conversations with our cross-functional team.
logo