I met with a client a couple of weeks ago who admitted that his knowledge of the internet was more or less zero, yet he managed to make me rethink the way we handle a lot of our website projects.

Now this guy is a Baby Boomer and has spent most of his life dealing with patients in his health practice and very, very little on the computer. He asked me to come in for a meeting and after a while I agreed that we’d build a website for his company.

We started to discuss the specifics of the agreement and had no problems fixing on a price and a design. He asked me how long it would take to complete the project.

"About a month", I answered.

His simple answer was "Why?". He went on, "If I can see a patient whose case is new to me, treat them and get them out of the door inside of an hour, why do webdesigners need a month to get their job done?"

Now, granted, he didn’t have the best view of webdesigners (the last one he’d contracted with had promised delivery in two months and hadn’t provided it within four months, which is why he came to us), but he had a point. Back when I started building websites, it really did take a month or more to build the design, copy the HTML template over to each new page and then to go back and forth with the client until the design was fixed. After all, once the website was complete, it would be a pain in the rear to make any changes. But now with Joomla, should I really be using a month as the default timeframe for a relatively straightforward site?

Simply – no. Theres no reason why Alledia can’t turn around a Joomla website inside of two weeks. And thats what we agreed on with the guy. We worked a little overtime and put off some in-house projects for a week or two, but we got the site done in ten days and found a new way of working.

We’ve done two more projects in the same way since and will probably keep doing it. Turning around projects in two weeks rather than one or two months means that:

  1. The client is more focused. Documents needed for the site materialise rapidly when the deadline is only a day or two away.
  2. We’re more focused. Like it or not, a deadline atmosphere is productive.
  3. We’re more profitable. We turn over more projects
  4. Our prices are cheaper. With a loose or far-away deadline, past clients often wanted to "try things out" and then put them back the way they were, or spend hours on a small issue, increasing the cost of the site. That can still happen, but now clients often prefer to launch and then wait for feedback from the clients and business partners who offer more practical ways to improve the site.

Has the quality of our sites suffered by working faster? I don’t believe so. After only three sites its not easy to tell, but we’ve spent the same number of hours on 2-week sites as we did on 2-month sites and we went through the same number of mock-up and revision phases. Simply, I’m now less inclined to believe that the umming and aaahing that goes on during the webdesign process helps more than does increasing a company’s speed-to-market.

Obviously there will still be plenty of large and complex projects that will need many weeks, and sometimes our schedule may not allow for such rapid completion, but in general projects that come to us requiring a template and off-the-shelf Joomla components will be complete within fourteen days, if thats what the client wants.

  • http://www.authoritysitepro.com rSean

    Terrific post! Thank you for sharing your new found (and speedy!) process. It’s good to hear that you are not sacrificing quality for speed, but rather using the deadline for motivation and drive. I feel it’s a very smart way to use something that is generally considered “negative”.

    If you have any more insight to share, please post – I’ll be reading. ;-)

    Sean

  • http://www.salyris.com Sean Cook

    I totally agree with your assessments! We struggle with this on large projects, but clients love our speed on the small one’s and this is very important to them. It depends on the client, but speed seems to be a constant in my personal experience and that should be on your mind if you are a developer/web designer.

    Side note: I was going to blog on my site just like you are doing here and now you saved me the time and effort! :P

    I read this blog every day! Keep it up!

    Regards,

    Sean Cook, MBA/TM

  • http://drupal.digidiamond.net Jon

    Normally I don’t post to these types of discussions but since this article is ranked so high on google I feel compelled.

    Exactly how many overtime hours were spent? I’ve been developing sites for over ten years on just about every CMS out there and my team can churn out a quality site in about 14 days or three weeks. But it took months of streamlining to achieve this process. I don’t believe a paradigm shift can achieve this in a single day.

    Cracking a whip and making people who are probably underpaid and certainly undervalued give up their live so a client can get a 2 week jump on a solution that should be long term seems like a bad business practice for everyone involved…

    I hope others that see this post will not mistake it as a reputable information and instead see it for the marketing hype that it is.

  • the future

    I’m sorry but you are wrong, and since when did speed mean quality. If it took you two weeks from concept to final design of a site than you are doing something wrong. Design should be a well thought out process not a two week race to the finish. It’s people like you that give designers a bad name.

  • Lao

    I came across this blog because I am just getting into web design and was curious how long sites typically take. I’m currently working in graphic design. Two weeks seems like a ridiculously short time frame to complete even a straightforward site. Clients I currently deal with sometimes take several days just to decide on simple printing designs. Working overtime just to please an unrealistic client seems like a step in the wrong direction. It does however make Alledia look awesome (at least for the time being), which I suspect is why this post was written in the first place.

  • Raggs

    Too bad this thread has gone somewhat stale. It is a great topic. My company has been building websites for over 12 years. We have built massive database driven web applications which take months to complete and small mom & pop info websites that can be completed in a few days. The whole kernel of truth is that with the proper planning, story boarding and production plan even a moderately complex site can be constructed in 2 – 3 weeks. Where we run into challenges most is the client not providing the necessary information about their business for us to complete the design and construction. If that is handled appropriately at the front end and you, the web designer, are in “control’ of the dialog, then it is possible to accomplish the impossible. The idea that you cannot design, develop and execute a quality website in 2 weeks using the wonderful tools available today just doesn’t hold water anymore

    To imply that working overtime to complete a project is somehow wrong and damaging to your business and people is very limited thinking in my point of view. We live in a :30 second society, where speed and timing are king. I would suggest that those who are unwilling to push the envelop and build these “impossible” sites in 2 weeks, simply get out of the way and let us do it It can be done, we have done it on many sites.

    That said, it does NOT apply to ALL sites. You must pick and choose the ones where this production scheduling and accelerated development make the most sense for your company. I have no problem advising a client that their complex and highly interactive e-commerce web application is going to take a month or more to build. But not all sites meet this standard. We shouldn’t lump every web site build together into a single model.

  • Amthony

    2 weeks is rare and only under ideal circumstances. unless youve got 4 people working on it at the same time. Interestingly there no link to these sites. I don’t imagine they look terribly original. And im pretty certain most web developers would look and in 5 seconds know immediately that it’s a canned joomla site. And there’s the issue of whether or not joomla is right for every client which it’s definitely not. You could create unnecessary problems for both you and the client. And let’s not even talk about how many times the client will break it if you give them the admin keys. Sometimes the last thing you won’t to do is introduce an unnecessary data base. It adds variables to the hosting and uptime equation. There are often times when just one or 2 services on a server can be down, if one of those services happens to be mySQL then your sites down, when if it didn’t rely on a database in that case it would still be up and without issue. I can say from experience. WordPress and joomla etc. are very tempting to build your business around because they “SEEM” to be the latest “get rich quick” ticket for web developers. But in the end often you have a bloated site that’s not quite what the clients wants in looks and functionality. You’ve got to try to maintain and trouble shoot code that was written by others, (and joomla? Boy were talkin A LOT of code) They also need to be consistently updated for security fixes, and if your hosting clients on your own server you sure as hell better make sure you keep ALL your clients up to date. Or they will be calling you asking why they are black listed on google, and why does it say my sight contains malicious content, and why are people e-mailing me telling me I spammed them… AND THEN because of those updates the plugins need to be updated, but ooppsie the maker of the plug in has not fixed his plugin yet so guess we’ll just have to do without pages 2 and 5 untill the plug-in is corrected and who knows when that will be. Oh wait the clients on the phone, what you can’t bring up your site? Oh yea ok mySQL is down temporarily. You understand don’t you?.. (yea sure try explain all this mud to a client who doesn’t care to hear it)…. Joomla, wordpress etc. very good frameworks for the right clients when developed by the right developers. But I would never suggest to anyone that those CMS are the answer to all your scheduling , production, and money woes….