Avoiding Masterchef style feedback

Her eyes widened and her mouth fell agape. I suspect the ticking clock suddenly stood still and the taste buds, that had become her all-powerful ally, dried up as fast as an unwatched pan of pasta. Her idea had been derailed.

Wherever I look I see processes of critique and feedback. It is unquestionably an integral process for learners. However, it is also a process that binds and carries the progress of many other professions and creative endeavours, as well as almost everything else in between.

That is why when watching the TV show Masterchef, the amateur cooking competition, the impact of feedback was all too present and obvious.

Masterchef style feedback refers to providing feedback at a point when it is creatively inappropriate as well as emotionally challenging to hear.

Now if you have never seen Masterchef let me share the scenario. The contestant I describe had begun a challenge in which they were in a small group of other contestants but cooking independently. They were given a time limit, like 30 minutes, to cook a particular style of dish or create something unique.

I recognise that the pace of the creative process (generating original ideas for a dish) on show here is very high along with the intensity of the environment, time, expectation and competition. This can be a block to creativity.

In this intensity, the contestants are immediately generating ideas as they hear the challenge ahead of them, even before the basket wielding supermarket sweep for ingredients begins. They are all drawing upon a history of cooking, a long line of experience using the ingredients they have and a range of ideas and principles of cooking that have been tried and tested before.

The action usually commences with everyone rushing off to a pantry filled with a plethora of fresh ingredients and cupboard essentials. The ideas for their dish begin to swirl as they are confronted by the swathe of stock laden shelves in the pantry. There are those that pluck what they need, the decision made and those that are still developing something, waiting for inspiration to strike, lost momentarily in the various types of vinegar on offer.

With baskets crammed the cooks rush to their workbenches and stovetops to begin cooking. Stakes are high (fill in your own pun) as they compete with each other, the clock, their own nerves and the judgement of professional chefs and food critics. Suffice it to say that emotionally the environment is highly charged for those involved.

And then comes the first moment of feedback.

Who knows really how much time has passed due to the editing process for television. However typically a trio of judges saunters across to a contestant to try and learn what dish is being made and observe the progress towards that goal. Comments both positive and negative are typically shared with the contestant at this point. This is a moment when really contestants are implementing their idea for the dish, they have committed to it and are pushing on. Feedback which is anything but affirmation is derailing.

So every now and then you see idea derailment in the eyes of the contestant. The widened eyes of an inner struggle to assimilate the expert advice with their emotional and technical commitment to an idea. “How can I possibly change my dish now?!” The contestant has invested in their idea and fast-tracked to implementing it. They are no longer making major decisions about what to do but are now amongst the intricacies of making it happen. Their mindset is no longer in a divergent state but is now one of convergence towards a more and more fixed goal.

It is this style of feedback which I think we have to seek to avoid. After all the cooking on Masterchef, however much a show for TV is still a microcosm of a creative process. This is similar in so many ways to when we ask the learners in our classes to create something, think high stakes, time, judgement.

To avoid Masterchef feedback or idea derailment we simply have to provide more feedback earlier on in the creative process.

In the case of Masterchef the time in the pantry, as the contestants jostle for ideas, inspiration and ingredients, would have been a good time to speak with people to offer ideas and feedback. Sometimes on a show, you see those stranded in the pantry getting a pep talk from a judge as they share and develop ideas together. That early feedback and dialogue are much more developmental and appropriate than derailing ideas already on their way.

In the classroom, we might build in earlier check-ins with learners as they begin the process of generating ideas for their writing, painting, modelling etc. The longer you leave that early check in the more committed to their ideas students will become and there is a higher chance of idea derailment if you offer critique. Plan for feedback to occur early and frequently to catch our young thinkers whilst their mindset is still divergent and open to ideas.

Second Score – use this meta-feedback strategy

In our work and learning, the quality of creative culture can be directly linked to the quality of the feedback culture.

We might also call this a Culture of Critique with its associated processes and dispositions.

It is no real surprise that we should invest time, energy and effort in getting good at feedback. What follows is an outline of a a handy technique, I will coin Second Score, which can aid the way we receive feedback from others.

I first came across it in “Thanks for the Feedback: The Science and Art of Receiving Feedback Well,” co-authored by Sheila Heen and Douglas Stone. Worthy of your time and standard reading for anyone interested in feedback.

It is pretty straightforward, basically we give ourselves a (you guessed it dear reader) Second Score. But importantly the assessment is about the way we received the feedback.

Let’s imagine the scenario where you have created a diagram to visualise a key concept. It will form part of larger written report you are collaborating on with your team. You pitch in the version you have drafted over the last few hours and have asked for some critique or feedback from others. That feedback arrives from a few of your team and overall it seems heavy handed and too general in detail to be useful. [PAUSE]

So at this moment just as you complete the reading of the feedback comments, you have a choice. We all have a choice in these moments. How we choose to receive the feedback. It is this reception that we can rate or assess. By explicitly thinking about your Second Score (how we receive the feedback) we increase our self awareness at this critical moment, increasing the likelihood of openness and more favourable conditions for it to be received well.

[PLAY] In this scenario we might: (a) throw up our hands and agree never to contribute a visual element to future reports (b) write down some questions in response to help clarify what needs your attention first (c) Nod our heads, retreat to our happy place, change nothing (d) delete the original files and say “I thought that is what you meant, oh fine, I can’t win!” (e) corner one of the feedback providers and ask them what their problem is.

You can hopefully see the choice that might score more favourably using our Second Score.[1] Although we might judge the quality of the feedback to have been low, we can happily give ourselves a higher Second Score in terms of how we received it. Well done you.

For us and for younger learners this type of technique will potentially develop a strong reflective habit. In many ways this falls into the meta-cognitive bucket insomuch that the act of reflecting on how we receive feedback. I am not sure if you can put the word meta in front of feedback but it feels like this is a meta-feedback technique.

So the next time you are providing feedback, and especially when we are on the receiving end consider your Second Score.

Photo by Adam Jang


  1. (a) good luck with that (b) yes definitely this one (c) no (d) see “a” (e) no that is just wrong  ↩

How To Make The Most Of The 30% Feedback Strategy

Feedback strategy is often focused on Giving feedback, but this is only part of the process. We have lots of assessment tactics for providing, offering and giving feedback, but little on receiving it.

This post outlines a feedback strategy to help you or your students receive feedback successfully.

The Feedback Dynamic

“It takes two to tango”, as the song goes, and the dynamic of feedback depends on a relationship between two (or more) people.

  1. The feedback giver
  2. The receiver of feedback

It is common for us to have feedback strategies for giving feedback, but we can also develop feedback strategies to receive critique effectively.

Receiving feedback has a unique set of skills, strategies, and dispositions. We overlook these too often and then wonder why feedback is not effective.

The 30 Percent Feedback Strategy

30% feedback is a feedback strategy for the receiver. It signals to the feedback giver your overall progress. Is it 30% complete or 90% complete?

You are referring to the progress of whatever you are making or creating. You might be writing an article or essay or creating a piece of artwork. Whatever the subject of the feedback is, signal the progress you believe you have made.

Consider these two statements: “This is 95% complete” and “I just started, it is about 10% done”. Imagine the mindset of these two people or students. Do you notice the difference? The different attitudes are essential to the effective receiving of feedback.

Don’t Polish Anything

I first came across this technique from Jason Freedman’s blog post and realised how useful it would be for students seeking feedback from others. Jason explains that he learned it from a colleague at 42Floors:

It’s a trick I learned from our investor, Seth Lieberman.  It came about because I once asked him for feedback on a product mockup, and he asked if I felt like I was ninety percent done or thirty percent done. If I was ninety percent done, he would try to correct me on every little detail possible because otherwise a typo might make it into production. But if I had told him I was only thirty percent done, he would gloss over the tiny mistakes, knowing that I would correct them later.  He would engage in broader conversations about what the product should be.

In this particular case, I was indeed ninety percent done and so we debated a few details, I got my pat on the back, and I moved on.

As he was leaving, he said:

“Next time come to me when you’re only thirty percent done and I’ll give you thirty percent feedback.”

So a few months later on a different project, I came to him with some questions on a project that was still in its early stages and we wrestled with the direction together.  I didn’t polish anything and he made sure not to critique things he knew I would fix later.  It was really freeing. I knew I wasn’t putting my best foot forward and he didn’t care.  He was able to help me shift course without the sunk cost of throwing away a ton of work.  Really awesome.

Jason Freedman

Imagine the time and energy you save if the feedback you offer is more targeted and you respond to these precise progress signals.

Your Progress Bar

For students, it could be as simple as a progress bar with their work.

  • What percentage do you think you have completed?
  • How much more do you think there is to do?

Before you receive feedback, signal to the other person your progress, talk about the features of early feedback and how later feedback is different.

Progress bar feedback strategy

The progress bar could even have markers for when to seek feedback to help structure those opportunities.

A Mindset Ready for Feedback

We need to help our students be open to feedback much earlier on in the making process.

Whether writing, drawing or building, being open to early feedback takes a specific, deliberate mindset switched to ‘open’ and ‘growth’.

This strategy’s key to success is a shared understanding of 30% or 90% feedback. We can develop our understanding of these levels and increase our readiness to offer the most appropriate support.

This responsibility also falls on the receiver. The additional signals they can offer to help us improve what they are doing.

Just remember feedback is a two-way street. We may refine our protocols for giving feedback, but there are many strategies we can implement to help us and our students receive feedback successfully.

Learning in Perpetual Beta

 

For today’s post I thought I would explore a little more deeply the themes and overlapping thinking surrounding my previous post about a Mindset of Failing. In particular I’d like to unpack this concept that learning is and always should remain in perpetual beta.

It is actually a considerable challenge to get perspective on the completeness of our work with students. I am not referring to when projects end or when we have finished that piece of artwork with them – the year long (sometimes much longer) development of learning relationships is often hard to wrap ourselves around. Since leaving the classroom I have experienced quite finite projects that have a short timeline and stuff you have to get done. I still find this refreshing.

Perpetual Beta = Prototyping Disposition

vIn an earlier post this month I referred to the mindset we need to take towards the things we create and the way we learn. It is not just about junk modelling or computer aided design or 3D printing or physical building – a disposition towards prototyping means we:

  • Are committed to the expertise and ideas we might gain from others and don’t just simply rely on our own perspective.
  • Believe in the value of feedback and how critique can move our ideas forward.
  • Engineer as many opportunities for feedback as we can as, early as we can.
  • Are willing to share what we create when it is extremely, painfully incomplete.

When a piece of software is being developed it has various stages it goes through, depending on the scale of the product of course. Beta is a time for testing, as defined below:

Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. It generally begins when the software is feature complete. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it.

Perpetual beta is when this state is extended, sometimes indefinitely, a web service or software product remains in constant development with feedback and testing driving new feature releases. A product remains in perpetual beta.

What does learning in perpetual beta mean?

The links here with the way we think about learning and feedback in particular are quite strong. In my post about the Mindset of Failing I pondered on the mental resilience of tennis players compared to other athletes. Losing points is regular and failing is part of the back and forth of a tennis match, very different to other sports. The post was commented on by Pam Hernandez who remarked that:

This made me think about how we traditionally provide feedback on student learning which is not unlike the analogy to football. I’m thinking American football in this case and getting an A on assignment is much like scoring a touchdown. It’s not uncommon to see teachers use sports analogies and comment “Homerun” or “Touchdown” on good work. I like the idea of rewarding effort along the way and making it okay to make mistakes along the way and be rewarded for the learning. It’s a different mindset for parents, teachers and students. (Pam Hernandez)

And it is here that we have the biggest opportunity to shift the way people are thinking about failure and failing. It is no small feat mind you. There are cultural and ethical stances people have that influence their perception of mistakes and failure in learning. We need to help the whole learning community appreciate this positive prototyping disposition. Learning in perpetual beta is all about continuous improvement with an emphasis on engineering as many opportunities for feedback as we can.

Take a look through some of these other posts from my this blog about assessment and feedback and plan to take some action:

Pic: failure is cool by Steffi Reichert

Keeping the main thing, the main thing – Posts about Feedback from #28daysofwriting

5727007519_7cf25af4d3_b
loopz by Rosa Menkman

I started 2015 in Perth. Well in actual fact I had trips to Brisbane and Sydney as aperitifs and then headed to Western Australia. I was helping with some professional learning days at a large independent girls school we have been working with since the beginning of 2014. Our mantra for the sessions was:

Keep the main thing, the main thing

And feedback with its long lost twin, feedforward, is pretty close to being one of the most important elements of learning and curriculum design. I will spend some time in future posts sharing how I see it all and how it aligns with a prototyping disposition. For now, here are some great blog highlights from educators sharing their thinking on feedback as part of #28daysofwriting.


 

Alex Gingell shares how he used an Experience Tour to help with the professional learning discussions on feedback in his school.

I wanted staff to ‘immerse’ themselves in feedback. To gain an understanding of how feedback works across the school and to give them a tool that would enable them to develop their own perspective of feedback in their practice. This tool is designed to be used over a slightly longer period of time and having started, I would now like to provide the opportunity for staff to continue their ‘tours’, moving from reflecting on feedback in books, to experiencing feedback in each other’s classrooms.

Experience Tour: Feedback by Alex Gingell

Great to see the DIY Toolkit being hacked to suit the needs of our school developments. An interesting post well worth a look.

 


 

In this post from the Four Seasons in One Kiwi blog, @StephT shares some of the discussion about feedback in terms of leading a school.

a good leader shows they are human, takes on board feedback, uses it to improve the way things are done but does not allow themselves to sink under the weight of it.  We did not think that the leader that journeys up the Nile in a heavy armour plated frigate was that of a good modern leader.  That, we felt, was a leader that ignores feedback and has armoured ears, which could, consequently turn into a disaster zone.

Day 7: Educational Piranhas #28daysofwriting by @StephT

Great to get some on the ground, fresh insight into the principal role within a school – read the rest of the post above.

 


 

This post from Dave Stacey outlined an interesting concept to explore when structuring the timing of feedback. Something I will be returning to in a future post of my own.

We need to get much better about the point at which we give our feedback and make sure students can act on it (DIRT time is an idea that’s been kicking around for a couple of years, and if you’re a teacher if you’re marking without it, you’re probably wasting a chunk of your time – try here and here to start, but there are loads of great blogs on it). We can restructure our assessments, we can make better use of cloud technology to provide feedback BEFORE the final deadline, or ensure that students get a second go at delivering that presentation.

I shouldn’t feel bad for saying ‘well done’ – #28daysofwriting day 5 by Dave Stacey

 


 

Nicola Richards shares her first steps into using the SOLO Taxonomy in helping students understand the specific parts of their journey. By the sounds of it the taxonomy helped the class also provide effective feedback to peers, which is often tricky if we don’t have a notion of what specifically to say.

So my first real “work” for my class this year was to write a paragraph with a video as a stimulus. Once they were finished we discussed the key concepts and then I asked them to peer assess the paragraphs using a simple SOLO rubric. Most found it easy to identify where their partners work was at and could also identify next steps. I can see me using this regularly for peer, self and teacher feedback. I am passionate about the use of SOLO taxonomy (thanks @arti_choke) and keep finding ways to incorporate it in my teaching and learning. This was a great example as it fulfills many of the key requirements of effective feedback too.

28 days of writing – day 5 by Nicola Roberts

Explore more of Nicola’s post on her blog nixpixmyideasonstuffeducational

 


 

I look forward to writing and learning more from the reflections of others about feedback and do my bit to keep the main thing the main thing.

Image loopz by Rosa Menkman