Coming into IT services from a very different operating context, I assumed many of the fundamentals would feel familiar.
Scale, delivery pressure, cross-functional coordination, and operational complexity, these were all familiar territory. What is interesting is seeing how differently the same fundamentals express themselves here.
Like most transitions, the first instinct is to look for patterns you already understand. To map what you know onto what you are seeing. I found myself doing that too.
It became clear fairly quickly that before looking for levers to improve, you need to understand what the system was already protecting.
A few patterns have become clearer over time.
Delivery here rarely sits still
In many operating environments, once the scope is clear, execution becomes about consistency and control.
Client needs evolve, dependencies shift, priorities change, and delivery teams are constantly adjusting in motion.
What might look like instability from the outside is often just the nature of the work.
It has changed how I think about resilience. Sometimes it is less about control, and more about preserving adaptability under pressure.
Bench looks very different when you understand its purpose
Early on, it is easy to view bench through a narrow utilisation lens.
But as you gain more context, you come to appreciate it as something much more nuanced.
It is really about readiness.
Too little flexibility and opportunities get missed. Too much, and the economics become difficult to sustain.
There’s a balancing act here that isn’t obvious at first.
People capability sits at the centre of everything
What becomes clear quickly is just how much outcomes depend on talent readiness.
Hiring, learning, deployment, transitions, retention, none of these feel like support functions sitting on the side.
They are central to how the business operates.
It is like supply-demand planning, except the variables are far more human and far less predictable.
Alignment needs a different rhythm
The frequency of reviews, conversations, checkpoints, and recalibration stood out to me initially.
At first, it feels like over-coordination.
Over time, you start understanding that this rhythm is what holds everything together.
When delivery is distributed and variables shift constantly, staying aligned can’t be treated as a periodic activity.
It has to be continuous.
Small decisions matter more than they appear to
In some businesses, a few big decisions shape the outcome.
Here, very often results are shaped by many smaller calls made consistently over time.
Staffing choices, timing decisions, resource allocation, small operational adjustments, may not seem significant individually.
Collectively, they define outcomes.
What I have appreciated most through this transition is the reminder that every operating environment has its own logic.
The instinct to optimise matters. But it only becomes valuable once you understand what the system is already optimising for.
Sometimes what looks inefficient on the surface is actually the system balancing trade-offs that only become visible with context
For those who have made similar cross-industry moves, what surprised you most in the first few months?
#OperationsLeadership #SystemsThinking #ITServices #Execution #LearningInPublic
