Chemistry trains you to distrust an outcome you can't explain. If a reaction works, you need to know why, or you can't reproduce it. I carried that instinct into product design almost by accident, and it's shaped every project since: I don't trust a good number unless I can point to the decision that produced it.

That's mostly what my work has been for the last 6+ years: joining companies where the product is growing faster than the design function supporting it, and closing that gap. Sometimes that's meant building a component library so a team stops re-solving the same button for the fifth time. Sometimes it's meant sitting with a compliance team long enough to understand why a "simple" flow legally can't be simple. The common thread across Africhange, Alerzo, MBiller and Mzuri, in markets from Nigeria to Canada, the UK and Australia, isn't the industry. It's the same gap between what the product has become and what the design practice around it was built to handle.

I'm as comfortable owning a project solo, start to finish, as I am leading a team of designers through one. Mentoring has become a bigger part of my last few roles than I expected, and it's the part I'd be least willing to give up.

The chemistry habit that's stuck around longest: I write down the reasoning behind a design decision when I make it, not after. It's saved me more than once when a decision was questioned six months later and I could point to exactly why it was made.

Based in Nigeria. Open to relocation, hybrid or remote roles across Europe (NL, IE, DE, SE), the UK and North America.