Systemic Shifts for Sustainable Product Success in Finance

This episode of Product Thinking, by Product Institute, dissects the intricate realities of building products within large, established financial institutions. It moves beyond the superficial allure of digital transformation to reveal how true progress hinges on fundamental shifts in people, culture, and operating models. The core thesis is that sustainable product success in these environments requires a deep, systemic understanding of how decisions cascade, how incentives shape behavior, and how long-term vision can overcome immediate pressures. Hidden consequences emerge when companies prioritize quick wins over foundational changes, or when compliance is treated as an afterthought rather than an integrated partner. Leaders, product managers, and anyone navigating complex, regulated industries will gain a strategic advantage by understanding these layered dynamics, enabling them to build more resilient, mission-aligned products and organizations.

The Slow Burn of Transformation: People, Process, and Patience

The narrative surrounding digital transformation often centers on shiny new technologies. However, Marco De Freitas and Amber Brestowski from Vanguard cut through this by emphasizing that the real transformation is fundamentally about people and culture. This isn't a superficial change; it's an end-to-end systemic shift that requires a deep understanding of the operating model, encompassing everything from agile practices to DevSecOps. The immediate benefit of such a transformation is the promise of modernization and agility, but the hidden cost lies in the multi-year, multi-hundred-million-dollar investment required. This extended timeline means that maintaining clarity on the vision and tangible outcomes is paramount. Without constant reinforcement of goals--like Vanguard's focus on transforming client experience (CX), building resilient platforms, and driving agility--teams can become disillusioned. The success of such an endeavor, therefore, is not measured solely by technological adoption, but by the sustained commitment to these foundational elements.

"We call it digital transformation, but my first lesson is that it's not about digital, it's not about technology, it's actually about the people. It is about the culture that you're building that is really the transformation."

-- Marco De Freitas

This systemic approach extends to how work is aligned. Vanguard links its business strategy directly to product strategy by setting clear incentives and problems for product teams. The focus shifts from prescribing features to empowering teams to solve specific outcomes. For instance, by framing the challenge as "removing financial barriers that get in the way of saving in a retirement plan," product teams were free to innovate, leading to a financial wellness experience with an unusually high completion rate. This demonstrates a second-order positive consequence: by empowering teams with a clear problem and aligning them via an OKR framework, the organization fosters ownership and drives outcomes that directly support its mission of making investors more successful. The conventional wisdom of dictating solutions fails here; instead, the system responds to problems framed with strategic intent.

Funding Capacity, Not Projects: The Long Game of Ownership

Jameson Troutman of Chase highlights a critical systemic shift required in large organizations: moving from funding discrete projects to funding product capacity. The immediate allure of project-based funding is the clear deliverable and timeline. However, the downstream effect is often a fragmented approach, where teams lack the stability and ownership to truly iterate and optimize. Troutman advocates for distributing capacity across product architecture, empowering teams to prioritize within that capacity. This approach creates a delayed payoff. While it might feel less controlled in the short term, it fosters stronger product judgment, better prioritization, and faster learning loops over time. The competitive advantage emerges because this model requires trust and a willingness to let teams closest to the customer make decisions, a path many organizations find difficult to embrace due to a preference for centralized control.

The challenge lies in balancing immediate business unlocks (revenue, reduced complaints, cost savings) with the long-term health of the product and customer experience. Troutman emphasizes the need for product managers to be transparent about these trade-offs, owning their point of view. For example, deciding whether to launch a feature that provides immediate customer value but creates an "awful experience" for an internal banker requires careful consideration of the entire system.

"What we tried to do as a first order principle was move away from this idea that we've been identified a thing we want to go do, budget for it and then deliver it. And when we flipped it to, and the mindset we really focused entirely on was how do we want to distribute the capacity that we have across the organization..."

-- Jameson Troutman

This shift from project funding to capacity funding is not merely an operational change; it’s a strategic one. It requires upfront alignment on key results and outcomes. Investing time in this alignment, though potentially uncomfortable in the moment, unlocks significant speed and empowers teams to make smaller, more informed decisions downstream. The conventional wisdom of defining every feature upfront fails because it doesn't account for the emergent nature of product development and the learning that happens when teams are empowered to own a domain.

Compliance as a Partner: Building Trust Through Integration

Vishal Kapoor of Affirm addresses a common friction point in regulated industries: the perceived adversarial relationship between product teams and legal/compliance departments. The immediate impulse is to view compliance as a blocker, a hurdle to overcome. However, Affirm’s approach treats legal and compliance as embedded partners. This integration, happening from the outset of product development, creates a delayed but powerful payoff: responsible innovation at scale. By proactively involving these functions, teams avoid costly rework and build products that are not only functional but also trustworthy and compliant.

This partnership is facilitated by a weekly cadence of product reviews where teams present key problems, fostering alignment and shared understanding. This consistent dialogue ensures that constraints are identified early, preventing the system from routing around intended guardrails. The "jazz" analogy is apt here: while there's improvisation and creativity, there's also a shared understanding of the "set list" and the inherent constraints.

"We actually see compliance and legal as very, very important part of the product development process. In fact, we lean on them to get the subject matter expertise and then partner hand in hand and understanding where can we go, what should we be aware of and what are the different inputs that we should be thinking about ahead of time so that we don't go five weeks in developing a thing and then realize, oh my goodness, I should have known this beforehand, right?"

-- Vishal Kapoor

The quantitative rigor at Affirm, with daily dashboards tracking business, product, and quality engineering metrics, further supports this integrated approach. Product managers are expected to be data-informed, using these metrics to understand performance and identify issues. This data-driven culture, combined with the collaborative model for compliance, ensures that innovation is not stifled but guided, creating a sustainable path for growth in a high-stakes environment. The conventional wisdom of isolating compliance leads to delays and missed opportunities; integrating it unlocks speed and builds foundational trust.

Key Action Items

• Shift from Project to Capacity Funding: Re-evaluate current budgeting models. Instead of funding specific projects, allocate budget to stable product teams based on domain or capability. This requires a longer-term view, with payoffs realized over 12-18 months as teams gain ownership and optimize their work.
• Embed Compliance and Legal Early: Integrate legal and compliance stakeholders into the product development lifecycle from the initial discovery phase. This immediate discomfort of early engagement will pay off by preventing costly rework and ensuring regulatory adherence, building a stronger, more trustworthy product.
• Define Outcomes, Not Features: Clearly articulate the business and customer outcomes desired, then empower product teams to determine the best solutions. This requires patience, as the optimal solution may not be immediately apparent, but it fosters innovation and ownership.
• Establish Regular, Cross-Functional Review Cadences: Implement weekly or bi-weekly forums where product teams present problems, proposed solutions, and key decisions for feedback and alignment. This consistent dialogue, though demanding in the short term, ensures strategic alignment and faster decision-making.
• Communicate Transformation Progress Transparently: For multi-year transformation efforts, establish clear goals and communicate progress, including setbacks, regularly. This manages expectations and maintains team morale, crucial for long-term success.
• Develop a Data-Informed Culture: Ensure product managers and teams are deeply familiar with key business, product, and quality engineering metrics. Regularly review dashboards and use data to inform decisions, creating a feedback loop that drives continuous improvement over quarters.
• Foster a "Problem Owner" Mindset: Encourage product teams to think end-to-end, understand the P&L, and feel accountable for outcomes in partnership with business stakeholders. This requires a cultural shift towards shared ownership, with the payoff being more resilient and impactful product development.