Anyone who’s ever gone through an ERP implementation during the early/late 90s and post Y2K knew it’s no walk in the park. There are a million and one things that could (and usually did) go wrong.
Now, imagine going through that same process while you are migrating to cloud or a SAAS application, but this time you have to deal with upper management who doesn’t fully understand or appreciate the work that goes into an ERP/SAAS migration. You’re constantly getting pull requests for features that aren’t related to the project, your team is starting to get frustrated, and you’re pretty sure your boss is about to have a nervous breakdown. It’s enough to make even the most experienced project manager want to pull their hair out.
Fortunately, we can learn from other people’s mistakes. In this blog post, I’ll share some tips on how to keep your cool and get the job done, even when upper management is breathing down your neck.
- Keep a sense of humor
One of the most important things you can do during a stressful situation is to keep your sense of humor. If you can find the funny side of things, it’ll be easier to stay calm and keep things in perspective. After all, it’s not the end of the world if a few things go wrong during the project. Just remember that you’re not in it alone—we’ve all been there before. - Communicate, communicate, communicate
Another important thing to remember is to communicate with your team and upper management as often as possible. Set up regular meetings (weekly or bi-weekly) so everyone is on the same page and knows what needs to be done next. This will help avoid any surprises down the road and will make it easier to keep everyone happy. - Know when to delegate
As the project manager, it’s easy to feel like you have to do everything yourself. But that’s just not realistic—or healthy! Delegate tasks to your team whenever possible so you don’t get overloaded and burned out. This will also give them a chance to step up and show what they’re capable of doing. - Take breaks
Last but not least, don’t forget to take breaks! Working around the clock will not do anyone any good—least of all you. Make sure you take some time for yourself so you can recharge and come back refreshed and ready to tackle whatever comes your way.
Conclusion: Cloud ERP/SAAS Migration might seem like a daunting task, but with proper planning and communication, it can be a breeze—even with difficult upper management breathing down your neck. So don’t get discouraged—keep your head up and power through! After all, this too shall pass.
Speak their language: risk, money, and dates
Here is the uncomfortable truth: your executives do not care about your middleware, your data mapping, or your sprint velocity. They care about three things: risk, money, and dates. Every status update that leads with tasks completed is a missed opportunity. Translate instead. “We finished the customer master migration” becomes “we retired the biggest go-live risk on the timeline.” “We need two more weeks for testing” becomes “two more weeks of testing protects a nine-figure revenue process from breaking on day one.” You are not dumbing the project down; you are reporting it in the only currency your audience spends. The project managers who survive difficult sponsors are not the ones with the prettiest Gantt charts. They are the bilingual ones.
Get every decision on paper before you need it
Remember those pull requests for unrelated features? They do not stop because you asked nicely. They stop when there is a visible cost attached. Start a one-page decision log: what was requested, who asked, what it displaces, and what it costs in time and money. When the VP of Sales wants a custom dashboard mid-migration, you do not say no. You say, “Absolutely, here is what it moves: the testing window shrinks by a week and go-live risk goes up. Your call.” Nine times out of ten, the request evaporates the moment it has a price tag. The tenth time, at least the trade-off was made consciously, by someone with the authority to make it, and it is written down when everyone conveniently forgets later.
Build yourself an air-cover committee
You cannot out-stubborn an executive sponsor, so stop trying and recruit one instead. A steering committee with real authority is your air cover: it absorbs the political pressure, kills the scope creep that you cannot kill, and gives your team permission to focus. Two rules make it work. First, escalate early and in writing, with options attached, never just problems. Executives engage with decisions; they tune out status theater. Second, make the sponsors say no to their own pet features in front of each other. Peer accountability among executives accomplishes in one meeting what months of project-manager diplomacy cannot.
Staff for the reality, not the org chart
Here is the staffing implication nobody puts in the project plan: when upper management will not engage, your team has to be self-sufficient. A cloud ERP migration led by junior consultants waiting for decisions that never come will stall, and the stall will be blamed on the team, not on the absent sponsors. This is exactly when you need senior people who have seen the movie before: consultants who can make reasonable calls without a committee, who know which corners can be cut and which will kill you, and who have the credibility to push back on a VP without getting fired. Experience is the shock absorber for weak sponsorship. Budget for it like the insurance policy it is.
The executive one-pager
If you take one artifact from this post, make it this. Every two weeks, put a single page in front of your sponsors with five sections: where we are against the date, the top three risks in plain English, decisions needed this week and from whom, what changed since last time, and what you need them to do. One page. No appendix. If they will not read one page, they were never going to read your thirty-slide deck either, and now at least the important stuff had a fighting chance.
