Why the IT Services CEO Is an Enterprise Doctor — Exactly Where Medicine Was in 1825
- Sunil Dutt Jha
- Apr 4
- 4 min read
Updated: 7 days ago
This article is not about delivery frameworks, cloud platforms, or utilisation rates.
It is about how IT Services CEOs are forced to operate today — and why that role increasingly feels reactive, escalatory, and personally burdened, even in firms with mature processes, certifications, and global scale.
Every day, the IT Services CEO listens to symptoms.
Margins erode as headcount grows.
Delivery quality varies across accounts.
Client escalations recur despite strong governance.
Knowledge walks out when key people leave.
Reuse exists in presentations, not in execution.
Problems appear “handled” — only to return with the next client or program.
The CEO reviews reports. Account dashboards. Utilisation and margin metrics. Delivery quality reviews. Risk and compliance summaries. Transformation and tooling updates.
And then the CEO is expected to diagnose what is really wrong — and prescribe interventions without destabilising client relationships, delivery teams, or revenue flow.
This places today’s IT Services CEOs exactly where medical doctors stood in 1825.
Medicine Before Anatomy: The World of 1825
In 1825, medicine was practised by capable, committed doctors.
They observed symptoms carefully. They documented cases. They refined instruments and treatments. They relied on experience, judgment, and precedent. What they lacked was not intelligence or intent. They lacked formal anatomy.
The human body was externally familiar but internally opaque. Diagnosis relied on observation and memory. Treatments varied by doctor. Outcomes were inconsistent. Knowledge did not survive when the doctor left. Medicine worked — but only as long as the right doctor was present. This was not poor medicine. It was pre-anatomy medicine.
Where the IT Services CEO Stands Today
Modern IT services firms appear far more advanced than medicine did in 1825.
Delivery models are mature. Frameworks are certified. Processes are documented. Data is abundant. Yet execution behaves in a familiar way.
Local account decisions undermine enterprise margins. Workarounds keep delivery moving temporarily. Critical knowledge concentrates in a few senior leaders. Escalations reach the CEO during client crises or renewals. This happens for the same reason medicine once struggled. IT services firms operate without an explicit, shared enterprise anatomy.
So IT Services CEOs practise enterprise medicine using experience, memory, intuition, and escalation.
Why the CEO’s Office Runs on Experience — Until It Breaks
In many IT services firms, execution does not truly run on structure. It runs on experience. Who knows how to stabilise a troubled account. Which delivery compromise keeps a client satisfied. Which architect can rescue a failing program. Which leader can bridge sales promises and delivery reality.
This works — temporarily. As long as the right people remain, performance appears controlled. When they leave, rotate, or when scale accelerates, familiar symptoms return:margin leakage,quality variation,client dissatisfaction,and the CEO becomes the final integration point again. This is not leadership failure. It is enterprise medicine without anatomy.
The IT Services Enterprise Has Organs — Even If They Are Not Visible
An IT services firm is a living organism. Its organs include sales, solutioning, contracts, delivery, talent management, knowledge reuse, platforms, partners, governance, finance, and transformation programs.
Each of these organs already operates across the same internal layers: intent, process, decision logic, systems, change activity, and daily operations. This anatomy already exists. But when it is not explicit and shared, each account interprets priorities independently.
The CEO becomes the point where contradictions surface — acting as nervous system, circulatory system, and immune response simultaneously. That is not scalable medicine.
Why Interventions Create Side Effects in IT Services
Before anatomy, doctors treated symptoms directly. Sometimes patients improved. Sometimes complications emerged. Often the underlying condition remained.
The same pattern appears in IT services firms. A margin fix reduces delivery quality. A quality initiative increases cost. A reuse mandate fails under client pressure. A tooling rollout increases dependence on a few specialists. These are not bad decisions.
They are interventions applied without full anatomical visibility.
What Changes Once Anatomy Becomes Visible
When medicine gained anatomy, doctors did not become less experienced. They became precise. Diagnosis replaced intuition. Treatment targeted causes, not symptoms. Knowledge survived individuals. Outcomes became repeatable.
The same shift occurs when IT services enterprise anatomy becomes explicit. The CEO no longer relies on experience alone to diagnose. Margin and quality stabilise structurally, not heroically. Interventions become targeted instead of disruptive. Scale increases leverage rather than fragility. Enterprise medicine becomes possible.
Why This Perspective Matters for IT Services CEOs
This article is not intended to explain Enterprise Architecture. It exists to explain why IT Services CEOs feel the pressure they do, even in firms with mature processes and global scale.
The repetition. The constant escalation. The dependence on a few trusted leaders. The sense that growth increases complexity instead of resilience. These are signals.
They are the same signals medicine experienced before anatomy transformed the discipline.
The Choice Facing IT Services CEOs
In 1825, medicine faced a choice: continue relying on experience and memory, or formalise anatomy and change permanently. IT services firms face the same choice today. Execution can continue to depend on heroics, escalation, and personal leadership.
Or it can be governed through an explicit enterprise anatomy that allows CEOs to diagnose conditions and intervene safely. If you are evaluating why Enterprise Architecture must sit with the IT Services CEO, begin with:
This article exists to explain why that question keeps returning — and why it will not go away.
