Eric in his natural habitat

---

👋 Oh hey, I'm Eric!

I got into design because I couldn't stop obsessing over the covers of my school projects when I was eight. That's either a great origin story or a red flag. Probably both.

I studied design at SFU in Vancouver, where I got deep into print, architecture, and web, and ended up falling in with a group of people who wanted to build things. We did. Some of those things worked. I learnt a lot.

Since then I've spent 10+ years figuring out what kind of designer I am. The through line across every role was the same question: how do you design for the bleeding edge without losing sight of the person actually using it? I'm still excited by that tension. And what I've learned is that the answer almost always comes down to the team, whether everyone in the room is genuinely connected to making something better for the person on the other side of the screen.

I do my best work in small, scrappy teams: the kind where the designer, PM, and engineer are basically finishing each other's sentences. Less process, more momentum. I tend to blur the lines a bit: I'll get into the roadmap, build out the system, sometimes write the code. I stay late when I'm shaping the problem. I'm a lot less excited when the answer is already decided and design is just the last step.

When I'm not glued to a screen, I'm usually wrangling a toddler, which turns out to have a lot in common with product design: lots of negotiation, unclear requirements, and the occasional complete rejection of something you spent a lot of time on.

---

If you want to talk design, technology, or how many "r"s in strawberry say hello! (it's 3 right?) I reply to every email.