- First, be clear on speed’s priority: Although speed is in the top 3 conversation pieces of every executive I’ve talked with in the last year, it doesn’t mean speed is a priority in every situation. I’d be surprised if every executive didn’t say “accelerating progress” was important; thus, just confirming this desire is not enough. Instead, you must probe further to better understand speed’s priority vs. other priorities.
Just having a conversation is a great place to start. In many of my clients, assumptions are made as to what the executives prefer, yet no one wants to ask/confirm. After all, who wants to take a risk and look dumb? You must! Be willing to ask clarifying questions.
For example, in one of my client projects, I’m partnering with my client to implement a sales and operations planning process. It is a corporate priority and can have a significant effect on whether the facility will meet its budget goals, and so it’s obvious that accelerating progress is critical. However, how does it compare with quarter-end results in terms of importance? Or with safety and quality goals? How about overtime pay? Have a discussion with the project sponsors and executives. Make sure they understand their choices and tradeoffs. Gain clarity in advance.
- Start with the right mindset: Once the project leader has clarity on the priorities, it is important to take the time to frame the mindset with the project team. It might sound like the opposite of what you should do on a project where speed is vital; however, taking an extra few minutes, days or weeks upfront will accelerate progress in the long run.
For example, I’m working with a client on better leveraging their ERP system. The right mindset can take weeks to obtain yet it is one of the most important ingredients to gaining speed. What is the right mindset?
In this case, the project team could think we need to replace the old processes with an improved process upfront since we spent a considerable amount on the new system. Or, the team could think that because we didn’t have solid processes in place that we should implement “best practices” and go 100% with whatever the new system requires – should we do that regardless of our employees’ preparation? Or, on the other hand, the team might think they want to get back to their normal jobs (which align with their performance reviews), and so they just want to get the system done rapidly, even if they sacrifice a little in terms of quality.
Let’s stop right there: if you skipped step 1, you must go back as you won’t know which of these many options to choose – and communicate! Then, no matter which option is chosen, I’ve found it is dramatically more successful to have the mindset of “if we’re 80% ready, GO”.
On any project especially one of this level of effort and importance, people will see it as their “ticket to success” and lean towards moving only when 100% ready. Or, they’ll go when 60% ready because they want to get back to a regular routine or they have no idea they are at 60%. Thus, you will have to continually remind people, mentor people and reward people for moving when 80% ready.
- Plan the work & work the plan! I know this advice sounds simple yet it is one of the most critical elements to accelerating progress on any project. Again, when speed is a priority, you’ll have to fight to take the time to develop a solid plan; however, I’ve found repeatedly that without a plan, your project will be guaranteed to take longer than you’d ever expect. Take the time to define the key tasks. Which are on the critical path? What are the key elements?
For example, in one client project to improve operational performance, the team truly believed they produced more with the “flexible/ no plan” approach they had in place. There was significant resistance to creating a plan, even a short-term plan. After all, speed was important. No one wanted to waste time. If you run across this roadblock, suggest a trial. A trial or test can be performed on a limited scope (perhaps 1 task) with limited resources yet it gives you the opportunity to prove out the need for a plan. Again, go back to step #2 – when 80% ready, GO. Thus, do not create the perfect test or trial as it will fail.
Once you’ve developed the plan, the 80/20 boils down to execution. Focus. Remove obstacles. Focus. Celebrate progress. Focus. And focus again.
Is your project focused on speed? If not, you’ll be left in the dust. So, why not strategize with your project team on how to incorporate speed? – You’ll achieve not only quicker results but also, most likely, higher-quality results.
Don't forget to leave your comments below.