Project Management Tips

Killing the Voice Inside, continued...

Handling criticism at work

Back to page 1


Soon after, Harold sat down with Alexander and discussed options for bringing the software in a little early. "You do realize," Alexander said, "That our testing and quality control will suffer greatly if we deliver when these guys want it." Harold could only nod in understanding. "Forget about testing this thing thoroughly," Alexander repeated, "if it breaks, don't come looking for me." Harold figured the trade-off was worth it, the project would be brought in on time even with the potential for some minor quality issues. We can always fix them after, he thought to himself. Harold contacted the VP of Technology to give him the news. "It looks like we can bring things in by your deadline," Harold said, "but it's going to be very difficult. We are afraid that this new push will result in the quality of the tool suffering somewhat." The VP paused a moment, and said, "Look Harold, we don't have a choice here, the product has to work, and it will work. I'm counting on you, and I know you can do it." Harold repeated his concerns about quality suffering, but the VP rebuffed quickly, "Harold, I understand your nervousness, but this is the way it has to be, and there's nothing we can do about it. Make sure you have a piece of software that is 110%." Harold knew he was on shaky ground promising something unrealistic, but he didn't want to blow the deal. Even if he damaged himself with worry, the project was going to work.

More Pressure as the Launch Date Arrives

The early launch date was fast approaching, and Harold and the programming team were exhausted by the speed and amount of work. Harold had a constant cough, and suffered from cold-like symptoms. The programming team started sleeping in the office most nights, taking turns on the office couch. One fellow even brought in his camping tent and put it up in a corner of the office. But, the program was looking pretty solid. The back-end was functioning as intended however some front-end screen stuff still looked a bit raw. Harold figured they could clean it up before the presentation Monday, "that stuff is easy," he thought, "we'll do that last minute."

The VP of Technology called again that morning, and wanted to know the project's status. "Things are looking good," Harold explained. The VP seemed pleased, and asked Harold if he could see the actual program. Harold was hesitant. Up until now, the VP had never seen the actual product, only the demo system. Also, some of the screens were simply not finished. He was concerned the VP might misunderstand the tremendous progress they had made seeing unfinished screens, while not realizing that most of the work was on the back-end. The little voice in Harold's head told him to come up with an excuse not to show the VP anything just yet, but Harold was also feeling a decent amount of pressure to show him the progress.

The VP pushed Harold again, and he acquiesced. He gave the VP the web address to the software repository, and he could hear the VP's keyboard clacking under the pressure of his rapid fire typing style. A long pause took place while they were on the phone, as the VP reviewed the software screens. The VP cleared his throat and began his speech, "Harold, I'm quite confused with the current screens you're showing me. It seems like we've gone backwards instead of forwards. I remember the screens we saw a couple weeks ago, and it seems like we're not as far along as I believed. I am sort of in a state of surprise here." Harold could feel his stomach knot up. He bent over in his chair and hunched forward while the VP continued, "Harold, I'm really worried. This is just killing me. What are we going to do? I thought you had this handled?" In a meek voice, Harold replied, "Listen, this system is farther along than what you've seen. I know you think otherwise, but the real advancement is on the back-end. We are making tremendous progress and I really feel we're on track." Even though Harold knew he was right, he couldn't shake the deep sense of disappointment that came over him. The VP said, "Well Harold, I have no choice but to believe you, even though frankly I'm confused here. I'll talk to you in a couple days." He hung up.


Continue...


Back to project management tips