Category Archives: customers

Make Wine with Me: How to Use Small Wins to Build Trust Between Partner Companies

Douro Boys is a group of five independent wineries in the Douro River Valley in Portugal that built an alliance network after realizing that they could not compete on their own. The partners act almost as a single firm, sharing knowledge about wine making and markets. Their wines, such as “Quinta do Vallado” or “Niepoort” now routinely get over 90 points by the Wine Spectator and sales have doubled over the last ten years.

As I write in a recent Harvard Business Review blog post, they achieved this through an unusual exercise: the CEOs of the five companies decided to pool a small amount of their best wine to make 500 bottles of a one-off premium wine they called the “Douro Boys Cuvee”. They auctioned the bottles off at Christie’s at an average price of 300 euros, a price that put the Portuguese wine on par with high-end Bordeaux. The success of this small joint project instilled a strong sense of collective achievement among the member companies, which helped them to work on other projects much more effectively.

Douro Boys solved the problem of trust building among alliance partners by achieving a small win, an initiative (or a small number of initiatives) that partners can accomplish within a maximum of twelve (or even six) months after starting collaboration. We are not talking about conquering a new geographical market or investing millions of dollars in joint R&D. A small win can be as simple as winning a new client together or modifying an existing product to serve a small new customer segment.

When I started working on my book Network Advantage: How to Unlock Value from Your Alliances and Partnerships, I was often struck by how little attention alliance partners pay to the importance of small wins.  They tend to focus instead on mobilizing their stakeholders around big, audacious goals.

Setting such goals is important, of course, but you first need to develop trust. Otherwise, a partner will not share their knowledge or resources with you. And the small win is the shortest way towards developing trust: it helps partners to learn about one another and develop informal rules of collaboration. This leads to familiarity, familiarity leads to trust, and trust leads to improved information and/or resource sharing.

Here’s another example. N2build is a startup that wants to disrupt the construction industry by using new composite materials. For example, some of the innovative fuselage material in a Boeing Dreamliner could also be used to make wall panels or roofs for houses. The new composites have higher insulation properties, are more resistant to the elements and, after substantial R&D, can cost much less to manufacture than conventional building materials.

N2Build has a large network of R&D alliances: it collaborates with researchers at the Fraunhofer Institute in Germany, Massachusetts Institute of Technology, and INEGI (National Institute of Mechanical Engineering and Industrial Management), the eminent Portuguese research institute.

But researchers are often not the best collaborators: they tend to prefer to work on solving problems within their academic disciplines without engaging in cross-department collaboration. What’s more, institutions like these are accustomed to working with multinational corporations or space agencies rather than startups. INEGI in particular was skeptical of N2build’s ambitious goals. The small, yet decisive win for N2Build was to organize seminars within INEGI that brought together scientists from INEGI’s different departments to discuss the idea of how composite materials can disrupt the construction industry. The researchers later commented that it was extremely unusual — as a matter of fact, a first in INEGI’s 25 years history — to have people from all around the institute together in the same room brainstorming towards a common goal. The event was a turning point for INEGI.  It is now an integral part of N2build’s R&D activities and has opened doors to other scientific collaborations.

Correos, the Spanish postal service operator, uses the same strategy to build partnerships in the e-commerce domain. It collaborated with Luis Krug, a Spanish Internet entrepreneur and now the CEO of Pixmania, to build an e-commerce platform The goal is to become one of the largest online marketplaces in Spain to connect companies of any kind, including small or very large retailers, to their customers. But before the two companies joined forces to work on Comandia, they started with a small win: collaboration over the website. This was a discount webshop started by Luis Krug in 2009 on which Correos worked as a logistics partner and had to adapt its logistics chain in order to handle a wide variety of products. The two partners learned a lot about each other and developed trust, which then lead to Comandia, a much more ambitious project in terms of the number of potential sellers and customers.

If your company is planning a strategic alliance, aim for a small win first — this strategy works just as well with customers, suppliers, and competitors.

Can Your Alliance Network Lift a Stealth Bomber Off the Ground?

Does this airplane look familiar?
1940s Stealth Bomber Image
Source: Wikipedia
As I recently wrote on Harvard Business Review blog network, it should, because it’s a predecessor of the famous Stealth Bomber, a prototype completed by Jack Northrop’s company in 1948. In his time, Northrop — the inventor of the flying wing concept — was considered to be the aerospace genius, but he was not able to deliver on his promise to the U.S. military. The revolutionary airplane you never got beyond the prototype.
In 1980, Jack Northrop, then age 85 and confined to a wheelchair, visited a secure facility to see the first B-2 Stealth Bomber — the most advanced military aircraft capable of flying at extremely high altitudes and avoiding radar detection.
1980s Stealth Bomber Image
Source: Wikipedia
Even after 40 years of technological development and use of sophisticated computer design tools, the new bomber looked like a replica of Northrop’s original design for the flying wing. Reportedly, after seeing the aircraft, Northrop said he now realized why God had kept him alive for so long.
So why did one model fail and the other succeed?  Part of the explanation can be found by comparing the different networks of alliances that Northrop’s company formed in the forties and in the seventies.
In 1941, his alliance network looked small and simple hub-and-spoke system. Otis Elevators worked on design, General Manufacturing and Convair provided production facilities. Notice that the partners don’t work with one another and the U.S. Army Corps was actually brought in to arbitrate a dispute between Northrop and Convair.
Northrup's Alliance Network, 1940s
In 1980, the alliance network was more complex and highly integrated.  Network partners worked with one another, jointly negotiating technical standards. Vought Aircraft designed and manufactured the intermediate sections of the wings, General Electric manufactured the engine, whereas Boeing handled fuel systems, weapons delivery and landing gear.   In addition, each main partner formed individual ties with other subcontractors specific to their areas of responsibility.
Northrup's Alliance Network, 1970s
As we discuss in our new book “Network Advantage”, networks like this have two main benefits.  First, alliance partners are more likely to deliver on their promises.  If information flows freely among interconnected partners, how one firm treats a partner can be easily seen by other partners to whom both firms are connected. So if one firm bilks a partner, other partners will see that and will not collaborate with the bilking firm again.
Second, integrated networks facilitate fine-grained information exchanges because multiple partners have relationships where they share a common knowledge base. This shared expertise allows them to dive deep into solving complex problems related to executing or implementing a project.
This is not to say that the hub-and-spoke network of the 1940s doesn’t have its uses. In fact, they are usually more effective at coming up with radical innovation than are complex, integrated networks. In a hub-and-spoke configuration it’s more likely that your partners will know stuff you don’t already know and combining new, distinct ideas from multiple spokes leads to breakthrough innovations for the hub firm.
But Northrop’s hub and spoke portfolio was not useful in 1940s, because he already had an innovative blueprint for the bomber. All Northrop needed to do was to build reliable manufacturing systems that would execute his ideas based on incremental improvements made by multiple partners at the same time.  That scenario called for the integrated network of the 1970s.
The key to choosing between the two types of network is to ask: do you already have a final idea that needs to be implemented with incremental improvements? Is it important that all of your partners trust each other and share knowledge in implementing your idea? If so, then the integrated alliance portfolio is right for you. If you are exploring different options and it is not critical that your partners trust one another, work together to develop and/or implement them, then the hub and spoke portfolio is the best.
You can read more about this and other network-related stories in my new book “Network Advantage: How to Unlock Value from Your Alliances and Partnerships”