If you're the least bit hesitant to ask for preliminary commitments from key participants, spend a moment to think back to a project where a key player's "schedule" forced you to revise your final plan and to go back to several other participants and/or the Prime for new dates/commitments. The bigger the project, the more important preliminary commitments are and the more disastrous 11th hour back outs can be.
Practice a short, clear, preliminary commitment request before you ask it of the key player. Actually say the words to yourself.
- "George, I'm firming up my Alpha project plan and wanted to know if you could commit to delivering milestone 'X'' on the 15th of May if John gets his completed do-hickey to you no later than the 1st of May?"
- Roberta, could you check your planner for a second. I'm putting my Beta project plan together and I need to know if you will have the 10 hours we discussed to complete the 'Z' milestone during the week of January 2nd. Maurice will need that milestone no later than Friday of that week if we're going to stay on schedule."
Don't be satisfied with anything but a "Yes" or "No" AND a notation by the participant in their planner. For the sake of your credibility, let them know that this preliminary commitment may have to shift somewhat (you're coordinating the input of several people), but (a) you'll try to avoid any changes that would impact their schedule and (b) if they have a priority request for the time they've committed to you, that you'd REALLY appreciate a call before changing anything.