The increasing urgency of a request to fill out a survey

Date:November 26, 2015 / year-entry #250
Tags:non-computer
Orig Link:https://blogs.msdn.microsoft.com/oldnewthing/20151126-00/?p=92221
Comments:    10
Summary:Here are some email messages I received from an automated system. October 20: "This survey must be completed no later than November 14." October 31: "Reminder, this survey must be completed no later than November 14." November 12: "Final reminder, this survey must be completed no later than November 14." November 14: "Extension, this survey...

Here are some email messages I received from an automated system.

October 20: "This survey must be completed no later than November 14."

October 31: "Reminder, this survey must be completed no later than November 14."

November 12: "Final reminder, this survey must be completed no later than November 14."

November 14: "Extension, this survey must be completed no later than November 19."

November 19: "Final reminder, this survey must be completed no later than November 19."

November 28: "This survey must be completed no later than December 16."

I gave in and clicked the survey link.

The link was broken.

I guess the people running the survey said, "Gosh, we're getting no responses. Let's extend the deadline."

ObSimpsons


Comments (10)
  1. Ken Hagan says:

    Based on the 3-in-ten-thousand who responded to that magazine card a few days ago, I suppose "no-one at all tried to respond" is at least as plausible as "no-one at all was able to respond".

  2. jk says:

    plot twist, 3 people psychically debugged the typo in the URL and responed

  3. cheong00 says:

    I guess even if you filled the survey, you'll still receive the email. There's no constraint that any survey have to be conducted exactly once only.

    See if there will be more email on Dec 16.

  4. Benjy says:

    Reminds me of the progressively more and more silly E-Mails I sent round my firm as we approached "strong password enforcement day". And of course, plenty still ignored them!

  5. John Styles says:

    (this is many years ago so when some Internet stuff for the general public was very new). I owned the domain for my late brother's company. There was a marketing company with almost the same name (2 Ls instead of one) – and they did a major marketing campaign with the web form set up to send things to the wrong domain i.e. mine. IIRC correctly I sent an email and didn't get any response so I found out the name of the MD and phoned him up. He was very exasperated with his staff.

  6. Kemp says:

    Our place has away days (essentially team building days, but mostly full of boring speeches) and your emails remind me of the ones they sent around for that, though not for exactly the same reason. We had a string of "this is a mandatory staff activity, all staff are required to attend" and then eventually "we have filled up all the places, apologies to any staff who hadn't yet confirmed their attendance".

  7. Anon says:

    @Benjy

    I bet "strong password enforcement" decreased security measurably across the entire company, too.

    Now everyone just uses !p4ssword as their password, instead of mary100179spotnewjersey

    Which is why smart people don't send those emails in the first place.

  8. Anon says:

    @Kemp

    "This is a mandatory activity. Sign up by COB X/Y/ZZZZ"

    COB X/Y/ZZZZ:

    "Any staff who haven't yet confirmed their attendance should clean out their desks by the end of the day tomorrow."

  9. Mr Cranky says:

    Doing the survey won't save you from getting all the subsequent reminders.  

  10. DWalker says:

    @Kemp: Weird: "We had a string of "this is a mandatory staff activity, all staff are required to attend" and then eventually "we have filled up all the places, apologies to any staff who hadn't yet confirmed their attendance"."

    Which means 1) that the company can't count, and 2) if you don't want to attend, you are rewarded for not confirming your attendance!

Comments are closed.


*DISCLAIMER: I DO NOT OWN THIS CONTENT. If you are the owner and would like it removed, please contact me. The content herein is an archived reproduction of entries from Raymond Chen's "Old New Thing" Blog (most recent link is here). It may have slight formatting modifications for consistency and to improve readability.

WHY DID I DUPLICATE THIS CONTENT HERE? Let me first say this site has never had anything to sell and has never shown ads of any kind. I have nothing monetarily to gain by duplicating content here. Because I had made my own local copy of this content throughout the years, for ease of using tools like grep, I decided to put it online after I discovered some of the original content previously and publicly available, had disappeared approximately early to mid 2019. At the same time, I present the content in an easily accessible theme-agnostic way.

The information provided by Raymond's blog is, for all practical purposes, more authoritative on Windows Development than Microsoft's own MSDN documentation and should be considered supplemental reading to that documentation. The wealth of missing details provided by this blog that Microsoft could not or did not document about Windows over the years is vital enough, many would agree an online "backup" of these details is a necessary endeavor. Specifics include:

<-- Back to Old New Thing Archive Index