Week 17 Day 4: 'Do You Have What You Need to Do Your Job?'

Leaders assign work and assume the team has everything needed to complete it. This assumption is wrong more often than most leaders realize. Missing access permissions. Outdated documentation. Dependencies on another team that has different priorities. A tool that does not work the way it should. These friction points are invisible to you because you do not experience them. Your team experiences them every day. This question makes the invisible visible.

The most revealing aspect of this question is what people identify as missing. It is rarely the obvious things -- budget, headcount, time. It is the small, chronic friction that nobody escalates because each instance seems too minor on its own. 'I need admin access to the staging environment and I have been waiting three weeks for IT to provision it.' 'The API documentation is six months out of date and I spend an hour every week figuring out the current behavior by reading source code.' 'I need a decision from the product team about the edge case behavior, but my emails keep getting deprioritized.' None of these are crises. All of them are productivity drains. When I started tracking what surfaced from this question, I found that the average team member was losing four to six hours per week to friction that could have been resolved in a single conversation. Multiply that by eight team members and you are losing a full-time employee's worth of productivity to problems nobody thought were big enough to mention.

The resource-needs question maps to Q2 of the Gallup Q12 instrument ('I have the materials and equipment I need to do my work right'), which Harter et al. (2002) found was the second strongest predictor of engagement after expectations clarity. Research by Morgeson and Humphrey (2006) on the Work Design Questionnaire identifies 'resources' as a fundamental dimension of job design that directly predicts motivation, satisfaction, and performance. The chronic-friction phenomenon described in level_2 aligns with what Perlow (1999) calls 'the time famine' -- the accumulated impact of small interruptions and inefficiencies that individually seem trivial but collectively represent massive productivity loss. Her research at a Fortune 500 engineering firm found that eliminating 'interaction-based interruptions' increased productive time by 65%. The concept of 'invisible blockers' relates to what Hackman (2002) calls 'enabling conditions' for team effectiveness -- the often-overlooked structural supports (information, tools, authority, process) that must be in place before team talent and motivation can translate into performance. DeMarco and Lister (1987) in 'Peopleware' documented that environmental and tool friction accounts for more lost productivity in software teams than any other factor, including technical ability.