5 Ways a Discovery Phase can help keep your web design projects sane

Feb 19, 2013
Jose Caballer

Regardless of whether you are an internal team, boutique agency or a freelancer – how do you set up a web project for real success?

The answer is; “Date a little before you get into bed together.”

“How do you do this on a web project?” you may ask.

You do this by conducting a Discovery Phase. Your next question might be; “What is a Discovery Phase?” A Discovery Phase is a period of time (4-6 weeks) before you “jump into IT” where you get to know each other better. During this time you find out what your client’s needs are and work closely together to create a vision and a set of shared goals for the effort.

I call it: Stop, Collaborate & Listen. (Yes I know those are Vanilla Ice lyrics.)

Ideally this is done before signing a contract for the subsequent phases and in addition you are getting paid for this dating period.

You might say “But my clients don’t want to pay for a Discovery Phase. They tell me that “they already know what they want and that they just need an estimate from me.” Your response should be; “I can’t give you an estimate until we have a better idea of WHY you need what you want.” And you can also use my classic; “If we put together an estimate now it would just be a WAG (Wild Ass Guess) and we would be lying to you.” What client wants to be lied to? If you tell them this you should be ready for them to bolt. Which is ok. In my experience if we are already at the table, it is because we came highly referred and honesty is usually looked upon with a positive light. The bottom line is that if the client is sufficiently sophisticated they will know that this is needed. Otherwise you have to educate your client as to the benefits of a Discovery Phase.

In my experience not doing this leads to pain and abuse, so I made the choice of no longer taking it. If you educate your community of contacts sufficiently and you don’t compromise on this “dating period” before you do IT (Information Technologies) projects, it will eventually become known this is standard for your practice and accepted by your future clients.

So you are like; “Ok, I am sold that I can sell it but tell me how can a Discovery Phase really help?”

What do I use the Discovery Phase for?

1. To dig deeper and find out what your client really needs vs what they say they need.

You will find that most clients talk about the features they want without referring to why they want these features. That is because they already brainstormed and looked at a lot of competitors and want to do “…something like that.”

Before you spend their money to “build something” per their request, you have to find out if you are building the right thing. For me this became a moral imperative, just because the agency business model is to charge for time spent doing design and development for clients, it doesn’t mean that you’ll just blindly build whatever you’re asked for. You have to do your best to try to build the right thing. Otherwise I would advise you to disclose this to your clients. For example, “Mrs. Client, I can build this website for you, but I don’t really know whether this will work for you or not.” It might be early in your practice and you might not be comfortable doing this, but it’s a choice between saying it at the beginning or having it come back to you in the form of, “What you built for us is not working well. Why did you do that? Did you not know that it wasn’t going to work? You suck!”

2. To find out how and with whom they are doing IT now.

And by that I mean, what do their current web / IT (Information Technologies)  / Marketing efforts look like. What other partners or vendors are involved. The “lay of the land” so to speak. This is when you ask questions about how they are doing things now. To not only see how the car looks on the surface but also to look under the hood and see what kind of engine the car has. Is this an IT dominated organization or is it Marketing dominated? Do IT and Marketing get along? Who are the key stakeholders? What are their interests? Will you be interacting with other vendors? If you don’t ask these questions you are walking into a “Wild West” scenario and you don’t know what challenges lay hidden behind that cactus up ahead.

3. To work together to define the goals for the project.

What are we trying to accomplish? Why is the organization embarking on this effort? This is often called “The Business Driver”. For example, it can be an upcoming tradeshow or it can be pressure from upper management to modernize or revenue has decreased. It can be all three of those. Once you know “why” they are embarking on this journey, work together to clearly define the destination, to set the broader “global” business objective. Unless both partners (vendor and client) worked together to set the destination or goal for the project, one or both partners will feel like their interests are not expressed. It is critical that once you know the destination, you assume the role of guide, have full control of the map (process), and both partners know where you are at all times. Without a destination and without a roadmap your project will be wrought with wrong turns, the stress of not knowing “where we are” and other challenges. If this sounds too much like a marriage it is because it is exactly like a marriage. You have to work at IT to be successful.

4. To create a roadmap for the project.

Now that you know the destination you need to know exactly how you are going to get there. Well not exactly. Here is the catch. In the 20th century, once you set the destination and you plotted a course you then proceed to try to keep that course. The problem is that with a “fixed roadmap” on a three month journey you don’t know what challenges will occur in route. A boulder might fall on your trail and you can’t pass. You might get robbed by bandits who take your mule. Who knows?

But the point is that in software (we are assuming you are building a website here) like in the Wild West, it’s hard to predict conditions in the future.

So how do you map out your project to address the possible bandits and boulders? Set rules for the journey. You get everyone together and you say; “Here is our destination and here is why we are going there. We have some idea of how we are going to get there, but some conditions will change. So you are all on your own. We will check in every 10 miles at these locations. For those of you who are not close to the locations you can use your Walkie-Talkies and call in” (these cowboys have radios, Marty McFly brought them from the future). So now you have cowboys and cowgirls who are smart and independent, all going towards the same destination and checking in regularly. It is not a “fixed plan” but more of a framework for planning and checking in during the journey. If you had two teams of cowboys on the same journey, which do you think would get to the destination faster: the ones that have a fixed plan and work to remove the boulder from their path (as not to veer from their plan) or the ones that have an adaptable plan and move around the boulder or take a different route completely that might be shorter?

5. To get to know the people.

It shouldn’t surprise you that the most important factor in a project is whether you like working with the people or not. The Discovery Phase is an opportunity to understand their individual needs and how best you can tailor your services to the individuals in the organization. Each person and department is going to have a different need. Each of the individuals also has general career goals and needs. I strongly believe that the best web designers, web developers, IT consultants or whatever you want to call yourself are those who understand the individual needs of team members and aim to help both the team members individually and the group collectively to be successful and therefore forward the mission of the company or organization as a whole. If you think your client is a company or a product, you are wrong. The company is people, you are not building a website for them, you are building a website with them. So what is more important? The technical details of the project or whether you feel that this is a person (team) that you can ride with through the peaks and valleys of your journey, taking on countless challenges together and hopefully riding into the sunset together?

In Summary:

  1. Dig deeper to understand the real challenges your clients face.
  2. Understand the lay of the land, so that you don’t get ambushed by bandits.
  3. Define the goal together, make sure that all interests are understood and aligned.
  4. Create a roadmap together and make sure everyone knows when and where you will be checking in.
  5. Get to know the people, find out what their goals and needs are. Individually.

Some of you might still ask; “But how do I sell a customer on doing a Discovery Phase?” The answer is; “educate them.” Tweet out a link to this article, share it on Linkedin, repost it on your blog. Make sure you “set the stage” for when you first meet them by letting them know what you believe in advance.

Find the original article and more like it on TheSkoolRocks.com.