01/29: Constraints: Sticking to your purpose (St. Dominick)

Assigned Today

Over the weekend, please read Michon, Chabet and Turley’s “Mall atmospherics: the interaction effects of the mall environment on
shopping behavior” (LINK)

Please also read the Open Technical Communication chapters on Tables, Charts and Graphs (LINK) and on Graphics (LINK).

Today’s Content

We’ll end our St. Dominick conversation by talking about one of the constraints of a technical report: the effect of declaring a specific scope of your document.

We will also talk about how our expertise—the subject of our memo this week—can affect our ability to declare a purpose in the first place. While technical reports offer us a lot of affordances in terms of limiting how much we need to write, some of these other factors will limit how much we can write, and we’ll need to find a balance between them.

Key takeaways for this week:

  • Technical structures, like report, offer a lot of support in figuring out what we need to write and what we can do with a document
  • Technical structures can also be limiting, in that we need to follow enough of their rules that our document is still recognized as something in that category.

Leave a Reply

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

css.php