Week 11 Day 6: What Happens When Only the Leader Understands the Numbers

When the leader is the only one who understands the financial picture, every prioritization decision routes through them. Every scope question requires their input. Every trade-off discussion stalls until they weigh in. This is not leadership -- it is a bottleneck disguised as expertise. The leader who hoards business context creates the same dysfunction as the leader who hoards technical decisions. The team learns to wait rather than act.

There is a version of this that looks like good leadership but is actually a trap. The leader who always has the answer. The leader who can instantly tell you whether a feature is worth building. The leader who resolves every prioritization debate with 'I know something you do not.' It feels efficient. The team gets fast answers. But watch what happens when that leader takes a week off. Everything stops. Not because the team is incompetent, but because the team has been trained to outsource their judgment to someone else's information advantage. I was this leader for years. I thought I was being helpful by making quick calls. What I was actually doing was creating a team that could not prioritize without me in the room. The fix was not delegating decisions -- it was sharing the information that made those decisions obvious.

This pattern maps to what Lencioni (2002) identifies in 'The Five Dysfunctions of a Team' as a failure of commitment -- team members cannot commit to decisions they do not understand. It also reflects what Argyris (1990) calls 'skilled incompetence' -- organizational patterns where well-intentioned behavior produces counterproductive results. The leader who provides fast answers based on private information creates what systems theorists call a 'single point of failure' in the decision-making architecture. Weick and Sutcliffe (2007) in 'Managing the Unexpected' argue that organizational resilience requires 'redundancy of knowledge' -- multiple people capable of making informed decisions under uncertainty. When business context is concentrated in one person, the organization lacks this redundancy. Research by Edmondson (2012) on 'teaming' demonstrates that high-performing teams distribute knowledge actively rather than passively, and that leaders who share context proactively enable faster, more autonomous decision-making at every level. The 'bus factor' concept in software engineering applies equally to business knowledge: if one person leaving or being unavailable would cripple the team's ability to prioritize, the knowledge distribution has failed.