2. CC: product related leaders, design team and related leaders, leaders of demand related departments, etc.
3. Subject: [Label ]XX version requirements (or other language description, which is beyond the control of the product)
4. Text:
Hi XX, XX: (Don't write your name wrong)
Requirement Description: Sometimes an attachment will be inserted, and there will be detailed background description and requirement description for the requirement.
Demand level:
Estimated delivery time:
Expected data effect (optional):
Background requirements (optional):
Data distribution (optional):
Project risks (optional):
Improvement measures (optional):
Please evaluate whether the demand is feasible. If you have any questions, please feel free to communicate! thank you
5. Attachments: If there are attachments, you need to submit them first to prevent forgetting.
sign
1. Key contents should be marked.
In the body of the email, there are some contents that need the attention of the other party. You can mark it in bold or highlighted way, so that you can catch each other's attention in the shortest time.
For example, project risks, improvement measures, key data, etc. are the focus of the whole email. After bold marking, it is easy to attract the attention of the other party.
In addition, try to use one form of labeling, and don't mix multiple forms. Otherwise, after the mail has been changed hands several times, readers will miss and misunderstand the information without knowing the meaning of different forms.
2. An email only says one thing, not many things.
If you want to discuss many things, you can write several emails to discuss them separately.
3. In the multi-person discussion email, if you delete the recipient or add someone, you should indicate it at the beginning of the email body.
For example, you can indicate at the beginning of your reply: add three, so that all recipients will know who has joined the discussion.
If a topic is more suitable for face-to-face communication or telephone conversation, don't write an email. Otherwise, it is a waste of time for yourself and each other.
Don't try to discuss complicated topics or topics with major differences by email. Especially when this topic involves many people, in this case, it is more suitable to make an appointment for a working meeting to discuss.
E-mail is more suitable for explaining factual content, such as a meeting minutes, a memorandum of cooperation, or you want to write a weekly report to your leader.
When some oral discussions form * * * knowledge and resolutions, e-mail is very suitable to be carried as the content and memorandum recognized by both parties. Because of the discussion between people, oral expression is prone to deviation in expression and understanding, and it is convenient for all parties attending the meeting to inquire in the future by sending it in writing.
Don't discuss company secrets or other people's privacy in emails.
For many standardized companies, company mail is actually the company's assets, not your personal assets. And it's not classified. Many companies' IT departments have access to your email, so if you don't want the discussion to be seen by others, then you should not discuss it in the email. This is not only the protection of the company, but also the protection of yourself.
6. After writing the important email, you'd better check it again.
See if there are any inappropriate expressions. The more important the email, the more careful it is. If it is not particularly urgent, you can have a drink or chat with your colleagues after the email is sent, and come back later to see if there is anything inappropriate in the previous email.
Reference article
Work email is our face. How to write a proper email? Remember these seven points.
How designers respond gracefully to demand emails | Everyone is a product manager (woshipm.com)
A collection of articles related to online mail
This is the correct posture of 100%!
Product Manager: 3W 1H analysis method, teaching you to write online letters | Everyone is a product manager (woshipm.com)