{"id":492,"date":"2017-05-25T06:29:38","date_gmt":"2017-05-25T12:29:38","guid":{"rendered":"http:\/\/richardcolby.net\/writ3500\/?page_id=492"},"modified":"2022-06-06T13:23:19","modified_gmt":"2022-06-06T19:23:19","slug":"postmortem","status":"publish","type":"page","link":"http:\/\/richardcolby.net\/writ3500\/schedule\/module-10\/postmortem\/","title":{"rendered":"Postmortem"},"content":{"rendered":"

I know, it sounds grim. The examination of a dead body. Its literal translation from Latin is \u201cafter death.\u201d However, the expression postmortem has taken hold in the design, tech, and business world as a way to think about lessons learned from a project. It\u2019s a type of reflective thinking that identifies the best and worst parts of project and thinks about how you have learned from the project. To be clear, the project is not just the immediate design of the portfolio, but the places you have been as a writer, in this minor, that got you here. The “project,” then, is every bit of writing, class, and design that is reflected in the final portfolio.<\/p>\n

This postmortem (like most) has\u00a0four parts:<\/p>\n

    \n
  1. Introduction (100-200 words) \u2013 Introduce the project and its purpose. Then, describe the process of working on the project. In describing the process, you might consider how long you spent in various parts, what decisions you made that were important, and how you applied past skill or knowledge to it.<\/li>\n
  2. What went right (200-300 words) \u2013 focus on 2-3 of the most important things that you are proud of. These details can be about the design of the portfolio, whether it was how a particular page turned out, or a clever solution to featuring or displaying your work. You should\u00a0also consider the actual writing featured, including the drafting, revisions, and the process of curation and arrangement.<\/li>\n
  3. What went wrong (200-300 words) \u2013 focus on 2-3 things that were particularly challenging or that never quite came together the way you wanted. What designs did you try that didn\u2019t work? Was there something you liked that the reviewers didn\u2019t? How did you respond? What caused delays or made the project frustrating? As with “what went right,” also think about the writing projects featured, or particular classes. Try to avoid excuses. Technology can be finicky, professors can be idiosyncratic, audiences can be insensitive–we all face moments when things don\u2019t work as they should or we expect. The focus here should be on naming these moments\u00a0and how you responded to them.<\/li>\n
  4. Applying the lessons (100-200 words) \u2013 in the last section, think about what you learned from the good and the bad and how you might apply that thinking in the future. This should be practical and not just abstract platitudes. Refer to how (and what) you learned to overcome the writing and design challenges, and how that process (or those skills) might be applied in a workplace or future academic setting. This can be everything from an increased literacy with Weebly or Wix to a recognition that sometimes an unfamiliar audience might read your writing in a way you hadn\u2019t intended.<\/li>\n<\/ol>\n

    The postmortem should be between 600\u20141,000 words. A longer postmortem isn\u2019t necessarily better. Use the four headings of the main sections, and even consider adding some subheadings based on certain parts you want to focus on. This is not an essay. Finally, while this is a reflection, you will be posting it to them public blog, so think at moments about communicating to an audience the lessons learned.<\/p>\n

    When you are done, post to the blog by June 8, 11:59pm<\/strong>. I realize this is a busy time, so if you need more time, please ask as I won\u2019t be able to read this until later in the week anyway.<\/p>\n","protected":false},"excerpt":{"rendered":"

    I know, it sounds grim. The examination of a dead body. Its literal translation from Latin is \u201cafter death.\u201d However, the expression postmortem has taken hold in the design, tech, and business world as a way to think about lessons learned from a project. It\u2019s a type of reflective thinking that identifies the best and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":490,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-492","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/492","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/comments?post=492"}],"version-history":[{"count":8,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/492\/revisions"}],"predecessor-version":[{"id":2414,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/492\/revisions\/2414"}],"up":[{"embeddable":true,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/490"}],"wp:attachment":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/media?parent=492"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}