Develop request to L web Dev net
14 client-screening questions to ask before designing a site
Website design client questionnaire to understand your clients’ needs
ALL OUR WEB SITES WE DEVELOP ARE RESPONSIVE [for all screen sizes] !!!
- Your Budget in Euros? eg 500 Euro
- Language(s), English, Greek, Russian,…?
- Total menu items (separate individual web pages)?
About, Contact, Home Page, …, Photos, Description, Booking, Prices, Terms.
- Total Images, Videos, Sounds, & Ready the Texts [in all languages] get inserted?
- Flash content (RIA), jQuery/Ajax/DHTML, part of or all …?
- Dynamic or Static? Database functionality or not? Advanced Site using PHP Framework like CodeIgniter/CakePHP [Login, Database, CMS…etc]
- E-commerce Site? CMS Site? Blog Site? …. Forum Site?
- Mobile App === Web Mobile App or Hybrid Mobile App or Native Mobile App?
Develop Enquiries: webmaster@L-web-dev.net
Web DESIGN / Web Re-DESIGN QUESTIONS – in more detail
[written for developer/designer viewpoint – so read appropriately]
Here are a few of the questions I like to ask in initial client meetings, even if I’ve already established the answer myself via a search engine:
■ What does the company do?
■ What is your role in the company?
■ Does the company have an existing logo or brand? What is your goal in developing a website?
■ What information do you wish to provide online?
■ Who comprises your target audience? Do its members share any common demographics, like age, sex, or a physical location?
■ Who are your competitors and do they have websites?
■ Do you have examples of websites you like or dislike?
■ What kind of timeline do you have for the project and what is the budget?
If the project is to redesign an existing website, I also like to ask:
■ What are your visitors usually looking for when they come to your site?
■ What are the problems with your current design?
■ What do you hope to achieve with a redesign?
■ Are there any elements of the current site that you want to keep?
■ How do you think your visitors will react to a new site design?
This is a rough list that can serve you well in any project. We’ll call it our “Need to Know List.”
- Who is the intended audience?
■ What is their age group and demographic?
■ Is the audience computer literate?
- What brand guidelines must be followed?
■ Are there color or design guidelines?
■ How closely do we need to stick with the brand’s identity?
■ What tone do we need to establish?
- What is the site’s intended purpose?
■ Are there marketing goals?
■ Is the client trying to sell a product or service?
■ What are some of the goals that the client hopes to achieve with the site?
- What is the site’s content?
■ What is the subject matter of the content?
■ Is the content structure complex?
■ How much content will be on the site?
■ Will the content constantly change or will it be relatively static?
- What additional restrictions are placed on the project?
■ Does it need to be viewed on legacy browsers or special devices?
■ Will the site be updated internally?
■ Does the site form part of a larger campaign?
■ Does the site need to work in conjunction with other media like print or film?
- What should we avoid?
■ What is off limits?
■ Should we avoid certain design choices?
- What is the project budget?
■ Is the amount the client wants to spend realistic for the project’s requirements?
- What is the project timeline and production schedule?
■ Does the client have realistic expectations for how long the project will take to complete?
■ What benchmarks need to be met?
■ What responsibilities will the client be taking?
This list is by no means complete. It serves as a basic starting point for communication between you and the client. You’ll probably never be able to anticipate all the questions that need answering over the course of a project, but this is a good place to begin.
The Bottom Line Recap of What You Need to Know
■ Talk to your client and study their business from a broader perspective, covering areas such as their:
■ business offering
■ customer relationships
■ business infrastructure
■ revenue streams
■ cost structures
■ Collaborate and communicate with other stakeholders.
■ Balance business needs (is it feasible and viable?) with user needs (will people want this product?).
■ Understand the end-to-end service customers currently experience with the business.
■ Think about the human context:
■ Who are your users?
■ What are their key tasks?
■ What will define a great experience?
■ Know which behaviors you’re targeting for change.
■ Make a plan for your project and consider what you should be mindful of at this point.
■ Set a clear project vision and refer to it constantly; this statement will help you and your stakeholders navigate through the project and make clearer decisions.
It is necessary to consider the financial drivers of your client’s business. Are they driven by a focus on creating low-cost and no-frills products, or is their goal to create a premium product? Knowing these drivers will affect your design work, as does knowing the client’s main source of revenue. The following questions will help you to distinguish the client’s revenue streams:
■ How does the client make money from customers?
■ How does the client make money from partners?
■ How do customers currently pay?
■ What do customers pay for?
■ How much does each channel contribute to overall revenue for the client?
■ What is the total value customers are willing to pay for the product?
The following questions will help you to identify the client’s cost structures:
■ What are the most important costs to the business?
■ Which resources are the most expensive?
■ Which activities are the most expensive?
■ Is the client looking to cut costs through the use of technology? If so, how?
Why does this project matter to the client?
The following questions will help uncover your client’s goals and objectives for the project:
■ Why is this project important to the business? Why was it initiated?
■ How will the success of the project be measured internally?
■ Who will be involved in determining the overall success of the project?
■ Who is paying for the project (often referred to as the “project sponsor” if you’re working within a larger corporate setting), and how will they be involved?
■ What other areas of the business should be invited to participate in your process?
■ Who will manage the expectations and involvement of other key stakeholders? (You? Your client?)
■ Are there dates, time frames, or other projects that your work needs to tie into?
■ Are there internal processes or constraints that you’ll need to be mindful of, or work within?
Understand the Target Segment
As a guide, you should focus your discussion around the following points:
■ Who are the assumed users of the client’s product?
■ Why are these users being targeted for this product?
■ What are the most critical tasks users need to complete in using the product?
■ How do users currently perform these tasks (without the use of technology)?
■ What behaviors are we hoping to shift or change in our customers with the product we’re creating?
■ What would trigger the users to want to engage with the product?
■ What does the entire experience around the product and its use entail?
■ How would the client define a great experience for the users of this product? Why?
■ How does this experience fit with the other products and services the client has on offer?
This all comes back to gaining an appreciation for the eventual context of use for the product; importantly, it also makes you think in more detail about human behavior in relation to your product.
2 Replies to “Develop request for a Web Site / Mobile App”
Pingback: Old Hallmark Romantic Movies