Success Stories

Architecture creates value when it helps teams make better decisions, align across domains, and deliver with greater confidence. This page brings together perspectives from our Domain Leads on how the architecture playbook supports their work in practice. Their experiences show how a shared architectural approach helps create clarity, consistency, and stronger collaboration across the organization.

What our Domain Leads say

Olivier Roche

Olivier Roche

Domain Head - Integrated Research

“FISH is a perfect example where the architecture playbook has helped build a coherent platform despite the complexity of the task by providing clear guidelines, both technical (Minerva, Gravitee, Pingfed, PostgreSQL, Kafka, graphDB…​) and conceptual "FAIR by design" heavily relying on RTS for semantic modeling and terminologies.”

Jan Kuentzer

Jan Kuentzer

Domain Head - Exploratory Disease

“For our federated, modular Roche Data Commons architecture, it is critical that all components work seamlessly together to enable the generation of insights for the benefit of our patients. The Architecture Playbook played an essential role by providing clear guidelines on topics such as authentication, token propagation, and API design. This ensured consistency across teams, enabled interoperability, and significantly accelerated our ability to deliver integrated, insight-generating solutions.”

Fabia Fricke

Fabia Fricke

Domain Head - Assay Workflows

“”

Why this matters

These perspectives reflect how the architecture playbook helps turn principles into practical outcomes across domains. By creating a shared understanding of architecture, the playbook supports better decision-making, stronger collaboration, and more consistent delivery.

To learn more about how architecture is applied in practice, see Architecture Process and How Architecture Works.