{"id":305,"date":"2016-10-12T20:10:41","date_gmt":"2016-10-12T19:10:41","guid":{"rendered":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/?p=305"},"modified":"2019-01-22T14:09:10","modified_gmt":"2019-01-22T14:09:10","slug":"what-makes-a-good-design-log-entry","status":"publish","type":"post","link":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/2016\/10\/12\/what-makes-a-good-design-log-entry\/","title":{"rendered":"What makes a good design log entry?"},"content":{"rendered":"
\n
\n
\n

On\u00a0this module, we use an online reflective log to share stories, notes, ideas coming from\u00a0the success and failures of our\u00a0design practice (across teams). This post gives some guidance on\u00a0how to\u00a0evaluate your project activities through a series of blog entries.<\/p>\n

Reflective writing helps your design projects in three ways (Zubizarreta, 2009). First,\u00a0it enables you to document and evidence<\/em> actions and activities. Second, it makes it easy to\u00a0support\u00a0feedback, mentoring, and collaboration. Finally,\u00a0it helps to\u00a0learn from success and failure, develop insight into why those occurred. Over time, it helps to make sense\u00a0of complex issues. As you make entries over time,\u00a0you capture\u00a0observation through images and document notes, you’ll help revise your insight and reflection. So do review older posts and refer to those\u00a0in\u00a0newer entries for example by commenting on new insights gained.<\/p>\n

Zubizarreta (2009, p. 46) mentions\u00a0a number of aspects\u00a0to consider for log entries:<\/p>\n<\/div>\n

\n
\n
\n
\n\n\n\n<\/colgroup>\n\n\n\n\n\n\n
\n
\n
\n

Dimensions<\/p>\n<\/div>\n<\/div>\n<\/td>\n

\u00a0Comments<\/td>\n<\/tr>\n
\n
\n
\n

Reflective depth<\/p>\n<\/div>\n<\/div>\n<\/td>\n

\n
\n
\n

Logs often focus on future improvements and change: to learn from an action,\u00a0indicate what improvement is desirable\u00a0and\u00a0critically assess why and how! \u201cWhat change was necessary?\u201d, \u201cWhat process did we use to facilitate change?\u201d, \u201cWhy was the change desirable?\u201d<\/em><\/p>\n<\/div>\n<\/div>\n<\/td>\n<\/tr>\n

\n
\n
\n

Source of evidence<\/p>\n<\/div>\n<\/div>\n<\/td>\n

\n
\n
\n

(1) \u201cInformation from self\u201d (teams’ set goals, earlier<\/em> reflective entries); (2) \u201cInformation from others\u201d (reflection on feedback\u00a0from peers, the tech advisor, lecturer etc); (3) \u201cProducts of learning\u201d (a note, or summary of, an achievement produced; interviews, requirements\u00a0gathered, for instance).<\/p>\n<\/div>\n<\/div>\n<\/td>\n<\/tr>\n

\n
\n
\n

Evidence<\/p>\n<\/div>\n<\/div>\n<\/td>\n

\n
\n
\n

(1) From field notes<\/span>: images, videos; (2)\u00a0From feedback<\/span>: emails, classroom discussions; (3) From research<\/span>: concept maps, references to published material<\/p>\n<\/div>\n<\/div>\n<\/td>\n<\/tr>\n

\n
\n
\n

Consistency<\/p>\n<\/div>\n<\/div>\n<\/td>\n

\n
\n
\n

Posts should be of sufficient length to make their point, so at last a substantial paragraph in length; and an indicative entry per week would be around 500 words at least. Referencing to theory, literature, activities is desirable (see point ‘evidence’).<\/p>\n<\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As a general note, try to start each log entry with a brief introduction (to give a bit of context to the post as a whole). This will help the reader understand where you are coming from; and you may also discover that your posts connections to reflections from previous weeks.<\/p>\n

An example of a good reflective log entry can be found here:\u00a0https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/2017\/10\/25\/2-statements-of-community-consultation-meeting-with-the-stakeholders\/<\/p>\n<\/div>\n

\n

Sources for follow-up<\/strong>:\u00a0Zubizarreta (2009).\u00a0The Learning Portfolio.\u00a0John Wiley & Sons<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

On\u00a0this module, we use an online reflective log to share stories, notes, ideas coming from\u00a0the success and failures of our\u00a0design practice (across teams). This post gives some guidance on\u00a0how to\u00a0evaluate your project activities through a series of blog entries. Reflective writing helps your design projects in three ways (Zubizarreta, 2009). First,\u00a0it enables you to document … Continue reading What makes a good design log entry?<\/span><\/a><\/p>\n","protected":false},"author":6384,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"gallery","meta":{"footnotes":""},"categories":[21],"tags":[30],"class_list":["post-305","post","type-post","status-publish","format-gallery","hentry","category-questions-answers","tag-design-log","post_format-post-format-gallery"],"_links":{"self":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts\/305","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/users\/6384"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/comments?post=305"}],"version-history":[{"count":6,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts\/305\/revisions"}],"predecessor-version":[{"id":1204,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts\/305\/revisions\/1204"}],"wp:attachment":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/media?parent=305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/categories?post=305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/tags?post=305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}