Your code quality is not good., In the last pull request for the authentication module, I noticed several issues were flagged in the code review. The impact was that the team needed extra time to fix them before merging. Going forward, it would help if we run the standard checks and tests before submitting the PR., You need to communicate better., Over the past week, I noticed there weren’t updates in the Slack channel about the database migration work. The impact was that the team wasn’t sure about the current progress. Going forward, it would help if we post short updates when key steps are completed., You interrupt people too much in meetings., In today’s architecture discussion, I noticed several people were interrupted before finishing their points. The impact was that some ideas weren’t fully explored. Going forward, it might help if we allow each person to finish before responding., You didn’t finish your tasks this sprint., During this sprint, I noticed the API integration task wasn’t completed by the end of the sprint. The impact was that the mobile team couldn’t continue their work as planned. Going forward, it would help if we raise potential delays earlier so we can adjust priorities., Practice Scenario: A strong developer works independently but does not collaborate enough with the team., I’ve noticed that most of the work on the caching module was done independently without much discussion with the team. The impact was that some design decisions surprised others later. Going forward, it would help to involve the team earlier when designing technical solutions., Practice Scenario: An engineer struggled with a problem for several days but didn’t raise it early., During the last sprint, I noticed the integration issue with the third-party API was only mentioned close to the deadline. The impact was that we had very little time to help solve it. Going forward, it would help if we raise blockers earlier so the team can support you., Practice Scenario: A senior engineer leaves very harsh comments in code reviews., In several recent code reviews, I noticed the feedback was quite direct and some team members seemed discouraged. The impact is that people may hesitate to ask for feedback. Going forward, it might help to include suggestions or explanations together with the comments.

Reframing Feedback

by
Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?