02/03: Affordances: IMRD (Atmospherics)

Assigned Today

Your third technical memo is due at the end of this week.

Today’s Content

We’ll talk about a common report structure today: IMRD. It’s something you’ve practiced if you’ve been a class with lab reports. It’s also something you’ve probably seen pretty frequently, even if we don’t have the headings named in this pattern (or even if we don’t have headings at all).

Introduction: Provide an overview of your document. Tell the reader its purpose, the reason you did this work in the first place, and any prior research or prior conversations you are building from. The introduction should always begin with something your audience already knows. Use this to build the rest of your conversation by linking each new point back to something previous.

Methods: Sometimes, this is a Procedure, Methodology, Research Design section or something else. But, a methods section should tell the audience how information was gathered or analyzed if they couldn’t safely assume it from your document’s introduction. So, if you’re in a geology lab and you’re testing minerals to see what’s igneous and what’s sedimentary, you’ll probably want to tell your reader what specific lab procedures you went through. But, if you’re in a literature class and you’re telling the reader about the theme of friendship in the Lord of the Rings, we’ll all safely assume that your procedure was “I read a thing and thought about it.”

Results: If your research process found brand new information that the world has never seen (even if it’s something as simple as the results of a survey you sent out), you should report them without any analysis or interpretation. Results sections typically have lots of non-text elements like graphs, tables, pictures and other visual representations of your data.

Discussion: At the end of your document, tell your reader why what you found was important. Connect your data/results back to the purpose of your document (what you said in your introduction). Every hypothesis or problem you intended to discuss should be discussed here. If you are recommending a particular course of action from your reader, your discussion section should make it clear why that action is a good idea. This section should also include any limitations to your work.

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php