<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">All -<br class=""><div><br class=""><div class=""><div class="">On Aug 10, 2020, at 5:02 PM, Caroline Kyungae Smith <<a href="mailto:caroline.kyungae@gmail.com" class="">caroline.kyungae@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"></div><blockquote type="cite" class=""><div class=""><div style="caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><b class="">has anyone had to map the workflows of a legacy system maintainer before?</b> What did you do and how did you manage a subject matter expert who knows so much but can't communicate it in a straightforward way? What was the final format of the documentation?</div><div style="caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">--</div><div style="caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">I am currently on a project where there is an 80-year-old subject matter expert and keeper of knowledge of an old mainframe that we are currently working to modernize, by converting the COBOL to Java and moving it to the cloud. </div></div></blockquote></div><br class=""><div class="">I am a specialty software vendor in this niche.</div><div class=""><br class=""></div><div class="">Our world view is IBM z/OS mainframes… which means big, old, poorly documented operational systems. </div><div class=""><br class=""></div><div class="">In most cases the code is the documentation plus the few remaining SMEs with the tacit knowledge between their ears.</div><div class=""><br class=""></div><div class="">Succession planning — actually from my very large down to departmental/small company — is a huge challenge.</div><div class=""><br class=""></div><div class="">It’s just human nature to ignore stuff that works & focus on today’s brush fires. When “the IT guy” who knows how the maze is cobbled together leaves… this is not good.</div><br class=""><br class=""><div class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; widows: 2; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; widows: 2; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; widows: 2; border-spacing: 0px;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">___________________<br class="">David Eddy<br class=""><a href="mailto:deddy@davideddy.com" class="">deddy@davideddy.com</a></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><a href="mailto:david.eddy@legacysoftware.co.uk" class="">david.eddy@legacysoftware.co.uk</a><br class=""><br class="">Legacy Software, Ltd.<br class="">www.legacysoftware.co.uk<br class=""><br class="">781-455-0949 (Boston)</div></span></div></span></div></span></div></div></div></div>
</div><br class=""></body></html>