Leadership Means Getting Your Hands Dirty: Why Real IT Experience Matters
Leadership Is Built on Experience, Not Just Dashboards
When I joined a small company in Chandigarh, I was the entire IT department.
If a cable had to be laid, I was there.
If software failed at 2 a.m., I was there.
If the network went down, I was sitting with the engineers until it came back.
Nobody asked me to do it.
I did it because I made a decision very early in my career:
I would never ask someone to do a job I hadn't done myself.
That principle became one of the most valuable lessons of my professional life.
Hands-On Experience Creates Better Leaders
Years later, when I was leading large technology teams, that early experience paid off every single day.
When someone told me a project needed three months, I had enough practical experience to understand whether that timeline was realistic.
When a vendor quoted a price, I could judge whether the proposal was reasonable.
When an engineer said they were stuck, I could often recognize whether the problem was genuinely technical—or whether there was another obstacle behind it.
That doesn't mean a leader needs to know everything.
It means a leader should understand the work well enough to ask the right questions.
Dashboards Can't Replace Experience
Modern technology leaders have access to incredible amounts of information.
Dashboards are useful.
Reports are useful.
KPIs are useful.
Analytics are useful.
But none of them completely replaces experience.
A dashboard can tell you that a system is performing poorly.
Experience helps you understand why.
A report can tell you that a project is delayed.
Experience helps you determine whether the timeline was unrealistic, the execution was weak, or an unexpected technical challenge caused the delay.
Data tells you what is happening.
Experience often helps you understand what to do next.
Credibility Comes From Doing the Work
People recognize leaders who understand their reality.
An engineer doesn't expect a CIO or IT leader to configure every server personally.
But they respect a leader who understands what it takes to solve a difficult production issue.
They respect someone who has spent nights troubleshooting systems.
They respect someone who understands the pressure of a network outage, a failed deployment, a security incident, or an impossible project deadline.
That credibility cannot be created by a job title.
It is earned through experience.
Leadership Doesn't Mean Doing Everything Yourself
There is an important difference between hands-on leadership and micromanagement.
A good technology leader does not need to do every task personally.
The role of a leader is to build capable teams, delegate effectively, remove obstacles, make decisions, and create an environment where people can succeed.
But having done the work yourself gives you something valuable:
Perspective.
You understand the difficulty behind the task.
You understand the dependencies.
You understand the risks.
And most importantly, you understand when someone genuinely needs help.
The Lesson I Carry Forward
My early career taught me something that no management book could fully teach me.
Before leading people, understand the work.
Before setting unrealistic deadlines, understand the effort.
Before challenging an engineer, understand the problem.
Before accepting a vendor's proposal, understand the value.
And before asking someone to work harder, remember what it feels like to be the person doing the work.
अपने हाथ गंदे करने पड़ेंगे।
You have to get your own hands dirty.
Leadership becomes easier when you've done the work yourself.
Not because you need to prove that you can do everything.
But because experience gives you judgment, credibility, empathy, and perspective.
And those are the qualities that turn an IT manager into a true technology leader.
Final Thought
The best technology leaders don't lead from dashboards alone.
They lead with experience, curiosity, technical understanding, and respect for the people doing the work.
Get close to the work. Understand the struggle. Learn the details. Then lead.
