Website Strategy: Timeline and Deadline

Whenever we take on a project for a customer whom will be our friend after, one of the basic things teams and clients don’t pay attention to is the timeline. Half the time teams pitching for a project concentrate too much on the quotation and ideas that can be offered but not the timeline. This is a basic but important factor involve in taking on projects especially if it’s part of marketing campaign.

It’s important to be able to get a rough deadline from the client. At least that way, you can prepare a better proposal inclusive with all the ideas that you have. It’ll also help you eliminate second priority ideas you have for the customer’s website.

The timeline is a basic tool that many overlook because half the time it’s hard to be punctual and many have made the mistake of dragging it too long as well. So let’s strategize better here.

It’s difficult to be punctual not because members of your team are burdened by other projects but because the design stage takes longer than expected. By stalling and changing the design over and over again, the client and us are actually procratstinating. Sometimes we need to be firm and tell the client politely that the design or template should be like this then come to a resolve between each other to incorporate the things they want.

After that’s been done and agreed on, both parties should sign on the final design. If you want this to be even more formal, (a little tedious as well) both parties should sign on an agreement stating the design has been finalized and there are no more changes until the project is launched.

From a client’s perspective, I understand that if the team is too quiet I’ll start to worry of what’s happening with the progress of my website. This is a reason that sometimes we have to take the initiative to communicate slightly more with the client. Even a simple email saying that, “We’ve just integrated the design and now are going to start on the backend of your website.” tells a client something is still going on.

There are many online services now offering you to manage projects more efficiently and one of the more reknown one is; Basecamp by 37signals. However, the best of course is still if the client had a prototype to check on the progress later.

Other than producing simple reports to the client, the team will have to always give themselves a little buffer in the timeline. This is incase any unforeseen circumstances does happen. The one known to me most of the time is the client going Absent Without Leave (AWOL) or the website requires further troubleshooting due to the sudden change of behaviour involving the techbology used. A great example later will be when Internet Explorer 7 is released or updated on everyone’s computer.

The final thing I’d like to say about time is that for teams to meet deadlines, keep the client happy and lastly, open a bottle of wine to celebrate. :)

2 thoughts on “Website Strategy: Timeline and Deadline”

  1. Totally agree with you, Danny.

    Timeline should be concentrated.

    Most Clients neglected this and ended up from a 1 month deadline project = 1 year to complete! Cos’ they are too worried with what they had been quoted. Plus, keeps giving ideas and additional materials to be included. This will mean more time and more work! Then, they will scream at you and pushing the job to be finish by deadline.

    Probably from day one, meeting with client to the day the project was started… might already taken more than 1 month due to discussion, exchange ideas, concept design, pre-investigation, info gathering, materials and contents, $$ negotiation, finalizing of contract agreement and etc….

    When we started to work on the project, client will turn up on day 3 and expect something to be done and mentioned they are already late to deliver this project.

    hmmm… and so on… day in day out, client will keep bugging you + keeps giving you extra stuffs to add on… and expecting to complete the next day… Sighs…
    This had prolonged for almost 1 year…

    Then delivery took place, client wasn’t that happy due to late late delivery…. Then pull shietsz on you!…. You will need to swallow this blame.. :(

    Too bad..

    Nevertheless, explain to client slowly with full detail. they will understand the situation.

    Lastly, when they see the BILL!…….Omg….
    There comes the rumble!!! %$#%$&%*

    The bill was rocked up from a 3 figures Quotation to 4 figures!? ??…what the..
    :)

    Then we will need to console them, But who cares. They will pay anyway… else just post them with Legal letters……
    HAhhaha…….

    Anyway…..Timeline to a project must be structure properly + following it as well.
    Both client and Developer has to cooperate with getting the project timeline in order.

    Good luck! This won’t happen till another few years! It’s been this ever since… :)

  2. Really a big thank you for sharing your experience there, Carlson. :)

    That’s why not only a buffer is important but at times we need to have the client on an invisible leash that will help us control them.

    One of these leashes is better known as the if the client is present or stalls on the delivery/response of items, than you can’t be held responsible for the late deadline. :)

Leave a comment