> "Increasing productivity" typically puts pressure on developers.
I agree frequently -- perhaps typically -- when managers put pressure on developers, they often explain their behavior as, they are trying to increase productivity. And indeed, this is probably genuine.
I'd also agree to the converse: That applying pressure in one form or another may be the most common thing that managers try to do to increase developer productivity.
Finally, I agree that applying pressure to developers is not a good way to increase their productivity.
Nonetheless, I'd respectfully disagree that attempting to increase developers' productivity is a fool's errand. Indeed, we often talk about the giant variance in individual developer productivity. If we agree that it's naive and ultimately self-defeating to pressure developers into increasing their productivity, I'd hope we could also agree that it's naive and ultimately self-defeating for managers to make no serious attempt to increase developer productivity.
There are lots of things that can be done to this end that reduce pressure on individual developers. Establishing good processes and tools, both hardware and software. Having quiet workspaces. Ensuring that managers don't suck the souls out of their reports. Establishing protocols that allow developers to work on a maker's schedule. Establishing coaching processes. Building a respectful work environment, where people aren't constantly worried about backstabbing, harassment, or being called an idiot. You get the idea.