<?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 Dale Hopkins on Medium]]></title>
        <description><![CDATA[Stories by Dale Hopkins on Medium]]></description>
        <link>https://medium.com/@dhopkins_65471?source=rss-3c85ed94a602------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qrLaZlv6K6WBFKof.</url>
            <title>Stories by Dale Hopkins on Medium</title>
            <link>https://medium.com/@dhopkins_65471?source=rss-3c85ed94a602------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:48:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dhopkins_65471/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[Public Speaking During COVID: Reflections & Questions]]></title>
            <link>https://medium.com/vendasta/public-speaking-during-covid-reflections-questions-b4e1759fc551?source=rss-3c85ed94a602------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4e1759fc551</guid>
            <category><![CDATA[engineering-colleges]]></category>
            <category><![CDATA[university]]></category>
            <category><![CDATA[speaking]]></category>
            <dc:creator><![CDATA[Dale Hopkins]]></dc:creator>
            <pubDate>Thu, 07 Oct 2021 12:13:38 GMT</pubDate>
            <atom:updated>2021-10-07T12:13:38.613Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6djwEgbsBL3c5v1w5fehXg.jpeg" /><figcaption>Speaking at Ideas on Tap in February 2019 — pre-COVID-19</figcaption></figure><p>I was recently invited to speak at the Hardhat Ceremony put on by the College of Engineering at the University of Saskatchewan. The ceremony marks students’ entry into the second year of their studies, where they must select one of the engineering disciplines. The event is all about affirming these decisions, and each discipline has an alumnus speak about their experience in the field. For the first time in nearly two years, I found myself standing in front of a room of people. Overwhelm, excitement, anxiety — I felt all of it as I walked onto the stage.</p><p>This year, the event was held in-person at Prairieland Park. Upon entering the venue, it struck me that it had been nearly two years since I’ve attended an event of this magnitude, or set foot inside this particular venue. Here we are in the midst of the Delta wave of COVID-19, but still able to have an event with over 500 people. Originally students were able to have up to two guests join them for the occasion, but the week before the event this was adjusted due to the volume of interested attendees, so guests were asked to join virtually. Everyone at the event wore a mask with the exception of the speaker while at the podium, and alcohol was not served to improve the safety of the event. It was a pleasure to participate in such a well-run event.</p><h3>Speaking to a Crowd</h3><p>It’s been a long time since I’ve sat in an audience anxiously awaiting my cue to speak. It dawned on me that this would be the first time I’ve spoken to more than 10 people in-person for over 18 months. These past few months, preparing for a speech meant cleaning up my home office, getting the lighting just right, and testing my microphone. For remote talks, you can have your notes on the screen for easy access and there is no view of the crowd. It is a completely different feeling to be there in person looking out at all of those people with the stage lights shining on you. There is a desire to actually address the people you are talking to and to adjust what you say based on the feeling in the room.</p><p>Dale Carnegie — no relation — said that the butterflies you get prior to speaking should never go away because they are a visceral indication of your investment in making a good impression and of your care for the audience. Anxiety often gave way to exhilaration at being able to be on stage, speaking to so many people at such an important life juncture. I hope that I was able to inspire in them a sense of the opportunity that lies in front of them and the myriad options that they truly have.</p><h3>Thoughts on Reading and Speaking</h3><p>Over the past year, I’ve made it my goal to read one book a week. While I’m a little bit behind on that goal, it has made me read a lot more than I have in the past. Whenever I’m reading now and I come upon a reference to another book, I consider adding that book to the queue. I’ve also started to ask others what they are reading and, with these two habits, I have been able to keep a full queue of high quality books to read.</p><p>It’s pretty incredible to me that I have been able to read over 30 books in 2021, and almost all of them have been good books, many of them are great. But why am I telling you this? I have noticed that this increase in reading has changed how I read content — I’m much more attuned to the mechanics of writing and the role of the author. That same awareness translated to how I perceived or “read” speakers during the Hardhat Ceremony. Sitting in the front row, I had a great opportunity to witness the various approaches that speakers took to the task of addressing the students of a particular discipline.</p><h3>To Script or not to Script?</h3><p>The first decision a speaker needed to make was that of a script vs. an extemporaneous approach to the speech. Most speakers chose to go with a written script, which is what I would have guessed. A written speech allows one to conquer their nerves as all they have to do is read it — no memorization required. A written speech allows one to agonize over the exact words and grammatical structure at the same level as written prose. This means that a person gets to come off sounding as eloquent as possible. It also simplifies pacing as one knows exactly how long it takes to read the speech. So the question is, why would anyone ever do an extemporaneous speech?</p><p>I chose to forgo the written speech in favour of a cue card. I wrote a speech ahead of time and then distilled it down into a few key points on a card. I spent an hour before the presentation reading through the written speech so that I knew the general story arc and some key phrases that I thought were important. To me, the value of this approach to speaking is the ability to adjust the speech to fit the situation. After talking with people before the event and listening to other speakers, it’s possible to incorporate new material more easily. It also frees my attention from the written paper to focus on the audience. This was particularly valuable during the event because I was addressing the second-year Engineering Physics students, who were at the front of the room to my right. In order to actually address them, I had to turn 90 degrees away from the podium, where normally a script would have sat. It was important for me to have this flexibility to connect and make eye contact with the audience. At the same time, a fixed podium mic had a limiting effect on my ability to interact with them — I prefer a handheld microphone for this type of speaking.</p><h3>How do Speakers Inspire?</h3><p>The goal of each speaker was to inspire students in each of the disciplines, thus affirming that their choice was a good one and that the practice of engineering is both exciting and serious. There are a few tools at the speaker’s disposal when trying to make an impression on people. Many speakers choose entertainment and wit as their tool to attract the attention of their audience.<a href="https://www.linkedin.com/in/darryl-kacher-83592614/"> Darryl Kacher</a>, a VP of Engineering at Calian (formerly SED Systems), had a well-coordinated speech full of Engineering puns and jokes. Darryl got the entire audience to laugh out loud a few times during his speech and used that engagement to share his experience travelling the world as an electrical engineer and his reflections on just how far technology has evolved during his career. This approach was appreciated by the audience and his fellow speakers alike, as it created a sense of wonder about the future and its possibilities.</p><p>Other speakers took the opportunity to impress upon the students the responsibility they are taking on as engineers and the fulfilment of the purpose that their career will entail.<a href="https://www.linkedin.com/in/andrew-drew-lockwood-62583427/"> Andrew Lockwood</a>, a Principle Functional Safety at BHP and the President of the APEGS, talked about his role in the regulation of the profession. Andrew has clearly given a number of speeches on this particular topic as he looked very comfortable on the stage discussing ethics and responsibility. He described the grandeur of the profession, because most of the modern conveniences we enjoy today are a result of engineers. Again, the other speakers and the audience appreciated this approach as it inspired a feeling of reverence for the profession.</p><p>My approach to the talk was different as I chose to focus more on the students’ schooling and what they can expect to learn. Looking at the world today, I see an exponentially expanding corpus of information alongside a narrowing worldview among people. As an institution, universities offer the opportunity to build critical thinking skills that will foster resilience in the face of criticism and openness to new information, both tempered with a healthy dose of scrutiny on the sources of information. I went further to describe critical thinking as the proactive seeking out of information that doesn’t align with one’s worldview so as to become better informed. My message was that learning is a lifelong pursuit that does not end after attaining a degree, and that the ability to think for one’s self is the true gift of a professional education.</p><h3>So, Which Approach is Best?</h3><p>I sat down to debrief after the evening was over and realized that the variety of approaches the speakers took to the topic was what made the evening great. With an audience as diverse as the second-year Engineering class, I’m certain that one of the talks succeeded in inspiring nearly every single person in that audience. In a lot of ways, oration is similar to penmanship in that each practitioner has a particular style and voice independent of the mechanical aspects of the discipline. A great speech, then, is more than words — it is the interplay of those words with the intention and energy behind the speaker’s delivery.</p><p>Again, perhaps it was the rare opportunity to attend an in-person event, but I was able to see the speakers in a new dimension and gain a new level of appreciation for the craft. I’m looking forward to seeing more great speakers in the near future, and I hope to improve my own written and spoken discourse skills as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4e1759fc551" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vendasta/public-speaking-during-covid-reflections-questions-b4e1759fc551">Public Speaking During COVID: Reflections &amp; Questions</a> was originally published in <a href="https://medium.com/vendasta">Vendasta</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preventing Blame From Entering the Workplace: a DevOps Story]]></title>
            <link>https://medium.com/vendasta/preventing-blame-from-entering-the-workplace-a-devops-story-299af149ee96?source=rss-3c85ed94a602------2</link>
            <guid isPermaLink="false">https://medium.com/p/299af149ee96</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[blame]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Dale Hopkins]]></dc:creator>
            <pubDate>Wed, 29 Sep 2021 15:31:12 GMT</pubDate>
            <atom:updated>2021-09-29T15:31:12.701Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ON38U2yXkhYC05bjimOKvA.jpeg" /><figcaption><a href="https://commons.wikimedia.org/wiki/File:William_Holman_Hunt_-_The_Scapegoat.jpg"><em>The Scapegoat</em></a> by William Holman Hunt</figcaption></figure><p>Blame has no place in a DevOps culture. This is showcased most clearly in the blameless post mortem espoused by Google in their book, <a href="https://sre.google/sre-book/postmortem-culture/"><em>Site Reliability Engineering</em></a>. The reasoning behind this is what I want to discuss today, and it is succinctly captured in Devin Carraway’s parable, “The cost of failure is education.” Of course, this is only true if we have processes in place to allow us to learn from our mistakes and capture that learning. Process management experts like W. Edwards Deming, the father of statistical process management, would have smiled to see the blameless post mortem at the core of our Agile software development practice (because Agile is just like any other process):</p><blockquote>Cease to blame employees for problems of the system. Management should be held responsible for faults of the system.</blockquote><p>- W. Edwards Deming, <em>Out of the Crisis</em></p><p>So if we know that blame isn’t a part of a healthy software development process, why does it always seem to sneak back into the organization? I’d like to start with a story to illustrate.</p><h3>Story Time</h3><p>In June 2020, one of our software development teams wrote about their plans to modernize the technology in their application to better match that of our other applications. This work would be taken on slowly over the coming quarters. Then, in January 2021, the team presented a set of mocks at our Vision &amp; Strategy meeting, showing off new functionality they would be adding to the software. The presentation was steeped in usability and a customer-first mantra, and everyone was excited about this great new feature.</p><p>Over the coming months, we were treated to more and more detailed mocks. In May, the team decided to start building the customer-facing features that would leverage the newly modernized infrastructure. The new functionality took a phased approach and would be put into users’ hands in early August. Then the team’s project manager parted ways with the company a few weeks before the initial delivery of the feature.</p><p>In order to bridge the transition to a new product manager, we brought in a senior leader to be the interim product manager and to help the team get this hotly anticipated feature delivered. In early August, the team was ready to show the first slice of the software to a set of trusted testers — customers who want to help us shape the product with early access to features.</p><p>During the demo, it became clear that the customers were not happy with the slice and went so far as to ask, “Why did you build this?” The feature was a revamped view of their customer relationship data that contained more information and allowed more flexible searching, but it didn’t offer all of the functionality of the old screen. Thus, it turned out that the new feature we were so excited about didn’t satisfy the most important use cases of the customer in its MVP form. This, unfortunately, was the moment when the interim product manager discovered that there wasn’t a written strategy to clearly articulate the “why”. Enter blame.</p><h3><strong>How Blame Enters</strong></h3><p>With a transition in product leadership for the team, it became natural to blame the previous product manager for the lack of strategy. It also became natural to blame the team. Why had they proceeded to develop software for over a year without releasing it to the customer? Why hadn’t the team spent more time with its customers along the way to ensure the first slice was a success?</p><p>Blame tends to surface in organizations when things do not go as planned and is often paired with the word “accountability”. This isn’t the accountability that Michael Lopp <a href="https://www.youtube.com/watch?v=lNE-Vm-q9Iwhttps://www.youtube.com/watch?v=lNE-Vm-q9Iw">talks about</a>, which refers to an ability to account for one’s actions and decisions. Instead, this version is the accountability that means “who do we blame when things go wrong,” so much so that an accountable person is often referred to as “the single wringable neck” (my least favourite phrase in business).</p><p>The logic is that if/when things go wrong, the organization needs to know who is responsible, which is a very natural human reaction to problems. We have to remember that the human brain is not optimized for statistical process control, which Daniel Kahneman points out in his incredible book <em>Thinking Fast and Thinking Slow</em>. Indeed, knee-jerk reactions based on habits or emotions (System I) take less mental effort and come more naturally than higher-level logical thoughts (System II).</p><p>So while this is completely natural, it yields the following process for fixing problems:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hNzEL70MwCOGwWBl" /><figcaption>Typical Process for Problem Solving</figcaption></figure><p>Now, imagine for a minute that you are the one affected by a problem (i.e. the customer). What is the problem with the above diagram? It seems obvious that the red portion of the picture adds unnecessary delay to the process, which further deteriorates confidence and trust. If we could skip straight into understanding the problem we would arrive at a workaround faster.</p><h3>Why Blame Enters</h3><p>This is where psychology comes into the picture. Fred Kofman talks about <a href="https://www.vendasta.com/developers/2020/11/19/cultivating-a-player-mentality-reflecting-on-accountability-in-the-context-of-vendasta-rd/">the Player vs. Victim mentality</a> in his seminal book <em>Conscious Business</em>. When a problem is encountered, a person can choose to accept their part in creating the problem and thus allow themselves the opportunity to fix the problem. This is how Kofman defines the Player mentality, which is described as having an internal locus of control — they are in control and can influence the situation. A person can also choose to deny any part in creating the problem and thus avoid any blame for the problem. This is how Kofman defines the Victim mentality, which is described as having an external locus of control — they are not in control and can’t influence the situation.</p><p>In his book <em>The Coaching Habit,</em> Michael Stainer further breaks down the Victim mentality (i.e. negative thought patterns) based on how a person decides to approach the solution. For people with an external locus of control, it is easy to assume the role of the Victim because being unable to fix the problem renders them passive. It is also possible that they will assume the role of Persecutor, which means they will actively push others — those who are to blame — to fix the problem because they can’t fix the problem themselves. This is reminiscent of the “Silence” and “Violence” roles from the <em>Crucial Conversations </em>framework.</p><p>For people with an internal locus of control, there is still a negative thought pattern possible called the Rescuer. This is a person who does not accept responsibility for the problem but chooses to take action to fix the problem. This is a person who believes that someone else is to blame but believes they have to fix that person’s mess.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/0*u6OpvZUIUroNv3BF" /><figcaption>Thinking Traps</figcaption></figure><p>All three of these negative patterns (Rescuer, Persecutor, Victim) require that blame be established upfront before proceeding towards a solution — they need to find the “accountable” person so as to make sure that person is made a scapegoat (as an interesting aside, the <a href="https://en.wikipedia.org/wiki/Scapegoat">etymology</a> of the word Scapegoat is incredible). This laying of blame allows everyone involved to feel that the situation has been resolved (a collective catharsis).</p><p>However, in addition to delaying a solution, this line of thought also sends a clear message through the organization: failure will not be tolerated. Unfortunately, this establishes a risk-averse culture and builds a type of perverse accountability often referred to as CYA (Cover Your Ass) where people are careful to keep a record of their actions so as to avoid any blame in future. This is the opposite of the Accountability that we want to see in DevOps as it reduces the ability of people to be vulnerable, which is an important precursor to any creative process. This type of culture quite effectively stymies creative problem-solving in favour of less creative approaches deemed less prone to criticism/blame.</p><h3><strong>How Can We Fix This?</strong></h3><p>We don’t need to fall prey to our instincts around blaming. Culture is a powerful tool for establishing social norms and it can be used to extricate blame from the workplace. This lowers the latency of problem-solving and increases innovation (i.e. calculated risk-taking) within the organization. It starts with a shift from blaming <em>people</em> to blaming <em>systems and processes</em>.</p><p>When something hasn’t gone to plan, this is exactly the moment when we need to acknowledge people’s efforts and rebuild their confidence. This shift encourages the iterative improvement of the process and over time disincentivizes playing the blame game. This change can originate anywhere inside of the organization but requires clear support from senior leadership as their actions will have a large influence on the culture, especially when it comes to deciding blame’s place inside the office.</p><p>In the earlier story involving a miss on customer expectations, we needed to pivot away from blame and restore the trust of the team. This effort started by removing the blame element from the equation. This problem quickly turned into fertile ground for the discovery of process improvements. The question of “Why didn’t you have a clear strategy?” became “How did our process fail to correct this problem?” And the question of “Why did we build such a large chunk of work before demoing to a customer?” became “How could our process bring the customer in earlier?”</p><p>While this change in approach certainly made improvements to our processes and the safety of future teams, it will be a long path to restoring the confidence of this particular team after allowing blame to enter their sphere. They say that time heals all wounds but in the software world, I prefer the adage “Shipping Fixes Everything” because it feels good to deliver a great product to customers. After a series of successful deliveries, the confidence of the team will return as long as we are able to successfully keep blame out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=299af149ee96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vendasta/preventing-blame-from-entering-the-workplace-a-devops-story-299af149ee96">Preventing Blame From Entering the Workplace: a DevOps Story</a> was originally published in <a href="https://medium.com/vendasta">Vendasta</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meaning and Motivation in the Workplace]]></title>
            <link>https://medium.com/vendasta/meaning-and-motivation-in-the-workplace-192c116ea28f?source=rss-3c85ed94a602------2</link>
            <guid isPermaLink="false">https://medium.com/p/192c116ea28f</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Dale Hopkins]]></dc:creator>
            <pubDate>Tue, 01 Jun 2021 20:50:53 GMT</pubDate>
            <atom:updated>2021-06-01T20:50:53.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Q-9NjE0qXB8Yf4G6GweJA.jpeg" /><figcaption>Saskatoon: the Beautiful</figcaption></figure><p>Are you confident that your organization firmly connects each employee with customer objectives in a way that maximizes their engagement and productivity?</p><p>For simplicity, you can think of work as accounting for approximately one-third of your time with sleep being another third and the remaining third dedicated to everything else. Most of us seek to find meaning and purpose in our lives and quickly rule out sleep as the answer to accomplishing either. It quickly becomes obvious that work must play a role in fulfilling the need for significance, which we see reflected in the language of “life’s work.” This phrase is often used to refer to a person’s purpose or calling, though the term generally refers to the grand sum of the work one accomplishes during their lifetime. I propose that, with effort, an organization can use customer-centric goals to surface the meaning and purpose inherent in the work for employees.</p><h3>A Personal Story</h3><p>When I started at Vendasta in 2010, we were a small startup with about 20 employees organized into 3 software teams. We had aspirations of being a product company but, at the time, we did a significant amount of contract software development to “extend the runway,” as the saying goes. The team I was hired onto worked with a large organization called the Ritchie Brothers Auctioneers, or RBA for short. We were hired to assist them with equipment intake at auction sites to accurately capture all relevant information about the equipment as it entered the lot. This allowed remote estimation specialists to determine the value of the equipment for the seller, in turn providing this data to the website to inform remote bidders. In my role, I would regularly fly to Vancouver to work in the RBA head office to work closely with them and interface with their QA team and Project managers. We also attended live auctions to better understand how our software was used and how auctions worked.</p><p>Looking back on this experience, I find it interesting how intrinsically motivated I was. We were doing contract software development, a frustrating process with its myriad of documents and contract negotiations. Still, in the midst of arguing over “implicit requirements” and the cost of various change orders, our whole team was excited to see the results of each release of the new software. We took time one Friday to read the RBA shareholder report that mentioned the software we had built was pivotal in their ability to increase margins by something like 200 basis points!</p><h3><strong>Motivation and its Relationship to Meaning</strong></h3><p>Last year, I came across the work of Neel Doshi and Lindsay McGregor, whose book <em>Primed to Perform</em> dives into the mechanics of human motivation. The core tenet of the book is that there are six factors that motivate all human behaviour. Three of these factors are referred to as positive and simultaneously build a person’s bond with their group; the other three factors are referred to as negative and erode the bond with that person’s group. Armed with this information, Doshi and McGregor prescribe companies a more diligent approach to increasing positive motivators and decreasing or even eliminating negative motivators.</p><p>The first and strongest of these motivators is <strong>play</strong> and reflects the fact that it’s pretty easy to motivate people to do things that are inherently enjoyable. As managers, we can consider the interests of people — which vary greatly — and optimize project and task assignments to allow people to spend more of their time doing work they like doing.</p><p>The next motivator is <strong>purpose</strong>, which speaks to the fact that people like to do work they find meaningful. Sure, it’s not as strong of a motivator as play, but why not? It comes down to “temporal coupling”: there is a larger temporal gap between when the work is performed and when the rewards are reaped. With play, on the other hand, the work itself is the reward, so no temporal gap exists. In the workplace and particularly in R&amp;D, there is a notable gap between doing the work and then seeing it realize its purpose. This is one of the most likely areas for improvement as a manager; we need to make sure our engineers are connected with the customer so they can see the purpose of their work regularly and with a conscious effort so as to minimize latency.</p><p>The last motivator is <strong>potential</strong> and it is the weakest of the three motivators. It applies when the person does not necessarily enjoy their work (<em>play</em>) and they don’t necessarily see the positive impact of their work (<em>purpose</em>) but they do see how it builds their future capacity or <em>potential</em>. This is something that R&amp;D managers understand and strive to do though training and growth opportunities to our engineers.</p><p>Getting back to the purpose motivator, if we dig a bit deeper, we see that a sense of purpose is grounded in human psychology and leverages our natural inclination towards curiosity. Humans in general are driven towards learning new things as doing so helps us discover our purpose as well as our limitations through mastery. This is an important point as the actual sense of purpose felt from an achievement is oftentimes linked to its difficulty rather than the significance of the achievement. Games are a prime example of this principle at work: there is no productive purpose to a game, only the satisfaction of mastering a skill and testing one’s mettle.</p><h3><strong>Add Context to Goals for Alignment and Motivation</strong></h3><p>As managers and leaders, we have a powerful tool for both motivation and alignment that too often goes unrecognized: <em>context</em>. So often we try to save time and tell our teams the solution that our customers need rather than sharing the full context of the problem and the trail of thinking that lead us to the proposed solution.</p><p>Context is key as it can be leveraged by the team to discover optimizations or select trade-offs more appropriately. This is the core message in Dale Carnegie’s classic <em>How to Win Friends and Influence People</em> that so often gets misinterpreted as “convince them it was their idea.” There is more to context than simply empowering the team to make optimizations and trade-offs (i.e. autonomous decisions). More importantly, this information helps the team understand the <em>meaning</em> and <em>purpose</em> of the work they are doing; it elucidates who the customer is and why this is important to that customer.</p><p>From speaking with other managers and leaders, most of us <em>think </em>we do this but I’ve found that we rarely do so effectively. Not only do you need to communicate context, you need to do it frequently and you need to make it discoverable. This usually means explicitly writing it down, which can be challenging for many people. It also means collaborating with people on the written document and making sure that it is complete. Most of us fail to capture the full context in our writing because we aren’t aware of the limits of “common knowledge” or what is or isn’t “obvious.” Reviewing your written documentation with your teams can help ensure these types of gaps do not hamper effectiveness. This type of writing also dovetails nicely with <a href="https://medium.com/vendasta/how-metrics-can-actually-help-e56694995f0f">good metrics</a> (i.e. OKRs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vI4NuPFK7OPuoU1YJGyerQ.jpeg" /><figcaption>It’s a good word but “cadence” always makes me think bicycles. Winter biking is the best.</figcaption></figure><h3><strong>Developing a Regular Review Cadence</strong></h3><p>Now that you understand the power of purpose and motivation in tandem with the value of written context, there is only one part left: cadence of review. When you regularly review the progress of your team(s) and share the impact of that progress on the business and customers, you have taken a major step towards the increased motivation of your team.</p><blockquote>“Goals are good for setting a direction, but systems are best for making progress.”</blockquote><blockquote><em>- Atomic Habits</em> by James Clear</blockquote><p>Review is an opportunity to change or double down on current strategies based on the results being achieved. This cadence should be regular and, as such, it makes a lot of sense to align this with the cadence of the sprint. The sprint review is a perfect opportunity for reviewing metrics in addition to the software that was shipped.</p><p>Agile methodologies have always leveraged a strong cadence punctuated with rituals in the name of the values like regular <strong>customer collaboration</strong> and shipment of <strong>working software, </strong>as espoused in <a href="https://agilemanifesto.org/">The Agile Manifesto</a>. I generally feel humbled when, after reading new material and doing some critical thinking, I come to the conclusion that there is even more depth to The Agile Manifesto than I realized and I’m able to further appreciate its truly insightful nature.</p><p>I understand now why the contract software work with the Ritchie Brothers was such an exciting time in my career: I had <em>context</em> and a clear understanding of my team’s goals, I understood my contribution to those goals, and I had wide autonomy over my approach to attaining those goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=192c116ea28f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vendasta/meaning-and-motivation-in-the-workplace-192c116ea28f">Meaning and Motivation in the Workplace</a> was originally published in <a href="https://medium.com/vendasta">Vendasta</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Metrics Can Actually Help]]></title>
            <link>https://medium.com/vendasta/how-metrics-can-actually-help-e56694995f0f?source=rss-3c85ed94a602------2</link>
            <guid isPermaLink="false">https://medium.com/p/e56694995f0f</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Dale Hopkins]]></dc:creator>
            <pubDate>Wed, 28 Apr 2021 19:33:15 GMT</pubDate>
            <atom:updated>2021-04-29T00:14:17.671Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Taking cues from Andy Grove and John Doerr, my thoughts on how we can use metrics and goals for good, not for evil</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIUrUUMhxvPEKOuyYR5vTA.jpeg" /></figure><p>The tale of <a href="https://en.wikipedia.org/wiki/Blind_men_and_an_elephant">the blind men and the elephant</a> is a classic parable that holds within it a clear lesson: our capacity to fully understand something is often limited by our own subjectivity and experience. This adage is used all the time in the business world, and it can be easily applied to the rift between business and engineering when it comes to metrics and goals.</p><p>The problem is that engineers tend to see metrics somewhere between a bridle and a noose — a tool for control and punishment. Business people, on the other hand, tend to see metrics somewhere between a carrot and a Maserati — a tool for motivation and drive. Both views arise from different correct albeit partial perspectives on the broad topic of metrics and goals. So, before fighting about “who’s right” when it comes to metrics, it pays to understand the other side’s perspective.</p><h3>TL;DR</h3><p>Metrics and goals are primarily communication and alignment tools. When used for performance measurement, <a href="https://en.wikipedia.org/wiki/Goodhart%27s_law">Goodhart’s Law</a> states that they immediately sabotage their accuracy and effectiveness. To be effective, metrics and goals need to be set by the individuals responsible for moving them; they must also be completely under the individuals’ control. Finally, the cadence of review and re-evaluation of the metrics and goals by those same individuals determines their continued usefulness.</p><h3>A Personal Story</h3><p>I’ll start with a personal story from my first job out of university at a hardware company here in town. After working as an FPGA developer for about a year, I was promoted to the position of project manager for a new piece of hardware we were building. This particular project had a lot of software that was needed to manage the particularly complex hardware inside. This was my first experience managing a project and I was introduced to the <a href="https://en.wikipedia.org/wiki/Gantt_chart">Gantt chart</a> for the first time. I built out the mother of all Gantt charts with over 100 little interrelated bars. Senior leadership <em>loved</em> it — clearly, I was on top of things! The problem was that in order to keep that chart up to date as the project moved forward, I had to spend 20 hours each week gathering feedback, updating the chart, and making the necessary downstream changes. Since that time, I have often felt that Gantt charts are evil by their very nature and that <em>they</em> were the problem. But, as with many challenges in life, the problem was a perspective that was too narrow.</p><h3>What are Metrics?</h3><p>At their simplest, metrics are quantitative measurements that provide insight into the inputs and/or outputs of a process. On the surface, metrics are fairly innocuous. Their hidden weight comes from the implication that they are indicators of what the business values. This implication results in obscuring the true goals of the business. The unintended consequences of this are clearly documented by V. F. Ridgway in his oft-cited 1956 journal article titled “Dysfunctional Consequences of Performance Measurements”:</p><blockquote>Even where performance measures are instituted purely for purposes of information, they are probably interpreted as definitions of the important aspects of that job or activity and hence have important implications for the motivation of behaviour.</blockquote><p>Ridgway’s paper discusses how performance measurement results in narrow job interpretation whether the metrics are single, multiple, or composite in nature. One example he uses is the centralized planning employed by the Soviet Union in its attempts to optimize factory efficiency and output. This is a fascinating subject on its own as Soviet workers were truly geniuses at gaming these performance management systems with comical results (e.g. You want to measure the weight of nails we make? What if we made 100 lb nails instead of the normal sized nails that most people need?).</p><p>The phenomenon discussed in Ridgway’s paper were later formalized by British Economist Charles Goodhart in 1975 and referred to as Goodhart’s Law:</p><blockquote>Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes.</blockquote><p>So the challenge is that measurement itself isn’t bad, but the problem arises when management declares it is going to measure something, thus initiating a game with employees to optimize that metric (or set of metrics) rather than serve the customer to the best of their ability. The most common instance of this game is the one where the business selects a deadline for delivering a project and then focuses metrics around that deadline. The result is invariably lower quality delivery.</p><h3>The Genius of Andy Grove</h3><p><a href="https://en.wikipedia.org/wiki/Andrew_Grove">Andy Grove</a> was the first employee of the Intel Corporation in 1979. He went on to be the President and later CEO of the company, leading it through some of its most innovative and successful years of business. He was a gifted manager who well understood the challenge of metrics and goals, leading him to create something he called <a href="https://en.wikipedia.org/wiki/OKR">Objectives and Key Results (OKRs)</a>. In his book <em>High Output Management</em>, Grove lightly touches on the OKR, but most readers would be forgiven if they missed the importance of the concept being introduced. <a href="https://en.wikipedia.org/wiki/John_Doerr">Jim Doerr</a> provides a much richer description of Grove’s OKR system in his book <em>Measure What Matters.</em> The key insight of the OKR is that the employee chooses the metric along with the goal (Key Result) to fit within the organizational goal (Objective). This cleverly sidesteps Goodhart’s law by avoiding management choosing the metric!</p><p>Many business books contribute to the lore of difficult goals and their ability to stretch those who set them. <a href="https://en.wikipedia.org/wiki/James_C._Collins">Jim Collins</a> calls it a Big Hairy Audacious Goal (BHAG) in his seminal book <em>Good to Great</em>, while Doerr refers to this trait as “stretch” in <em>Measure What Matters</em>. Doerr goes on to discuss how Google famously sets both “committed” and “aspirational” OKRs with the aspirational ones being only “70% achievable”:</p><blockquote>At Google, in line with Andy Grove’s old standard, aspirational OKRs are set at 60 to 70 percent attainment. In other words, performance is expected to fall short at least 30 percent of the time. And that’s considered success!<br>(p. 139)</blockquote><p>The entire idea behind this stretch aspect of an OKR is to encourage people to aim higher than they might normally consider. The question that one should ask though, is “Why does a stretch goal improve performance?” Doerr lays at the answer as follows:</p><blockquote>Setting specific challenging goals is also a means of enhancing task interest and of helping people to discover the pleasurable aspects of an activity.<br>(p. 134)</blockquote><p>This is an important piece of data because it explains that the stretch goal serves to make a task more interesting or to pique the person’s interest/curiosity. It bears repeating that this only works when the employee chooses both the metric and the target as the Key Result. If management chooses the metric or the target, the benefit is nullified immediately and Goodhart’s Law dominates. The key component here is to trigger a person’s natural desire for Autonomy and Mastery to drive performance.</p><h3>Curiosity’s Role in Motivation</h3><p>One of the particularly vexing things about performance is that a person will push themselves harder when there is nothing monetary at stake. The human motivator with no limitation is actually the desire to play or to satisfy one’s curiosity. The desire to learn one’s limits and improve one’s skills is an innate part of human nature. <a href="https://en.wikipedia.org/wiki/Daniel_H._Pink">Daniel H. Pink</a> describes this quite clearly in his book <em>Drive.</em> He points out that people are motivated to action in three ways:</p><ol><li>Extrinsic (Biological) — The desire for food, sleep, water, and sex motivates behaviour.</li><li>Extrinsic (Reward &amp; Punishment) — The desire to provide for one’s family.</li><li>Intrinsic — The desire for self-actualization (Mastery, Autonomy, Purpose)</li></ol><p>Interestingly enough, Pink points to research on the topic that shows how different types of motivation affect task performance. The research shows that creative tasks like Engineering tend to see lowered performance when motivated extrinsically and increased performance when motivated intrinsically. If you want to trigger intrinsic motivation, his suggestion is to focus on the following three areas:</p><ol><li>How employees organize their work</li><li>How employees think about their work</li><li>How employees do their work</li></ol><p>The more autonomy employees feel in these three areas, the more strongly they will be intrinsically motivated. If we let employees choose their own metrics and goals that they can directly influence, let them instrument those metrics, and give them control over their approach to achieving the goal, we’ll maximize intrinsic motivation.</p><h3>Metrics: Tools for Communication &amp; Alignment</h3><p>Coming back to the original problem, even though engineers and business people tend to see metrics and goals very differently, we now have the tools to broaden our perspective to both understand the conflict and resolve it. We need to see metrics and goals as tools for communication and alignment rather than for performance measurement and management.</p><p>Business people need to see that setting another person’s metrics and goals (Key Results) rather than letting them choose their own within an area of focus (Objective) results in decreased performance and a reduced sense of ownership and accountability. When a person sets their own Key Results, instruments the measurement of them, and feels free to adjust those Key Results when new information comes to light, that person is empowered to provide transparency into what they think is important. Understanding what employees think is important can be used by management to better understand the state of the business and to spot opportunities to clarify Objectives to achieve better alignment.</p><p>Engineers need to see that choosing metrics and setting goals (Key Results) within a corporate strategy (Objective) allows them to bring focus to their work while not losing sight of the ultimate goal of the business, which is to meet the needs of its customers. By viewing these Key Results as opportunities to challenge themselves while remaining agile with respect to changing assumptions and conditions, goals and metrics can be an effective defence against imposter syndrome and a way to discover purpose in their work by connecting their daily activities with the organization’s higher-level goals (Objectives).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e56694995f0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vendasta/how-metrics-can-actually-help-e56694995f0f">How Metrics Can Actually Help</a> was originally published in <a href="https://medium.com/vendasta">Vendasta</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>