Slide 1

Slide 1 text

Say It Right The Art of Giving Feedback Tasneem Minadakis [email protected] @tazneemiandevil

Slide 2

Slide 2 text

Who am I? Engineering Leader Rider Growth Since Jun 2016 Engineering Leader Data Platform Since Sep 2014 Principal Engineering Manager Ad Delivery Mar 2013 - Sep 2014 Senior Product Manager Bing Apps Jan 2012 - Mar 2013 Senior Engineer (Tech Lead) Surface Jun 2005 - Jan 2012

Slide 3

Slide 3 text

Agenda ● Foundation for Giving Feedback ● Framework for Giving Quality Feedback ● Feedback Pitfalls ● Bring It All Together

Slide 4

Slide 4 text

Agenda ● Foundation for Giving Feedback ● Framework for Giving Quality Feedback ● Feedback Pitfalls ● Bring It All Together

Slide 5

Slide 5 text

Foundation for Giving Feedback ● Trust ● Respect ● Care

Slide 6

Slide 6 text

Agenda ● Foundation for Giving Feedback ● Framework for Giving Quality Feedback ● Feedback Pitfalls ● Bring It All Together

Slide 7

Slide 7 text

Make it Receivable Situation Behavior Impact describe the Situation the behavior (what they did) and the Impact of that behavior Blur word is a word whose definition is not 100% clear. Even if you had a video camera, you couldn’t quite capture the intent Avoid Blur Words

Slide 8

Slide 8 text

Make it Receivable Situation Behavior Impact A In the design review meeting You did a good job hearing feedback from others while sharing your ideas We ended up with a really good design for the project at the end B In your last few code reviews I noticed you do not provide a detailed description on your code reviews When the code review does not have a description, it makes it much harder for me to know what the review is about and it takes me longer to get through the review

Slide 9

Slide 9 text

Make it Receivable Situation Behavior Impact A In the design review meeting You did a good job hearing feedback from others while sharing your ideas We ended up with a really good design for the project at the end B In your last few code reviews I noticed you do not provide a detailed description on your code reviews When the code review does not have a description, it makes it much harder for me to know what the review is about and it takes me longer to get through the review

Slide 10

Slide 10 text

Make it Receivable Situation Behavior Impact describe the Situation the behavior (what they did) and the Impact of that behavior then discuss & clarify, create options, agree on next steps

Slide 11

Slide 11 text

Make it Receivable Situation Behavior Impact double-check the facts direct may have had good intentions, but… impact you felt or observed should be understood I disagree with your feedback!

Slide 12

Slide 12 text

Make it Actionable Negative Feedback - Not Specific Your presentation could have gone better. You didn’t make your point very well credit : LifeLabsNewYork

Slide 13

Slide 13 text

Make it Actionable Negative Feedback - Specific Your presentation could have gone better. You rushed through the slides and were not able to connect with your audience. That made it difficult to follow along credit : LifeLabsNewYork

Slide 14

Slide 14 text

Make it Actionable Positive Feedback – Not Specific You did a great job today presenting in front of engineering. Keep it up credit : LifeLabsNewYork

Slide 15

Slide 15 text

Make it Actionable Positive Feedback – Specific You did a great job today presenting in front of engineering. You were well paced and you did a good job connecting with the audience through your body language. You also got good questions after that shows that people had good takeaways credit : LifeLabsNewYork

Slide 16

Slide 16 text

● 1 negative interaction takes 5 positive interactions to remedy ● Avoid Deficits ● When managing out, try to maintain trust ● Avoid Feedback Sandwich Make it Balanced

Slide 17

Slide 17 text

● Giving and receiving feedback should be ongoing ● Skill versus Will (resource) Make it a Norm

Slide 18

Slide 18 text

● Discuss sphere of impact and scope of influence Make it a Norm Staff Engineer Impact at Engineering level + other Leadership initiatives Impact at org level (Rider Acquisition) + other Leadership initiatives Impact beyond their immediate project at team level (Rider Virality) + Extra Curriculars Impact on project they are part of Senior Engineer Software Engineer New Grad

Slide 19

Slide 19 text

Agenda ● Foundation for Giving Feedback ● Framework for Giving Quality Feedback ● Feedback Pitfalls ● Bring It All Together

Slide 20

Slide 20 text

Feedback Pitfalls Making Sure You Are Understood Do I make sure my message was understood? Even twin brothers could misunderstand each other. The more differences we have, the higher the possibility that my message wasn’t received quite as intended. Be sure to recap, then ask to see what the direct thinks and clarify the message ? credit : google training

Slide 21

Slide 21 text

Feedback Pitfalls Based on Assumptions Do I sometimes filter based on assumptions, and if so how can I avoid it? I know Jim graduated from Stanford. But he is probably not interested in public speaking, so I won’t even mention the opportunity to recruit and do a tech talk Can they handle it if I give a piece of tough feedback?

Slide 22

Slide 22 text

Feedback Pitfalls Feedback Triangles You Feedback from someone for your direct report credit : google training

Slide 23

Slide 23 text

Agenda ● Foundation for Giving Feedback ● Framework for Giving Quality Feedback ● Feedback Pitfalls ● Bring It All Together

Slide 24

Slide 24 text

Bring It All Together ● Situation Behavior Impact ● Club Spade Heart Diamond ● Make it Ongoing ● Avoid Assumptions and Misunderstandings ● Takeaways (anyone like to share?)

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

References — LifeLabs Great Manager Training — Google New Manager Training — How to give negative feedback — Building Trust in your team — Feedback sandwich This material has been possible due to a lot of training I have received over the years. Thank you to all those great managers that have been part of my journey!