By PYMNTS | July 10, 2026
In the high-stakes world of financial services, "digital transformation" has become the industry’s most overused buzzword. Banks and FinTech firms spend billions annually on cloud migration, AI-driven automation, and modernized payments architecture. Yet, the history of the industry is littered with expensive initiatives that failed—not because the technology was flawed, but because the human infrastructure couldn’t support the change.
Jay Michelini, Vice President of Product at Capital One Business, argues that the most critical phase of any transformation happens long before a single line of code reaches production. In an era defined by rapid technological shifts and rising customer expectations, the ability to shepherd people through change is the ultimate competitive advantage.
The "Why" Before the "How": The Foundation of Change
The traditional model of corporate change is often top-down: an executive team identifies a gap, designs a strategy, and rolls out a directive. Michelini asserts that this approach is fundamentally broken. When leaders prioritize the "what" and the "when" over the "why," they inevitably encounter resistance, apathy, or confusion.
"You’ve got to lead with the ‘why,’" Michelini emphasized in a recent interview. For employees to truly commit to a new way of working, they must understand the broader context. Is the change driven by a shift in customer behavior? Is it a response to a new regulatory landscape? Or is it a fundamental pivot in the firm’s value proposition?
When employees understand the purpose, the change ceases to be an arbitrary burden and becomes a shared mission. This creates a cultural shift where the organization stops treating transformation as a series of isolated, painful events and begins viewing constant, agile adjustment as a permanent, healthy state of the operating environment.
The Anatomy of Ownership: Moving from Mercenaries to Missionaries
One of the most persistent traps for product leaders is the reliance on formal, executive-led communication. While an email from the CEO might announce a new policy, it rarely builds the internal conviction necessary for successful implementation.
Michelini advocates for a model of distributed leadership. Organizations gain significant traction when they identify "internal champions"—employees at various levels who are genuinely invested in an initiative. These individuals act as translators, articulating the practical value of a new system or product in a way that resonates with their peers.
"I think about creating missionaries, not mercenaries," Michelini said. "It’s very important to empower the teams to outthink you."
This philosophy shifts the internal dynamic. Instead of employees feeling like "mercenaries" hired to execute a task list, they become "missionaries" who understand the broader goal and are encouraged to innovate on how to reach it. This autonomy is vital in the FinTech space, where the complexity of the problems requires collective intelligence rather than rigid adherence to a pre-set plan.
Breaking the Silos: The Collaborative Imperative
Organizational change frequently falters when departments—product, engineering, compliance, and legal—operate as isolated checkpoints. In a traditional "waterfall" model, one team finishes a phase and hands it off to the next. This creates friction, delayed feedback, and a lack of shared responsibility.
Michelini suggests that the most effective leaders break these silos by bringing cross-functional partners into the decision-making process at the very beginning. By the time a project reaches the execution stage, it should not be a "finished plan" being presented to others; it should be a co-created strategy.
Leaders can evaluate the health of this collaboration by asking probing questions during project reviews:
- Were operational and compliance teams consulted in the discovery phase?
- Is this the first time a key stakeholder is hearing about the initiative?
- Are we solving problems collectively, or are we simply passing the buck?
If the answer to the last question is "passing the buck," the project is likely on the path to failure. True collaboration means that everyone, from the product manager to the risk officer, feels a sense of ownership over the final outcome.
Listening as a Strategic Asset: Beyond the Dashboard
In the modern enterprise, managers are inundated with dashboards. They track velocity, sprint completion, bug counts, and revenue impact. While these metrics are essential for operational health, they are notoriously poor at capturing the "human pulse" of an organization.
"Instead of asking where a project is at, ask, ‘How do you feel about how progress is going?’" Michelini suggested.
This simple shift in framing exposes issues that traditional reporting overlooks. A team might be meeting all their deadlines, but doing so through unsustainable overtime or by suppressing vital feedback about architectural risks. When leaders prioritize the "how do you feel" conversation, they gain visibility into morale, burnout, and systemic bottlenecks that quantitative data obscures.
Michelini emphasizes the importance of stepping away from the desk to gather this intelligence. "I just spent time visiting with our sales team… It was so eye-opening to sit with them firsthand," he noted. "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."
Chronology of Effective Organizational Change
To successfully navigate a period of transformation, leaders should follow a structured, human-centric timeline:
- The Context Phase: Before announcing changes, leaders must socialize the "why." This involves deep listening sessions with cross-functional partners to ensure the strategy is grounded in reality.
- The Co-Design Phase: Bring diverse stakeholders—legal, risk, sales, and operations—into the room to help shape the solution. This builds early buy-in and ensures that diverse perspectives are accounted for before the plan is finalized.
- The Empowerment Phase: Identify and empower internal champions. Let the message propagate from the bottom-up, rather than just the top-down.
- The Feedback Phase: Establish a cadence of qualitative check-ins. Use "How do you feel?" conversations to identify friction points that dashboards fail to flag.
- The Iteration Phase: Be willing to change the course of travel. A leader’s conviction should be strong, but their commitment to a specific plan must be flexible enough to accommodate the lessons learned from the field.
Implications for the FinTech Sector
The implications of this leadership style for the broader financial sector are profound. As FinTech companies scale and traditional banks adopt more aggressive digital strategies, the competition for talent and market share will only intensify.
Organizations that treat employees as a resource to be managed will struggle to compete with organizations that treat employees as partners to be empowered. The "missionary" culture, as described by Michelini, is inherently more resilient. It allows companies to move faster, pivot more effectively in response to market changes, and—perhaps most importantly—retain the high-level talent necessary to execute complex digital transformations.
Furthermore, as regulatory scrutiny increases, the integration of risk and compliance teams into the early stages of product development is no longer just a "best practice"—it is a necessity. By breaking down the walls between these functions, firms can move faster while simultaneously reducing the risk of costly, late-stage project failures.
Conclusion: The Humility of Leadership
Ultimately, Michelini’s message is one of humility. The era of the "all-knowing" executive who dictates every move is fading. In its place is a new model of leadership characterized by curiosity, active listening, and a willingness to be wrong.
"I don’t have all the answers," Michelini admitted. By modeling this transparency, he encourages his teams to speak up, challenge assumptions, and take ownership of their work.
Transformation, in the final analysis, is not about the technology you buy or the software you deploy. It is about the environment you create. When employees feel heard, when they understand the mission, and when they are empowered to contribute their own perspectives, the technology succeeds—not because it was forced upon them, but because they built it themselves.

