Putting my argument up front would have made my presentation better

I attended a workshop by Nick Hopwood on presenting qualitative research. It was full of tips and strategies – check out the storify – and useful frameworks; Hammersley’s framework for critical review of ethnography (reminding me again that I need to read Hammerlsey) and Kamler and Thompson’s framework for writing abstracts from their ‘Helping doctoral students write’ book (which I promptly ordered).

‘No’ by JDAC available at https://www.flickr.com/photos/jdac/15747357176 under a Creative Commons Attribution 2.0. Full terms at http://creativecommons.org/licenses/by/2.0.
‘No’ by JDAC available at https://www.flickr.com/photos/jdac/15747357176 under a Creative Commons Attribution 2.0. Full terms at http://creativecommons.org/licenses/by/2.0.

I’m a keen reader of Nick’s blog and have used his tips for conference presentations. For my last conference however, I failed to implement one: ‘turn it upside down’; that is, state my argument at the beginning rather than pull it all together at the end. This was because I love a good mystery novel and my co-presenter wasn’t keen.

At the workshop, Nick asked us to review a recent presentation in light of what we’d just learnt. I used this last conference presentation. And funnily enough, I could see how much better it would have been if I had turned it upside down. Here’s why.

The logic for turning the presentation upside down is that it helps you achieve your key motivation for presenting at all – give the audience a clear sense of your key take-home message. If someone pulls the plug on you 10 minutes in (maybe because the previous presenter rambled on), at least they know your argument. And Nick insists the audience is less likely to fall asleep. Luckily, I got the whole 12 minutes allotted at my conference presentation, and as far as I could tell, everyone stayed awake.

After the workshop three compelling reasons to ‘turn it upside down’ occurred to me.

First, if I’d made my big statement upfront then the audience might have been more engaged, curious as to how I’m going to convince them (i.e. the mechanism for ‘the audience is less likely to fall asleep’).

Second, it would have meant the rest of the content would be more likely to be relevant to that argument and not just self-justifying waffle about methods or demonstrations of how clever and well-read I am (no of course I didn’t do that).

The best reason I could think of? Making my argument up front would have given the audience time to digest it. Usually – and indeed in my case – the key argument is in the last slide or two. That gives them about a minute to catch it and process it before the chair calls for questions. This might be the reason for the measly post-presentation discussion at so many conferences. If I’d put it up front, they would have had a whole 10 or 11 minutes to think about my argument, in context, in relation to my data, and more importantly for engagement, in relation to their experience and knowledge of the phenomena. So I’m convinced by Nick’s advice.

But there is a problem. Putting your argument up front means you have to have one. I’m not being flippant here. How many qual presentations have you been to where the main game seemed to be to describe what participants said? You get to the end and think, well gee people really thought some stuff / felt some stuff / needed some stuff. But it can be a bit meh, you’re not sure what it all means, why it matters. I find this kind of qual research depressing; I am sure I have been guilty of it.

Making an argument is scary (people might disagree with you!). Arguments involve taking a stand, saying, this is how we should think about this phenomena. They require I work to persuade you, generally through presenting evidence, like my data analysis. If you think of it, data interpretation in basically an argument. I am claiming that mine is the best (or at least, most productive) way to understand what this participant means. Moving from description to interpretation can be a difficult things students to accomplish. It requires they develop confidence in their ability to interpret (not easy at all). Some tips I give my students:

Lyn Richards uses a great metaphor in her book ‘How to handle qualitative data’ for understanding the difference between data description and interpretation:

‘Somebody’s dead, they were shot and there’s a gun on the ground’ is the beginning of the detective’s questions. We hardly expect the enquiry to end with the facts of a dead body and discarded gun.

In her book ‘How to write a journal article in 12 weeks‘, Wendy Laura Belcher draws on a similar metaphor when talking about making arguments in papers:

Present evidence that supports your case, cross-examine evidence that doesn’t support your case, ignore evidence that is irrelevant to your case, and make sure the jury always knows whom you are accusing of what and why.

So, write the lawyer’s brief not the detective’s report. Can you imagine a prosecuting barrister standing up on front of the judge and jury and not telling them who they think did it? Or, to return to my topic, holding the punchline for the end? I would speculate that if you give the argument up front the audience starts doing some of the work for you – they know where you’re going so they are looking for the links. Hey’ that’s four reasons to put your argument first.

Last piece of advice from Wendy Laura Belcher to relieve you of some argument making anxiety:

Arguments don’t need to be unassailable or bullet proof, just interesting.

2 Comments

  1. nickhopwood says:

    A wonderfully candid and insightful piece (of course I’d say that, though…)

    Liked by 1 person

  2. Reblogged this on conversationandcare and commented:
    What a great post!

    Liked by 2 people

Leave a Comment