Yesterday I had lunch with one of my best friends and all around stand-up guy, who also happens to be a web designer. Like the complete geeks that we are, we spent the entire lunch discussing web design, a possible JV project, common pain points etc., but most of the conversation revolved around the difficulties with project definition and scope creep.
I spend most of my days talking and working with web designers and developers, and hands down this is THE most common problem that I hear across the board. With that in mind, I thought the topic of defining the scope of a project would be perfect for Web Design Business Builder since that is what so many designers and developers struggle with.
The scope creep scenario usually plays out something like this:
…Midway through a web design project, your client sends you a Word doc with 21 unexpected pages of content that they have decided to add and expect done at no additional cost.
…Or after your client signs signs-off on the design, they show it to a partner or friend or their mom, someone who “really has an eye for this sort of thing”, and that person says that the website doesn’t look good. Your client, who yesterday loved your design, suddenly doesn’t think it is very professional, or that it doesn’t reflect their image. Of course they expect it to be revised at no additional cost.
Unfortunately, not only are the above scenarios of a project-gone-wild, frustrating to us, but it usually becomes frustrating to our clients as well. They had planned on adding those 21 pages from the beginning and thought they had mentioned them to you, so they are surprised when you didn’t expect them. They assumed that revisions where included in the package so completely changing the color scheme and layout of the site at the end of the project doesn’t seem like a big deal to them.
I call it Project Frustration Disease. In the end you become a frustrated web designer who often dislikes, or is at least annoyed by their own clients, and your clients feel like they didn’t get what they expected to get in the beginning. And THAT is the root of the problem, to begin with false or vague expectations. You see the battle to keep these projects in budget and under time was lost to begin with because the right expectations, from both parties, were not set up front.
It is too easy to get “just enough” information from a client that you go ahead and start the project. “Just enough” information is the worst amount of information you can have. It is like having “just enough” rope to hang yourself… and chances are you will.
I don’t have all the answers here, but I want to give some solid guidelines to get a conversation started with the hopes that we will all be better off with our next web design or development project.
1. Define the Website Stakeholders
Each project has certain stake holders. The most simple project will have two stakeholders, the customer and the designer/developer. More complex projects may have a client, their partners, a designer, a developer, a project manager, testers, marketing, etc. Each additional stakeholder or decision maker will make the project exponentially more complex and difficult to manage. So the less stakeholders the better, but no matter how many there are, be sure to clearly define WHO they are.
At the beginning of the project you need to define who the stakeholders are and how much say they each have. Make sure a business owner doesn’t decide this whole website thing is way too much work, and then give the project to a secretary, who in the end doesn’t actually have any decision making power. That is where you get to the end of the project only to have the owner step in and pull the rug out from underneath you.
2. Set Signposts Throughout the Web Design Project
These signposts are meant to be markers along the way to signal all parties involved that the project is going in the right direction. Every signpost should require the sign-off of each of the defined stakeholders.
Like any signpost when you are traveling, you should not pass the sign without everyone in agreement that you are on the right path and going the right direction. Don’t start integrating content until the template design is signed-off on. Don’t start the template design until the wire frame layout is agreed on.
Be sure to get the sign-ff for each signpost in writing. Don’t let your customer be a pansy! It seems easy at first, but it will only hurt you in the long run. Force them to say yea or nay. Tell them that you are at a stopping point and can’t continue until you have their sign-off on the completed work. Once you pass a signpost you can’t go back without additional fees.
3. Strictly Define as many details as possible upfront
There is no room for being vague here. Chances are, you are not asking enough questions and nailing down enough details. Exactly how many pages do they need? How many slides in the jquery slider? How many stock photos? How many services in the accordion content menu? Notice a theme? “How many”, get solid numbers on everything.
Again don’t let your customer be a wimp here. Yes, it is true that often a client has no idea what they really want. This is how you become their “trusted adviser”, lead them! Tell them what they need. If you don’t know, research it before you talk to them. See what their competitors are doing, what pages do they have? How could you improve your clients site compared to their competitors.
The battle for keeping a project under control begins at the beginning. Remember that you can always be flexible if the client wants to add more and you think it is reasonable, but defining who the stakeholders are, setting signposts and agreeing to all the details upfront, gives you the power to easily keep a project under control.
With these guidelines you can stop project scope creep in it’s tracks. No more web design projects-gone-wild, no more angry clients, no more wasted time, no more Project Frustration Disease!
What stories do you have of Projects Gone Wild? What did you learn from it?