<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=1675378&amp;fmt=gif">

FinTech Partnership Series: Making Partnerships Work

Alliances are inherently about difference. Two organizations decide to work together toward common objectives because of - not in spite of - those differences. Whether they are differentiated capabilities, scale, or expertise, those very differences are what bring value to alliance relationships. For this reason, alliance success hinges not on our ability to sideline our differences, but on our ability to actively manage those differences.

So how do we manage these differences, and avoid the challenges of the most common approaches to collaboration?

A Common Approach: By jointly defining a strategy, and a plan to execute against it, we will effectively sideline our differences

Challenges with this common approach: Our differences are, in many cases, the very reason for collaborating in the first place. Organizations entering partnerships do so with often vastly different strategies, and with different organizational structures, processes, capabilities, and cultures. A focus on eliminating differences ignores the value that those differences can bring- it is these very differences that drive value for a partnership.

How might this common approach play out? Consider the launch of the fictional partnership between Goliath National Bank (GNB) and FinanceIt. First, the large bank and small technology company agreed on a strategy and a high-level execution plan.

G2 Making AP_Managing Differences 900px

Immediately, GNB deployed its large project management function, which began requesting, and frequently requiring, tons of input from FinanceIt. The requests overwhelmed the small tech company’s project team, which was accustomed to (and staffed for) the fast pace of a technology start-up versus the bureaucratic requirements of a large bank. The project stalled before it really even started, as the project team began spending all discretionary time either (a) pushing back on GNB’s requests or (b) pulling together information for GNB’s project managers.

Despite the best laid plans and partnership strategies, execution will fall short if we focus on a strategy and project plans alone, and sideline our differences.

A Better Approach: Focus on developing an effective working relationship that enables us to appropriately leverage one another’s differences to most effectively execute our joint and individual goals for the partnership.

Rather than exclusively focusing on executing the alliance’s business plan, pay attention to the working relationships that will enable success. Successful working relationships require more than clear decision-making lines or assigning responsibilities. An effective and efficient alliance partnership also requires:

  • Clear articulation and alignment on what you are trying to achieve by working together – both individually and jointly
  • Joint leadership manifesting the commitment to the goals of the partnership, and helping working teams to resolve the obstacles they encounter by re-focusing on these goals; and
  • On-going (re-)assessment and re-articulation of the alliance partnership as the best means to achieve those goals.

The “secret sauce” of alliance partnerships—and personal ones—is made when we share a common commitment, yet clearly recognize and respect one another’s differences. On that basis, we can have the difficult conversations that inevitably arise as we work together—and figure out with every new challenge how to play to each other’s strengths (and obviate each’s challenges) while we pursue the goals of the relationship.

G2 Making AP Work_Key Principles 900px.

Download The Article

This piece is part of our Fintech and Financial Services series.