In Focus

7 vital questions to ask your web designer

Questions 1 and 2

How would you solve our problems?

Whether you're talking about a redesign to an existing website or you're launching an entirely new product, you're always going to be working to solve existing business problems. Unfortunately, a lot of clients don't share these problems with their designers, which means that work suffers, solutions remain out of their grasp, and costs can easily go over budget.

"Clients should come to the table with a list of problems their business faces on a high level and look to the expertise of the agency to help suggest solutions that solve those problems," says Nick Finck, director of user experience at Blue Flavor. "A website agency will operate much more effectively when they are asked to solve problems around an online strategy than they will if they are told what solutions they should be including in their response to an RFP."

Who's doing the technical work?

Here's a simple reality check: Just because you hired XYZ Design Firm doesn't mean that XYZ will be doing all the development on your website. In fact, a lot of designers often outsource their development work to a regular pool of freelancers, according to Scott Paley, co-founder of Abstract Edge, who says that outsourcing isn't a bad thing, per se. But Paley cautions that clients need to understand the nature of that working relationship.

"It's key for a client or agency to ask their web design firm who will be managing the technical aspects of the project," Paley says. "Is it somebody on staff? Is that person very technical him/herself or is he/she relying heavily on the sub-contractor? If there is a sub-contractor, are they in the same or similar time zone? Or, will all of the work be done during overnight hours with nobody around to fix anything during regular business hours? The client or agency should be looking for answers that provide comfort that the web design firm has somebody on staff who is highly technical and will be managing the project, and will also be in direct contact with the client or agency."

According to Paley, the best thing clients can do when they identify the technical person in charge of building their website -- whether that person is a freelancer or in-house -- is to interview that person directly. After all, you're going to be hearing a lot from them over the course of the project.

 

Comments

Samuel Beavan
Samuel Beavan September 26, 2010 at 5:33 AM

http://www.onevisiontv.co.uk

Samuel Beavan
Samuel Beavan September 26, 2010 at 5:31 AM

Great article but nothing mentioned about seo practice. One of the things that can get forgotten is the importance of creating an xml sitemap, submitting this to Google, creating optimissed URL's and header tags. It's not a given that the design agency will include this as part of the service as I found out.

Sean Breslin
Sean Breslin October 13, 2009 at 9:21 AM

Good article! One thing I would add is make sure You buy the domain name and not the design company!
A small point but important. If you did fire them and had to start again, You own the basic building block the domain name.

Peter Nelson
Peter Nelson October 1, 2009 at 9:48 AM

Some other points I'd add to Michael's fine article.

1. Understand how testing will occur.
Ideally you want to hear the technical guys talk about "test driven development" or a very mature testing methodology. You also want to hear explicit statements about testing on "all" browser platforms (you can define what "all" should be).

2. Don't slough off administrative processes
I've seen time and time again that organization's that don't think about the medium term administration of the application. The organization ends up becoming less and less efficient as they cobble together processes that are inefficient. If you have any kind of e-commerce spend lots and lots of time hammering out all of those flows. Don't forget the nasty use cases of abandonded shopping carts, refunds, complaint resolutions, etc.. These are not necessarily the "sexiest" of things to work on, but they have a major impact on the customer experience and they also have a major internal impact on your overall efficiencies.

3. "Documentation"
Obviously we don't create lots of "pulp-based media" these days, but even so, the process is the same. Think about how best to support your web site visitors with tutorials, videos, PDFs, or PPTs. Here again, if you don't plan for this your organization will be scrambling to support the users reactively and this will give a bad impression to the users and it will put unnecessary stress on your in-house team.

Thanks Michael for a great article!

Michael Estrin
Michael Estrin September 30, 2009 at 1:19 PM

Thanks everyone. And Ken, I agree good open source software with great developers is a wonderful thing.

Bill Ferrara Sr.
Bill Ferrara Sr. September 30, 2009 at 1:02 PM

Great article, Thank You.
Anyone working with a web designer should read this before the first meeting.
Bill PappyFerrara

Ken Mocabee
Ken Mocabee September 30, 2009 at 10:30 AM

Excellent article, and spot on. The only thing I would add is that good open-source software that is implemented and managed by competent developers with good technical skills can be a tremendous cost savings. Where we see some web developers get in trouble is when they get in over their heads with an open-source system that looks great but they don't have experience with it, and when implemented it has problems or deficiencies that can't be addressed. The key is to make sure that you truly understand the open-source products you bring to the table, and that they can meet the client's needs and expectations. It is also critical that the developer has a good strategy for security updates and customizations when needed.

Kit Latham
Kit Latham September 30, 2009 at 10:25 AM

Hey Michael,

Nice overview to the current web development world. You hit the key points !

Bravo !

Kit