anujbiyani · November 30, 2016 16:40
diff --git a/feedback_presentation.html b/feedback_presentation.html
 <!DOCTYPE html>
 <html>
  <head>
    <title>Feedback</title>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
    <style type="text/css">
    @import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
    @import url(https://fonts.googleapis.com/css?family=Droid+Serif:400,700,400italic);
    @import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);

    body { font-family: 'Droid Serif'; }
    h1, h2, h3 {
      font-family: 'Yanone Kaffeesatz';
      font-weight: normal;
    }
    .remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }

    .inverse {
      background: #272822;
      color: #fff;
    }

    .inverse a {
      color: #fff;
    }

    h1 {
      text-align: center;
    }

    p {
      margin-bottom: 0.2em;
    }

    ul {
      margin-top: 0.2em;
    }

    li {
      line-height: 1.5em;
    }

    .multi-slide-section h1 {
      margin-top: 0;
    }

    .section-title {
      color: #777;
    }

    .small {
      font-size: 15px;
    }

    .footnote {
      position: absolute;
      bottom: 3em;
    }

    .red {
      color: #fa0000;
    }
    </style>
  </head>
  <body>
    <textarea id="source">
 class: center, middle, inverse

 # Feedback

 #### How to give it
 #### How to get it
 #### How to take it

 ---

 # What do we mean by feedback

 **Anything your colleagues feel about working with you**
 * job-specific (coding/(T)PMing)
 * socializing with you within work hours ("the beer test")
 * your desk (too messy)

 ---

 # Why feedback is important

 **Get better at coding**
 * more £££
 * more experience

 **Get better at working with others**
 * more <3

 ---

 # When to get feedback

 **All the damn time.**  
 * 6 months is way too long
  * Your memory of yourself will fade drastically
  * Other people's memory of you will get even worse
  * That much more time where you might be annoying your colleagues
 * "Big bang feedback"
  * Might have too many things to improve on at once
  * Takes much longer to measure your improvement

 **2-4 weeks is a nice cadence.**

 ---

 class: center, middle, inverse

 # How to get feedback

 ---

 class: multi-slide-section

 .section-title[Getting feedback]

 # Ask

 ### Make it easy to get responses
 **Use whatever medium your recipients find most convenient**
  * google form
  * plain e-mail
  * in person
  * build a website

 **Let people e-mail your manager directly, but encourage named+direct responses.**
  * anonymous feedback is a closed loop; can't ask for more detail

 ---

 class: multi-slide-section

 .section-title[Getting feedback]

 # Provide prompts

 ### People have terrible memories
 **Help them remember with prompts**
 * *How do you like pairing with me? Were we nicely working together to solve problems, or did I solo-dive off the deep end?*
 * *How are my PR reviews? Am I badgering, or helpful?*
 * *What could I do (or stop doing) to make your job more pleasant?*

 **Specific questions are fair game, too**
 * *What could I have done better to help ship *some project* on time?*
 ]

 ---

 class: multi-slide-section

 .section-title[Getting feedback]

 # Open-ended answers

 ### Ask questions that get you actionable answers.
 * *On a scale of 1-10, how was pairing with me?*
  * 7
 * *How did you feel while we paired? Did you feel like we were better working together than apart?*
  * Sometimes you go a bit too fast and I feel lost.

 ---

 class: center, middle, inverse

 # How to give feedback

 ![](http://i.imgur.com/SGznp.gif)

 ---

 # Giving feedback

 * Do criticize. There's always something to improve on
 * Don't limit yourself to the prompts
 * Be specific. Give examples
 * Give your name. Let the other person circle back and ask for more information

 ---

 class: center, middle, inverse

 # How to take feedback

 ---

 class: multi-slide-section

 .section-title[Taking feedback]

 # Don't explain yourself

 **You giving me feedback:** *You were a bit rude in that last meeting*

 **Me defending myself:** *I think I was just expressing my opinion*

 Your initial reaction will most likely be defensive; try giving yourself time to digest before responding.

 Instead of trying to justify yourself, patiently listen and then follow-up with questions.

 To quote Tom Johnson:

 *be inquisitive, be empathetic and try to understand why*

 ---

 class: multi-slide-section

 .section-title[Taking feedback]

 # Do listen

 ### Let the other person talk.

 Think about their perspective.

 Other people don't think about the world the way you do; try and see things through their eyes..red[*]

 .footnote[.small.red[*] This is also why you should slow your initial response -- you're likely seeing their feedback from your perspective.]

 ---

 class: multi-slide-section

 .section-title[Taking feedback]

 # Follow-up

 ### Ask for advice
 *I don't quite follow what you mean, could you give me a specific example? Perhaps point it out next time we're working together?*

 *How do you think I could have better handled the situation?*

 ---

 class: multi-slide-section

 .section-title[Taking feedback]

 # Act on it

 ### Write down some action items

 Much like retrospectives, take note of specific things you will improve on.

 **Hold yourself accountable:** in your next feedback request, ask if you improved on these things.

 ---

 class: center, middle, inverse

 # That's it.

 Slides made with Remark: [https://github.com/gnab/remark](https://github.com/gnab/remark)

    </textarea>
    <script src="https://gnab.github.io/remark/downloads/remark-latest.min.js" type="text/javascript">
    </script>
    <script type="text/javascript">
      var slideshow = remark.create();
    </script>
  </body>
 </html>
	<!DOCTYPE html>
	<html>
	<head>
	<title>Feedback</title>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<style type="text/css">
	@import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
	@import url(https://fonts.googleapis.com/css?family=Droid+Serif:400,700,400italic);
	@import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);

	body { font-family: 'Droid Serif'; }
	h1, h2, h3 {
	font-family: 'Yanone Kaffeesatz';
	font-weight: normal;
	}
	.remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }

	.inverse {
	background: #272822;
	color: #fff;
	}

	.inverse a {
	color: #fff;
	}

	h1 {
	text-align: center;
	}

	p {
	margin-bottom: 0.2em;
	}

	ul {
	margin-top: 0.2em;
	}

	li {
	line-height: 1.5em;
	}

	.multi-slide-section h1 {
	margin-top: 0;
	}

	.section-title {
	color: #777;
	}

	.small {
	font-size: 15px;
	}

	.footnote {
	position: absolute;
	bottom: 3em;
	}

	.red {
	color: #fa0000;
	}
	</style>
	</head>
	<body>
	<textarea id="source">
	class: center, middle, inverse

	# Feedback

	#### How to give it
	#### How to get it
	#### How to take it

	---

	# What do we mean by feedback

	Anything your colleagues feel about working with you
	* job-specific (coding/(T)PMing)
	* socializing with you within work hours ("the beer test")
	* your desk (too messy)

	---

	# Why feedback is important

	Get better at coding
	* more £££
	* more experience

	Get better at working with others
	* more <3

	---

	# When to get feedback

	All the damn time.
	* 6 months is way too long
	* Your memory of yourself will fade drastically
	* Other people's memory of you will get even worse
	* That much more time where you might be annoying your colleagues
	* "Big bang feedback"
	* Might have too many things to improve on at once
	* Takes much longer to measure your improvement

	2-4 weeks is a nice cadence.

	---

	class: center, middle, inverse

	# How to get feedback

	---

	class: multi-slide-section

	.section-title[Getting feedback]

	# Ask

	### Make it easy to get responses
	Use whatever medium your recipients find most convenient
	* google form
	* plain e-mail
	* in person
	* build a website

	Let people e-mail your manager directly, but encourage named+direct responses.
	* anonymous feedback is a closed loop; can't ask for more detail

	---

	class: multi-slide-section

	.section-title[Getting feedback]

	# Provide prompts

	### People have terrible memories
	Help them remember with prompts
	* How do you like pairing with me? Were we nicely working together to solve problems, or did I solo-dive off the deep end?
	* How are my PR reviews? Am I badgering, or helpful?
	* What could I do (or stop doing) to make your job more pleasant?

	Specific questions are fair game, too
	* What could I have done better to help ship some project* on time?*
	]

	---

	class: multi-slide-section

	.section-title[Getting feedback]

	# Open-ended answers

	### Ask questions that get you actionable answers.
	* On a scale of 1-10, how was pairing with me?
	* 7
	* How did you feel while we paired? Did you feel like we were better working together than apart?
	* Sometimes you go a bit too fast and I feel lost.

	---

	class: center, middle, inverse

	# How to give feedback

	![](http://i.imgur.com/SGznp.gif)

	---

	# Giving feedback

	* Do criticize. There's always something to improve on
	* Don't limit yourself to the prompts
	* Be specific. Give examples
	* Give your name. Let the other person circle back and ask for more information

	---

	class: center, middle, inverse

	# How to take feedback

	---

	class: multi-slide-section

	.section-title[Taking feedback]

	# Don't explain yourself

	You giving me feedback: You were a bit rude in that last meeting

	Me defending myself: I think I was just expressing my opinion

	Your initial reaction will most likely be defensive; try giving yourself time to digest before responding.

	Instead of trying to justify yourself, patiently listen and then follow-up with questions.

	To quote Tom Johnson:

	be inquisitive, be empathetic and try to understand why

	---

	class: multi-slide-section

	.section-title[Taking feedback]

	# Do listen

	### Let the other person talk.

	Think about their perspective.

	Other people don't think about the world the way you do; try and see things through their eyes..red[*]

	.footnote[.small.red[*] This is also why you should slow your initial response -- you're likely seeing their feedback from your perspective.]

	---

	class: multi-slide-section

	.section-title[Taking feedback]

	# Follow-up

	### Ask for advice
	I don't quite follow what you mean, could you give me a specific example? Perhaps point it out next time we're working together?

	How do you think I could have better handled the situation?

	---

	class: multi-slide-section

	.section-title[Taking feedback]

	# Act on it

	### Write down some action items

	Much like retrospectives, take note of specific things you will improve on.

	Hold yourself accountable: in your next feedback request, ask if you improved on these things.

	---

	class: center, middle, inverse

	# That's it.

	Slides made with Remark: [https://github.com/gnab/remark](https://github.com/gnab/remark)

	</textarea>
	<script src="https://gnab.github.io/remark/downloads/remark-latest.min.js" type="text/javascript">
	</script>
	<script type="text/javascript">
	var slideshow = remark.create();
	</script>
	</body>
	</html>