Project Management Tips

Killing the Voice Inside

Handling criticism at work

The project's deadlines were tighter than any Harold P. had ever taken on, but there were reasons he took on the challenge despite every little voice in his head telling him, no, screaming, the same uneasy message - we're way out of our comfort zone on this one Harold. As Harold sat in front of the VP of Technology for one of the largest PR agencies in the country, all he could think about was the six-month deadline, for a project that should take at least a year and a half. He wasn't even sure the project was feasible, but it meant big dollars for his small programming company, and he wanted to take it to the next level of revenue and project size. Harold knew it was a big risk, but he also believed that no one got anywhere without taking risks, and he figured he would do everything possible to hedge his bet. This was the right opportunity, he thought, even if he wouldn't sleep much for several months.

The project got off to a reasonable start, programmers striking keys, screens filling with alien text more reminiscent of math formulas and functions rather than what your normal person on the street would call a language. Harold received a call from the VP of Technology, requesting Harold's presence at his office. "We have a huge demo next week for the boss's boss," said the VP. "The program needs to do something, it doesn't really matter what, it just has to move." Harold scratched his head, replying, "That's not really going to be possible, we are three weeks into this puppy, and we're nowhere near ready to show you anything. We've got large amounts of back-end work before the first character will appear on anyone's monitor." The VP frowned as he walked around to the front of his desk, leaning against it near Harold. He bent down a bit towards Harold, as if to slightly violate Harold's personal space and said, "Harold, I need to show these guys something, so get your people to make something appear, it's that simple. If you can't do that, then I might have to consider finding someone else to finish the project, someone that can give me what I need. And by the way, there isn't anymore money in the budget, so this work will have to fall into the general fee already agreed upon between us."

Harold was angry about the added work. He knew he had no choice in the matter, but the demo would basically be a useless program written simply to please nervous and compulsive management. They insist on seeing 'something', while unbeknownst to them, that something is really a lot of nothing. Harold wasn't sure how he could take on the extra work, but with no other options he called Alexander, his programming lead and set things in motion.

Months passed and the program grew in size and functional ability. As the program matured, so did the demo program meant to represent the 'real' application underway. Early on, Harold realized that building and delivering the actual program was going to be difficult enough, but with the added demo program, he was working non-stop. The production pace was intense and he had missed relaxing on most weekends. Despite the workload however, Harold was able to smile to himself, even on those tired, late nights, as he felt a surge of pride about how well the project was coming together and how slick it would be when finished. "There was really nothing like it," he thought to himself, "everyone is going to be impressed with our company for the work we're doing on this one."

Deadlines Made Worse

Early one morning, Harold received a phone call. It was the VP of Technology. "Harold," he said, "how are things going with the application?" Harold immediately tensed up. The VP continued, "I met with the bosses and they kept repeating something you're not going to like. They need the software early." Harold felt his stomach start to convulse. "Early?" Harold responded weakly, "We are doing everything we can just to meet the already approved deadlines. The programmers are tired enough, and have been pulling all-nighters, how do you expect me to bring this one in early?" The VP of Technology fell silent, and then replied, "Listen Harold, I need you to come through for me on this one. Do what you have to do, because our neck is on the line." All the while, Harold thought he was kicking butt, stepping up and making the mark, but this new request was unreasonable and he wasn't quite sure how to handle it. Harold understood what tight deadlines do to his people, and he didn't need anymore proof of their loyalty and commitment. He could see the wear and tear the project was having on his programming team, and they weren't even in the homestretch. Harold grew depressed and started feeling overwhelmed. He had never signed up for a project of this size, and he wasn't entirely prepared to deal with this new demand. The entire time, Harold thought he was doing a standup job, but now he started to doubt it.


Continue...


Back to project management tips