I'm writing this so other developers can share in the laughter (ha!) and designers/managers can learn.
I've seen this a few times. It feels like there's a mad-libs form that designers/managers use to communicate things in a software project.
$normal_behavior_of_our_product_for_the_past_year, $insulting_phrase, $client_need_never_mentioned_before_this_month, $high_stress!!!!!
So, an example letter:
I tried changing my password and instead of sending me a new password via email the system sent me a link to a place to change it. This is backwards! No systems work like that. We're about to roll this product out for Wonka Inc. and I'm sure they will kill us for this. Please don't sleep until this is fixed.!!!!!
Advice to managers/designers/people who write these emails
Here's how to actually handle this:
- Verify that the decision maker and end-users at client will actually think this is a problem
- Add a new task to your issue tracker
- You can even make it critical
- Have reasonable expectations about when it will get fixed - sure, you can move it to the front of the queue, but it's still in the queue.