我的会议纪要 v.s. 别人的会议纪要

上次和总监和另一个部门的经理开完会之后，我写了一份会议纪要，大概是这个样子的：

There are the meeting minutes for <XXX> follow-up:

Development A:

1. Current status
   1. QA functional testing covered <number> <xxx> engines but didn’t execute all cases yet;
   2. Important issues found on <feature A>, <feature B>, and <feature C> testing;
   3. There was not a solid result for performance testing yet due to <component D> was not loaded.
2. According to the risk consideration, the next steps are:
   1. <product A> goes by default in <release A>;
   2. Provide a new installer with <product B> enabled, which uses for new customer who wants <product B> by default;
   3. Enabling <product B> would be involved in Hotfix after it is qualified in the future.

Development B:

1. Current status:
   1. Didn’t have an end-to-end testing yet;
   2. <product C> needs to make changes to support <protocol A> protocol in Cloud.
2. Next steps:
   1. The target is still pointing to <Release B> now;
   2. After QA testing, enabling <product C> in one <node A> as beta test, spread to more <nodes> if the result is good;

Will handle a separate meeting with Trevor to discuss more it.

总监看到后，直接给我回了一封邮件，直接把内容改了……

Development A:

1. Current status
   1. QA functional testing is in progress
   2. Most functionality is in place, with the exception of <feature A>, <feature B>, and <feature C>. The expectation is to be feature complete in ~<number> weeks.
   3. Critical severity issues found and are being addressed
   4. No reliable performance test result yet due to point b.
   5. Known test plan gaps due to lack of manpower and/or schedule time – <test A>, <test B>.
   6. No clear mitigation strategy for <Development A> since we do not have safe remote mechanisms to switch customer (or customers) from <product A> to <product B> or vice versa
2. Potential relatively safe option:
   1. <product A> as default for upgrading <release A> customers
   2. <product B> as default for newly installing <release A> customers
   3. Should we gain better confidence in <product B> due to new <release A> customers and/or <customers B> and/or other integrating products, bundled automated enabling of <product B> to one of the scheduled <product X> Hotfixes.

Development B:

1. Current status:
   1. No functional end-to-end integration yet. Tentative ETA is <number>-<number> weeks from now.
   2. <Problem A> requires a reasonable amount of work
2. Next steps:
   1. The original target of <release C> for software deployment is under risk due to the two points above.
   2. After software deployment, gradual enabling strategy for <product C> will unfold, with typical ETA (assuming disable/fix/reenable cycles) of <number>-<number> months.
   3. Escalation strategy and full deployment plan TBD

确实比我说的好多了，感觉就是一个业余的一个专业的。

了解了差距才知道向哪个方向进步，自知才能自强。