Here is something that everyone may not know. In the 10+ years that I led project delivery, most of the projects have been on or ahead of schedule. Rare as it in the IT world, in the ERP world, its even more rare.
So, am sharing my learning of how it was possible to make people go home at 5, and still deliver on or ahead of time in the very dynamic, very slippery world of ERP delivery to large clients.
It was actually, quite simple. In Hindsight. Here goes:
- They are not consultants. They are project managers.
2. De-glamorise the "Late Stayer"
Yes. One of the most powerful things we did was to make it negative to stay long hours as a matter of course. When someone stayed late, I called them the following day to ask which part of their work plan had failed, to force them to stay late. If they tried to tell me that there was too much work, I asked them whether they created a project plan for 8 hour work day or 10 hours work day. If they had budged for an 8 hour work day, why was a 10 hour work day necessary. Just this one step of de-glamorising the late stay, allowed us to send people home at reasonable time. I learnt this from the leader at SAP GD when I joined.
However, I also actively communicated why it was important for them to go back and sharpen the axe, how their personal time contributed to their in office productivity, and how, in insisting that they plan for, and deliver in the same time, they were training to become better leaders and role models of people in the future.
3. Active Risk Management
Most of us view Risk Management as a set of templates and formats that need to be filled in. But I am a strong votary of Risk Management because I have seen the miracles it is capable of. We entered Active Risk and Opportunity Management in the internal reviews, in the leadership decks, in everything. Just keeping an eye out at all times helped everyone immensely. That's why, one of the first disciplines I wanted to create in the non profit world, was Risk and Opportunity Management. The common sense variety. Not the template and format variety.
4. Templatise, Templatise, Templatise
I cannot count the number of times team members have come back and said, "The requirements are unclear." and the number of times they have heard, "No. You did not ask the right questions."
Using all those years of experience, esp in HCM, I created question templates that were in the language of the client. We used those to get requirements, and we found that when we asked the right questions, we got the right answers. If the client did not know the answers, they at least knew which questions they needed to answer and why. And that took away the biggest risk to ERP delivery - "Changing/Unclear Requirements"
I think the biggest change we need to make is in ourselves - as client and delivery leaders, in believing that it is possible to create productivity without urgency. With that, the rest of the change happens, as it were, in a Domino effect.