Slide 1

Slide 1 text

How to give feedback Charles-Axel Dein July 2017

Slide 2

Slide 2 text

Table of contents 1. Why it's important 2. How to do it 3. Bad examples

Slide 3

Slide 3 text

Intro The "T3B3" tool

Slide 4

Slide 4 text

T3 = "Top 3" things you do well Reinforcing feedback

Slide 5

Slide 5 text

B3 = "Bottom 3" things you can work on Redirecting feedback

Slide 6

Slide 6 text

This presentation is applicable to both redirecting and reinforcing feedback

Slide 7

Slide 7 text

Part 1. Why It's Important

Slide 8

Slide 8 text

Great mentors deliver great feedback

Slide 9

Slide 9 text

Being great at delivering feedback helps receiving it

Slide 10

Slide 10 text

Part 2. Howto Deliver Feedback

Slide 11

Slide 11 text

Here's an example situation Your colleague said the software you just shipped on the connected toaster was "a piece of shitty spaghetti code".

Slide 12

Slide 12 text

Let's try without a framework!

Slide 13

Slide 13 text

"You make disrespectful comments about code." — Inexperienced Feedback Giver

Slide 14

Slide 14 text

How does that make you feel?

Slide 15

Slide 15 text

Now, let's review some better ways to share feedback.

Slide 16

Slide 16 text

First we'll review the model Then we'll have an example feedback

Slide 17

Slide 17 text

Framework 1: Non-Violent Communication's ONFR 1. Observations 2. Feelings 3. Needs 4. Request

Slide 18

Slide 18 text

Simplified example: Non- Violent Communication 1. Observation: yesterday you said that my code was "a piece of shitty spaghetti code". 2. Feelings: this made me feel disrespected because I had put a lot of energy in this new feature. 3. Needs: for our team to function well, we need feedback to be shared in a respectful manner. 4. Request: moving forward, can you try to find better words and more actionable feedback?

Slide 19

Slide 19 text

Framework 2: Crucial Conversations' STATE 1. State your facts 2. Tell your story 3. Ask for others' paths 4. Talk tentatively 5. Encourage testing

Slide 20

Slide 20 text

Simplified example: Crucial Conversation 1. State: yesterday you said that my code was "a piece of shitty spaghetti code". 2. Tell: I can't help but think you want to hurt my feelings with such strong words. 3. Ask: what was your intention with sharing those strong words? "Hold to your belief; merely soften your approach"

Slide 21

Slide 21 text

Framework 3: behavioral interview's STAR 1. Situation 2. Task 3. Action 4. Result

Slide 22

Slide 22 text

Simplified example: behavioral STAR model 1. Situation: yesterday in the chat room you said that my code was "a piece of shitty spaghetti code". 2. Task: N/A here. 3. Action: I felt disrespected as a result. We need everyone to share feedback respectfully. 4. Outcome: when feedback is shared respectfully, people are more keen acting upon it.

Slide 23

Slide 23 text

Part 3. Bad Examples

Slide 24

Slide 24 text

Feedback antipatterns 1. The Generalization Attack 2. I'm not talking to you 3. The CIA Antipattern 4. The Sloth Sandbagging 5. The Feedback Sandwich

Slide 25

Slide 25 text

All of those are inspired by real examples

Slide 26

Slide 26 text

1. The Generalization Attack By far the most common, and the worst

Slide 27

Slide 27 text

If only you could be less aggressive when giving feedback on code reviews, it would make discussions easier! — Inexperienced Feedback Giver

Slide 28

Slide 28 text

What's wrong about this feedback?

Slide 29

Slide 29 text

Avoid generalizations! 1. Use examples (facts). 2. Be specific (situation: where & when?). 3. Talk tentatively, avoid attacks. It's your story.

Slide 30

Slide 30 text

How would you re-write it? ❓

Slide 31

Slide 31 text

2. I'm not talking to you

Slide 32

Slide 32 text

"Our team's code quality has lowered recently." — Inexperienced Feedback Giver

Slide 33

Slide 33 text

What's wrong about this feedback?

Slide 34

Slide 34 text

Talk to the person 1. Use "you" when sharing feedback. 2. Talk about concrete action your interlocutor did or didn't take. 3. Make it concrete and actionable!

Slide 35

Slide 35 text

How would you re-write it? ❓

Slide 36

Slide 36 text

3. The CIA Antipattern "Can't Impact Anyway"

Slide 37

Slide 37 text

You could have led more projects! — Inexperienced Feedback Giver

Slide 38

Slide 38 text

What's wrong about this feedback?

Slide 39

Slide 39 text

Don't give feedback about things the individual can't impact E.g. leading a project is mostly dependent on staffing and business priorities

Slide 40

Slide 40 text

How would you re-write it? ❓

Slide 41

Slide 41 text

4. The Sloth Sandbagging

Slide 42

Slide 42 text

You could have done more mentoring! — Inexperienced Feedback Giver

Slide 43

Slide 43 text

What's wrong about this feedback?

Slide 44

Slide 44 text

We can always do more! 1. Everyone's pretty busy. Focus your feedback on prioritization. 2. Clarify what impact was missed.

Slide 45

Slide 45 text

How would you re-write it? ❓

Slide 46

Slide 46 text

5. The Feedback Sandwich

Slide 47

Slide 47 text

You're such a knowledgeable person! You could mentor me more. But I love working with you! — Inexperienced Feedback Giver

Slide 48

Slide 48 text

What's wrong about this feedback? ❓

Slide 49

Slide 49 text

Go straight to the feedback! The feedback sandwich introduces cognitive dissonance and make it more difficult for your interlocutor to understand it.

Slide 50

Slide 50 text

How would you re-write it? ❓

Slide 51

Slide 51 text

Conclusion

Slide 52

Slide 52 text

How to train? 1. Focus on positive feedback delivery (5:1 ratio). 2. It's fine to generalize if you can find examples. 3. Do not nitpick!

Slide 53

Slide 53 text

Read more • charlax/engineering-management • Negative feedback antipatterns

Slide 54

Slide 54 text

Thank you! Questions?