Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

If your website's # of visitors produced a weekly bell curve, with say Sunday generally being the lowest and Wednesday or Thursday being the peak... What day of the week would be best to regularly add major content updates?

share|improve this question
2  
...from a user experience perspective, or from a 'business goals' perspective? –  Roger Attrill Mar 28 '12 at 19:26
    
How is the content being consumed? –  Nic Mar 28 '12 at 19:42
    
From a user perspective. –  aslum Mar 28 '12 at 19:56

2 Answers 2

Though sunday seems the logical conclusion,do inform your users in advance that you will be bringing the site down on Sunday during this time period (mention the time zone too) so that people are aware of it well in advance and are not surprised to find it down.

When your site is down do provide an informative or even fun message which tells them when the site will be back up.

enter image description here

share|improve this answer
1  
Or perform updates side by side with existing version and switch the user to the updated version without any downtime. –  Danny Varod Mar 28 '12 at 19:47
1  
That would be ideal if the site is just html but if there are databases which have to be updated,then you will have downtime and better to tell people that the site is not working rather than run a query and get frustrated –  Mervin Johnsingh Mar 28 '12 at 19:49
    
Downtime isn't an issue. It's more that if we post something on Friday say, in the example I gave most people would miss it, or see it "late". –  aslum Mar 28 '12 at 19:57
    
Thats the reason you dont post the downtime on the last minute. Post a notification about it on top of the site for a week so that all users can see it –  Mervin Johnsingh Mar 28 '12 at 20:08
1  
@MFrank2012 You can either have an additional mirrored database and switch between the two at each update, or plan the updates better, so that they don't require DB downtime. –  Danny Varod Mar 29 '12 at 0:16

Assuming you don't require downtime...

If you want user feedback prior to the "busy hours" (so you can make amendments), perform update on lowest demand.

If the update doesn't require feedback and you want users to feel like they are getting the newest content, perform the update prior to the peek (e.g. at 50% of the expected peek on the way up to the peek) so that the peek users will get the freshest content.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.