forked from Techtonica/curriculum
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(issue-1151): added feedback document inside career folder
- Loading branch information
1 parent
f5ea1a2
commit 48472aa
Showing
1 changed file
with
52 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
# Feedback | ||
### Projected Time | ||
Approximately 45 minutes | ||
|
||
## Overview | ||
|
||
> “You can't achieve excellence in life if you fear opinion.” | ||
― Janna Cachola | ||
|
||
Feedback is the best way to steer your actions toward your goals. Understanding the significance of feedback within tech environments is crucial. This document outlines key concepts and practices to effectively give and receive feedback, promoting growth and improvement. | ||
|
||
## Key Points | ||
1. **Importance of Feedback**: Feedback is essential for personal and professional growth, helping align your actions with your goals. | ||
2. **Feedback Culture**: The culture of feedback varies significantly across organizations. It's important to actively seek and foster a feedback-rich environment. | ||
3. **Feedback Focus Areas**: | ||
- **Code Quality**: Ensuring clarity and efficiency in coding. | ||
- **Communication**: Enhancing both written and spoken interactions. | ||
- **Behavior**: Observing and improving professional conduct. | ||
|
||
|
||
|
||
## Goal | ||
|
||
- Aim to provide constructive feedback daily, fostering continual improvement and adaptation. | ||
|
||
## Common Misconceptions | ||
- Feedback has to be about something HUGE | ||
- Many assume that feedback should only be given for significant issues or mistakes. Regular feedback on everyday tasks and small achievements can also drive continuous improvement and build confidence. | ||
- Feedback has to be about mistakes | ||
- While addressing mistakes is a part of giving feedback, it's equally important to acknowledge what someone is doing right. Positive feedback reinforces good practices and behaviors | ||
- Feedback will cause resentment | ||
- If delivered thoughtfully and constructively, feedback does not lead to resentment. It's crucial to approach feedback with empathy, focusing on growth and solutions rather than blame. This approach helps build trust and fosters a supportive environment where feedback is viewed as a tool for development rather than criticism. | ||
|
||
# Techniques for Effective Feedback | ||
### Techniques | ||
- [Lara Hogan's Feedback equation](https://larahogan.me/blog/feedback-equation/) | ||
1. **Observation:** Focus on observable facts without personal opinions. | ||
2. **Impact:** Discuss how specific behaviors or actions impact the team or project. | ||
3. **Question:** Pose genuine questions to encourage dialogue and collaborative problem-solving. | ||
|
||
# Group Exercise | ||
## Rewrite feedback in the O.I.Q. format | ||
|
||
### Step 1 | ||
|
||
Write down a scenario where you wanted to give someone else feedback, but you didn't. | ||
|
||
### Step 2 | ||
Write out the Observation, Impact, and Question to foster a more constructive dialogue. | ||
|
||
### Conclusion | ||
Mastering feedback techniques is invaluable for anyone moving into the tech industry, promoting a healthy work environment and personal career growth. |