Feb. 10, 2022
Minutes of the big-data team regular meeting
Dear all,
I am writing to follow up on our earlier decision on the regular meeting fo big-data group last wednesday.
As mentioned before, the to-do list is:
1. formulate the flow of event tracker development (needs ferther descussion with PM and front-end engineer).
2. set the meeting agenda and descussion filed of tripartite bi-weekly communication meeting ( big-data team, PM and content operation team).
3. tracking the progress of development of user label, expecting landing by the end of this month .
4. analysing user portrait and publishing an analysis report by the end of this month .
Besides, the 2022 work planning report of big-data team has attached to the email, please find the attachment.
Best wishes.
I want to practice my English e-mail writing skills, so here it is.
-- 中文英文并不是一一对照的，中文有些表达（在我的能力范围内）无法用英文一一对照翻译，所以我就换了一种方式表达
各位领导，同事：
现将大数据组工作沟通例会讨论内容及后续工作事项整理如下：
1.制定数据埋点工作流程，后续需要与产品经理以及前端工程师一起确认方案
2.确定数据产品运营三方双周沟通会会议议程以及常规讨论内容
3.用户标签开发进度跟踪，计划月底前落地
4.用户画像洞察，预计本月底输出分析报告
2022年数据组工作规划报告附在邮件中，请查收
谢谢。
I am writing to follow up on our earlier decision on the regular meeting fothe big-data group meeting last wWednesday.
What you originally wrote is understandable, but a little convoluted. I hope to simplify it a bit.
As previously mentioned before, the to-do list is:
1. formulate the flow of event tracker development (needs feurther deiscussion with PM and front-end engineer).
Language is a bit technical here so I hesitate to correct it!
2. set the meeting agenda and defile discussion filed ofof the tripartite bi-weekly communication meeting ( big-data team, PM and content operation team).
3. tracking the progress of development of the user label, expecting landing by the end of this month .
4. analysinge user portrait and publishing an analysis report by the end of this month .
BesidesIn addition, the 2022 work planning report of of the big-data team hais attached to theis email, please find the attachment.have a look.
Feb. 10, 2022
It's a little tricky to offer corrections when the subject matter is quite technical and specific, but tried my best!
Feb. 10, 2022
Your correction is very helpful, luck to have you in this community!
|
Minutes of the big-data team regular meeting |
|
Dear all, |
|
I am writing to follow up on our earlier decision on the regular meeting fo big-data group last wednesday. I am writing to follow up on What you originally wrote is understandable, but a little convoluted. I hope to simplify it a bit. |
|
As mentioned before, the to-do list is: As previously mentioned |
|
1. formulate the flow of event tracker development (needs ferther descussion with PM and front-end engineer). 1. formulate the flow of event tracker development (needs f Language is a bit technical here so I hesitate to correct it! |
|
2. set the meeting agenda and descussion filed of tripartite bi-weekly communication meeting ( big-data team, PM and content operation team). 2. set the meeting agenda and |
|
3. tracking the progress of development of user label, expecting landing by the end of this month . 3. track |
|
4. analysing user portrait and publishing an analysis report by the end of this month . 4. analys |
|
Besides, the 2022 work planning report of big-data team has attached to the email, please find the attachment.
|
|
Best wishes. |
You need LangCorrect Premium to access this feature.
Go Premium