{"id":95,"date":"2020-02-08T09:21:58","date_gmt":"2020-02-08T09:21:58","guid":{"rendered":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/?post_type=chapter&#038;p=95"},"modified":"2020-04-23T08:04:36","modified_gmt":"2020-04-23T08:04:36","slug":"managing-your-information","status":"publish","type":"chapter","link":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/chapter\/managing-your-information\/","title":{"raw":"Managing your information","rendered":"Managing your information"},"content":{"raw":"&nbsp;\r\n\r\n<hr \/>\r\n<p style=\"text-align: center\"><em>It\u2019s often the small things that make or break a big project. For a risk assessment, that\u2019s often the ability (or inability) to manage all the information you\u2019re gathering<\/em><\/p>\r\n\r\n\r\n<hr \/>\r\n\r\n&nbsp;\r\n\r\nBy now, you should have picked up that a successful risk assessment is a combination of high-level and tactical thinking and both soft and hard skills. This is one of the reasons that flying solo is so difficult: even if you have a mix of all the required skills, you need to switch between them frequently\r\n\r\nOne of the most overlooked parts of the risk assessment is managing all of the information that you\u2019re going to amass over weeks - months even - of research, interviews and workshops. It\u2019s very easy to start gathering information and for it to quickly get out of hand with a mixture of annotated company reports, print-outs of documents, notes from interviews and flip charts from workshops. At least if you are working by yourself, you have an idea of where everything is but imagine how quickly this becomes a mess when you have a team of people involved in the assessment.\r\n\r\nImportantly, this isn\u2019t just a case of keeping things neat and tidy for the sake of it: if you cannot collate and review all the information you\u2019ve gathered, then you aren\u2019t going to be conducting the assessment with a comprehensive picture of the organization. That\u2019s not to say that you need to gather every possible piece of data, that\u2019s impractical. But you need to be able to find and access all of the information that you\u2019ve gathered.\r\n\r\nMost importantly, you are conducting a process that may have a significant effect on the organization. As such, and particularly if something doesn\u2019t work out or there\u2019s an incident in the future, you might need your notes to be able to go back and review what information you had. In the worst case, you may need these as part of an investigation or legal action.\r\n\r\nSo when it comes to managing your data, there\u2019s not really such a thing as too much organization. Here are a couple of things to keep in mind that will help.\r\n<h1>Think more is better<\/h1>\r\nThere\u2019s not really going to be a time when you have too much information: issues concerning the time, availability of data, and access to key individuals mean that you will almost always be missing some information. Therefore you need to gather as much as possible while you are in the Understanding phase. And if information is available but you don\u2019t think you need it, grab it anyway.\r\n\r\nAnnual reports? Check! Sets of SOPs? Check! Incident reports? Training Logs? Check and check!\r\n\r\nDigital storage is essentially free and takes up no physical room so keep whatever you can at this point. You never know what you might need to turn to at a later date and you can always dispose of peripheral documents once the assessment is over.\r\n<h1>Write for someone else<\/h1>\r\nWrite your notes as though someone else is going to have to read them because they are: future you! What seems like an obvious abbreviation or contraction today could be meaningless in a few weeks time. Also, be accurate with the date \/ time \/ location \/ source of the information. \u2018London, January 12\u2019 isn\u2019t going to be much use if you conducted six interviews that day and collected two documents. Also, if you need to take photos, make sure you will be able to remember where and when the image is from. Something I\u2019ve found helpful is to take a context image, such as the front of the building or a map showing where you are, before you start with detailed images. This helps future me separate a series of similar photos at a later date.\r\n<h1>Cross reference<\/h1>\r\nSimilar to the issues that abbreviations can cause, quotes or pieces of data you capture need to be put into context and referenced. This is something that I continually mess up when I\u2019m researching online and I close out a dozen tabs at a time and then have to re-open each one to attribute the quote or data. Something I\u2019ve found helpful is a browser plug in the captures the URL of every tab you have open. So I capture all the key points I want from my research and quickly copy and paste all the URLS into the bottom of the source document. This literally saves me hours each month.\r\n\r\n<hr \/>\r\n\r\n<h2 style=\"text-align: center\">A quick note on quotes<\/h2>\r\n<p style=\"text-align: center\"><em>Quotes are incredibly helpful to make your point in a report but these can cause contention where someone disagrees with the point and then targets the individual. Therefore, I usually explain at the beginning of an interview that I might quote answers but these would always be anonymous. I keep a note of who said what for myself as this is useful if I need to go back for clarification but I avoid including anything the identifies the source in any of the report documentation.<\/em><\/p>\r\n\r\n\r\n<hr \/>\r\n\r\n<h1>Back up, back up, back up<\/h1>\r\nIt goes without saying that you need to back up your work. This goes for paper notes too so scan these into a back-up location online, ideally daily but at least weekly. Again, make sure that each page or set of notes is clearly identifiable both on the page and in the file name.\r\n<h1>Identify and collate themes<\/h1>\r\nA lot of what I\u2019ve talked about here is to help manage the raw data but as you collect and collate your information, you can begin to flag themes and recurring points. You need a system for this, particularly if there\u2019s a team working on the assessment so find a way to mark up notes so you can quickly pick out themes. If you have already determined the threat categories then you could mark items as \u2018threat\u2019, \u2018objective\u2019, \u2018vulnerability\u2019 mirroring the definition for risk you are likely to use. Whatever system you use, this will help you pick out the key data points when it becomes time to bring the report together.\r\n\r\nA friend of mine back in the military was fond of saying that the path to excellence was \u2018small things, done well, consistently\u2019. Managing your data is an example of a seemingly small thing but something essential to your success. Without an effective way to manage your data, your risk assessment will at a minimum, be much more difficult. At worst, it will be inaccurate because your data, and therefore your understanding, will be incomplete.\r\n\r\n&nbsp;","rendered":"<p>&nbsp;<\/p>\n<hr \/>\n<p style=\"text-align: center\"><em>It\u2019s often the small things that make or break a big project. For a risk assessment, that\u2019s often the ability (or inability) to manage all the information you\u2019re gathering<\/em><\/p>\n<hr \/>\n<p>&nbsp;<\/p>\n<p>By now, you should have picked up that a successful risk assessment is a combination of high-level and tactical thinking and both soft and hard skills. This is one of the reasons that flying solo is so difficult: even if you have a mix of all the required skills, you need to switch between them frequently<\/p>\n<p>One of the most overlooked parts of the risk assessment is managing all of the information that you\u2019re going to amass over weeks &#8211; months even &#8211; of research, interviews and workshops. It\u2019s very easy to start gathering information and for it to quickly get out of hand with a mixture of annotated company reports, print-outs of documents, notes from interviews and flip charts from workshops. At least if you are working by yourself, you have an idea of where everything is but imagine how quickly this becomes a mess when you have a team of people involved in the assessment.<\/p>\n<p>Importantly, this isn\u2019t just a case of keeping things neat and tidy for the sake of it: if you cannot collate and review all the information you\u2019ve gathered, then you aren\u2019t going to be conducting the assessment with a comprehensive picture of the organization. That\u2019s not to say that you need to gather every possible piece of data, that\u2019s impractical. But you need to be able to find and access all of the information that you\u2019ve gathered.<\/p>\n<p>Most importantly, you are conducting a process that may have a significant effect on the organization. As such, and particularly if something doesn\u2019t work out or there\u2019s an incident in the future, you might need your notes to be able to go back and review what information you had. In the worst case, you may need these as part of an investigation or legal action.<\/p>\n<p>So when it comes to managing your data, there\u2019s not really such a thing as too much organization. Here are a couple of things to keep in mind that will help.<\/p>\n<h1>Think more is better<\/h1>\n<p>There\u2019s not really going to be a time when you have too much information: issues concerning the time, availability of data, and access to key individuals mean that you will almost always be missing some information. Therefore you need to gather as much as possible while you are in the Understanding phase. And if information is available but you don\u2019t think you need it, grab it anyway.<\/p>\n<p>Annual reports? Check! Sets of SOPs? Check! Incident reports? Training Logs? Check and check!<\/p>\n<p>Digital storage is essentially free and takes up no physical room so keep whatever you can at this point. You never know what you might need to turn to at a later date and you can always dispose of peripheral documents once the assessment is over.<\/p>\n<h1>Write for someone else<\/h1>\n<p>Write your notes as though someone else is going to have to read them because they are: future you! What seems like an obvious abbreviation or contraction today could be meaningless in a few weeks time. Also, be accurate with the date \/ time \/ location \/ source of the information. \u2018London, January 12\u2019 isn\u2019t going to be much use if you conducted six interviews that day and collected two documents. Also, if you need to take photos, make sure you will be able to remember where and when the image is from. Something I\u2019ve found helpful is to take a context image, such as the front of the building or a map showing where you are, before you start with detailed images. This helps future me separate a series of similar photos at a later date.<\/p>\n<h1>Cross reference<\/h1>\n<p>Similar to the issues that abbreviations can cause, quotes or pieces of data you capture need to be put into context and referenced. This is something that I continually mess up when I\u2019m researching online and I close out a dozen tabs at a time and then have to re-open each one to attribute the quote or data. Something I\u2019ve found helpful is a browser plug in the captures the URL of every tab you have open. So I capture all the key points I want from my research and quickly copy and paste all the URLS into the bottom of the source document. This literally saves me hours each month.<\/p>\n<hr \/>\n<h2 style=\"text-align: center\">A quick note on quotes<\/h2>\n<p style=\"text-align: center\"><em>Quotes are incredibly helpful to make your point in a report but these can cause contention where someone disagrees with the point and then targets the individual. Therefore, I usually explain at the beginning of an interview that I might quote answers but these would always be anonymous. I keep a note of who said what for myself as this is useful if I need to go back for clarification but I avoid including anything the identifies the source in any of the report documentation.<\/em><\/p>\n<hr \/>\n<h1>Back up, back up, back up<\/h1>\n<p>It goes without saying that you need to back up your work. This goes for paper notes too so scan these into a back-up location online, ideally daily but at least weekly. Again, make sure that each page or set of notes is clearly identifiable both on the page and in the file name.<\/p>\n<h1>Identify and collate themes<\/h1>\n<p>A lot of what I\u2019ve talked about here is to help manage the raw data but as you collect and collate your information, you can begin to flag themes and recurring points. You need a system for this, particularly if there\u2019s a team working on the assessment so find a way to mark up notes so you can quickly pick out themes. If you have already determined the threat categories then you could mark items as \u2018threat\u2019, \u2018objective\u2019, \u2018vulnerability\u2019 mirroring the definition for risk you are likely to use. Whatever system you use, this will help you pick out the key data points when it becomes time to bring the report together.<\/p>\n<p>A friend of mine back in the military was fond of saying that the path to excellence was \u2018small things, done well, consistently\u2019. Managing your data is an example of a seemingly small thing but something essential to your success. Without an effective way to manage your data, your risk assessment will at a minimum, be much more difficult. At worst, it will be inaccurate because your data, and therefore your understanding, will be incomplete.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"author":253,"menu_order":7,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[47],"contributor":[],"license":[],"class_list":["post-95","chapter","type-chapter","status-publish","hentry","chapter-type-standard"],"part":50,"_links":{"self":[{"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/chapters\/95","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/wp\/v2\/users\/253"}],"version-history":[{"count":4,"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/chapters\/95\/revisions"}],"predecessor-version":[{"id":315,"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/chapters\/95\/revisions\/315"}],"part":[{"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/parts\/50"}],"metadata":[{"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/chapters\/95\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/wp\/v2\/media?parent=95"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/pressbooks\/v2\/chapter-type?post=95"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/wp\/v2\/contributor?post=95"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/authorlab.pro\/layout\/beyondthespreadsheet\/wp-json\/wp\/v2\/license?post=95"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}