In the San Francisco Bay area, the typical polycule and the typical early startup have a similar number of members. And, specifically: similar actual members, though most people are employed by at most one startup, while they may be part of several polycules, depending on calendar compatibility.
While the typical startup has venture funding and a much larger explicit IT budget, the typical polycule has more robust IT infrastructure, better phishing resistant authentication for its single-sign-on service, and higher reported satisfaction with IT support, despite having a much wider range of device types, ages, and operating systems to secure, and no MDM, mandate, or authority to enforce policies.
In this paper, we use an interview-based and embedded ethnographic approach to study these two very different approaches to IT requirements-gathering, decision-making, and implementation, and extrapolate relevant lessons for in the deployment of resilient IT systems which are responsive to community feedback.