The MGS Blog

Showing posts with label presentation. Show all posts
Showing posts with label presentation. Show all posts

Thursday, February 9, 2023

Writing a precis


The commentary or précis of a reading/article conveys what you learnt and how you might employ the knowledge. In addition you can employ a critical or analytical interpretation, i.e. what is the intention of the authors, who is the audience, how valid are the claims?

Patterns for a basic précis:
  • Sentence 1:Name of author, genre, and title of work, date in parenthesis; a rhetorically accurate verb (such as "claims," "argues," "asserts," "suggests"); and a THAT clause containing the major assertion or thesis statement in the work. 
  • Sentence 2: An explanation of HOW the author develops and supports the thesis, usually in chronological order. 
  • Sentence 3: A statement of the author's apparent purpose, followed by an "in order to" phrase. 
  • Sentence 4: A significant quote from the paper used in a sentence.

Focus on the article being reviewed, not so much on other readings, books, articles etc.

Please do identify key quotes from the article. These a short statements or at most a sentence or two that distill some essential aspect of the article. A key quote is used: to point to the authors' evidence or claims; to make a justification for your own arguments; to act as a foundation for your own ideas. However, there must be clear delineation between the authors' content and your use of it therefore.

  • For quotes: use quotation marks followed by cite.
  • For paraphrasing: follow with cite.
  • For extracts and transformations like lists and tables: explain source followed by cite.
  • When reviewing, do not quote the author's quotes of other authors. Instead, quote an original passage written by the author of the article you are reviewing.

Please use double quotation marks and page number to identify "the quoted text" p. 23. You could apply one of the standard citation methods if you like e.g. Harvard style:

  • (Surname et al., Publication Year, p.#)
  • (Surname et al., Publication Year, pp.#-range)
Something like "some text" (AuthorSurname et al, 2033, p.7), or similar according to the citation standard required for the document.

Saturday, January 15, 2022

Cases - analysis/learning/synthesis

Possible ways to respond to a case. These approaches can be used for your own engagement with the mini cases. But note, you must bring your own creative spark to case analysis/learning/synthesis. The following is for inspiration and guidance and is not intended to be overly prescriptive.

Read the case. Search for and read relevant article(s) and books.
What made you curious? Have you further questions about any aspect of the case?
Identify learning-points, challenges or problems evident in this case.
Disclose personal experience, knowledge and skills you have relating to the area.
What personal knowledge gaps has the case revealed for you?
Provide evidence of key learning sources you identified to address the questions raised by you about the case and used by you to bridge your personal knowledge gaps.
Propose concrete actions (not mere recommendations) that you would employ in theory to address the case and/or to your own future projects based on the learning you gained from the case.

One possible approach to encapsulating your case analysis/learning/synthesis: 
Write 'Action Item' statements applicable to your own practice/team/company/and-or-the-case. Each Action Item to be a single (long) sentence covering the basics...
  • (Why) reasons linked to specific observation(s) based on or related to the case;
  • (What) elaborating on selected element(s) linking the case context with additional research/readings;
  • (How) 'for examples' suggesting things to be done that activate the recommended action item in a practical manner.

Friday, January 24, 2020

Reading an article and not sure how to write about it yourself?

- readings, precis, impact, application -

Prompting questions:
  • What did I learn from reading this article?
  • What was the intention of the authors?
  • Who is the audience for the article?
  • How could I use the article?

Readings are often difficult to understand or alternatively, to interpret and make sense of. I've often read a paper and said to myself "so what", "it's obvious", "what's the appeal of this stuff?" Sometimes I've been confused, overwhelmed with detail or just don't get the point. I've also read papers that have set off ideas, recalled past experiences, given an outlook that changes something I thought I knew well but now see in a different light.

Writing a precis of a paper turns the whole process back on itself somewhat; I go from being the reader of the paper to being a writer. Writing about a paper demands something of me, not just my impression of the paper and the information contained within, but how I felt about the ideas expressed, how I saw them applied, and reflected on their wider impact.

Written comments on a reading need to be succinct (if you go past a page then perhaps you should be writing a new paper?), and impact-full. Get to the point, don't just summarise, criticise! Refer to other works in a meaningful way (counter examples, supporting examples), and reflect on the bigger picture. If there are implications for practitioners and practice then state them, particularly if they are personal, affecting you.

When criticising a paper you should always attempt to be fair. Criticise it on its terms, not because it doesn't address certain areas that you think are more important; there may be good reasons for a paper's omissions: limited space, out of scope, irrelevance.

Finally, keep to the limits, word counts shouldn't be treated as "targets". If you can say less then say less; less is often more. It takes time to distill your comments and the result is often unexpected, but often in good ways.

Pointers
  • Pick out some aspect of interest from the paper
  • Comment on it (there are no wrong answers, it's just an opinion)
  • Link it back to design processes.
  • And consider linking your argument with pertinent external readings.
Try not go off on a tangent or indulge yourself in a flight of fancy. But if the paper sets off your creative side then explain your logic:
"The reading included a discussion of X which made me consider Y (not in the reading) because...".
Relate it back to the course; to continue:
"...but both X & Y are pertinent to Z which we have seen is a fundamental to the work of analysis, design and development"

The following rubric (a protocol or procedure) on assessing a written work may also be useful...
Audience: Who is the reading directed at? Is a question formulated, is it interesting and clearly put? Did the author clearly explain the purpose of the article?
Structure: Are the thoughts/arguments connected? Is there a logic to the presentation of ideas? Is theory utilised? If so is it treated critically or uncritically (just applied)? Do the authors anticipate and respond to counter-arguments?
Style of evidence: Does the work offer conjecture and possibilities based on the literature? Does the work offer empirical matter? Are assumptions stated? Is a philosophical foundation indicated?
Validity: How is the work positioned such that we understand how to test the extent of its claims, justification, rigour.
Rhetoric: Is the article persuasive? Are the findings, discussion and conclusions convincing? Does the work present implications and impacts? Are there behavioural, managerial, organisational consequences?


Further reading (about reading...no irony in that is there?)

  • R. Subramanyam. Art of reading a journal article: Methodically and effectively. Journal of Oral and Maxillofacial Pathology : JOMFP, 17(1):65–70, Jan-Apr 2013. (link)
  • E. Pain. How to (seriously) read a scientific paper. Science, March 2016. Available online at http://www.sciencemag.org/careers/2016/03/how-seriously-read-scientific-paper (Accessed: 29 November 2017). (link)
  • A. Ruben. How to read a scientific paper. Science, January 2016. Available online at http://www.sciencemag.org/careers/2016/01/how-read-scientific-paper (Accessed: 29 November 2017).