High-Trust Networks and High-Performing Teams

High-Trust Networks and High-Performing Teams

In an earlier blog I introduced the distinction between high-trust networks and low-trust networks as a key principle for understanding the topology of work, be it in the private or public sector, for profit or not-for-profit.  High-trust networks put the bulk of their resources into getting the most out of the people on the ground with little to no investment in checks and balances, supervision, regulations, or the like.  They rely instead on aligned values, self-discipline, and a clear sense of True North.  When they work well, they accomplish amazing things. 

Low-trust networks, by contrast, invest significantly in checks and balances, supervision, and regulations because they want to prevent the misappropriation of resources.  In zones of conflict, where there is no True North to be found, they are key to maintaining order and security.  Elsewhere, they are a defense against corruption and other abuses of power or position.  They are much less effective and efficient than high-trust networks, meaning they can only deliver on a small part of the mission that led them to get funded in the first place, but they can operate under conditions in which a high-trust network cannot.

In Silicon Valley, and particularly in venture-backed companies, the focus is overwhelmingly on building high-trust networks to create high-performing teams.  In general, the conditions and culture here are highly supportive of this, but there are two recurrent failure modes which team builders need to watch out for vigilantly and address immediately if they come up.  The first is the free rider syndrome, someone who enjoys the empowerment of being in a high-trust network but does not contribute the extra capability or effort necessary to achieve extraordinary outcomes.  The network itself will identify this person and “route around them,” so that in the short term you can still get lots of good work done.  But if the situation is allowed to persist, the rest of the team will get tired and then resentful of this overhead tax on their efforts, and performance will drop.  The intervention is simple: the team leader must simply expel the free rider from the team.  Empowerment comes with responsibility—if you don’t deliver, you’re out.  This doesn’t mean you are fired.  It just means you are no longer part of this team.

A more subtle challenge to face is the presence of a low-trust operator inside a high-trust network.  This person is not untrustworthy—they are simply low trust.  At the margin, that is, they will hoard resources, sand-bag performance objectives, and take credit wherever they can, not because they are bad people but because they assume that is what everybody else does.  Often these people are extremely competent and can get a ton of stuff done, so again, in the short term this can work out OK.  Longer term, however, they undermine the high-trust network culture, diminishing its capacity and performance, so again, they have to be identified and expelled.

In both these cases, however, team leaders who believe in empowerment often have trouble seeing the problem and making this call.  Their instinct is always to give everyone another chance to show their best stuff—that’s why they do not supervise intrusively and give lots of leeway to personal style.  That’s why high trust networks form around them.  But in the case of free riders and low-trust operators, the people involved are very good at managing up to show themselves to best effect.  So team leaders can’t rely on their personal experience with them as reflective of their overall behavior.  Instead they must learn to take signals from these people’s peers in the network, as solicited and surfaced by a third party, typically via a 360 peer review.  Then, when the signals come in, team leaders have to act on them without waffling.  Again, these are not firing offenses—you just have to take the person out of the line of fire.  But you have to do it decisively in order to signal to the everyone else in the network that high-trust empowerment is as privilege, not an entitlement.

That’s what I think.  What do you think?

_________________________________________________________________________

Geoffrey Moore | Zone to Win | Geoffrey Moore Twitter | Geoffrey Moore YouTube

Hans Berggren

Group CEO & Co-founder at PipeChain

6y

Spot on, Geoffrey. The younger generation, used to creating high trust networks when e.g. playing computer games online, will soon reach management levels on a broad scale and I think we'll see a lot more of "network companies" built on high trust networks the coming years.

Like
Reply
Somesh Bhagat

Increasing sales through customer success®| Learner, Orbit-changer, Coach, Volunteer

6y

V nice. Like the idea of being able to build a high trust network within a low trust one and manage API's. High trust network envisages people with high capabilities. So the key is to get such people or to groom those who can be groomed in case you do not have enough ready talent. What are suggestions to groom people fast? On 360 degrees, I have not found them effective, where I encountered them. May be they were not implemented well....but then not many have done so in any case. They were mainly popularity exercises - and management is not a popularity contest. Or trade ins of 360 feedback...you give me a good one and I will return the favor! They were actually dysfunctional. All participants in a 360 need to be very skilled to judge - often tough to achieve.

Like
Reply

One of the few reliable signals I have noticed is how low-trust operators use emails and standing meetings. I pay particular attention to (and have very low tolerance for) the low-trust practice of using Cc: for ass covering, blame shifting or, frankly, any reason beyond informing someone who is known to need the information. Standing (not standing up) meetings are often thinly disguised resource hoarding exercises - if I can make you attend my meeting instead of doing your work, you are mine. My approach is to forbid them, with the exception of a team leader meeting with their own team for a defined purpose, always cancelled if the agenda is null. There still a lot of detection and intervention work required to maintain a high-trust environment, but elimination of the two most common trust toxins makes that job much easier.

Like
Reply

To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics