Bring-Build-Buy Map Advances Strategic Partnerships in Innovation

The Bring-Build-Buy Map from The Designing for Growth Field Book, pg. 71

The Bring-Build-Buy Map from The Designing for Growth Field Book, pg. 71

This simple tool can be revelatory for a corporate innovation team and I have observed that repeatedly, but I have been particularly amazed how insightful it is for strategic partnering. It's far too common for internal groups to zoom past a conversation around capabilities, and it's astonishing how even more infrequent the conversation is for two teams who hardly know anything about one another (other than that they want to do the deal). It makes sense, of course. They feel like unspoken truths - "we all know what we're good at, right?" But, the reality is the deal-makers usually aren't on the innovation team, so when it comes time to execute we don't know what strengths are leveragable, or even who does, or wants to do, what. 

I watched this interaction play out between a client and a partner firm (an application developer) while facilitating a joint working session to plan in-market testing of a service. The session started with the "bring" side of the conversation, allowing the client team to talk through their most relevant, key assets, and also to hear what the partner firm thought belonged on that list– an eye-opening conversation. Then, both parties sorted out what capabilities needed to be created, and whether to "build" or "buy" those (i.e have the partner deliver them), allowing for transparent conversation about what was realistic and efficient for the project. The Bring-Build-Buy Map helped level all conversations to what was best for the service and for speed to market, instead of opening doors to territoriality. 

The Bring-Build-Buy Map puts collective assets (present and future) out in the open, and, better still, it allows them to be positioned and repositioned strategically to best fit the project at hand. It gives all parties the opportunity to raise points like, "I expected this, not that," and "We should own that." These conversations will strengthen any project team, whether comprised of all internal staff or multiple stakeholder groups. Give it a try.

- Clay Maxwell (@bizinovationist)