<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kelly Simonson on Medium]]></title>
        <description><![CDATA[Stories by Kelly Simonson on Medium]]></description>
        <link>https://medium.com/@kellyannsimonson?source=rss-33c654e88881------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j_HmHjmsWcLwiWt8lz-plg@2x.jpeg</url>
            <title>Stories by Kelly Simonson on Medium</title>
            <link>https://medium.com/@kellyannsimonson?source=rss-33c654e88881------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 12:53:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kellyannsimonson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Hellloooo to the internet]]></title>
            <link>https://medium.com/kelly-simonson/hellloooo-to-the-internet-538cb128c865?source=rss-33c654e88881------2</link>
            <guid isPermaLink="false">https://medium.com/p/538cb128c865</guid>
            <dc:creator><![CDATA[Kelly Simonson]]></dc:creator>
            <pubDate>Sat, 01 Aug 2020 04:46:49 GMT</pubDate>
            <atom:updated>2020-08-01T04:51:11.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxgB9JI29oWusSLvlIVX9A.jpeg" /><figcaption>Photo by Kelly Simonson</figcaption></figure><p>So, I started a website. And I would like to start by saying, “I have no idea what I’m doing”. First of all, I feel like I must have done something wrong, because it was way too easy to publish a website.</p><p>It’s a Wordpress site and it’s nothing complicated at the moment, but I was amazed at how simple it was to get going. I didn’t count the steps, so I hope I’m not misrepresenting the experience here, but my impression after the fact is that it was published and live in about 10 clicks. I started out this morning thinking that I was going to play around with learning how to get a site set up. There would be no way I’d make much progress and I’d have plenty time to contemplate what to actually <em>put</em> on a website once I finally got it working, which I expected to be in about a month or so. Well, that didn’t go as planned, and here I am, live on the big wide internet wondering what to do with myself.</p><h3>“You must have had some idea of why you wanted to start a website or you wouldn’t have even tried, right?”</h3><p>Ya, I have a lot of ideas, all of which I’m terrified of sharing with <em>anyone</em>, let alone anyone that might end up on my site.</p><p>Ok, here’s what I think I know. I’m interested in technology and how it shapes people and businesses. I like looking at process in business and I like thinking about how to make processes better using technology. I wanted a forum to write and think and get feedback on ideas. I have a strong desire to create, whether it be new processes for using for existing tools, or maybe someday a completely new tool that does something new. But that’s another post all together.</p><p>At this point I’m just hoping to put my ideas out into the world and participate in the conversation in a way that I’ve been scared to in the past. Here we go!</p><p><em>Originally published at </em><a href="https://www.kellysimonson.com/writing/2019/08/09/hellloooo-to-the-internet"><em>https://www.kellysimonson.com</em></a><em> on August 9, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=538cb128c865" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kelly-simonson/hellloooo-to-the-internet-538cb128c865">Hellloooo to the internet</a> was originally published in <a href="https://medium.com/kelly-simonson">Kelly Simonson</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Broke My Workflow]]></title>
            <link>https://medium.com/kelly-simonson/you-broke-my-workflow-a83412a2f4ad?source=rss-33c654e88881------2</link>
            <guid isPermaLink="false">https://medium.com/p/a83412a2f4ad</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Kelly Simonson]]></dc:creator>
            <pubDate>Sun, 18 Aug 2019 15:57:32 GMT</pubDate>
            <atom:updated>2019-08-18T16:19:08.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZjKQQ8WYs0RkVS2mZl7uKg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@carlheyerdahl?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Carl Heyerdahl</a> on <a href="https://unsplash.com/search/photos/business-process-carl-heyerdahl?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>“Having an environment where people can take advantage of their full potential and become recognized as experts is a huge motivator.”<br>-Denis Robitaille, CEO at World Bank Group</blockquote><p>I work constantly at changing (hopefully improving) the software tools people use all day long to do their job. I’ve rolled out new updates that contained great improvements, where I thought I did a good job explaining to users what the changes would be and provided appropriate training. Feedback after the update told a different story.</p><p>“Ever since that update I can’t find anything.”</p><p>“It seems slower.”</p><p>“It’s just frustrating to work with now.”</p><p>“I liked it better before.”</p><p>To be clear, I know the software did not get slower. I’m fairly certain the menus and screens did not get so convoluted to be called frustrating. There were a handful of things that were appreciably different and that broke some users worlds. Experiences like that have made me wonder, how do I really change <em>anything</em> without making people feel lost?</p><p>When considering process changes and implementations of new tools, we cannot take away people’s competence and their ability to do their job effectively and efficiently. We have to be able to support them in the new environment and process we’re asking them to live in. If we can make significant changes to improve processes, and during those implementations, have the right structures in place to train people to become experts in the new process, then we’ve given them the keys to unlocking their potential.</p><h4>So what is the best system to document and train processes?</h4><p>My experience working in a small business is that flowcharts and documents for some critical processes get created and filed away but at the end of the day, achieving well written, really useful, organized, full coverage of all business processes is hard to accomplish. In a company that’s not big enough to have dedicated job positions for internal trainers, technical writers, etc. you end up with a small group of people, creating content as a secondary task to their main job, trying to fill in the gaps for the rest of the business that’s mostly not participating. When processes are documented, how often do the people doing the daily work ever look at those documents? Never? If there’s some structure around it, then internal audits might bring them up occasionally and identify where the business has changed and now the documentation no longer aligns. Is that enough? Even if all critical processes are documented somewhere <em>and</em> there’s a system for auditing and keeping them up to date, chances are that documentation is in a separate stream of activity and focus from where the actual work happens.</p><p>Once a user knows the steps required to do their daily tasks why would they need to see the documentation of that memorized process? Isn’t it fine for the documentation to be off in it’s own space? It’s true people do know the steps they perform every day. They probably know them so well they can almost function on muscle memory. That only makes it worse when there does have to be a change because now we’ve not only made them think differently about what they are doing but we’ve taken away what they see as their expertise in the quick and efficient execution of their tasks. So they already feel less adept and then we ask them to go out into a documentation system that they aren’t familiar with (because they aren’t forced to use it on a daily basis) and filter through a large set of information to figure out what they need to know. Even if the changes to the process are explicitly documented, its still largly on the user to re-look at the big picture and figure out what they need to do.</p><p>This sounds like a nightmare for the user, who at the end of the day, really just wants to be good at completing their tasks. I think a critical turning point to improve this experience would be put to the process documentation, the “how to”, into the system where the work is happening.</p><p>Isn’t this just a BPMS (Business Process Management System)? Maybe, but I’m not convinced that those systems do everything I’m looking for. I plan to dig more into BPMS systems, and I’ll write about that when I do.</p><h4>In the mean time, here’s my ideal</h4><p>Make the process documentation part of the tools being used to do the daily work. Make it not only easily accessible but tightly integrated. This integration should be done so well that people don’t even realize that they are looking at documentation. The next step in the process should just be obvious. The required inputs should be immediately identifiable, even to a new employee performing the process for the first time, or for an experienced employee that might be going through a new process. The muscle memory being built includes looking for the verification that’s visible within the system that the next required step is what’s expected.</p><p>Surface the “why this step is the next step” so that users can gain understanding about their process. Remember we want users to be empowered to become experts. If all they are doing is going through the steps and clicking the button the documentation, or process management system, tells them to click, then they don’t really have understanding of their work. And what happens when there’s a nuance that the current process map isn’t covering, how do users know that there might need to be an extra consideration added to the process?</p><p>Make the documentation and process map editable or at least auditable by the users doing the process. Business processes get complicated, but the definition and documentation of them can’t be something that needs to be only set up and maintained by IT. Users have to be able to invest in the creation, refinement, and maintenance of the workflow they are participating in. I think this is how they become true experts and really feel ownership in what they are doing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a83412a2f4ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kelly-simonson/you-broke-my-workflow-a83412a2f4ad">You Broke My Workflow</a> was originally published in <a href="https://medium.com/kelly-simonson">Kelly Simonson</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>