I would like more quantified and peer-reviewed content here, buit I will take what I can get.
Coda Hale, Work is work:
Keep the work parallel, the groups small, and the resources local.
When presented with a set of problems which grow superlinearly intractable as \(N\) increases, our best bet is to keep \(N\) small. If the organization’s intent is to increase value delivery by hiring more people, work efforts must be as independent as possible. …
Prioritize the development of force multipliers.
If an organization is largely working on the same types of problems it was in previous years, it’s cause for concern.
The Agile Manifesto is an immune response on the part of programmers to bad management. The document is an expression of trauma, and its intellectual descendants continue to carry this baggage. While the Agile era has brought about remarkable advancements in project management techniques and development tools, it remains a tactical, technical, and ultimately reactionary movement. As long as Agile remains in this position it will be liable to backfire, vulnerable to the very depredations of bad management it had initially evolved to counter.
Denise Yu, Habits of high-functioning teams:
Generous communication between peers means that at all times, we assume that anyone asking a question:
- Has done the basic research, e.g. they’ve googled the thing already
- Is asking a human, because they’ve been unable to find their answer in any written-down place. Because that written-down place is difficult to find, or it doesn’t exist yet.
In other words: assume your peer is a competent, intelligent, reasonable person who is asking a question because they’re lacking context, that they’ve already attempted to procure on their own.
There is some famous Google research here (not peer-reviewed, mind).
Google: Foster psychological safety
Of the five key dynamics of effective teams that the researchers identified, psychological safety was by far the most important. The Google researchers found that individuals on teams with higher psychological safety are less likely to leave Google, they’re more likely to harness the power of diverse ideas from their teammates, they bring in more revenue, and they’re rated as effective twice as often by executives.
Ben Reinhardt Why does DARPA work?
Gallons of ink have been spilled describing how DARPA works1, but in a nutshell here is how DARPA works. Around 100 program managers (PMs) with ~5 year appointments create and run programs to pursue high-level visions like “actualize the idea of man-computer symbiosis.” In these programs they fund researchers at universities and both big and small companies to do research projects of different sizes. Collectively, groups working on projects are called performers. Top-level authority lies with a Director who ultimately reports to the Secretary of Defense. DARPA has an incredibly powerful model for innovation in defense research, and I believe an abstract ‘ARPA Model’ could yield similar results in other domains. In this piece I’ll explain in detail why DARPA works. I’ll use that description to feel out and describe to the best of my ability a platonic ARPA Model.