Change Management in IT – Corporate Freshers Guide

Episode 8: Corporate Fresher’s Survival Guide – “The Approval Wars” – Change Management Chronicles

🗓️ Location: Any high-rise building where Slack pings never stop
🎯 Topic: Change Management (aka Corporate Red Tape on Steroids)


🎭 Scene Opens:

You’ve survived Incidents. You’ve RCA’d like Sherlock.
Now, you want to improve the system? Push a patch?
Deploy a fix?
Hold up, rookie.
You forgot the golden law of the land…

💥 NO CHANGE SHALL PASS WITHOUT APPROVAL! 💥

Welcome to Change Management, where ideas go to queue… and sometimes to die. ☠️


🧠 So What Is Change Management, Really?

Change Management = The process of proposing, reviewing, approving (or rejecting) any changes to the IT environment. 🖥️🗂️

It protects services from chaotic cowboy coding 🤠 and ensures everything is controlled (even your hopes).


🕹️ Types of Changes You’ll Hear:

  1. Standard Change – Pre-approved. Safe. Routine.
    (Like brushing your teeth. Boring but necessary.)
  2. Normal Change – Needs CAB approval. Meetings. Slides. Blood tests.
    (Okay not blood, but close.)
  3. Emergency Change – Server’s on fire. Client’s screaming.
    Just do it. 🚨
    (Fill the form later… maybe.)

🤖 Enter: The CAB – Change Advisory Board

🧓 👩‍💻 👨‍🏫 👩‍🔬
A roundtable of senior folks (aka The Circle of No) who review your change request.

👨‍💼 You:

“We just need to update this one script to avoid future failures.”
👴 CAB Member:
“What’s the rollback plan if the moon collides with the earth during this change?” 😐


🔄 The Freshers’ Cycle of Pain

🔸 You submit a change ticket.
🔸 It gets sent back.
🔸 You fix the wording.
🔸 Sent back again.
🔸 You add impact analysis.
🔸 Rejected.
🔸 You question your degree and life choices. 🎓💔


⚔️ “The Approval Wars” Begin…

🧙 Your Manager becomes Gandalf:

“You shall not deploy… without a CAB sign-off.”

🧟‍♂️ You become a zombie waiting for approval emails.

🧊 Your change sits in backlog like frozen code in the Arctic.


🧘 Pro Tips for Surviving Change Management:

✔️ Always include:

  • Impact
  • Risk
  • Rollback plan
  • Stakeholder details
  • Timing
  • Dependency matrix (yes, even if there are none)

🗓️ Schedule ahead. CABs hate surprises.
🤝 Make friends in compliance. They hold the keys.
🍩 Bribe them with donuts (just kidding… maybe).


💡 Freshers, Remember:

Change Management is not your enemy.
It’s a shield — protecting systems, services, and sometimes your job.

But yes, it’s also a test of patience, clarity, and your MS Word formatting skills. 🧾✍️


🎬 Final Scene:

You finally get the change approved. 🎉
You deploy. Nothing crashes.
You write a glorious change report.
You feel… invincible.
Until the next ticket. 😅

Leave a Reply

Your email address will not be published. Required fields are marked *