<?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 Kip Armstrong on Medium]]></title>
        <description><![CDATA[Stories by Kip Armstrong on Medium]]></description>
        <link>https://medium.com/@kip.armstrong?source=rss-e80865cf9607------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6iF2Pk1YYk8hUjoX.</url>
            <title>Stories by Kip Armstrong on Medium</title>
            <link>https://medium.com/@kip.armstrong?source=rss-e80865cf9607------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:15:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kip.armstrong/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[From Player to Pawn? One Engineer’s Perspective (Part 3)]]></title>
            <link>https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-part-3-bb7aa79761c0?source=rss-e80865cf9607------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb7aa79761c0</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[autonomy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Kip Armstrong]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 14:35:17 GMT</pubDate>
            <atom:updated>2018-08-22T14:59:23.990Z</atom:updated>
            <content:encoded><![CDATA[<p>In <a href="https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-part-2-c72c0ddac2b4">Part 2</a> of this series I shared my experience going from highly motivated and engaged to discouraged and unengaged. In doing so I focused only on negative events (which really was not enjoyable). That doesn’t mean that there haven’t been plenty of positive experiences along the way as well, and chances for improvement are never far away.</p><p>In this third and final installment, I will discuss my thoughts on how with just a few minor changes I could return to feeling like a “player” rather than a “pawn”. This isn’t meant to be a description of how every team should work, but simply a description of how I’d like a team to work.</p><h3>There and Back Again</h3><p>Let’s begin by reviewing the four things that made me feel like a “player”:</p><ol><li>The feeling that what I’m working on is important and impactful</li><li>Meeting and talking with the people who my work will help</li><li>Decisions being made openly based off information gathered from and visible to all involved parties.</li><li>A sense of freedom and autonomy to solve problems and make decisions within requirements.</li></ol><p>And the four things that made me feel like a “pawn”:</p><ol><li>Feeling like I don’t have the big picture of how everything I’m working on fits together and why it is important.</li><li>Feeling too far removed from the people I’m helping.</li><li>Feeling like I have little or no insight into how decisions are made and feeling like not all involved parties are considered in the decision.</li><li>Feeling unable to take initiative or make autonomous decisions without prior approval.</li></ol><p>Next I’ll look at each pair together and discuss how I might transition from “pawn” back to “player”.</p><h3>Was Blind But Now I See</h3><p><em>Feeling like I don’t have the big picture of how everything I’m working on fits together and why it is important</em> -&gt; <strong>The feeling that what I’m working on is important and impactful</strong></p><p>I think this is actually a fairly simple one to solve. In truth I’ve already started to see progress on my team in this area. My company has recently embraced the concept of OKRs¹ and my team has defined ours for the remainder of the year. Although I didn’t feel as if I had an opportunity to help define what those are, I did have a chance to review them and give feedback and they seem appropriate to me. Simply having those defined will help me understand the bigger picture as I’m looking at the day to day issues.</p><p>Moving forward I hope that my team can discuss OKRs together before they are officially determined and go over the reasons why they are important for the business or customers. I also believe creating a list of “someday” goals for the product would help me see the big picture and feel inspired. Even if those things aren’t high priority right now, knowing where we hope to get someday can provide a reference when making decisions for the short term.</p><h3>The Power of the People</h3><p><em>Feeling too far removed from the people I’m helping -&gt; </em><strong>Meeting and talking with the people who my work will help</strong></p><p>This one may be fairly straightforward as well. Members of my team have recently suggested we follow a process called “Directed Discovery”. On searching to figure out what that means I found <a href="https://www.pluralsight.com/blog/career/product-development-directed-discovery">this</a>. From that article:</p><blockquote>We use<a href="https://hbr.org/2009/03/ethnographic-research-a-key-to-strategy"> ethnographic techniques</a>, which means we try to understand how people live their lives and interact with our product from their point of view, not ours … Developers are all part of the ethnographic research with product experience manager (PXM) and UX design in daily work — or they should be.</blockquote><p>I like the sound of that. I recently had a few opportunities to meet with customers and participate in a “Customer Preference Test”. I found these meetings both insightful and motivational. One of the people I met with was so enthusiastic about our product I left the discussion wanting to go build everything he’d suggested right away just to return the love. If I were to continue to have regular contact with users both inside and outside of my organization, I believe it would not be long before I again start to feel that connection and sense of purpose that I am helping people rather than the feeling I’m just building things to check things off a list.</p><h3>The Truth Shall Set You Free</h3><p><em>Feeling like I have little or no insight into how decisions are made and feeling like not all involved parties are considered in the decision -&gt; </em><strong>Decisions being made openly based off information gathered from and visible to all involved parties</strong></p><p>This one is not quite as simple. On a large product with a lot of customers it isn’t always feasible (or perhaps even desirable) to include every team member in every discussion. That being said, I don’t see any reason why every team member shouldn’t be informed of the results of discussions they aren’t involved in and given an opportunity to comment.</p><p>One way to do this would be an asynchronous communication tool like Slack. In my previous posts I mentioned a “Core Workflow Collaboration” channel where I could go to ask questions and share information with the various people that would be consuming my product. This generally led to open discussions where everyone could come to a consensus on what the right to do was and why. I hope to see more of these channels created for having these types of discussions².</p><p>Additionally, I would love to see more communication about impromptu discussions or decisions that are made. It could be as simple as posting a message to the team saying “I talked with so and so and I think we’re going to do X — does anyone have any concerns with that?” or “I recently met with customer X and it turns out we need to move in a different direction on feature Y — let’s discuss.”</p><p>I’m a big fan of communication in print for several reasons. In addition to providing information to those not involved in the discussion, it forces you to slow down and solidify your thoughts. Often something seems perfect in my head, but when I start to write it down I suddenly see issues. Recording thoughts and decisions also allows those involved in the discussion to make sure everyone gathered the same meaning from the discussion. I’ve often left a discussion with someone thinking we agreed on something only to later learn they had a completely different understanding. Recording the decision allows people to say “whoa — that’s not at all how I understood our discussion.” Finally, recording results of discussions provides a history so that the same discussions don’t have to happen over and over again. A history also prevents common phrases such as “I don’t remember agreeing to that” or “that’s not what we said we were going to do”.</p><p>In short, if more communication was done openly and everyone on my team (myself included) were to better communicate the results of major discussions that don’t happen openly, I believe I would soon feel again as if I was part of a team rather than a cog in a machine, only learning things on a “need to know basis”.</p><h3>Don’t Tread on Me</h3><p><em>Feeling unable to take initiative or make autonomous decisions without prior approval</em> -&gt; <strong>A sense of freedom and autonomy to solve problems and make decisions within requirements</strong></p><p>At first glance this seems to be a daunting challenge. How does a team strike a balance between making sure everyone feels autonomous while also making sure everyone isn’t moving in different directions and doing whatever they feel like? The answer, I believe, may actually be all the things I’ve already discussed above. If I feel a sense of purpose in the mission of my team, connected to the people who will use the product, and informed and included in discussions and decisions that take place, it should lead to a natural consensus of what the “right thing” to do is.</p><p>If I have all the same information as everyone else on the team I believe conversations like “don’t work on that — do this instead” and “why are you doing that thing you’re not supposed to be doing” will almost completely disappear because I will already be aligned with the direction we’re moving. On the occasions where disagreements do come up, I can have an open discussion based off the same information everyone else has and come to a mutual decision. Even if I still don’t agree at that point, I can still disagree and commit without feeling like I’ve given up my freedom and autonomy because I won’t feel as if the decision was already made without my knowledge and I’m just now being informed of it with no real opportunity to question it.</p><h3>Conclusion</h3><p>In the previous two articles I discussed how in a relatively short period of time I went from feeling like an excited an engaged “player” to a unmotivated “pawn”. For a time I believed that was just how things were and there was no real hope for change. However, now that I’ve pinpointed the causes of my concerns and looked at potential solutions I’m cautiously optimistic that I may not be as far as originally thought from going back to feeling like a “player” again. With eyes to the future I can only hope that down the road I can add a part 4 to this series entitled “From Pawn to Player — How I Got My Groove Back”.</p><h4>Footnotes</h4><p>1 See <a href="https://weekdone.com/resources/objectives-key-results">https://weekdone.com/resources/objectives-key-results</a></p><p>2 Since writing the first draft of this article I’ve already seen this start to happen on my team and I am loving it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb7aa79761c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Player to Pawn? One Engineer’s Perspective (Part 2)]]></title>
            <link>https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-part-2-c72c0ddac2b4?source=rss-e80865cf9607------2</link>
            <guid isPermaLink="false">https://medium.com/p/c72c0ddac2b4</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Kip Armstrong]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 18:48:36 GMT</pubDate>
            <atom:updated>2018-08-22T14:37:53.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPNFOviLrqZKVNj_EM6utw.jpeg" /></figure><p>In <a href="https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-83696fb7f66f">Part 1</a> of this series I shared my experience feeling extremely motivated and engaged while working on a project to build a new workflow engine. Reflecting on that experience I discover four things¹ I pointed out in the last article that I discovered to be important for me to feel motivated and inspired:</p><ol><li>The feeling that what I’m working on is important and impactful</li><li>Meeting and talking with the people who my work will help</li><li>Decisions being made openly based off information gathered from and visible to all involved parties.</li><li>A sense of freedom and autonomy to solve problems and make decisions within requirements.</li></ol><p>In this article, I will discuss how changing circumstances led me to feel less motivated and engaged, in an attempt to understand what it means for me to feel like a “pawn”.</p><h3>One For All and All For One</h3><p>During the time I had been working on the new workflow engine, I was technically still on the team that would be utilizing the engine and not the team actually responsible for building it. The engine is meant to be used by a number of company products, so it seemed appropriate when I was asked to join the actual workflow team. The plan was to help build out the engine for all of these products once we’d completed the requirements for my old team’s product.</p><p>In the previous post I discussed a promise I’d made to our customers that I would do everything in my power to make the new workflow engine a positive experience for them. I soon learned however that we really only had the time to add the features needed for one of these customers, due to the pressing needs of other products. To be fair, this one customer was funding the entire project, so we really had no obligation to help any of the other customers. Nevertheless it was still a disappointment to learn that there would be no way for me to fulfill my promise to help all of the customer in the foreseeable future. First conclusion:</p><ol><li><strong><em>I no longer felt the same connection and inspiration to the mission I was working toward and the people I was helping.</em></strong></li></ol><p>I was still determined to meet the needs of the one customer and I think, in my heart, I hoped that maybe if I worked hard enough I could still find time to complete some of the things needed by the others.</p><p>In truth, I didn’t necessarily even believe that only focusing on one customer was the wrong decision. I understood that the place where we could make the biggest impact might actually be in helping these other products. However, because I didn’t have that same connection with the other products and their customers, I couldn’t find that same level of motivation and excitement to help them.</p><h3>Autonomy or Automaton?</h3><p><em>Before proceeding I should emphasize that the following examples are not meant to condemn or criticize the people I work with, but are an attempt to understand and explain how I felt.</em></p><p>Soon after joining the workflow team I found that suddenly people were a lot more interested in the details of what I was working on. That by itself wasn’t a concern (I like to show off my work) but in time I started to feel over-scrutinized.</p><p>Early on I was publicly reprimanded for forgetting to test a specific use case before pushing a change to production. On multiple occasions I posted in Slack saying “FYI, I finished my current task — I’m going to work on X next” and was asked “actually can you work on Y instead?”. Another time I reported I had spent part of a day helping a colleague come up to speed on a workflow issue. I was warned that if I helped every engineer that asked for assistance, my work life might end up a “living hell”.</p><p>By themselves these weren’t major issues, but added up they were starting to make me uncomfortable. In the past these situations would have been handled differently. I would have noticed that I missed testing something and quickly rectified the situation with little fuss. I was accustomed to having the entire set of requirements in front of me and would simply pick up the next thing with little need for discussion. When others came to me for help, I would assist them if I felt like it was the right thing for the project, and ask them to get their request prioritized through the Product Manager if I wasn’t sure.</p><p>To be fair, I never felt like I was being ordered to do or not do anything and I always felt like the intent of the feedback was good. Nevertheless I started to feel like every action I took or decision I made was being analyzed and questioned. These occurrences were frequent enough that I reached the point where I found myself often paralyzed by indecision. I would go to make a decision or start on something and question whether it was right. I knew what I thought was right, but I constantly worried that it might not be what others wanted me to do.</p><p>In time I found it easier to stop making decisions and wait for them to be made for me. This definitely eased the stress of conflict, but left me feeling a little hollow and uninspired. Next conclusion:</p><p><strong>2.<em> I no longer felt free to act or make decisions without first seeking approval.</em></strong></p><p>Previously I felt that I’d been given a huge amount of trust and freedom act autonomously and make decisions. That inspired me to work hard and take accountability for my decisions to live up to that trust. I also wanted to communicate those decisions as much as possible to others to make sure they were the right ones. Now I felt untrusted and unengaged. I was even tempted at times to communicate as little as possible about what I was working on so as to avoid conflict.</p><h3>You Can’t Handle the Truth!</h3><p>In the previous post, I discussed meeting with coworkers and customers to gather information and working with my Product Manager to build a prioritized list of requirements. Before joining the workflow team that list had been my “source of truth” for knowing what to do. However, that list belonged to my old team so it made sense that on my new team I would have a new “source of truth”.</p><p>I assumed that this new requirements list would simply be fed from my old requirements list and for a time that was true. After a while though I started to see requirements I didn’t recognize appear and requirements I had thought to be important disappear from the list. When inquiring about these differences, I usually discovered the change had come from a discussion that I had been unaware had taken place.</p><p>I also mentioned in my previous post that a “Core Workflow Collaboration” channel had been created. In this channel I could post questions for the community of products to discuss together. At some point this channel was removed and I no longer knew where to go to solicit feedback and generate discussion among the community of products. Instead I just pushed my questions “up the chain” and waited for answers to come back “down the chain”.</p><p>I think part of the issue was that before I was basically a team of one and now I was on a larger team. I understood that on a larger team not everyone could be involved in every discussion, but I couldn’t help but feel like I no longer had any insight or input into discussions that were taking place or decisions that were being made. At one point I described the feeling to someone as “having my baby taken away by the state and having infrequent visitation rights”.</p><p>On occasion I felt strongly enough about a decision that I voiced my opinion against it. Whether it was the intended message or not, I usually felt like the response was “The necessary parties have discussed this and the decision has already been made.”</p><p>Perhaps the largest example was a decision to redesign the UI. Simplifying the UI is something that had been hotly debated, even before I switched teams. My feeling was that the solution was to iterate on what we already had over time. Therefore I was disappointed when I learned that a UI redesign had been decided on, and that in order to accomplish the work we would need to double the team size only months before the project deadline. The disappointment didn’t really come from the fact that I disagreed with the decision, but rather that I was unsure of how the decision was reached and I wasn’t certain if all consequences of this decision had been considered. Furthermore, adding more people to the team only made me feel more distant from conversations that were taking place and decisions that were being made. Final conclusion:</p><p><strong><em>3. I no longer felt like I had any insight or input into decisions that were being made.</em></strong></p><p>It is entirely possible that every decision I disagreed with was actually the right one, but by not having insight into how decisions were made it was difficult for me to understand why.</p><h3>Conclusion</h3><p>As I reflect on these circumstances these are the things I believe make me feel like a “pawn”:</p><ol><li>Feeling like I don’t have the big picture of how everything I’m working on fits together and why it is important.</li><li>Feeling too far removed from the people I’m helping.</li><li>Feeling like I have little or no insight into how decisions are made and feeling like not all involved parties are considered in the decision.</li><li>Feeling unable to take initiative or make autonomous decisions without prior approval.</li></ol><h3>But wait, there’s more!</h3><p>I just couldn’t leave this discussion on a down note. Besides, what good does it do to present problems and no solutions? In the <a href="https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-part-3-bb7aa79761c0">third and final part</a> of this series I’ll discuss potential ways that I might be able to go “from Pawn back to Player”.</p><h4>Footnotes:</h4><p>1 Since publishing the first part of this series, several people have pointed out to me that there is a popular book entitled <em>Drive: The Surprising Truth About What Motivates Us</em> that focuses on several of the very things I’ve discovered about myself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c72c0ddac2b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Player to Pawn? One Engineer’s Perspective. (Part 1)]]></title>
            <link>https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-83696fb7f66f?source=rss-e80865cf9607------2</link>
            <guid isPermaLink="false">https://medium.com/p/83696fb7f66f</guid>
            <category><![CDATA[squad-health-check]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Kip Armstrong]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 03:52:53 GMT</pubDate>
            <atom:updated>2018-08-09T21:08:56.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*KtzzCSsnG-2ef336ocp6fw.jpeg" /></figure><p>My company has recently started using Spotify’s <a href="https://labs.spotify.com/2014/09/16/squad-health-check-model/">Squad Health Check</a> to track team health. One of the questions a team asks themselves is “Do you feel like a player or a pawn?” Recently I’ve been feeling much more like the latter of the two, but it hasn’t always been that way. Following are my thoughts on how in just a few months I went from feeling like a player on a team to little more than a cog in a machine. These are simply my feelings and opinions — it is not my intent to layout how I believe every team should work, but rather the way I like a team to work. I wouldn’t be surprised to learn that other engineers share some of my views though.</p><p>In order to understand what it means for me to feel like a “player” on a team let’s go back to a year ago and follow my journey from “player” to “pawn”.</p><h3>The Mission</h3><p>A year ago I had been working on one of my company’s products that required extensive use of a Workflow engine. I don’t need to go into details, but suffice it to say that the thing was a mess. Proposals would inexplicably get stuck in workflow with no way of knowing how it got that way or how to get it unstuck. Other proposals would somehow skip right through the remaining workflow steps and go straight to a published state. Customers were frustrated and engineers baffled. It will come as no surprise then that when I was approached and asked to help the company’s Core Engineering team build out the new Workflow tool to replace the existing solution, it took no convincing for me to hop on board with enthusiasm for the task ahead. This leads me to my first conclusion:</p><ol><li><strong><em>For me it is important to understand and feel that what I’m working on is valuable and will have a major impact to the company or its customers.</em></strong></li></ol><h3>The People</h3><p>Not long after I started working towards getting the new Workflow to where it needed to be for my team’s product, I was asked to assist with a presentation on the upcoming Workflow tool at a company conference where many of that product’s customers were present. It sounds cheesy, but honestly during this presentation I looked into the faces of these people and thought I saw reflected there the frustrations of the past as well as the hope and anticipation of a better future. Talking with them inspired in me a desire to make that future a reality for them. I stood in front of them and expressed my sorrow and sympathy for the challenges the old workflow engine had caused them and pledged that I would do everything in my power to ensure that the new Workflow engine would be an immensely more positive experience for them. I left that conference determined to make the Workflow tool everything these people wanted and needed. Second conclusion:</p><p>2. <strong><em>When I actually meet and talk with the people who will be using my work it humanizes them for me and I feel inspired to make them happy.</em></strong></p><h3>The Plan</h3><p>Sometime around this same time period we were asked to perform a Gap Analysis between the product’s workflow needs and the existing functionality in the new Workflow engine. We started by holding a meeting with members of my team that were most involved with dealing with issues in our current workflow solution. This included the Implementation Manager, the Support Manager, the Product Manager, and myself. We brainstormed everything we could think of that our current workflow solution did or that had ever been suggested it could or should do. Nothing was off the table. Then over the course of the next several weeks we met with someone from each of our clients and allowed them to also share ideas on what they’d like to see from Workflow, while making it clear that this was brainstorming and not requirements gathering. I also showed each of them what their Workflow might look like in the new tool in order to give them an idea of what was coming, as well as an opportunity to offer feedback. In the end, we had a spreadsheet with hundreds of requirements that we had all discussed together.</p><p>The Product Manager, Implementation Manager, and I each gave what we thought was an appropriate priority to each of these requirements. The Product Manager took that information and separated the requirements into High, Medium, and Low priority buckets. It didn’t bother me one bit that the Product Manager had the “final say” in what was High, Medium, or Low because I felt like the decision was made with all of the relevant information and input. In the few instances that I disagreed with a prioritization, a respectful discussion usually followed in which we both left agreeing on an appropriate priority¹. After this exercise I was more invigorated than ever. I’d already had the motivation and now I had the direction — and more important — I felt like it was the <strong>right</strong> direction. Third conclusion:</p><p><strong><em>3 It is important for me to feel like decisions on direction are made based on information gathered from all involved parties — particularly customers, engineers, and UX (User Experience) people.</em></strong></p><p>Who makes the decision is not as important to me as how the decision is reached. This doesn’t mean I believe in decision by committee, but I do believe that in almost every case, everyone involved should understand why a decision is being made. In those cases where the person who makes the final decision goes against the suggestions of one or more of those involved, they should accept accountability for the consequences of that decision and everyone should commit to doing everything they can to make the decision work, even if they don’t agree with it.</p><h3>The Journey</h3><p>With the requirements broken into priority buckets we then organized them into two week sprints based on prerequisites and logical order. We did high level estimates and I was on my way. I found this incredibly motivating because I knew not only what I should be working on this week, but every week right up until the project deadline. Of course the plan changed over time — we moved things forward or backward in priority or even dropped them completely but the changes felt natural and logical and never happened without some sort of group discussion ahead of time. During this time period I was specifically asked by a fellow engineer — “don’t you feel like our company wants engineers to be pawns rather than players?“ and I replied without hesitation “not at all — I totally feel like a player.”</p><p>I think it’s also useful to note that when later attempting to describe to others how happy I was during this period I told them “I was just doin’ my thing” which I think may have mistakenly conveyed the message that I was “off in the weeds working on whatever I felt like without any collaboration or oversight.” While it may seem that I had an abnormal level of autonomy and minimal supervision during this time period, I made sure to report in Slack every day what I was currently working on so that anyone interested could be aware of what was going on². I also kept the status of the JIRA tickets associated with my work up to date and added new JIRA tickets when necessary (informing the PM when doing so). When major technical decisions were needed I would consult the other engineer assigned to the project and we never failed to come to a solution we both felt was appropriate. Halfway through this phase a “Core Workflow Collaboration” Slack channel was created where I would go to post product related issues that came up in order to allow the PM’s from all affected teams to discuss and come together to an appropriate decision. Thus I think the more appropriate description of this period would be that I was “working autonomously within agreed upon requirements and spontaneously collaborating with interested parties when necessary.”</p><p>These were without question my happiest days at my company. Rarely in my career have I felt so motivated, engaged, and inspired to give my very best work. I was excited every day to come into the office and work harder and smarter. Fourth and final conclusion:</p><p><strong><em>4 Autonomy and trust are essential for me to feel happy and motivated in my work.³</em></strong></p><p>I need to feel like I have the freedom to make decisions and solve problems within the guidelines of the agreed requirements.</p><h4>To recap the 4 things that inspired and motivated me during this period:</h4><ol><li>The feeling that what I’m working on is important and impactful</li><li>Meeting and talking with the people who my work will help</li><li>Decisions being made openly based off information gathered from and visible to all involved parties.</li><li>A sense of freedom and autonomy to solve problems and make decisions within requirements.</li></ol><p>In the <a href="https://medium.com/@kip.armstrong/from-player-to-pawn-one-engineers-perspective-part-2-c72c0ddac2b4">next article</a> I’ll discuss how in a short span of time I went from being inspired and motivated to feeling frustrated and “stuck”.</p><p>Footnotes:</p><p>1 There was one major exception to this statement which I’ll get to later — the “Simple UI”</p><p>2 It should be noted that my daily updates were posted to a channel private to my team and therefore there may have been people who felt like they had no idea what I was doing. However, I believe that my PM was communicating and coordinating with other PMs and management as necessary.</p><p>3 It turns out I’m not alone in this regard. See <a href="https://facilethings.com/blog/en/pillars-of-motivation">https://facilethings.com/blog/en/pillars-of-motivation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83696fb7f66f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>