What Is The Last Thing You Do Before You Launch A Website?

About The Author

Rob Bowen is a staff writer for Web Hosting Geeks, a longtime freelance designer, and burgeoning videographer and filmmaker whose creative voice and works can … More about Robert ↬

Email Newsletter

Weekly tips on front-end & UX.
Trusted by 200,000+ folks.

One thing that can be said about human beings is that we are, by and large, creatures of habit. We establish routines, consciously and subconsciously, that help us accomplish tasks or move us more quickly or comfortably through our day. Habits are formed in the design and development community just as they are in nearly every other professional and personal environment, and they serve any number of purposes. In design and development circles, one established habit is seen with the launch of a website or project.

Naturally, each of us has developed a process that we engage in as we wrap up a project, but a few procedures tend to be used over and over again by the masses. We know this because we ran a poll on this very topic on Twitter. We got many great responses, but the community tends towards a few common practices. We could see as we looked through the list of entries that certain wrap procedures seem to have mass appeal (judging by the number of times they were given as answers), so we began to examine the benefits they offered and what they say about those who fall back on them.

Designers and developers obviously adopt routines for a reason — perhaps because they suit their personalities or even their other routines — so it is possible to gain a little insight into those who follow them. There certainly was quite a range of responses, and we really appreciate everyone who took the time to get back to us with an answer.

Consider our previous posts:

Now, let’s examine the final steps that handfuls of people in the design and development community take when the clock says that it is officially “go time.”

Freak Out!

One of the responses that seemed to resonate among so many was, basically, to freak out as the launch date draws nearer. Who needs a calm and collected approach when you can run screaming back and forth in front of the computer and pull your hair out as the final hour draws near? The time-honored (even if impractical) tradition of panicking, which flies in the face of the hitchhiker’s motto, is not without its merits. However, for sanity’s sake and the sake of those who share your space, another approach near launch time might prove a bit better.

Freak Out
Image source, by Maks Karochkin.

What our friends on Twitter said:

  • “Panic!”
  • “Cry.”
  • “Simple answer: pray!”


  • There is a great release of pent-up energy when you freak out, which can have numerous benefits — one of which is no longer holding nervous energy inside.
  • A last-minute chaotic whirlwind of panic can also benefit the project because it ensures that you are alert and ready should any fault be found.

What This Says About You

Perhaps panic mode teaches us that those who fall back on such an approach lack organizational skills. The tendency to freak out more than likely stems from a lack of confidence that everything is in place. It could also indicate a slightly pessimistic outlook (à la Murphy’s Law): no matter how prepared you feel for launch, you have a nagging feeling that something will go wrong — not because you neglected something, but just because it can. A comprehensive check list could help to curb this tendency in some cases.


A somewhat different approach — in fact the exact opposite of the previous tactic — taken by many is to just kick back and relax. Though it may seem reasonable, relaxing just as a project will be introduced to the online world might not be an easy approach. In fact, achieving your desired level of calmness could take a lot of effort. If you can find your center and bask in relaxation during the pre-launch phase, then this approach might refresh you before you throw yourself into the next project.

Image source, by VinothChandar.

What our friends on Twitter said:

  • “Get a good night’s sleep. Launch when you’re fresh, not tired.”
  • “Relax. Have a smoke, read some jokes online.”


  • Peace of mind is naturally a welcome benefit of this approach, especially given how hectic things can get upon launch.
  • Mental decompression often helps because, as your mind is switches gears, your subconscious is free to review the project and scan for any missed elements.

What This Says About You

Being calm in the face of a wrap-up is not always easy. If this is your approach, it says one of two things about you: either you are extremely confident in your abilities, and therefore at ease because you know the job is as complete as you could have made it; or you simply don’t care — you’ve done your part, things are out of your hands, and you’re free to move on or just kick back. Confidence is not a bad thing; it could mean that you are prepared and thorough. Not caring, though, may not necessarily be a good thing — but you don’t care, so why harp?

Await Final Payment

Some of those who responded to our query take another route altogether: their final moves are all about the financial aspects of the project. They try to get paid. These people have run all their normal checks, and now they’ve turned for the final check from the client. Most professionals in the design and development community hold off on launching until the client has made their final payment. Whether that would be the final installment or full payment, the last thing on the check list for many is to collect everything owed for their work — and to stay in a holding pattern until that is done.

What our friends on Twitter said:

  • “Wait for final payment confirmation.”
  • “Send an invoice.”
  • “Get the cash!”


  • One benefit of this approach is that you get to move on until payment is received, being freed up for other things.
  • It also puts the responsibility for ultimately launching the website on the client.
  • Finally, by not launching until you get paid, you ensure that final payment does actually come.

What This Says About You

One thing this tells us about the person who uses this approach is that they are trusting… to a point. They are willing to meet the client halfway and do most of the remaining work for them on good faith. But it also shows that good faith will carry the project only so far; this professional is not willing to give up their only leverage to the client. It also shows a certain level of professionalism, seeing as some sort of contract was agreed on before the project began.

Run Diagnostics

Some members of the community opt to run a final set of comprehensive diagnostics. They go through a full range of tests to determine whether any areas are still exposed to the elements as it were (speed tests, script checks, link trials, spell checks and so on). The list of oft-overlooked yet ever important details can be quite long and intimidating to tackle. But tackle we must, and some save this daunting diagnostic imperative until they are on the verge of launching. Several members of the community even create a helpful check list to aid in this phase.

What our friends on Twitter said:

  • “Test, test, test!”
  • “I go through my check list and see that I just forgot something. I check or preview the project before launch. I do simple and wide checks.”
  • “Test whether everything works properly and look for spelling mistakes. Tick off the project check list.”


  • Of course, a full project diagnostic test will be beneficial, but doubly so if you’ve saved it for last, because no little changes you’ve made will fall through the cracks.
  • A thorough examination also brings peace of mind, especially when you use a comprehensive check list to ensure that everything is covered.

What This Says About You

Running diagnostics on your projects simply says that you are professional, sensible and efficient. While that may seem an impressive peek into your personality, those are not surprising qualities in the design and development field. But the depth of your diagnostics process gives a little more insight into who you are. If you take the time to conduct a meticulous check on a project, then you are more than efficient: you are anal, and your personality reflects that perfectionism. If you take a more lackadaisical approach and cover only a few key areas, then you may be efficient but have some traits of a slacker.

Final Cross-Browser Compatibility Check

One obvious and important check to perform at some point during any Web-based project is cross-browser compatibility, and according to the responses we received, some members of the community repeat this frustrating step before the project goes live. In fact, it is usually a safe bet that at least one browser will give you some sort of headache before all is said and done. Some resources can make these checks quicker and easier (we’ll link to them later).

What our friends on Twitter said:

  • “Do a quick cross-browser check…”
  • “Make sure it doesn’t totally explode in IE6.”
  • “Run through a quick check — analytics, etc. — and a last x-browser check.”


  • The benefit of this kind of testing is self-evident. Saving it for last, though, generally gives you a sound starting point for the testing. However, it is always a good idea to test early, and test often. The earlier you test your working protoypes, the more likely you are to avoid compatibility issues in the long run.

What This Says About You

Checking for cross-browser compatibility is unavoidable. Leaving it for last simply speaks to your knowledge and ability to handle the full range of browser checks. What you check tells us even more. If you do a comprehensive test, it shows that you are responsible enough to see your tasks to completion. If you do everything but ignore IE6 (leaving its glitches in place), it shows you are responsible but have limited patience for idiocy.

Get An Outside Opinion

Another oft-mentioned approach is to turn to outside sources for opinions and feedback (always important whenever you do it). There is a reason why the saying about having a second set of eyes around has become so entrenched. Getting someone else in your field, whose opinion you value and insight you trust, to look at a project when you feel it’s ready is always useful. Given the size of the online design and development community and the willingness of its members to offer feedback, all you have to do is ask.

What our friends on Twitter said:

  • “Have someone test the website out, check for bugs and give you a quick review.”
  • “Pass the website over to a network of Web dev friends for them to pull apart and find anything you’ve missed.”
  • “Delete and start over (kidding). Send out a password-protected URL to a select group of Web buddies for a last look.”


  • Getting feedback from someone who is not close to the project, someone who would see things you have overlooked, is always helpful.
  • A second look can reveal elements that don’t work as well as you would like or believe.
  • Feedback from people who are actually in your field is invaluable. Most other feedback tends to be vague and superficial.

What This Says About You

Anyone who makes this their wrap-up routine plays well with others. Those who seek input from others also possess confidence and understanding and rarely rely solely on their own judgment. They are secure enough in their abilities and know enough about their field to be able to handle professional criticism of their work. These qualities are also needed to implement the recommendations that they get. Also, you are at least somewhat likeable, having a network of trusted friends in the community.

Back Up

The final approach we’ll feature here is an extremely important step that is often forgotten: backing up all relevant data and materials before launching. Backing up all the parts of your project before handing over the files not only is sound and sensible, but in the event of an unforeseen catastrophe, it saves you from losing the entire project and having to start at square one. Backing up is an easy way to play it safe and cover your bases. You cannot know what will happen once the project is in the hands of your client.

What our friends on Twitter said:

  • “Make a snapshot of it (including data) and put it somewhere in case you need to restore at a moment’s notice.”
  • “I take an SQL dump of the database and store it somewhere safe.”
  • “Back up and archive! Twice!”


  • Backing up is beneficial in and of itself, but it also saves you the headache of repetition if your diagnostics uncover an issue.
  • Backing up too early could inadvertently cause you to save an inferior version of the project. Then, if you need to restore the website, you won’t have the launch-ready version ready.

What This Says About You

Relatively few people tend to back up last. Doing so indicates a thoughtful nature and a completist approach to work. It also shows that you prepare for the worst-case scenario, either because you are a bit paranoid and pessimistic or because you like to play it safe (or a combination of both).

A Final Word

Thanks again to everyone who contributed to this post and made it possible, including all of you who have taken the time to read it. We have a few related resources for you to check out. After that, feel free to share your thoughts and your final steps before launching below.

Further Resources

As always, here are a few more posts and tools that might assist you in your final hours. Enjoy these helpful check lists:

Smashing Editorial (al)