Email Follow-up sau Meeting — Template & Phrases cho Developer

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

Subject: Follow-up: [Meeting Name] — [Date]

Hi team,

Thank you for joining today's [meeting type]. Here's a summary of what we discussed:

## Key Decisions
- [Decision 1]
- [Decision 2]

## Action Items
| Owner | Task | Deadline |
|-------|------|----------|
| @[Name] | [Task description] | [Date] |
| @[Name] | [Task description] | [Date] |

## Open Items
- [Item that needs further discussion]

Our next meeting is scheduled for [date/time]. Please let me know
if I missed anything or if you have any questions.

Best regards,
[Your name]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

Subject: Meeting Summary: [Topic] — [Date]

Dear [Client name],

Thank you for your time today. It was a productive discussion,
and I'd like to summarize the key points for your reference.

## Discussion Summary
1. [Topic 1]: [Brief summary of what was discussed]
2. [Topic 2]: [Brief summary of what was discussed]

## Agreed Next Steps
- [Your company] will [action] by [date].
- [Client company] will [action] by [date].

## Pending Items
- [Item requiring client's input/decision]

If anything above doesn't accurately reflect our discussion,
please don't hesitate to let me know.

We look forward to our next meeting on [date].

Best regards,
[Your name]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

Subject: Follow-up: [Feature/System] Design Review — [Date]

Hi all,

Thanks for the design review today. Below is a summary of
the decisions and next steps:

## Design Decisions
- Architecture: [e.g., "We'll go with microservices approach"]
- Database: [e.g., "PostgreSQL for transactional data, Redis for caching"]
- API: [e.g., "RESTful API with versioning (v1/v2)"]

## Action Items
- @[Name]: Create the database schema — by [date]
- @[Name]: Set up the CI/CD pipeline — by [date]
- @[Name]: Write the API specification — by [date]

## Open Questions
- [ ] [Technical question that needs further research]
- [ ] [Decision pending on performance benchmarks]

Please review and add any comments by [date]. If no objections,
we'll proceed with this approach.

Thanks,
[Your name]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

Subject: Follow-up: Sprint 12 Review — March 6, 2026

Hi team,

Thanks for a great sprint review today! Here's a summary:

## Completed Stories (8/10)
- ✅ USER-301: Implement SSO login with Google
- ✅ USER-302: Password reset flow redesign
- ✅ USER-305: User profile API v2
- ⬜ USER-308: Email notification service (carried over)
- ⬜ USER-309: Dashboard analytics widget (blocked by API)

## Key Decisions
- We'll prioritize the notification service in Sprint 13
- Dashboard analytics will wait until the Analytics API
  is stable (ETA: end of March)
- Team agreed to increase test coverage target from 70% to 80%

## Action Items
| Owner | Task | Deadline |
|-------|------|----------|
| @Sarah | Create Sprint 13 backlog | Mar 7 |
| @Mike | Fix the flaky CI tests | Mar 8 |
| @Linh | Sync with Analytics team on API timeline | Mar 7 |
| @Everyone | Update story point estimates | Mar 9 |

## Sprint 13 Planning
📅 Monday, March 9 at 10:00 AM (JST)

If I missed anything, please reply to this thread.

Best,
Cuong