Project delays test perseverance and commitment
Lately, I have been challenged by a problem. The trouble with it is that it is something I really want to do and I keep running into roadblocks. When is the last time you faced something that seemed to be impossible to conquer? Do you find that you doubt yourself?
In the past, my motto has been to go with the path of least resistance. Roadblocks might be telling you to move on. The energy you expend making something work that is unworkable can very draining. Then there is the adage, nothing good in life is free, meaning you have to work at it.
A colleague encourages me to keep going. “Everyone you have talked to says this project has value. It is not the project; your problem is finding people who want to do the work.”
It is hard to believe with unemployment so high, but true.
So here is the situation: I want to launch a new website. The idea was conceived in early 2009 and it has been nine months since writing the specifications for the site. Since then, I have been through two Drupal website programmers.
The first one was probably overqualified and my site does not fit the profile of his clients. It took us about two months to figure out it was not a good match. His projects usually run $75,000 and up.
After we parted ways, I stepped back and decided to teach myself a bit of Drupal. First, it would give me a better way to communicate with the programmer and second, to gauge the kind of programmer I needed for the project.
Several months into the learning curve, I was starting to develop the test site. I fancy technology.
Knowing that I can be an overachiever, it was important to step back and let someone else do the technical parts. There is more to a website than the framework and structure and content needed to be my primary focus.
Fortunately, the first Drupal programmer and I left on good terms and he offered to refer someone who would be a better fit for the size of my project. That was about three months ago.
The new programmer and I come to terms. He begins work on 6/24 to develop the “test site” within 3 weeks; an estimate of 20-25 hours of work.
Several weeks later, I called to find out how things were progressing; I had not heard from him or seen anything. Were there any questions?
He responds that quite a bit of work is done and he’s plugging away at it.
A week goes by and I have not seen anything. I am beginning to get a bit concerned and I follow up with him.
Six and a half weeks into the project, I get to see progress on the site; development is severely handicapped.
It’s time for a conversation. He has been ill and there have been family issues over the last month. He is embarrassed that the project is not done. He offers to let me find someone else or if I want he will continue to work on it.
At this point, the thought of looking for yet another programmer is not my first option. If he will invest the time (remember this is a 20-25 hour job), I am willing push through with him.
A question nags at me though, why did he not tell me about the delays earlier?
He says he’s going to focus on the project for the next few days.
It remains dormant for the next few weeks.
Almost 60 days into the project, I call again on a Friday.
On Monday, there is an email notice from his bank sending a full refund of my deposit due to a project delay. To his credit, he did what was fair.
Perseverance is another one of my strengths. I think my colleague is right, it is not the idea. There is something about my selection process that is not working.
So now, I am in the market for an experienced Drupal programmer to get the test website in action. Some key attributes and skills: technical know-how, accountable, manages project and time efficiently, problem solver, ethical, enthusiastic, easy to work with and most importantly- a proactive communicator. Recommendations?