I like first email more (the one marked as bad example). It's simple, and to the point. After reading it you know exactly what is changed and why. It's a bit harsh, but we are not kids, we can handle it.
The other mail (the one marked as good example) is apologetic, lengthy, and doesn't get to the point cleanly. It might be good when talking to other managers, investors, customers or suits, but not when talking to your developer employees. If you write specifications like that, the job will never get done.
The other mail (the one marked as good example) is apologetic, lengthy, and doesn't get to the point cleanly. It might be good when talking to other managers, investors, customers or suits, but not when talking to your developer employees. If you write specifications like that, the job will never get done.