Just wrapped up my 4th semester at Boston University's MBA program

Just wrapped up my 4th semester at Boston University’s MBA program - and this one was a ride.

I never really thought about risk management as a formal concept before. Diving into brand, legal, financial, and operational risk frameworks this semester made something click:

I’ve already been applying these ideas in my design and product work for years.

Every decision I’ve made, whether in UX, CX, or product strategy, they all came down to the same questions:

1. What’s the potential risk?
2. How likely is it?
3. What’s the cost of ignoring it?
4. Is it worth solving?

Turns out, I’ve been managing risk, I just didn’t call it that.

The module made that clearer because it did not treat risk as one department’s problem. Brand risk, operations risk, legal risk, and financial risk all connect. A product decision can sit in the middle of all four.

Take a checkout flow as a simple example. A confusing payment state is not only a UX issue. It can become a brand issue if customers stop trusting the product, an operations issue if support tickets spike, a legal issue if consent or disclosure is unclear, and a financial issue if abandoned payments compound over time.

That is why I kept seeing the overlap with product work. Designers often talk about friction, confusion, trust, and abandonment. Risk management gives those same observations a sharper business language: likelihood, impact, exposure, mitigation, tradeoff.

That language matters, especially when you need to argue for work that does not look urgent yet. Fixing a confusing flow before it becomes a support problem is not just polish. It is risk reduction.

Trying to enjoy the short break before summer semester kicks off. The finish line is in sight. Just need to keep pushing till December.

Honestly? I’ve really been enjoying the ride.