The University of Washington (UW) adopted a dual-provider cloud-computing strategy, focusing initially on software as a service. The original project--to replace an obsolete alumni e-mail system--resulted in a cloud solution that soon grew to encompass the entire campus community. The policies and contract terms UW developed, focusing on compliance and reducing barriers to collaboration among faculty, staff, and students, provide a solid foundation for additional cloud computing endeavors. This article tells the story of how and why UW arrived at this dual-provider strategy, what the university has learned along the way, and what still needs to be done. The story combines evolution, adaptation, and a modicum of planning--but it reflects a conviction that this cloud computing thing is actually a big deal. The final chapter of this story has not yet been written; this is a snapshot of a work in progress. This article presents the UW cloud-computing narrative in the following sequence: (1) origins; (2) strategy; (3) rationale; (4) obstacles; and (5) conclusions. (Contains 2 figures and 3 endnotes.)