<?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[Benjamin Mosior - Medium]]></title>
        <description><![CDATA[understand systems, manage complexity, seek answers - Medium]]></description>
        <link>https://medium.com/benjamin-mosior?source=rss----67d1910768eb---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Benjamin Mosior - Medium</title>
            <link>https://medium.com/benjamin-mosior?source=rss----67d1910768eb---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:49:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/benjamin-mosior" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Buffer Management for Meal Prepping]]></title>
            <link>https://medium.com/benjamin-mosior/buffer-management-for-meal-prepping-9278d28d80e9?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/9278d28d80e9</guid>
            <category><![CDATA[cooking]]></category>
            <category><![CDATA[food]]></category>
            <category><![CDATA[inventory]]></category>
            <category><![CDATA[theory-of-constraints]]></category>
            <category><![CDATA[buffer]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:15:37 GMT</pubDate>
            <atom:updated>2017-02-02T03:07:47.988Z</atom:updated>
            <content:encoded><![CDATA[<p>This post describes an attempt to apply theory practically (praxis) to solve a silly little problem.</p><p>My wife and I are getting serious about cutting our restaurant spending, so we have been cooking large batches of food to store and eat throughout the week. Cooking in large batches like this is a practice known as meal prepping, and we’ve had enormous success in our first few months with it (we spend more in groceries, but we save much more overall). We are very busy and don’t particularly enjoy cooking, so we often go a little wild by cooking and freezing a few weeks of meals at a time.</p><p>For a while, it’s absolute bliss; we just microwave food in a couple minutes each meal and go about our merry way. When we run out, however, it’s always a bit of a scramble. We usually end up eating at restaurants again until we can find the time to plan and cook. To solve this problem, I realized we can use buffer management concepts from the Theory of Constraints.</p><p>We know the consumption of food is a critical activity — we don’t much like starving — that requires some inventory to always be available (i.e., food in the freezer). Using ToC concepts, we can designate part of the inventory as a buffer in order to ensure that food is always available. As long as the buffer remains intact to some degree, the inventory never hits zero. We just need to know when the initial threshold into the buffer is crossed so we can find the time to cook more food.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bwNsU5LDK7UN26dToGbh0w.jpeg" /><figcaption>A quick draft of an inventory level chart, indicating the current and threshold levels.</figcaption></figure><p>To put these ideas into practice, we could start by improving the visibility of the inventory (perhaps with a simple chart like that pictured above), making sure to mark the current level, the buffer, and the corresponding replenishment threshold. In my head, a process is developing… We’ll need to check the freezer inventory regularly (perhaps whenever we take food out of it), update the chart, and determine if the the threshold has been crossed. If the threshold has been crossed, then we’ll need to make more food.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*W-OBOPO4XBomD1ElxB5ZvQ.png" /></figure><p>Thinking about it a little bit more, I realize this approach actually seems… annoying. Even if I develop a nice way to visualize the inventory, there’s no way I will care enough — <em>when I’m hungry, of all times — </em>to keep it updated. I’m sure my wife will feel the same way. We’ll follow this system for a week and then drop it the moment things get busy. The design needs to be more accommodating.</p><p>Also, I think I am making everything more complicated than it needs to be; it’s time to question some assumptions. Do I <em>really </em>need to visualize inventory? Why isn’t it good enough to open the freezer and look? Why can’t I know from just one glance? I demand immediate gratification!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/233/1*ripIkyMb_WGTNdZffBG7tw.jpeg" /><figcaption>Calvin &amp; Hobbes (Bill Watterson)</figcaption></figure><p>Instead of keeping track of exact inventory and visualizing it, I really just need to develop a simple heuristic. The only thing I need to know is, “Has the replenishment threshold been crossed, yes or no?”</p><p>As it turns out, the heuristic isn’t all that hard to develop: I know one shelf in the freezer can hold 6 small containers, and about 3 containers will get us through a single day. That’s 2 days per shelf, so if we want a buffer of 3 days, then we need 1.5 shelves of food for the buffer to remain intact. I can certainly determine whether we have ~1.5 shelves of food at-a-glance!</p><p>This process feels much more intuitive, cuts out all the unnecessary busywork, and doesn’t require any disruptive change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/391/1*_1WA_32bQZq93Jbwx5B_KQ.png" /></figure><p>We still need to figure out how to signal that the threshold has been crossed, though. The nerd in me wants to program an Amazon Dash button + Lambda to send an email or calendar reminder, but I think that’s just looking for an excuse to play with cool tech. Having a simple, physical, visible reminder is probably better, so both of us can know the status just by walking by. What about a sign of some sort?</p><p>As it turns out, this is a solved problem. I can order a cheap <a href="http://a.co/duBGYCW">two-sided magnet</a>, originally designed to indicate stocking status (FULL or EMPTY). I can just throw that on the freezer!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*oH3vI7b5So7aAsAmc9a7EQ.jpeg" /><figcaption>A variety of available 2-sided magnets.</figcaption></figure><p>The problem is solved with application of theory (praxis), a heuristic, and a magnet. Despite my best efforts, I managed to not reinvent the wheel!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9278d28d80e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/buffer-management-for-meal-prepping-9278d28d80e9">Buffer Management for Meal Prepping</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Diversity]]></title>
            <link>https://medium.com/benjamin-mosior/on-diversity-ce384ee2de93?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/ce384ee2de93</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:15:28 GMT</pubDate>
            <atom:updated>2017-02-05T06:58:39.414Z</atom:updated>
            <content:encoded><![CDATA[<p>Just a few years ago, I would not have been able to articulate why organizational diversity matters. (I know that for a fact, because I once offered a barely adequate, fumbling answer during an interview. Despite somehow getting the job, I remained largely clueless for some time.)</p><p>Times change, I’ve learned some things, and now I’ll share one overly simplistic but perhaps helpful view.</p><p>If every organization needs to best-match a particular pattern to be successful…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*13uVhbjKbVnUTm2H8NKagQ.png" /></figure><p>…and the people in the organization have only homogeneous backgrounds, life experiences, identities, abilities, skills, and approaches…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/399/1*BUVkU6lQMRWrY9TqrNmYkg.png" /></figure><p>…failure or harm is inevitable.</p><p><em>Use cases will be missed. Critical flaws will be overlooked. Real people will be implicitly designed against (or not designed for).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*hr5M7lK5hyOGfEGdd2UVkA.png" /></figure><p>Diversity is one necessary component to improve how well an organization is able to match the success pattern at a point in time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*DfTElpEQY9sEpl4pIJ-wgg.png" /></figure><p>Lastly, diversity is <a href="http://www.d5coalition.org/tools/dei/">necessary but not sufficient</a> (don’t forget equity and inclusion).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce384ee2de93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/on-diversity-ce384ee2de93">On Diversity</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wardley Mapping, A PowerPoint Template]]></title>
            <link>https://medium.com/benjamin-mosior/wardley-mapping-a-powerpoint-template-8e0381a913ca?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e0381a913ca</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[template]]></category>
            <category><![CDATA[mapping]]></category>
            <category><![CDATA[wardley-mapping]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:15:03 GMT</pubDate>
            <atom:updated>2019-04-23T05:32:14.469Z</atom:updated>
            <content:encoded><![CDATA[<p>One particularly coherent approach to “strategy” involves using a map to pursue increased situational awareness from which to execute various forms of gameplay. This technique is known as Wardley Mapping, and I highly recommend reading through <a href="http://blog.gardeviance.org/2015/02/an-introduction-to-wardley-value-chain.html">An Introduction to Wardley (Value Chain) Mapping</a> and watching Simon Wardley’s 2014 OSCON keynote.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNnFeIt-uaEc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNnFeIt-uaEc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNnFeIt-uaEc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c98486eafc0957d069cd5cd1d243b595/href">https://medium.com/media/c98486eafc0957d069cd5cd1d243b595/href</a></iframe><p>I’ve been learning about and using mapping for a few months at this point, and pen/paper and whiteboarding have been my go-to methods (for good reason). I found myself eventually held back by the friction of the process, however, and embarked on a passive and meandering search for tools that might sate an impatient novice like myself. The three areas of concern were the construction of the value chain, the placement of nodes on the evolutionary axis, and the creation of a shareable artifact.</p><h4><a href="https://hiredthought.com/2016/11/14/wardley-mapping-a-powerpoint-template/">Read the rest and get the template here…</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e0381a913ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/wardley-mapping-a-powerpoint-template-8e0381a913ca">Wardley Mapping, A PowerPoint Template</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cutting Costs. Or, How to Pretend Complex is Simple.]]></title>
            <link>https://medium.com/benjamin-mosior/cutting-costs-or-how-to-pretend-complex-is-simple-db447d995a87?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/db447d995a87</guid>
            <category><![CDATA[cost]]></category>
            <category><![CDATA[cynefin-framework]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:14:51 GMT</pubDate>
            <atom:updated>2016-11-14T20:58:43.158Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published March 20, 2016</em></p><p>Suppose a company discovers that its projected revenue is below original expectations for reasons outside of its direct control. The bottom-line numbers are going to look bad, so something must be done immediately. Cost-cutting measures will be explored, and when every budget has been squeezed and nothing else remains, the company will cut people. The numbers will start to look better, and the company will appear to make it through the crisis.</p><h3>Cynefin, as always…</h3><p>The <a href="https://en.wikipedia.org/wiki/Cynefin_Framework">Cynefin Framework</a> describes a cliff between the borders of the Simple/Obvious and Chaotic domains, over which it is easy to fall and from which recovery is difficult. In short, treatment of any non-Simple/Obvious situation as if it is Simple/Obvious will result in this fall. To wield cost-cutting as a best-practice (a Simple/Obvious approach) for a bottom-line problem (a Complex issue), therefore, is to confuse Complex for Simple/Obvious and to cause a fall into the Chaotic.</p><p>From the <a href="https://en.wikipedia.org/wiki/Cynefin_Framework">wikipedia article</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*OG6Jn1fXlCW2BkENzfP7fA.png" /></figure><h3>Bottom line as Complex</h3><p>Theory of Constraints thinking approaches the bottom line as an ordered (Complicated) problem, analyzing <a href="http://www.dbrmfg.co.nz/Bottom%20Line.htm">the outcome of increased productivity</a> or even <a href="https://www.youtube.com/watch?v=jU2iWZEYbKA">deliberate inaction</a> to that of cost-cutting (and layoffs). The mere existence of alternatives satisfies the assertion that the problem domain is not Simple/Obvious (no single best practice). For the bottom line to be Complicated, however, it must be completely knowable and predictable through analysis. The many unpredictable elements in the equation (influenced by humans, in particular) prevent that conclusion from being reached.</p><p>The bottom line is likely in the Complex domain, because the relationship between cause and effect is not predictable. The company cannot make any change to the system or its actors while fully predicting the consequences. True, layoffs will immediately influence the bottom line — the numbers will add up to a different result — but the reduction in organizational capacity, loss of tacit knowledge, and effect on morale will have an unpredictable impact. Lack of predictability indicates membership to an unordered domain (Complex or Chaotic), and we can retrospectively explain cause and effect (i.e., looking back, these various factors contributed to the loss in revenue and therefore the bottom line). The bottom line is Complex.</p><h3>Descent into the Chaotic</h3><p>Per the notion of the cliff, cost-cutting measures applied as a Simple/Obvious solution in a non-Simple/Obvious space will cause the company to temporarily enter the Chaotic domain. Company leadership will have to will act authoritatively to recover to a more comfortable ontological domain, but costs in terms of effectiveness, morale, and so on will be high. The bottom line may be negatively affected over the long term by reduced organizational capacity, driving the company into a spiral of further cost reduction measures unless otherwise prevented.</p><p>Prevention is rooted in understanding. Approaching the problem as it is, a member of the Complex domain, might enable a more favorable outcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db447d995a87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/cutting-costs-or-how-to-pretend-complex-is-simple-db447d995a87">Cutting Costs. Or, How to Pretend Complex is Simple.</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cynefin, Culture Change as Complex]]></title>
            <link>https://medium.com/benjamin-mosior/cynefin-culture-change-as-complex-78e1d1c09fe3?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/78e1d1c09fe3</guid>
            <category><![CDATA[culture-change]]></category>
            <category><![CDATA[cynefin-framework]]></category>
            <category><![CDATA[complexity]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:14:41 GMT</pubDate>
            <atom:updated>2017-02-03T21:27:57.501Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published February 27, 2016</em></p><p>The Cynefin framework (created by Dave Snowden) reveals that Complicated or Simple approaches break down and can only succeed <em>by complete accident</em> in the Complex domain, because causality is only clear in retrospect. From this basis, let’s briefly refute the notion of culture change as Simple or Complicated.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FN7oz366X0-8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DN7oz366X0-8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FN7oz366X0-8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/045706cbbcfb50ebcad30a1ef2de33b3/href">https://medium.com/media/045706cbbcfb50ebcad30a1ef2de33b3/href</a></iframe><p>If you are new to the Cynefin framework, I recommend watching the above before reading through the rest of this post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9gszJqu2Ia2ws16fAo0wqA.jpeg" /></figure><h3>Culture as Simple</h3><p>The Simple domain has obvious, predictable cause-effect relationships. We can sense the situation, pattern-match to categorize it, and respond with the best practice.</p><p>The dominant management theory “best practice” for culture change is the manipulation of incentives. <a href="https://www.youtube.com/watch?v=u6XAPnuFjJc">People are not endlessly manipulable or predictable</a>, however, and incentives are <a href="https://en.wikipedia.org/wiki/Transformation_of_culture">not the only path to culture change</a>, so the notion of “best practice” is incorrect. We also know from the vastness of fields of study such as <a href="https://en.wikipedia.org/wiki/Anthropology">Anthropology</a> that humanity and culture are not “obvious” concepts. Culture is not Simple.</p><h3>Culture as Complicated</h3><p>The Complicated domain has cause-effect relationships, but they are not immediately obvious. We can sense the situation, perform analysis or bring in experts, and respond with one or more good practices.</p><p>The standard procedure for companies aiming to holistically change culture involves hiring expert consultants to analyze the current culture, define a desired future state, and provide “good practice” to drive towards it. We know from experience, however, that the disposition of the workforce or the company might prevent otherwise good tactics, even those that have succeeded at countless other companies, from working again.</p><p>Consider all the variables that might derail a given solution, including untimely personnel changes, life-changing events for critical people, unrelated shifts in individual attitudes, and distracting business crises. These types of events are numerous and completely out of the control of any company or consultant. No ordered model can adequately accommodate every single possibility, therefore complicated solutions are simply too generic and ill-fitting for a particular company at a particular point in time. Culture is not Complicated.</p><p>As an aside, the counter to systemic rejection of forced change seems to be centered on wearing down the will of the workforce so that it might be too weary to care, which is simply harmful. Worse still, success might be declared after enough people leave and their replacements assimilate into the changed culture.</p><h3>Final words</h3><p>Culture change lacks causality, except in retrospect; it is Complex. We can probe the situation with safe-to-fail experiments, sense the effects, and respond with amplification or dampening strategies to safely contain failure and discover emergent practice. In short, we can quickly evolve from successful experiments and safely abandon those that fail. The granularity of this approach enables the development of solutions that truly fit the organization.</p><blockquote><em>“Culture arises from actions in the world, ways of doing things which may never be articulated, and which may not be capable of articulation. In effect culture is always complex, never complicated. So it follows that cultural change is an evolutionary process from the present, not an idealized future state design.”<br> — Dave Snowden (</em><a href="http://cognitive-edge.com/blog/omg-they-want-to-change-the-culture/"><em>OMG, its culture change time</em></a><em>)</em></blockquote><p>Originally, I ended this post with an intent to explore the validity of Cynefin:</p><blockquote>Upcoming challenges for me include proving why Cynefin is an appropriate framework for deciding how to approach culture change (intuition is not sufficient, and this exploration has admittedly been out of order), as well as investigating data collection and experiment design in the Complex domain.</blockquote><p>As of June 25, 2016, I’ll amended the post with the following;</p><p>Cynefin is one of many sense-making frameworks. It makes little sense to use just one or attempt to prove that one is better than the other. If more sense is made through the use of a framework, then it fulfills its purpose; keep using it. More importantly, use others as well to increase the diversity of the potential sense that is made.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78e1d1c09fe3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/cynefin-culture-change-as-complex-78e1d1c09fe3">Cynefin, Culture Change as Complex</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Motivation Cycles]]></title>
            <link>https://medium.com/benjamin-mosior/motivation-cycles-78e4b22775ff?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/78e4b22775ff</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[cynefin-framework]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:14:32 GMT</pubDate>
            <atom:updated>2016-11-14T20:51:31.194Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published February 24, 2016</em></p><blockquote>You could find the Abstract listening to hip hop<br>My pops used to say, it reminded him of Bebop<br>I said, well daddy don’t you know that things go in cycles<br>Way that Bobby Brown is just amping like Michael<br> — <a href="https://en.wikipedia.org/wiki/The_Low_End_Theory">Excursions (A Tribe Called Quest)</a></blockquote><p>I work in a challenging environment where the effects of improvement efforts are only perceivable in retrospect over quite some time. It is one thing to state that improvement has occurred, even to cite specific examples as evidence, and something else altogether to vividly experience the difference. (We humans tend to recalibrate our expectations frequently based on current circumstance, but our perception often misses the quiet signals of small changes over time).</p><p>One way or another, the circumstance has led me to notice that motivation waxes and wanes in a somewhat cyclical pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*FuPPW8uNzvWmonI32xJaEA.jpeg" /></figure><p>Objectively, a motivation model being cyclical is not problematic, as long as some degree of positive learning or other progress can be observed along the way. I’m not yet sure if “learning” is the right way to describe it, though, or if there should even be a linear measure of it in the first place. It seems that a cycle can enable a new level of <em>something</em>, be it fundamental understanding, existence, or maybe happiness.</p><p>Assuming the <em>something</em> is positive, I’d want to exploit such a model to maximize the movement in a positive direction (i.e., towards periods of high motivation) while minimizing the opposite.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*ZvG_ySFtWOxqMoDBAlk4Og.jpeg" /></figure><p>The problem is that these cycles can vary in severity, length, and frequency, but no cause will be immediately apparent, except in retrospect. In other words, motivation is complex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*IHIg6N4FM4e0uQv6W-hNIA.jpeg" /></figure><p>Complexity isn’t a reason to give up. Rather, <a href="https://en.wikipedia.org/wiki/Cynefin_Framework">operating within a complex space necessitates deliberate experimentation</a>. The key is to amplify the effects of good experiment results and dampen those of poor ones.</p><p>Recognition of the cyclical nature of motivation enables certain awarenesses. For example, what does a series of motivation cycles without positive movement in learning or improvement or that <em>something</em> indicate?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*rjQUol2YhnLueeNE3tHjLQ.jpeg" /></figure><p>All I know is that I do not want to be there, so I thought I might try something to disrupt the cycle when it’s not in my favor. What is the effect on the motivation cycle if I take a break from work for a period of time (e.g., take a vacation day) whenever there’s a trend towards “unmotivated,” for example? If the effect is positive, then it can be amplified by more deliberately planning for such opportunities in the future. If the effect is negative, it can be dampened by doubling down on involvement in order to restabilize the situation or by pursuing other activities within the context already known to be motivating.</p><p>I ran a few tests, and sometimes found myself recovering by the following day (trending towards “motivated”). Other times, it was a less effective treatment, but it might have kept the dive a shallow one. I can’t know for certain. The experience leads me to believe that disrupting the cycle has value, but a more fundamental change might be necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*L6bLBeF9Rjo6UZvV2-LQkw.jpeg" /></figure><p>Other pursuits may have longer cycle times skewed in favor of motivation; I’ve experienced them before. Their discovery is not deterministic and viability not guaranteed, though, so here I am. More on that in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78e4b22775ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/motivation-cycles-78e4b22775ff">Motivation Cycles</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual WIP]]></title>
            <link>https://medium.com/benjamin-mosior/visual-wip-429156e74832?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/429156e74832</guid>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[wip]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:14:22 GMT</pubDate>
            <atom:updated>2016-11-14T20:48:00.803Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published February 21, 2016</em></p><p>I have been searching for a temporary work visualization method to adequately convey both how a given process works and the WIP (Work In Progress) within it at any given moment. With eventual improvement set as a goal for the former, a prerequisite for any productive discussion is a common understanding from which to work. For the latter, understanding WIP prevents us from making a bad process worse and allows us to free up capacity to improve.</p><p>Kanban seemed like something to try, but I realized I was considering only the information Kanban provides and not the functional purpose it is intended to fulfill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*584Z6ZAtp6UmoUmrUmQ1Hw.jpeg" /><figcaption>Work In-Progress, visualized as a Kanban board.</figcaption></figure><p>More specifically, an organization addicted to <em>pushing</em> work through the system will probably fail to adequately control the release of work, allowing for further inventory buildup between steps. Only simplistic bottlenecks on individual steps will be apparent, and representation of a nonlinear flow in terms of system constraints isn’t accounted for (i.e., one particular step performed at one particular station precludes the ability of a different step at that same station to be performed).</p><p>I considered a value stream map next, but the detail of a fully-formed VSM would only serve as a barrier to common understanding and is not meant to represent WIP. Hence, consideration of a stateful, simplified form:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*CNnAtKAaoqMK-2hLcUP8ow.jpeg" /><figcaption>Work In-Progress visualized as a box-and-wire diagram acknowledging both dependency and bidirectionality.</figcaption></figure><p>This visualization steals a bit from Critical Chain concepts by acknowledging the utilization and occupation of individual resources, conveying circumstances where a resource (or a person) might be busy with another step of the process, such as with Workstation A above with the work from Workstation C piling up in front of it. A diagram like this can serve as a temporary means for establishing common understanding of the process and the work flowing through it, and it becomes more clear how limiting the release of work can offer improvement in flow and the opportunity to catch our breath enough to improve the process itself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=429156e74832" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/visual-wip-429156e74832">Visual WIP</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Four Questions]]></title>
            <link>https://medium.com/benjamin-mosior/the-four-questions-15f93a16e41?source=rss----67d1910768eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/15f93a16e41</guid>
            <category><![CDATA[change]]></category>
            <category><![CDATA[theory-of-constraints]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ben Mosior]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 02:14:12 GMT</pubDate>
            <atom:updated>2015-08-13T06:44:12.773Z</atom:updated>
            <content:encoded><![CDATA[<p>Dr. Eliyahu M. Goldratt, in his lecture titled <a href="http://www.amazon.com/Beyond-Goal-Theory-Constraints/dp/B000ELJ9NO"><em>Beyond the Goal: Theory of Constraints</em></a>, describes the necessity of answering the following questions when adopting a technology:</p><ol><li>What is the power of the technology?</li><li>What limitation does it diminish?</li><li>What rules helped us accommodate the limitation?</li><li>What rules should we use now?</li></ol><p>As a cofounder of a small software development business, I thought it would be interesting to describe how we applied this approach to a technology-oriented decision.</p><p>Several months ago, we developed a business process application for one of our clients, making use of Node.js and a relatively new framework (stop laughing). As the market shifted, so did the client’s business needs and goals, and we built out new features or adjusted previous ones to accommodate. However, we began to feel that our design and development process, as it pertained to the technologies we were using, had become a severe limitation. As we started planning the next major version of the application, we decided to make some changes. One of our cofounders had been looking into Laravel, a relatively stable PHP framework (it has an LTS release). I had worked with it successfully in the past, and we decided it was worth another visit. In order to more fully understand whether it was a worthwhile change, we answered Goldratt’s four questions.</p><p><strong>First, what is the power of the new technology?</strong></p><p>Simply put, PHP and Laravel are very mature and operate within a healthier ecosystem (support-wise). Resources like <a href="https://laracasts.com/">Laracasts.com</a> offer education on topics of varied complexity, and tools like <a href="http://laravel.com/docs/5.1/homestead">Homestead</a> take a lot of the guesswork out of local development environments. Laravel itself has a number of out-of-the-box features we’ve been missing in the other framework, including queueing, encryption, and payment management.</p><p><strong>Second, what limitations does it diminish?</strong></p><p>The skills required to be effective as a PHP developer are generally less specialized and more accessible for our team, which increases each member’s potential contributive ability and enables us to hire employees from a larger, more diverse pool of candidates.</p><p>Testing practices with Laravel are well-documented and inherent, whereas the amount of work involved to effectively test in our other circumstance was painful.</p><p>We had been constraining our schema and query design to a less-effective ORM, but Laravel’s Eloquent ORM resolves each of our specific problems.</p><p>We can also have much more choice with our supporting tools, including the ability to utilize a fully-featured IDE.</p><p><strong>Third, what rules helped us accommodate the limitations?</strong></p><p>We performed very involved manual testing prior to a deployment.</p><p>Starting development on any given day involved spending several minutes to provision local infrastructure in a specific and error-prone way.</p><p>Error handling and logging in the application had to be done in a specific (roundabout and inefficient) manner.</p><p>Our data structures were designed according to the limitations of the less-capable ORM.</p><p>Batch processes had to be used because setting up appropriate event-driven mechanisms were too effort-intensive.</p><p><strong>Fourth, what rules should we use with the technologies being evaluated?</strong></p><p>We should write tests that cover areas of concern and make use of continuous integration to improve confidence in deployments.</p><p>The process for development setup should minimize the amount of infrastructure and setup involved.</p><p>Exception handling, logging, and collection should be inherent to the system and easy to use.</p><p>Data structures should be designed according to logical relationships and proven approaches, not arbitrary limitations.</p><p>Events and queuing should drive application behavior and data processing.</p><blockquote>“Technology can bring benefits if, and only if, it diminishes a limitation.”<em> — Dr. Eliyahu M. Goldratt</em></blockquote><p>When reality has been defined a specific way for any extended period of time, it becomes an assumption in the minds of those involved. The most difficult thing then about any change is comprehensively adjusting surrounding behavior, which has had the opportunity to evolve to accommodate that assumption and persist in subconscious process. We find it to be true that, as humans, we won’t always make good decisions about a technology by comparing a feature list or discussing supposed “benefits”. Rather, we must additionally map the technology back to behavior and make a determination based on the full context. Goldratt’s four questions helped us get closer to that goal, and they can help you do the same.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15f93a16e41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/benjamin-mosior/the-four-questions-15f93a16e41">The Four Questions</a> was originally published in <a href="https://medium.com/benjamin-mosior">Benjamin Mosior</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>