Product design is about decisions, not just deliverables.

Somewhere around year ten, I stopped thinking of myself as a designer and started thinking of myself as someone who helps teams make better decisions about their products.

Most products run into trouble before anyone opens a design tool. The problem definition is vague, the business case is assumed, and the team starts building before they have agreed on what success looks like. I try to get into that gap early — not to slow things down, but so things can move more clearly later.

I also think about the business side in a way that not every designer does. If a product does not create real value for the company, it gets cut eventually. That reality shapes every decision I make, not as a constraint but as a useful lens.

Working across very different markets taught me that assumptions travel badly. Bangladesh and Trinidad and Tobago are completely different economies, different user behaviours, different expectations. Moving between them permanently changed how I ask questions and how quickly I let go of thinking I already know the answer.

Most designers think primarily about UI and UX. Over twenty years I have built enough experience across design, frontend development, team leadership and business strategy that I do not fit neatly into one lane. I think about all of it together because that is where I have found I am most useful.