Learn Fast, Grow Faster: Book Review of Gorillas Can Dance

By — October 2, 2026

Oct 2, 2026 · @Sumit

Most R&D leaders share one quiet worry. Our teams are strong at what we already do, and the world keeps moving faster than our roadmaps. Startups look like the obvious answer, yet many corporate attempts to work with them fade after a pilot or a press release.

Gorillas Can Dance by Shameen Prashantham asks a better question than “should we work with startups?” It asks why the partnership is so hard, and what a large organization must build to make it repeatable.

For anyone who leads R&D, the promise is simple: learn fast from startups, then grow faster by turning those lessons into products.

The book in brief

Shameen Prashantham is a professor of international business and strategy, and Associate Dean (MBA), at CEIBS in Shanghai. His book, published by Wiley in 2021, draws on more than a decade of research across China, Germany, India, Israel, Kenya, South Africa, the UK and the US. The cases include Microsoft, BMW, Walmart, SAP, Unilever, Bayer, IBM and Intel, among others.

The structure is clean. Part One explains why corporations should partner with startups and why it is hard. Part Two covers how to do it. Part Three looks at where in the world to look and how to use partnerships as a force for good.

The phrase “dancing with gorillas” came early in his research, when someone he consulted told him that startups must learn to dance with large gorillas. The title turns it around: the gorillas have been learning to dance too.

Why: managers and entrepreneurs see the world differently

Chapter 1 starts with a useful distinction. Entrepreneurs begin with an opportunity and then go looking for resources. Managers are trained to make the best use of resources they already control. Drawing on James March, the book separates exploitation, which is using what you are good at, from exploration, which is building new capabilities. Large firms become very good at exploitation, and that strength is exactly what makes disruption possible.

The answer is not to turn managers into founders. It is for managers to act entrepreneurially, with proactiveness, innovativeness and risk-taking. Partnering with external startups is one of the clearest ways to do that. Startups can disrupt a corporation, but when managers engage the wider ecosystem, they become a source of co-innovation.

Chapter 2 explains why this is hard. The author calls it the Paradox of Asymmetry: the differences that attract the two sides, startup agility and corporate scale, are the same differences that make working together difficult. He names three asymmetries.

  • Goals: the two sides want different things, on different timescales.
  • Structure: it is hard to find a matching counterpart on the other side.
  • Attention: corporates cannot tell which startups deserve their time, and startups cannot reach the people who matter.

What stands out is that the book does not blame culture alone. It names concrete gaps, and each gap gets a concrete fix.

How: three pillars and a capability journey

Chapter 3 gives the core framework. Each pillar answers one of the three asymmetries.

AsymmetryPillarWhat it means in practice
GoalsSynergyState the win-win clearly, for both sides
StructureInterfaceGive startups one clear first port of call
AttentionExemplarCultivate early success stories that show what good looks like

Chapter 4 is the most practical for anyone building a team. Partnering is a process, not a one-shot event, and the corporation has to build the capability to do it repeatedly. The book describes three stages.

  1. Initiation: start small and specific. A subsidiary can begin without top-level blessing.
  2. Expansion: if the intent is serious, win buy-in from senior leaders and business unit heads, and bring in mentors from other departments.
  3. Systematization: align startup partnering with the company’s wider strategic and cultural transformation.

Along the way, dedicated teams help the organization refine, replace and add partnering practices over time.

Three cases that make the framework real

BMW Startup Garage. Created in 2015, it works like a funnel. Startups are screened step by step, and fewer finish than begin. BMW acts as a venture client: it connects startups with business units that could use them and helps them get a supplier number, which most startups cannot get alone. Two people carried the program. One was the approachable public face for startups. The other was an insider who handled internal politics. That pairing is a clean example of an interface that works from both sides.

Microsoft. BizSpark began in 2008, partly in response to open source tools, and gave startups software at no cost. Microsoft’s accelerators ran as cohorts, like an MBA class, where everyone goes through together and peer interaction creates serendipity. Over time the company combined top-down programs led from Silicon Valley with bottom-up efforts from managers in places such as Israel.

Walmart China. Walmart wanted speed, so it took a shortcut. It asked Microsoft’s accelerator for relevant retail tech alumni and ran a weekend hackathon with eight startups. Three went on to pilots, each completed within 60 days, with one pilot per startup at a time. Within a quarter something tangible existed, and it started as a subsidiary level initiative.

The cohort versus funnel contrast is worth remembering. Cohorts give you serendipity. Funnels give you predictability.

Where: partnering around the world, and for good

Chapter 5 asks where to find startups. Silicon Valley is only one dance floor. The book offers three approaches: think global, act local (adapting practices), think local, act global (adopting practices), and think global, act global (aligning practices). Using several of them helps established companies tap startup energy worldwide, especially in emerging markets.

In the author’s interviews, newer ecosystems tend to need more handholding because startups there are less familiar with corporate partnering. Local platform players, such as Baidu, Alibaba and Tencent in China, must be factored in. Governments matter too, at both national and local level. His example is IBM partnering with startups in Ningbo through a smart city program, in a city not known as a tech hub.

Chapter 6 widens the lens to the Sustainable Development Goals. When partnerships contribute to the SDGs, the benefit runs to the corporation, the startup and society. The author sees this as an overlooked facet of SDG 17, partnerships for the goals, and suggests sustainability may do for the 2020s what digitalization did for the previous decade. The book carries the three pillars into this space as societal synergy, inclusive interface and hybrid exemplar. I will leave the detail of those variants to readers of the book.

What this means for an R&D organization

The book gives a sharper way to think about learning speed. An R&D group learns through experiments. Startups can often run experiments faster, and they work in areas such as AI, sensing, software and new materials, where a mature engineering team may not yet have built depth. Partnering turns their experiments into our learning, and our scale into their growth. That is the learn fast, grow faster loop.

The three pillars translate well into R&D terms.

Synergy: name the technology gap. Before talking to any startup, write down which capability gap or product bottleneck the partnership should close, and what the startup gains in return, such as validation data, a reference installation or a route to market. A general wish to be innovative is not synergy.

Interface: one door. Startups should know who in R&D owns the relationship. That person needs credibility with engineers and the empathy to speak a startup’s language, while a colleague may need to handle internal politics, as BMW’s pair did. Procurement, IP and quality processes can be adapted so a startup can get through them without a year of paperwork.

Exemplar: one visible win. A single pilot with a measurable result, such as a shorter cycle time, a diagnostic that catches a failure early, or a controls feature that ships, will earn more attention from business units than any strategy deck.

The capability journey fits R&D just as well. Initiate with one small, time-boxed pilot. Expand by bringing business unit leaders and senior engineers in as mentors. Systematize by making startup engagement part of how technology roadmaps are built.

Where the book is thinner

No book fits every industry, and a good review should say so.

  • Digital lean. The best known cases come from software, digital and retail settings, where a 60-day pilot is realistic. In my view, hardware heavy industries face longer validation cycles, tougher safety and certification demands, and more sensitive IP, so pilot sizes and timelines will need adapting.
  • Non-equity focus. The author says most of his work covers non-equity partnering. Readers weighing investment or acquisition will need other sources.

None of this weakens the core framework. It means the book works best as a map to adapt, not a manual to copy.

Verdict and five takeaways

Gorillas Can Dance is a clear, research-backed framework for a problem most large companies recognize and few solve. Its biggest strength is naming three asymmetries and answering each with one pillar. The book closes on three mindsets for the journey: entrepreneurial, collaborative and global. For R&D leaders in hardware industries, the value lies in adapting the framework rather than copying the examples.

  1. Treat startup partnering as a capability to build, not a project to run.
  2. Write the synergy down before the first meeting.
  3. Give startups one clear door into the organization.
  4. Build an early exemplar and share it widely.
  5. Start small, expand with senior buy-in, then systematize.

Learn quickly from startups, then grow faster by making those lessons part of how the company builds.

References

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.