When You Stop Thinking in Features

Being a PM means wearing many hats.

Some days you’re Sales. Some days you’re Finance. Sometimes you suddenly become the Fraud team. And occasionally, you’re translating between engineering logic and business pressure.

In fintech, this gets amplified.

I’ve been in Lending.

Moved to Wealth.

Then into Digital Banking.

What surprised me wasn’t how different the products were. It was how much there was to learn beyond the products themselves. Risk, operations, finance, compliance, and the countless trade-offs happening behind the scenes every day.

And honestly?

That juggling didn’t happen across decades. Sometimes it happens in a single day. Lol.

Morning: discussing credit risk exposure. Midday: reviewing revenue impact. Afternoon: aligning roadmap with growth targets. Evening: debating onboarding UX and compliance implications.

It’s intense. And strangely, I enjoy it.

The Debate: Specialist vs Generalist

At some point, the question appears:

“Are you a specialist PM or a generalist PM?”

In fintech especially, specialization feels important. Payments expert. Lending expert. Fraud expert. Wealth expert.

Depth matters. Regulations are real. Complexity is real.

But over time, I’ve realized something.

These two ideas are not opposite directions.

They are different dimensions.

The more domains I explored, the more curious I became about how they influenced one another.

In lending, you learn about risk appetite and capital efficiency. In wealth, you learn about trust and long-term behavior. In digital banking, you learn ecosystem thinking. In accounting discussions, you learn real constraints , not theoretical ones.

When you’ve seen multiple systems from the inside, something shifts.

You stop thinking in features. You start thinking in consequences.

If we push growth here, what happens to risk? If we simplify onboarding, what happens to fraud rate? If we change pricing, how does accounting treat it? If we accelerate release, what compliance debt are we creating?

You begin to see product as a living system.

That perspective feels more valuable to me than a label.

Depth and Breadth Are Not Opposites

Earlier in my journey, I went deep because I was curious.

How does credit scoring really work? How does portfolio yield behave over time? How are accounting entries structured? How do fraud patterns evolve?

That depth builds credibility. But breadth builds judgment.

When you’ve touched different domains, you start recognizing patterns across them.

They look different on the surface. But underneath, they are all trade-offs between speed, risk, and value.

That realization changes how you make decisions.

What I’ve Learned Along the Way

1. Curiosity Is More Important Than Labels

You don’t need to be the deepest expert in every domain, but you need enough understanding to ask the right questions and connect perspectives.

2. Systems Thinking Is a Superpower

If you only optimize one part, you might unintentionally break another. Seeing the system makes decision-making calmer.

3. Generalist Doesn’t Mean Scattered

If you reflect often, extract lessons, and connect dots intentionally, you’re building perspective.

4. Leadership Is About Integration

It’s about helping different perspectives align:

• Risk being cautious
• Growth being ambitious
• Finance being careful
• Engineering being realistic

Leadership is often about helping teams move forward when different perspectives, priorities, and constraints collide.

Final Reflection

I’ve moved across lending, wealth, digital banking. Worked closely with all teams to understand the downstream impact of product decisions. Balanced risk, growth, compliance, UX, sometimes within the same day.

And I’m genuinely grateful for that experience.

Because now, when I look at a product problem, I don’t just see a feature request.

I see ripple effects.

And perhaps that’s what has shaped my perspective more than any title, domain, or label along the way.