IT Leadership & Governance

Group IT Governance & Centralization Program

Group-wide operating model for technology governance, centralization, standards, ownership, documentation and service-management maturity.

EnvironmentExperts Care Medical Group
Period2026-Present
RoleGroup IT Manager
LifecycleActive / group operating-model developmentThe public case study describes a governance and centralization program across multiple group entities. It intentionally omits private account inventories, credentials, commercial data, internal contacts and detailed security configuration.
Group IT Governance & Centralization Program architecture representation for IT Leadership & Governance
Architecture RepresentationGeneralized group operating model showing group-level standards and accountability connected to entity-level execution.
Project overview

Group technology governance built around ownership, standards and service visibility

A group-wide operating model that moves technology management from fragmented entity-by-entity practices toward clearer ownership, shared standards, documented responsibilities and coordinated service management.

StatusActive / group operating-model developmentEnvironmentExperts Care Medical GroupPeriod2026-Present
Context & challenge

The operating need

Multiple healthcare and related entities needed a practical technology governance model that could improve consistency without removing local operating responsibility or creating a single monolithic support bottleneck.

Role & responsibility

Ahmed's contribution

As Group IT Manager, Ahmed defines governance structure, technology ownership, shared standards, documentation expectations, vendor coordination and cross-entity service visibility while working with local stakeholders and support teams.

Solution

How the work was approached

Environment: A multi-entity operating group spanning healthcare, optical, project, equipment and supporting business operations with different local technology needs and maturity levels.

A federated governance model separates group standards and accountability from local execution, using common registers, ownership rules, access controls, documentation conventions and escalation paths to improve consistency and operational visibility.

Execution highlights

  • Established a common view of companies, branches, technology services and accountable owners across the group scope.
  • Defined shared standards for repositories, technical documentation, corporate account ownership, access lifecycle and service responsibility.
  • Separated group-level governance from local support execution so standardization does not block operational responsiveness.
  • Introduced a clearer vendor and escalation model to reduce ambiguity around renewals, support cases, service dependencies and cross-functional handoffs.
Security & operational controls

Designed for responsible operation

  • Public material excludes credentials, account identifiers, private contact lists, internal access details and confidential commercial information.
  • The operating model distinguishes business ownership, technical custody, local support responsibility and escalation accountability.
  • Governance controls are presented as an operating framework rather than as disclosure of internal security procedures.
Key decisions

Choices that supported the outcome

  • Use a federated model instead of centralizing every operational action into one team.
  • Treat ownership and documentation as control mechanisms, not administrative paperwork.
  • Standardize the minimum necessary foundations first: scope, service ownership, access lifecycle, repositories, escalation and asset visibility.
Lessons

What the work reinforced

  • Technology centralization succeeds when accountability becomes clearer without slowing local operations.
  • Service continuity depends on ownership, finance/vendor handoff and escalation as much as on technical configuration.
  • A group operating model needs explicit boundaries between standards, shared services and entity-specific execution.

Delivery status

Current project maturity

Implemented, validated, in-progress and planned elements are shown separately where the project is still evolving.

IMPLEMENTED

Core group scope, ownership, documentation and operating standards have been established across the active governance program.

IN-PROGRESS

Service-management maturity, shared controls and cross-entity standardization continue to expand.

PLANNED

Additional service catalog, workflow and governance automation remains staged for later maturity.

Technology

Technology used in this work

The stack and platforms associated with this project.

IT Governancecurrent production
Asset Managementproject specific
Access Managementcurrent production
ITSMplanned
Documentationcurrent production
About the project visuals

Generalized group operating model showing group-level standards and accountability connected to entity-level execution.

Private account inventories, credentials, supplier details, internal contacts, commercial data and detailed security configuration are intentionally excluded.

Copied