Exchanging Bricks for Jade at Business Network International



Last Friday I visited the Business Network International (BNI) team Draken (The Dragon) in Gothenburg. I have made a couple of visits to other BNI teams before and it has always been interesting experiences.

BNI is a business reference network. A BNI team in the network consists of up to 40 people. The group meets once a week for the purpose of exchanging business references.

What makes the teams work is that each individual represents a different kind of business. A team may have only one car salesman, one hairdresser, one IT service provider, one accountant...

An IT service provider never has to worry about an accountant stealing her business, or vice versa. On the other hand, the accountant might have customers who need IT services. The IT service provider might know of a company that wants to lease cars, and so on.

BNI team members provide each other with information that is of little value to the sender, but of great value to the receiver.

This is of course a feature of all trade. If you buy a bar of chocolate, you buy it because the value of the chocolate bar is greater to you than the value of the money you must spend to get it.

As with all business transactions, the exchange of business references in a BNI team works better the greater the difference in perceived value by the team members.

This may seem way to obvious to be useful, but it is often the obvious things we miss. Finding something you have that is of low value to you, but of high value to someone else, so that you can trade it for something of value to you is a basic negotiating technique.

For example, the thing that brings new people to BNI is the promise of business references, but once you visit a team, you will discover that a considerable part of the value is the sense of community within the team. Of course, that sense of community also drives the sharing of business references.

BNI teams have a fixed meeting agenda they may not deviate from. The same agenda is used by BNI all over the world. Within the framework set by their meeting agenda, there is a lot of freedom. It is a great example of complex, intelligent behavior, that arises from a simple set of rules. You can see the same thing in an Agile (Scrum, XP, etc.) software development team that works well, or in some network based companies, like the famous Semco, W.L. Gore & Associates and Richard Branson's Virgin Group.

Managers and management consultants are like chess players: We look for patterns. When I first visited BNI I recognized the strategical set up as Exchanging Bricks for Jade, one of the Chinese 36 Stratagems. BNI calls the idea Givers Gain. One of the things givers gain in the BNI community is trust. Trust is valuable currency, because if people trust you, they will give you references.

Here is a diagram showing how it works:


Thus, the more you give, the more you gain. It is a nice reinforcing loop. I do like the setup. A lot. BNI does of course add a lot of tweaks to the basic process in order to strengthen the reinforcing loop above.

Comments

Post a Comment

Popular posts from this blog

Waterfall vs. Agile: Battle of the Dunces or A Race to the Bottom?

Image
The major software methodology wars since the mid 1950’s. Someone was wrong on the Internet, so here we go… In a recent HBR article, It’s Time to End the Battle Between Waterfall and Agile , the author sets up a false premise: There is a war between Waterfall methodology and Agile. The war must end. And finally, you can combine the approaches to get the best of both worlds. This sounds good, but the article is based on a misunderstanding of both Waterfall and Agile. Also, there is no war between Waterfall methodology and Agile. There can’t be, because Waterfall methodology does not exist! Waterfall is a name for large projects that failed in the 1960’s. Waterfall was never a methodology, but a failure to apply the methodologies that existed back then. As I will show towards the end of this article, at least one of the “successful” Waterfall projects mentioned in the HBR article was neither successful, nor a Waterfall project. I got invaluable help from Alistair Cockburn. He fact che...
Read more

Performance Evaluations, Business Strategy, and Agile Methodologies

Image
It is performance evaluation time in many companies. This can be stressful, both to the people being evaluated, and the people doing the evaluation. In companies adopting agile software development methods, the tension can be extraordinary. Individual performance evaluations run counter to agile philosophy, which emphasizes team performance over individual performance. However, managers and corporate leaders need to take a few steps back, and consider the impact performance evaluations have on the organization as a whole. Especially now, in the midst of a recession, it is important to look at a companies current policies to see if they can be improved, or if they are actually holding the company back. So, how can a manager evaluate policy? Performance evaluation policies can serve as an excellent example. I'll confine myself to discussing the so-called ‘rank and yank’ methods. These are performance reviews were employees are ranked using a forced ranking system. It usually looks so...
Read more

Agile Requirements Structures, Part 1

Image
If you have worked in large Agile projects or programs, you may have noticed that there is often quite a bit of confusion about requirements, what the requirement types are, their purpose, how to write them, how to use them, and above all, what not to do with them. There are many causes for this confusion. Here are some of the more common I have seen: Nobody in the organization has read up on the requirements model it is using, so everyone makes their own interpretation. The organization deviates from a standard requirements model, but nobody knows which standard model the organization is deviating from, and/or there is no agreement about how they deviate from it. The organization has not documented its own requirements model very well. The organization mixes two or more different requirements models, often without realizing it. The organization has documented its requirements model, but finding the documentation is an epic project in itself, on par with when Henry Sta...
Read more