Design Process Model – The Data Gathering Key Validation Point

The high-level model presented in my last post shows three major validation points.  These come at the end of Data Gathering, Analysis / Synthesis, and Creative Development.  In this post, we are going to deal with the first major validation point, Data Gathering.

Key Validation Points

At the end of Data Gathering, you should have all client needs and a complete site analysis.  The overlap with Analysis / Synthesis is included to provide you the opportunity to go back and ask more questions or gather more data as needed.  In the process of gathering data, you may undertake some analysis that leads you to reconsider the need for more client input or site data.  You should use this key validation point as a test to determine to your complete satisfaction that you have done all necessary data gathering.

Client needs are the most difficult to gather and validate.  As I have mentioned in previous posts, you may have clients who are not aware of all of their own needs.  You may also have clients who are less than forthcoming about their motivations for the project and their expectations.  Given these types of obstacles, it is necessary to approach client needs gathering in a variety of ways.  Asking questions isn’t really enough.  You need to observe the client and their environment to confirm what the client is saying is consistent with their lifestyle.  Asking the same question in different ways at different times may help you confirm that the client is consistent in what they are asking for.  Asking the client to pick samples of things they like such as hardscape samples or softscape materials can also help confirm that the client is clear and consistent.  At the core of any client needs gathering process is the ability to get the client to tell you what they really need, rather than their preconceived solution, what they think you want them to say, or what they think you might be able to deliver.

The site analysis portion of data gathering is more straightforward.  However, it should go beyond simple measurements and note taking.  Digital pictures or drawings are usually helpful.  Viewing the client’s site from different perspectives or at different times of the day can be useful.  Evaluating the neighboring properties and the neighborhood or community can help provide context.  There are also the very specific tasks such as soil samples, surveys, etc.  One of the key points in site analysis is observation.  The context of how the property is currently maintained and landscaped is important.  What the client may have done in the past can provide clues to their tastes and preferences.  Observing the details of how the site is viewed from the outside in and the inside out may provide you with ideas that you can capitalize on later.

In a subsequent post, I am going to go into detail about the specific methods, tools, and techniques you can use to gather the client and site data.  But for now the validation questions you should be asking yourself are:

• “Have I captured all of the client’s needs?”
• “Do I know what the client does not want?”
• “Have I cross-checked and confirmed the client’s answers to my questions?”
• “Do I understand their tastes and preferences?”
• “Can I describe the client’s lifestyle?”
• “Do I have all the site data I need?”
• “Do I have an understanding of how the site relates to the surrounding properties?”

If you feel confident that you can answer these types of questions, you should be done with Data Gathering.

This is a key validation point for a reason.  Missing or incomplete requirements are a huge risk.  This includes requirements that were never identified, requirements that are not fully understood, requirements that are changing, requirements that are not prioritized, and requirements that are  wish list items.  You have to have ALL requirements, and fully understand them.  You also have to know where they stand in the client’s priorities.

The site itself is not so much a set of requirements as a set of constraints and opportunities.  Incomplete site analysis may mean designs that are not feasible due to constraints or missed opportunities to capitalize on existing assets.

The natural tendency is “the smaller the job, the less data gathering you do”.  Regardless of the size of the job, there are two big holes to fill in.  The client, who are they, what do they need, and the site, what do you have to work with.  Realistically you do have to scale back what you do when the scope of work is extremely small.  However, given that, you should be open to learning as much as possible about the client.  That information may come in handy in the current project and in the future.  Also, evaluating the entire site may lead to future projects.

Upcoming posts will go into detail about the methods, tools, and techniques used within each phase.  I will also be discussing the remaining two key validation points that come at the end of Analysis / Synthesis and the end of Creative Development.