Skip to content
Chimera readability score 71 out of 100, Expert reading level.

Every financial institution talks about transformation. The technical work may attract the headlines, but the organizational work often determines whether new initiatives succeed or stall.
Jay Michelini, vice president of product at Capital One Business, said successful change management begins before new software reaches production. The first responsibility for leaders is making certain employees understand why change is taking place.
“You’ve got to lead with the ‘why,’” Michelini told PYMNTS in an interview.
Within the FinTech space, new entrants, changing customer expectations and emerging technologies regularly reshape priorities. Leaders should acknowledge that constant adjustment has become part of the operating environment instead of treating each shift as an isolated event, Michelini said.
He also argued against relying solely on executive messaging. Organizations benefit when they identify employees who are genuinely interested in a particular initiative and can help explain its practical value across the business. Whether the subject is product modernization or a new payments capability, internal champions often carry more credibility than formal announcements alone.
Ownership also depends on showing employees how their work affects people beyond their immediate teams.
Michelini described three perspectives that help create that connection: understanding customer needs firsthand, appreciating how operational colleagues experience day-to-day work, and recognizing how competitive developments across the FinTech sector reshape expectations. Each offers a different reason for embracing change, making the discussion less abstract and more closely tied to daily responsibilities.
Michelini encouraged product leaders to spend time with customers and internal stakeholders rather than relying exclusively on reports or dashboards.
“I just spent time visiting with our sales team … It was so eye-opening to sit with them firsthand,” Michelini said. “You see different angles to a problem … You need to have conviction in the direction that you’re heading but be open to different perspectives and feedback that are going to change your mind or adjust your course of travel.”
Organizational change frequently falters when departments work independently rather than together, Michelini said. Instead of treating product, technology, operations, compliance and other functions as sequential checkpoints, leaders should use them to shape decisions from the outset.
Leaders can often tell whether collaboration is genuine by asking simple questions during project reviews. Were operational teams consulted early? Have legal and risk partners already weighed in? Is this the first time an executive stakeholder is hearing about a significant initiative? These signals reveal whether teams have been solving problems collectively or merely handing them to someone else.
Listening Reveals Problems Before Dashboards Do
Managers should also reconsider how they measure progress during periods of change, Michelini said. Delivery schedules and performance metrics remain important, but they rarely capture whether a team is under unnecessary strain or whether obstacles are beginning to undermine morale.
“Instead of asking where it’s at … [ask] ‘How do you feel about how progress is going?’” Michelini said. “That shift in framing gives you a better sense … that this may be moving forward, but it may not feel great to that team.”
The approach can expose issues that traditional reporting overlooks. Teams may technically be meeting deadlines while depending on excessive overtime or waiting for decisions from other parts of the organization. These conversations also help leaders identify where they can remove obstacles instead of merely monitoring them.
Cross-functional partners often provide another useful perspective because they work across multiple initiatives simultaneously, Michelini said. Functions such as legal, compliance, risk and product specialists can quickly identify where collaboration is working well and where projects are creating avoidable friction.
“I think about creating missionaries, not mercenaries,” Michelini said. “It’s very important to empower the teams to outthink you.”
At an individual level, “I don’t have all the answers,” he added.
Watch the full interview with Capital One’s Jay Michelini to learn more about:
- Why Michelini said frontline employees often provide the earliest warning signs that a transformation is drifting off course.
- How product leaders can use trusted delegates inside other business units to build stronger executive alignment.
- Why recognizing cross-functional partners before your own team can strengthen future collaboration.
- The practical difference between leading with certainty and leading with conviction.

Facts Only

Jay Michelini, vice president of product at Capital One Business, stated that successful change management begins before new software reaches production. Leaders must lead with the reason for change. Leaders should identify employees interested in an initiative and allow them to explain its practical value. Connection is created by understanding customer needs, operational experiences, and competitive developments. Leaders should involve departments like operations, compliance, and legal in shaping decisions from the outset. Managers should shift progress reporting to include team sentiment, asking how teams feel about progress rather than just where they are at.

Executive Summary

Successful organizational change is determined by leadership action preceding technical implementation. Leaders must establish the "why" behind transformations to secure employee understanding before new software is deployed. Within FinTech, constant adjustment due to new entrants and evolving customer expectations necessitates viewing shifts as ongoing operating environments rather than isolated events. Credibility in driving initiatives stems from identifying internal employees who can articulate the practical value across the business, rather than relying solely on executive messaging. Building this connection requires demonstrating how work impacts customers, operational colleagues, and competitive market shifts. Furthermore, change falters when functions operate independently; integration is necessary by involving departments early in decision-making to ensure alignment.

Full Take

The emphasis on leading with "why" over mere delivery metrics exposes a common failure point in large-scale change management: the disconnect between technical output and human buy-in. The reliance on executive messaging alone is insufficient because true organizational adoption requires tangible, relatable context; this suggests that abstract goals are insufficient drivers for behavior. The pattern of internal friction arises when functional silos operate sequentially rather than collaboratively, indicating a systemic preference for segmented accountability over integrated problem-solving. The recommendation to shift measurement from purely quantitative delivery schedules to qualitative emotional states reveals an underlying assumption: morale and strain are critical predictors of success that traditional performance indicators miss. This reflects a broader organizational pattern where visibility is often prioritized over authentic engagement, leading to downstream inefficiencies when change is mandated top-down without genuine cross-functional consensus. The suggested approach seeks to shift the locus of control from directive command toward empowered, context-aware ownership by leveraging internal expertise for navigation rather than simple execution.

Sentinel — Human

Confidence

This text exhibits strong human markers, characterized by direct dialogue, personal reflection, and a narrative structure built around lived experience rather than purely objective reporting.

Signals Detected
low severity: Varied sentence length and conversational flow typical of an interview transcript.
low severity: Passionate engagement and shift in perspective, suggesting genuine thought process rather than sterile balancing.
low severity: The structure flows organically from one point to the next, reflecting an evolving argument rather than pre-set talking points.
low severity: Specific anecdotes and direct quotes anchor the text in a believable human narrative.
Human Indicators
Use of direct, conversational quotation and personal reflection ('I just spent time visiting with our sales team...')
The weaving together of abstract concepts (change management) with concrete operational advice (asking 'How do you feel?')
The motivational tone and the use of metaphor ('missionaries, not mercenaries') suggest an authored voice.
Capital One Urges Leaders to Listen Before They Launch — Arc Codex