From CoSy to Teams: A Familiar Story of Collaboration

In 1987, the University of Arizona stood at the edge of something new. Today, as Microsoft Teams becomes the hub of collaboration across campus, it’s easy to think we’re navigating uncharted territory. But for many in IT, especially those who remember the early days here at the university, the story feels strikingly familiar.  

Nearly 40 years ago, when CoSy (short for conferencing system) was introduced, Microsoft was only laying the groundwork for its computing framework with the release of Windows 2.0. The idea of threaded conversations and persistent shared spaces for groups marked a cultural shift that took decades to become the norm. At the time, the university had already experimented with communication technologies such as email and user-group electronic bulletin boards, but none had unified the campus. CoSy aimed to change that by creating a shared digital space for discussion, coordination, and information exchange.  

CoSy wasn’t implemented overnight. It followed two years of evaluation, months of pilot testing, and a carefully staged rollout. Early adopters were brought in first. Training evolved in real time. Policies were written and revised as people figured out how to actually work in this new environment.

The technology was only half the challenge. If there’s one lesson that echoes across decades, it is that the hardest part wasn’t the technology; it was the people. CoSy required the university to build what they called a “conferencing culture.”  

That included teaching users not only how to use the system but also why. It encouraged departments to adopt shared practices and to create norms for communication, etiquette, and participation. Training began informally, peer-to-peer, hands-on, even improvised. This gradually matured into structured support, documentation, and help networks.

Today, the Microsoft Teams adoption looks remarkably similar. We have champions and early adopters leading the way. Departments have adapted the tool to their own workflows, and “best practices” will evolve as usage grows.  

Different platform. Same human dynamics. History has brought to the surface the Conferencing Selection and Implementation: University of Arizona Case History. Take a moment to read the full dialogue, including an Abstract, Introduction, and metrics, that summarizes implementation of the university’s chosen conferencing system in 1987. The CoSy paper closes with a quiet but powerful insight: success came from focusing on people, relationships, and shared purpose, not just the technology.

That idea aligns directly with today’s vision for UITS.  While the tools will change, and the platforms will evolve, the goal remains the same. Help people connect, collaborate, and do their best work – together. And if history is any guide, we’re on a path we already know how to navigate.