Week 46 Day 5: Do You Feel Like I Have Your Back?

The leader who has the team's back is the one who says to the VP: 'The team made the right call with the information they had. I support their decision.' The leader who does not have the team's back is the one who says: 'I will talk to the team about why that happened.' The first leader absorbs the pressure. The second redirects it downward. The team feels the difference immediately.

Here is how to diagnose and repair a 'no' on this question. The diagnosis: a low score on 'I have your back' usually stems from one of four leadership failures. Failure one -- throwing the team under the bus: in a meeting with senior leadership, you attribute a problem to the team rather than to yourself. 'The team missed the deadline' instead of 'We missed the deadline and here is what I am doing to address it.' Every time you use 'the team' as the subject of a failure sentence when talking to people above you, you are signaling that the team is the problem and you are separate from it. The team hears about these moments -- through people who were in the room, through tone shifts from stakeholders, through organizational grapevine. Failure two -- not defending team decisions: a stakeholder questions why the team chose approach A over approach B. Instead of defending the team's reasoning, you agree with the stakeholder: 'Good point, I will have the team reconsider.' You just undermined the team's authority and told the stakeholder that the team's decisions are provisional -- subject to override by anyone who questions them. Failure three -- absorbing credit for successes: in the quarterly review, you present the team's accomplishments using 'I' language. 'I shipped the new feature. I reduced latency by 40%.' The team did the work. If you absorb the credit, the team learns that their contributions are invisible to leadership. Failure four -- not shielding from unreasonable demands: a stakeholder demands a feature in an impossible timeline. Instead of pushing back on the stakeholder, you pass the demand to the team: 'Can we make this work?' The team now bears the pressure of saying no (which they may not feel authorized to do) or saying yes and overcommitting. The repair for each failure is specific. For failure one: practice using 'we' for failures and 'the team' for successes. 'We missed the deadline' and 'The team shipped an excellent feature.' For failure two: when a stakeholder questions a team decision, say 'The team evaluated multiple approaches and chose this one because [reasoning]. I support their decision.' For failure three: in every presentation to leadership, name the specific people who did the work. 'This feature was architected by Alice and implemented by Bob and Charlie.' For failure four: when unreasonable demands arrive, intercept them: 'I will evaluate whether this timeline is realistic and get back to you. I will not commit my team to something I have not validated.'

The 'having your back' dimension of trust maps to what Mayer, Davis, and Schoorman (1995) call 'benevolence' -- the perception that the leader genuinely cares about the team members' welfare and will act in their interest even when doing so has a personal cost. Their research found that benevolence was the strongest predictor of willingness to be vulnerable (the behavioral definition of trust), stronger than ability or integrity, because benevolence signals that the leader's interests are aligned with the team's interests. The credit attribution pattern is documented by Campbell and Sedikides (1999) in their research on 'self-serving bias in leadership,' which found that leaders in organizational settings attributed team successes to their own leadership 60% of the time and team failures to team members' performance 70% of the time -- a self-serving pattern that was detectable by team members and that predicted lower team trust. Research by Dirks and Ferrin (2002) in their meta-analysis of 'trust in leadership' found that the single strongest behavioral predictor of team trust was 'organizational protection' -- the perception that the leader would defend the team to the organization and absorb organizational pressure rather than redirecting it downward. Teams whose leaders demonstrated organizational protection showed trust levels 0.8 standard deviations higher than teams whose leaders did not, making it the largest effect size in their analysis.