That seems precisely what is hard to do when you depend on others for your livelihood, as most employers do. How to avoid a sense of urgency when you are told that if XYZ do not happen, you may ultimately benefit less or lose your benefits?

Team work is unavoidable in most organizations. The easiest way to create some kind of collaboration if not synergy is through a sense of urgency. In part because it is much faster to create than a sense of purpose. A sense of urgency can appeal to very different people, who may not be able to otherwise agree or see a common sense of purpose. After all the basic idea of the employee, or entrepreneur, is that you get your benefits (salary, funding, etc) not because of your purpose, but because it fits the purpose of those you depend upon.

Open source is often centered around a common “itch”, but the debates rage on whether an “itch” is motivating because of urgency or purpose. Difficult distinction to make in practice, which is why the efficiency of urgency trumps the slow benefits of purpose: urgency never fails to satisfy the itch (trial and error is an efficient algorithm when lacking heuristics), whereas purposes might fail and require changing course to get to an itch.