Talking About What Went Well
In her review with her manager, David, Emma highlights a successful project, the results she delivered, and how she supported her team. David recognizes her contributions and asks what she learned along the way.
Dialogue12

Thanks for putting together your notes, Emma. Let’s start with what went well this year. Which accomplishment are you most proud of?
I’m especially proud of leading the customer onboarding project. We launched it six weeks ahead of schedule, and new clients were able to get started much faster.
That was a significant improvement. Do you have a sense of how the project affected the team’s workload or the client experience?
The average onboarding time dropped by about 30 percent. We also received fewer support requests during the first month, so the team could focus on more complex issues.
That’s a strong result, and it sounds as though you looked beyond the launch itself. How did you get the different teams to work together?
I set up short weekly check-ins and made sure everyone had the same timeline. When priorities shifted, I tried to flag the impact early rather than let people get caught off guard.
I also want to recognize how you supported the newer members of the team. You made time to walk them through the process, even when things were busy.
I’m glad that came through. At first, I worried that coaching would slow me down, but it actually helped us catch issues sooner and share the work more evenly.
What did you learn along the way? Looking back, is there anything you would handle differently if you led a similar project again?
I learned that getting agreement on ownership early saves a lot of back-and-forth later. Next time, I’d also build in more time to test the handoffs between teams before launch.
That’s a thoughtful takeaway. You delivered measurable results, brought people together, and identified ways to improve. Is there another contribution you’d like to make sure we cover?
I’d add that I kept our project documentation up to date, which made it easier for others to step in when needed. I’m proud of the outcome, and I know there’s still room to grow.
Vocabulary7
- ahead of schedule
Finished earlier than planned. Here, the project launched six weeks before its expected date.
- get started
Begin doing something. Here, new clients could begin using the service sooner.
- flag the impact early
Point out the likely effects of a change as soon as possible. This can help others prepare instead of being caught off guard.
- caught off guard
Surprised by something unexpected and unprepared for it. In this context, Emma wanted to warn people early about shifting priorities.
- walk them through the process
Explain or show someone each step of a process. Emma did this to help newer team members learn the work.
- build in more time
Plan extra time for something as part of a schedule. Emma would allow more time to test the handoffs before launch.
- step in
Take over or help when someone else is unavailable or needs support. Up-to-date documentation made it easier for colleagues to step in.
Key Sentences7
- 1
We launched it six weeks ahead of schedule, and new clients were able to get started much faster.
This sentence clearly describes an accomplishment and its benefit. You can reuse the structure to explain a project result and how it helped others.
- 2
The average onboarding time dropped by about 30 percent.
This is a concise way to report a measurable result. Replace the metric and percentage with evidence from your own work.
- 3
When priorities shifted, I tried to flag the impact early rather than let people get caught off guard.
This sentence shows how you handled change and communicated proactively. Use “I tried to…” to describe a thoughtful approach without overstating it.
- 4
At first, I worried that coaching would slow me down, but it actually helped us catch issues sooner and share the work more evenly.
This is useful for explaining how an initial concern turned into a positive outcome. The “At first…but…” structure helps describe what you learned.
- 5
I learned that getting agreement on ownership early saves a lot of back-and-forth later.
This sentence shares a practical lesson from experience. You can adapt it to explain why an early decision or conversation makes later work easier.
- 6
Next time, I’d also build in more time to test the handoffs between teams before launch.
This is a constructive way to describe what you would change in a future project. “Next time, I’d…” introduces a specific improvement without dwelling on blame.
- 7
I’d add that I kept our project documentation up to date, which made it easier for others to step in when needed.
This sentence adds a contribution and explains why it mattered to the team. Use “I’d add that…” to bring up another relevant point in a review.