Enterprise Architecture · Healthcare & Life Sciences EMEA & Americas

Trajectory

Thirteen years at Microsoft on a single segment, Healthcare & Life Sciences, across three successive roles whose perimeter expanded in stages. This page restitutes the trajectory less as a chronological sequence than as a convergence: each of the three positions refined the same gesture, which consists in designing AI and data systems that are governable by construction in environments where regulatory compliance is not a downstream validation test but an upstream design constraint.

The HLS segment imposes this posture more than any other. Pharmaceutical manufacturing combines GxP, MDR/IVDR for medical devices, the AI Act for high-risk AI systems, GDPR Article 9 for health data, and country-by-country sectoral regulations. Reading these corpora crosswise rather than in silos is the proper object of the work, and that reading is what distinguishes a deployable architecture from one that is technically valid but legally fragile.

2012-2018. Senior Enterprise Architect

The foundation work. Three hybrid cloud modernization programs conducted on heavily regulated hospital and industrial information systems, with a technical debt reduction of around 30% on the engaged perimeters. One merger and one carve-out in the pharmaceutical sector, executed with no critical incident, on the original timelines and budgets. The architectural gesture, at this stage, consists in standardizing sovereign cloud blueprints for government and defense contexts, where runtime jurisdiction becomes a functional requirement on the same footing as latency.

Two illustrative instances from this period. The definition of an operational cloud architecture for a European defense equipment supplier, outside the Five Eyes perimeter, with strong sovereignty requirements in the contractual and jurisdictional sense; integrating multi-sensor correlation in constrained environments and AI-coordinated automation in theatre of operations. In parallel, the development of disconnected cloud solutions on Azure Stack for defense environments requiring hardened appliances and operational autonomy in degraded networks. These two assignments, by their requirement of contractualized rather than declared sovereignty, shaped the subsequent reading of HLS engagements.

2018-2021. CDO/CTO Strategic Accounts S500

Strategic expansion. Driving digital transformation for S500 segment clients, with emphasis on the architecture of native multi-tenant SaaS models enabling recurring revenue. Design and launch of new services that produced, on the targeted verticals, a market share progression of around 15%. Concurrent leadership of large-scale cloud migrations with application rationalization.

On the public health segment, contribution to the preliminary architecture and business model definition for the French Health Data Hub, in a period when the operationalization of the national health data infrastructure had not yet settled its choices on governance, sovereignty and interoperability. The gesture, at this stage, is no longer merely architectural in the technical sense: it is doctrinal, in that it requires qualifying what counts as legitimate health data infrastructure for decades to come.

2021-Present. Director of HLS Innovation EMEA & Americas

The centerpiece. Consultative selling of a €148M three-year contract with a European pharmaceutical company, in a Winback context, that is, the strategic account recovery from a competing hyperscaler. The contract decomposes into €113M of Microsoft Azure Consumption Commitment and €35M of Enterprise Agreement, with a dedicated Digital Enablement Office of €28M to drive large-scale Azure migration on a multi-region landing zone, with GxP compliance integrated into the architectural design rather than added post-deployment.

This last point, GxP by design, is the signature of the assignment. An Azure landing zone can be technically irreproachable and structurally non-deployable in the GxP sense if the validation chain, audit log, environment separation and decisional traceability are not instructed as design constraints. The program delivered the inverse: an architecture where the validation file and the architecture file are not two separate objects but the same thing, read by two audiences.

On the manufacturing perimeter of the same client, refactoring of a production line in Cloud+Edge architecture with the decomposition of the monolithic Manufacturing Execution System into microservices fed by real-time IoT feedback. The operational result: 20% less OPEX, 20% more SLA, on a line where prior performance was already seriously measured. And zero major regulatory non-compliance across all client implementations led during the period.

The reference Manufacturing 4.0 architecture produced on this occasion combines Data Mesh (federated governance of data products), an AI layer structured around specialized models rather than a single LLM, and GxP by design as a transverse grammar. It was deployed as a sectoral blueprint on EMEA accounts, and constitutes the material from which, by doctrinal abstraction, the RAISE architecture published by the Twingital Institute is derived.

Doctrinal signature

The trajectory restitutes, in thirteen years and three roles, a regularity: no governable HLS architecture is built by adding compliance layers downstream. This regularity later structured the doctrinal formalization of the RAISE framework (five pillars, 5×5 interdependency matrix, anti-patterns), and the analysis of the domains of work that make explicit its conditions of application.

This page is a ground of implementation, not a general proof. It does not demonstrate that every HLS architecture should adopt the same grammar; it demonstrates, on an instructible perimeter, that a publishable AUC and a governable system are not the same engineering object, and that a deployable cloud landing zone and a GxP file are not two separate works.