The Hidden Risk of Team Homogeneity
A team can look diverse on paper and still think alike in the room, because diversity of membership and diversity of thinking are two different things. The real question for any risk-bearing team is how much genuine diversity of thought it actually has, across age, experience, professional background, technical expertise, geography, culture, gender, personality, customer exposure, digital capability and institutional knowledge. Lynda Gratton ' s research on high-performing teams points to cooperation, trust and diversity of experience and thinking as critical, while flagging homophily, our tendency to gravitate toward people similar to ourselves, as something that quietly limits innovation once the environment turns uncertain.
Take a credit decision. What happens when everyone around the table has a similar banking background, similar career history and roughly the same appetite for risk? You may get excellent agreement. But agreement isn ' t the same thing as good risk management. Sometimes the most valuable person in the room is the one who says, " I don ' t think we ' re looking at this correctly," and whether that voice gets heard is what decides if diversity of thought is worth anything at all.
I sat as head of credit risk in a committee that nearly approved a large facility to a seemingly strong manufacturing borrower. Everyone at the table had a similar banking background and had watched similar deals perform well before. It was a junior analyst, new to the team, from a different industry entirely, who asked whether we ' d properly stress-tested the borrower ' s exposure to a specific imported raw material with a volatile price. That single question uncovered a concentration risk the rest of us had walked straight past. The deal was restructured with tighter covenants. One outside perspective had done the work of a risk control.
The Young, the Experienced, and the AI-Enabled Workplace
Teams today contain people who grew up in entirely different technological worlds. Some professionals learned systems manually over decades. Others grew up with smartphones, cloud platforms, social media, AI tools and instant information at their fingertips. Younger professionals often bring speed, digital confidence and a willingness to question established practice. Older professionals bring institutional memory, judgement built through experience, and a memory of what previous failures actually looked like. Neither side automatically has the better answer. The risk shows up when an organization pits experience against youth instead of combining them.
128 MAL74 / 26 ISSUE
McKinsey ' s recent work on leadership in the age of AI draws a useful line: AI can execute many tasks at extraordinary speed, but leadership still needs distinctly human capabilities, setting direction, making hard calls, building trust, holding accountability, generating genuinely new ideas. Their 2025 Superagency research found employees were largely ready to work alongside AI, while leadership readiness was the bigger obstacle to scaling it. Which raises the real question for a risk column: if AI is changing what individual employees can do, are we changing how teams are designed to work together, or just bolting a new tool onto an old structure?
I watched this play out directly during a training assignment with a bank whose younger credit analysts were using AI tools to draft initial credit memos at remarkable speed. Senior reviewers, uneasy about trusting the output, were quietly redoing large portions of the work by hand, which defeated the purpose and created its own friction. The exposure nobody had named yet was straightforward: an AI-drafted memo moving through the process without anyone genuinely interrogating its assumptions is a credit decision resting on an unchallenged model. That ' s model risk wearing a new face. A senior manager I later followed up with told me the bank had since introduced a " human-in-the-loop " protocol, where every AI draft is deliberately challenged by an experienced credit officer against a structured checklist before it goes further. Turnaround got faster, not slower, and nothing rode on an unexamined draft anymore. The team became more effective not because it chose speed or experience, but because it stopped treating the two as opposites.
Remote Teams: When Distance Becomes a Risk
As area manager for personal and business banking in the bank ' s Eastern( administrative) region, I oversaw business development across 16 branches spanning eastern, rift valley and the arid and semi-arid north regions. The distances were long, the geographies varied, and product uptake shifted from one area to the next: deposit mobilization was the heavy lift in some Islamic-dominant areas, lending drove the agenda in others. Teams were stretched across skills, focus and coordination. But physical distance wasn ' t really what separated them. Poor connection between the teams was.
Remote and geographically dispersed teams offer real flexibility, but they come with their own risks: information gaps, weak relationships, misunderstanding, delayed escalation, thinner informal communication, isolation, and gaps in accountability. The question that matters is how you keep trust, accountability and information flowing when people no longer share a physical space, which is, at its core, a risk management question.
Working in that region showed me just how much happens through informal communication. In branches where I had a strong personal relationship with the manager, issues escalated quickly. In others, problems festered quietly until they became incidents. We introduced structured regional huddles, peer-to-peer learning sessions, and a rotating " buddy branch " system pairing managers across regions to trade challenges and solutions. Isolation eased. Information moved faster. And we started catching emerging issues before they became expensive.
Psychological Safety Is Not the Absence of Challenge
Amy Edmondson and Michaela Kerrissey ' s 2025 Harvard Business Review piece, " What People Get Wrong About Psychological Safety," makes an important correction: psychological safety is often mistaken for simply making people comfortable, when it ' s really about candid speaking, learning, constructive debate and performance. A team where nobody feels safe challenging an assumption isn ' t a harmonious team so much as a team carrying hidden risk.
Psychological safety doesn ' t mean everyone feels at ease all the time. It means someone can say " I think we ' re getting this wrong " without fear of punishment or humiliation. That matters enormously for risk management, because a healthy team needs to be able to say: the numbers don ' t look right; I don ' t agree with this assumption; we may be underestimating the exposure here; the customer is telling us something different; this rollout isn ' t working; AI has given us an answer, but I ' m not convinced it ' s the right one. That last one is more relevant now than it ' s ever been.
In one credit committee session, a senior relationship manager pushed back hard against a risk officer ' s recommendation to decline a facility. The tension in the room was obvious. But because the team had built real norms around constructive challenge, the debate, tense as it was, stayed professional, and it produced a restructured deal with stronger security and tighter monitoring. The friction hadn ' t weakened the team. It had done exactly what a good team is supposed to do under pressure.