How Do You Keep ‘em On Schedule?
A perennial challenge is how to keep the team on schedule so your production can proceed professionally.
The last minute scramble to throw things together and get it out the door is nonsense. It will cost you contracts you should have won. I always say the most expensive proposal is one that didn’t win. But really, the most expensive proposal is one that didn’t win because it never got reviewed because it was late or non-compliant and was tossed out before the reviewers saw it. (How ’bout the time the RFP specified that every page be numbered, but someone’s 11×17 z-fold wasn’t, and it got tossed out by the compliance clerk?)
How do you get everyone’s cooperation to stay on schedule?
Storytelling
Never let a teaching moment slip by. Broadcast stories about your near misses and heroic saves that were possible because the schedule was met by the technical staff.
- When a competitor’s proposal was not accepted because the team stepped off the elevator on the wrong floor with less than one minute to delivery deadline, we made sure everyone in the firm knew about it.
- When a FedEx truck broke down with a proposal inside, and we had to empty a PMs discretionary account to courier a backup copy on the last flight out (at 10 times the usual flight cost), we made sure everyone knew about it. And the story included how lucky we were that the proposal team followed our schedule so that we actually had a) backup copies ready and b) time to get on a plane with the proposal.
- When a proposal was due in a remote corner of West Virginia, and our production schedule includes a step to confirm at least two delivery paths, we found that FedEx doesn’t deliver to that town. Because the schedule was adjusted for this, we prepared for electronic delivery to a Kinko’s in that town, where they could print, bind and courier the proposal on our behalf. When the roads became impassable during a storm, 3 of our esteemed competitors failed to make delivery deadline, but we were on time.
- When a proposal was discovered to have a mistake that under-priced the fixed fee by 18%, which we found while running through our production checklist, we made sure everyone knew about our production checklist saving the day.
- When the client server went down the day before the proposal was due, and didn’t come back up for 3 days, but since you’d accounted for the possibility of their new system backing up, you’d delivered 2 days before deadline and then told everyone in the firm about it.
Don’t assume your technical staff has any idea what you guys do once they turn in their materials. They don’t know and don’t care.
But don’t think they aren’t interested in hearing a good story. They are.


Email