Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notes from meeting - Monday 14 November #1

Open
lucymonie opened this issue Nov 14, 2016 · 3 comments
Open

Notes from meeting - Monday 14 November #1

lucymonie opened this issue Nov 14, 2016 · 3 comments
Assignees

Comments

@lucymonie
Copy link
Contributor

Developing a feedback culture at FAC

Meeting attendees: Dan, Nick, Cleo, Jen, Esraa, Nori, Lucy (apologies from Steve)

Downsides

  • Mandatory feedback can feel contrived, forced or repetitive
  • Feedback can cause unnecessary anxiety
  • Badly managed feedback can damage team trust

Upsides

  • Positive feedback can be very bolstering
  • Giving and receiving feedback is an opportunity to grow and improve

Way forward?

There was agreement that feedback should be delivered verbally as there is less room for misconstruction. There was less agreement about how feedback should be organised. There were two main schools of thought: group-based and individual

Group-based ideas

  • Tie feedback to tasks and groups rather than individuals
  • Stop/go/continue in teams
  • Someone (eg Dan) could lead each team's group feedback sessions
  • Individuals could ask for feedback from the team on specific areas
  • Feedback could lead to mutual coaching within the team

Individual ideas

  • Each individual in the team gives feedback to one other individual (privately)
  • Teams could split into pairs and give feedback to each other

Alternative ideas

  • Feedback could be encouraged but given on the fly as the spirit moves you
  • Half-group, half-individual approach: self-reflection followed by the team giving feedback as a group to each individual (in front of others)
  • Pair coding observations
@sofer
Copy link

sofer commented Nov 15, 2016

So, let's trial something in the next couple of days, i.e. before the next project begins. Perhaps each group can come up with a different approach and then we can feed back on Friday at the SGC session.

@lucymonie
Copy link
Contributor Author

Outcomes of retrospectives discussion

Friday team stop/go/continue
  • 20 minutes post-its on the wall, 20 minutes of discussion (with Dan)
  • 2-4pm Wednesday 23 November
Individual feedback
  • Teams to consider individual feedback and try it out if they want to

@sofer
Copy link

sofer commented Nov 23, 2016

Thoughts from today's retrospectives:

  • we didn't quite manage to stick to 20 minutes; arguably we might want to next time;
  • some of the suggestions provoked a fair amount of discussion. While it's important to clarify a point to make sure you understand it, once that's done it may be more productive to acknowledge a controversial or interesting point and move on;
  • going round at the end of the session to identify one thing that each member of the team wants to work on in their own practice seemed to be a helpful exercise.

I found the sessions very useful. I cannot believe that we haven't been doing them regularly before now.

@stevehopkinson stevehopkinson removed their assignment Feb 17, 2017
@Cleop Cleop removed their assignment Mar 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants