You’ve been selected to be the project manager for your company’s website. It’s a big project, but a fun project… so be excited about it. You might not be aware of this, but you can have your web developer help you. Not only will the website turn out great due to collaboration, but you will be successful at yet one more project.
Based on over 13 years of experience, here are some tips on how to make this work.
1. Hire the right web developer.
There are many web development companies out there who can do the technical aspect of the job. But you are looking for more than that. You need to find a developer who will help you with strategy and planning as well and who sees the big picture. Do they have systems in place? Do they have a team? Do they have checklists and other documents to facilitate what you need to do? For more specific information see our posting on “How to hire the right web developer for your website“.
2. Know who the decision makers are.
Your boss may have assigned the project to you, but he might not be the only decision maker on the project. Make sure you understand whom you need to get input from. A big part of the success of the project will be coordinating schedules and making sure all feedback is processed.
3. Know how the website will be judged.
Before you even get started, make sure you know what outcome(s) are needed in order to call the website “successful”. You want to clearly understand what the business goals and requirements for the website are so you can keep the developer in check throughout the project.
4. Insist on an in-person meeting between the key decision makers and the developer.
They are busy and that’s why the want you to take care of the job. But an hour or two of their time is definitely needed at the beginning so the developer can hear the requirements first hand, can mediate between contradictory requests, and can immediately follow up with questions. Since you are not the technical guru, you might miss or not even think about some issues that can come up at this meeting.
5. Ask for weekly progress reports from your developer.
You need to show progress and that things are being done. Keep them posted before they ask you how things are going. Your developer should be able to write a quick e-mail once a week to let you know where they are within the project and if any issues have come up.
6. Understand the project scope.
You should understand every line item in the developer’s contract. Don’t let them get away with “it’s technical”. If they are good, they can explain everything in plain English. And, understand it well enough so you can communicate it clearly, by yourself, to your boss and any other decision makers.
7. Require change orders.
A successful project is typically evaluated on whether it was completed on time, on budget, and per the agreed to project scope. If any of these three areas need to significantly change, require that your developer submit the request in writing prior to doing any additional work. This gives you time to get approvals rather than being caught unaware.
8. Do thorough reviews.
When it’s time for reviewing work done, be thorough. Take out your written project scope and use it as a checklist. You also want to involve all decision makers in reviewing the final site map (the architecture of the site) and the final design concepts. You may even want to do so in writing.
9. Be organized.
Part of your job will be to gather all internal feedback, going through it, and making sure the developer gets a clear set of instructions. If you are running behind, don’t just pass on emails hoping that things will go faster. That’s the easiest way to go over budget. And, believe me, the developer rather wait a little than get something they need to decipher.
10. Ask. Ask. And, ask.
Don’t ever be afraid to ask your developer for anything you are in doubt about it. Their job is to make the development process as smooth as possible, and that means helping you.
Have you had experiences managing a website before? Any of your own tips you would like to share?
Recent Comments