6 ideas
Projects almost never fail for lack of technical skill; they fail because of politics, communication breakdowns, motivation, and team dynamics. Managers spend their energy on the technology because it is familiar, while the real risks live in the human dimension they avoid.
Knowledge work requires a deep immersion state called flow that takes roughly fifteen minutes to enter and is destroyed instantly by interruption. Because re-immersion is slow, environments full of phone calls, meetings, and noise can reduce a worker's truly productive hours to a fraction of the time they spend present.
Pushing people into sustained overtime produces a short-term burst followed by compensatory undertime, errors, and burnout that erase the gains. The visible extra hours mask invisible losses in quality, attention, and eventual attrition.
A jelled team is a group that has become so aligned it produces more than the sum of its members and resists dissolution, marked by low turnover, a sense of elitism, and shared ownership of the work. Managers cannot manufacture jelling directly but can create conditions for it and, more importantly, must stop the 'teamicide' behaviors—defensive management, bureaucracy, physical separation—that prevent it.
In coding competitions, the best performers came overwhelmingly from the same organizations, and the dominant predictor of high output was workspace quality—floor space, quiet, privacy, and freedom from interruption. This means productivity differences attributed to individual skill are largely produced by the environment the company provides.
Treating people as fungible resources—optimizing for easy replacement, tight control, and standardization—signals distrust that drives away exactly the talent that makes work succeed. The alternative is viewing each person as a unique investment whose retention, growth, and intrinsic motivation are the manager's primary capital.