Leaving Microsoft

A member of staff opens a case, checks a document and sends a decision. To the person waiting for an answer, the software behind that work is usually a secondary concern. For the public body, keeping the task possible as its technology changes is a lasting responsibility. This investigation starts with ordinary administrative work and follows a political question: how can an institution choose its tools and pass the means of making that choice to the people who come after it?

Microsoft provides the thread connecting the chapters. The records examined reveal relationships between office software, email, accounts, applications and hosting. Chapter one follows a roads agency application in Schleswig-Holstein that still calls Excel during a move to another office suite. That small connection takes the investigation behind the desktop. A digital case depends on its contents, the people permitted to access it and the operations they need to perform.

An original introduction opens the book and connects the seven investigations.

Across these chapters, an exit becomes a succession of responsibilities. Someone must identify an application’s dependencies, check the available rights, fund parallel operation and help staff facing difficulties. Another team will eventually inherit that work. Freedom of choice therefore has an institutional dimension: the knowledge, records and resources needed to exercise it must remain usable through changes of personnel. The handover matters as much as the initial decision.

The opening chapters show how early that responsibility begins. One procurement helps establish the environment for the next. A licence assignment rule shapes access for new users. A procedure built around a workbook or an email service can extend the dependency to other teams. Preserving options requires the public body to explain those choices and retrieve the materials needed to change them. That knowledge also supports an informed decision to retain an integration whose benefits justify its constraints.

The full conclusion connects architecture, contracts and the continuing work of the teams who run the service.