📅 We Had a Plan. Then the Client Changed Everything.

A story of how one mid-project change nearly derailed everything — and what I learned from it.

We had the perfect plan.

I had just started getting confident in managing projects. This one was for a mid-sized enterprise, and everything seemed to be falling into place.

👉 Scope? ✅ 👉 Timelines? ✅ 👉 Approval from stakeholders? ✅ 👉 Design and development team aligned? ✅

We even had a beautiful Gantt chart with every dependency mapped out. Honestly, I felt like I was finally “getting it.”

💥 And Then, It Happened

Exactly 11 days into the development sprint, I got a message from the client:

“Hey, can we make one small change? Our internal team is now thinking of doing multi-level approvals instead of a simple one-click confirmation. Just a small change, should be easy, right?”

That phrase still echoes in my head: “Just a small change.”

But here’s what that “small” change actually meant:

• Rewriting backend logic
• Redesigning the database
• Adjusting user flows
• New test cases
• More training for the client

And here’s where I stumbled: I nodded. I agreed. I said, “Yeah, sure, we’ll do it.”

I didn’t:

• Push back
• Ask clarifying questions
• Get a formal change request
• Reassess the impact with my team

Why? Because I thought I was being helpful. Because I didn’t want to say “no.” Because I was scared to look incapable.

🚨 What Followed?

The team got confused. We had to undo a lot of what we already built. Timelines shifted — but we were still expected to deliver on the original date. My developers were exhausted, frustrated, and losing trust in the plan.

One of them said to me:

“Abhilash, are we building for their idea of the week, or are we executing a proper roadmap?”

It stung. Because he was right.

💡 What I Learned (The Hard Way)

✅ Change is part of the job. But how you handle change defines your strength as a PM.

✅ Always ask questions. “Why the change?” “What’s driving it?” “Is this a permanent shift?”

✅ Have a formal change control process. Even if it’s a small project, set boundaries.

✅ Educate the client. It’s our job to help them understand the domino effect of every change.

✅ And most importantly — don’t let the fear of disappointing the client silence your voice.

This experience changed the way I managed every project afterward. I learned to say:

“Yes, we can do that. But let’s first talk about the impact, trade-offs, and timeline changes.”

It’s not about saying no. It’s about saying yes, responsibly.

If you’re a project manager or just someone handling client requests, I’m sure you’ve had your version of this story.

📩 I’d love to hear how you handle sudden scope shifts. Or tell me your biggest “small change” disaster.

Let’s learn together.