<?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 Mark Harris on Medium]]></title>
        <description><![CDATA[Stories by Mark Harris on Medium]]></description>
        <link>https://medium.com/@ma_harris1011?source=rss-8c7c910354a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dTu6RPlFis5nV_k7v4VmGQ.jpeg</url>
            <title>Stories by Mark Harris on Medium</title>
            <link>https://medium.com/@ma_harris1011?source=rss-8c7c910354a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:53:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ma_harris1011/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[A Proposal your Co-workers will Love]]></title>
            <link>https://medium.com/@ma_harris1011/a-proposal-your-co-workers-will-love-d01e9a98d3d2?source=rss-8c7c910354a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d01e9a98d3d2</guid>
            <category><![CDATA[proposal-writing]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Mark Harris]]></dc:creator>
            <pubDate>Wed, 14 Aug 2024 12:31:36 GMT</pubDate>
            <atom:updated>2024-08-14T15:13:18.405Z</atom:updated>
            <content:encoded><![CDATA[<p>In the early 2000’s, I attended a week-long, stay-over leadership course in North Bend, Washington as part of becoming a new manager at Microsoft. During the day we went through the curriculum, and by evenings, we hiked, chatted, debated, and generally helped one another learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XJuc21nnGbhED55GKAXHSw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@parabol?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Parabol | The Agile Meeting Tool</a> on <a href="https://unsplash.com/photos/man-in-blue-crew-neck-t-shirt-sitting-beside-woman-in-black-tank-top-VWLCR5Bt4fc?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>There were a lot of great lessons that week, but one that has stuck with me ever since is the general format of a solution proposal. It works for long-form written documents (like at <a href="https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595/ref=asc_df_1250267595/?tag=hyprod-20&amp;linkCode=df0&amp;hvadid=692875362841&amp;hvpos=&amp;hvnetw=g&amp;hvrand=10462290220645152260&amp;hvpone=&amp;hvptwo=&amp;hvqmt=&amp;hvdev=c&amp;hvdvcmdl=&amp;hvlocint=&amp;hvlocphy=9014885&amp;hvtargid=pla-2281435177178&amp;psc=1&amp;mcid=341a830494293d818297805da4e70c3a&amp;hvocijid=10462290220645152260-1250267595-&amp;hvexpln=73&amp;gad_source=1">Amazon</a>) or for more traditional PowerPoint presentations. This format leads the authors and the readers to critically examine the problem before jumping to proposed solutions.</p><p>The proposal comes in 5 sections:</p><ul><li>Problem Statement</li><li>Solution Requirements</li><li>Proposed Solution</li><li>Mapping the Proposal to the Requirements</li><li>Discussion of Discarded Solutions</li></ul><h3>Problem Statement</h3><p>In this section, you clearly and succinctly identify the specific business impact of the problem, how long it has been occurring, who feels the impact of the problem, and any specific metrics that apply. Ideally, this section is brief — one paragraph will do.</p><p>One anti-pattern is to identify the problem as the absence of your proposed solution. I see a lot of problem statements like, “Our problem is that we don’t do CI/CD” or “Lack of automation in our inventory system prevents accurate financial reporting.” While these statements identify a problem, they also are clearly biased toward the proposal, which compromises the argument.</p><p>Importantly, you should strive to get to the root problem. Root causes are usually a matter of subjective analysis, but typically become obvious with a <a href="https://asq.org/quality-resources/fishbone">Fishbone analysis</a> or a typical <a href="https://www.cms.gov/medicare/provider-enrollment-and-certification/qapi/downloads/fivewhys.pdf">“Five Whys” exercise</a>. Identify a root cause of the problem you’ve observed and write a succinct problem statement.</p><h3>Solution Requirements</h3><p>The next section outlines the requirements for any ideal solution. This should include constraints and each requirement should map to one particular aspect of the problem. The requirements will be used as a litmus test to prioritize and filter the potential solutions you may generate when brainstorming.</p><p>Imagine that the problem is solved, then list out the characteristics of that solution. Is there a budget to follow? A timeline to hit? Staffing constraints or needs? Are there legal or compliance regulations that must be satisfied? Privacy concerns? Is there a legacy system that you have to integrate with? Will revenue increase or will costs decrease (or both)?</p><p>Brainstorm constraints with your team, prioritize them, and ruthlessly question each one. When you have your agreed-upon list, put them into your document.</p><h3>The Proposed Solution</h3><p>This is the proposed solution you intend to put forward. After evaluating all the potential solutions, this is the one that matches best with the constraints and solves the problem as proposed. Take a stand! Describe your proposed solution as clearly as you can. Lead the reader to see the vision of a world without the problem as described - due to the solution you propose.</p><p>It is the specificity of your description that helps the reader know that you and your team have done the research and are confident in this solution. A good format is the <a href="https://www.atlassian.com/blog/productivity/how-to-write-smart-goals">SMART goals </a>often used for performance objectives: Specific, Measurable, Action Oriented, Reasonable, and Time-Bound.</p><p>“We will increase deployments per day by 50% before the end of Q3 with a fully-integrated CI/CD platform, daily pull requests, and integrated testing. To implement this solution, we need 5 additional DevOps engineers, …”</p><h3>Mapping to the Ideal Solution</h3><p>In this section, you take each of the solution requirements and show how closely they map to the proposed solution. This can be done one-by-one, or in general. Often, this section is combined with the proposed solution, optimizing space to both describe the actual solution and the requirements that are satisfied.</p><p>“Implementation of the CI/CD platform automates work currently performed by 5 engineers, saving money and redirecting their attention to improving the platform.”</p><p>“Integrated testing ensures that the code meets requirements before deployment, improving stability of our system.”</p><p>This mapping shows the reader your thought process and gives them an opportunity to decide to agree.</p><h3>Discarded Alternatives</h3><p>The most important part of this proposal (aside from the actual solution description) is the list of alternate solutions that were considered but discarded for specific reasons. A product manager I worked with once used to refer to this as the “Yeah, buts.” Every problem solver you put your solution in front of will have a list of “Yeah, but did you consider XYZ?” This is the section that silences those objections. A reader can go through the list to understand your reasoning for why any alternate solution was not sufficient for the task.</p><p>“One alternative solution is to construct a checklist that is closely followed by any engineer doing releases. While this increases repeatability, it does not improve the throughput of releases per day.”</p><h3>Putting it All Together</h3><p>I have consistently used this framework for presenting problem solutions since the early 2000’s. It has helped me convince managers to invest budget, convince engineers to adopt particular architectures, or to convince customers to buy my solutions.</p><p>If you make use of it, let me know in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d01e9a98d3d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There Are At Least 12 Graveyards on the Route between Columbus and Sandusky, Ohio]]></title>
            <link>https://medium.com/@ma_harris1011/there-are-at-least-12-graveyards-on-the-route-between-columbus-and-sandusky-ohio-29589c2f9b7d?source=rss-8c7c910354a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/29589c2f9b7d</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[family]]></category>
            <dc:creator><![CDATA[Mark Harris]]></dc:creator>
            <pubDate>Sat, 09 Mar 2024 15:51:12 GMT</pubDate>
            <atom:updated>2024-03-09T15:51:12.223Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2bhiW5q0HW4Ij-jD68LVw.png" /></figure><h3>How do I know? Because we counted them.</h3><p>My son and I have a now 20-year run of the classic game “Graveyard” going. If you’ve never played, here’s how it works: for each graveyard you see along a trip, the first person to call out “graveyard” gets one point. Any set of tombstones counts — a family plot in the field or an artfully manicured cemetery next to a stately church. At the end of the trip, the person with the most points wins.</p><p>Not real complicated, but it gives you a chance to engage during the trip.</p><p>A few years ago, I took a solo motorcycle trip from Columbus through my hometown and up to Sandusky, on Lake Erie. My 2 hour trip through flat-as-a-350-million-year-old-inland-seabed North Central Ohio was the perfect opportunity to hone my skills for spotting collections of tombstones.</p><p>I don’t know if it was the wind on my helmet or the endless sea of September corn, but the questions began somewhere north of Attica: “Do families even *do* road trips these days?”, “What happens to road games when there are iPads, iPhones, DVD players, PS4s, and XBoxen in the wayback?” I know I should have been thinking about staying vertical on the bike, but these questions sneaked in.</p><p>Draped in i-devices, AC/DC converters, and game-players, my kids used to zone out as soon as we hit the freeway. It never ceased to surprise and thrill me to hear, “GRAVEYARD. Left side. Ha! 1–0.” pipe up from from my oldest in the back seat, despite the headphones hanging from his ears — Some things endure despite technology.</p><p>In our over scheduled family lives, time in the car is some of the only time you can get alone with your child. I hear from my friends that devices steal that time.</p><p>What games did you play in the car as a kid? Do you play those games with your children now? How do you handle the electronics-in-the-car situation? Do movies &amp; TV in the car take away or add to your road trip?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29589c2f9b7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned in One Year at a Tech Startup]]></title>
            <link>https://medium.com/@ma_harris1011/what-i-learned-in-one-year-at-a-tech-startup-eebe7c748324?source=rss-8c7c910354a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/eebe7c748324</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[scaling-up]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[technology-team]]></category>
            <category><![CDATA[startupş]]></category>
            <dc:creator><![CDATA[Mark Harris]]></dc:creator>
            <pubDate>Tue, 26 Sep 2023 15:01:33 GMT</pubDate>
            <atom:updated>2023-09-26T15:01:33.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-M55IADDRN7opRlw" /><figcaption>Photo by <a href="https://unsplash.com/@marvelous?utm_source=medium&amp;utm_medium=referral">Marvin Meyer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In early 2021, I was faced with a career dilemma: stay with my awesome boss &amp; team at my corporate innovation job or take a chance with a local startup in a CTO role.</p><p>Deciding to take on this risk was one of the most difficult career decisions I had ever made. I loved the kind of work I was doing. I enjoyed working with my team and my leadership. Yet, the opportunity to scale and run an engineering team of my own was too much to ignore. Ultimately, I knew I would regret not taking the risk.</p><blockquote>We only regret the chances we didn’t take, the relationships we were afraid to have,and the decisions we waited too long to make. — <a href="https://www.goodreads.com/quotes/1135671-in-the-end-we-only-regret-the-chances-we-didn-t">Lewis Carroll</a></blockquote><p>My 15 months at <a href="http://www.awarehq.com/">Aware</a> were some of the most demanding and engaging of my career. It was an unparalleled opportunity for applying my experience and for accelerated learning. A full list of the lessons learned would fill several books. Below are 6 of the top lessons I will take with me to my next roles.</p><h3>Make the Business Successful</h3><p>More so than at any other role in my career, it became obvious that the role of the technology team was to make the business successful (profitable, market dominating, customer delighting). We do whatever we can do toward that goal, from reducing costs, to five-nines reliability, to hackathons, and timely, innovative solutions.</p><p>Our job is to be a full partner in the business — not just order takers. We must understand the customers’ needs intimately and commit to delivering on those needs on time and under budget. Understanding customers takes an investment of time and energy to observe them, discuss their needs, and to experiment obsessively. Engineers who “get” customers are only way to enable innovation at scale for the business.</p><p><strong>As a technology team, we only build solutions that advance the business.</strong></p><h3>Builders Build</h3><p>As a technologist with an MBA and who spent time in product management, I tended to lean toward “buy” in the classic buy/build conflict. It took my time in the CTO seat to truly understand why that was a problem. Technologists are builders. Builders <em>build</em>, we don’t <em>use.</em> We don’t <em>buy.</em> We <em>build</em> so that we are in control of our own destiny. We build so that we can stretch our skills. We build to fully understand the solution from stem to stern so when there is a pivot, we can deliver.</p><p>We also build to bring the top talent to our team. No engineer worth her salt wants to join a company just to configure a 3rd-party system. The engineers we want to attract come for the chance to build their own versions of those 3rd-party systems. We are developers, engineers — <em>builders.</em> Lean into it.</p><p><strong>Be a builder and require a building culture. Your team will be better off by just about every dimension.</strong></p><h3>Technology Choices Matter to the Business</h3><p>In a role at another startup, our CEO wanted to weigh in on my team’s decision to use Elixir for an API project. When I asked why, his answer was (characteristically) brilliant: because the choice of programming language influences the type of engineer we hire, which heavily influences the team culture. We had hired Ruby engineers because we liked that culture. Was Elixir on the same trajectory?</p><p>We approached our technology choices with that in mind. The technology choice was .NET Core, running on AKS in containers, which led us to a particular type of engineer: corporate but slightly rebellious, willing to apply Unix principles to typical corporate problems.</p><p><strong>Engineering culture follows the technology choices, not the other way around.</strong></p><h3>Leadership is Lonely</h3><p>As the leader, it’s your job to support your team, which means helping them deal with their issues, making sure they have the tools, capacity, &amp; knowledge to handle the work, and inspiring them to greater heights. Yet, there’s always more you could have done, and someone will always point that out. There’s always someone on the team whose needs you could serve better.</p><p>To add to it, your peers are not likely to give you kudos either. They are too busy dealing with their own teams to notice that you crushed performance goals or reduced cost or delivered some awesome feature. At best, you get a thank you. Usually, you get ignored. Either way, be happy with it.</p><p><strong>You have to find your own internal kudos. Find ways to spread joy throughout your team and to be happy with their accomplishments.</strong></p><h3>Follow the Leader</h3><p>As the leader, your team will follow your lead, especially in new &amp; unfamiliar circumstances — which is all the time at a startup. If you want your team to stay calm and address the situation at hand, then you need to manage your own responses first.</p><p>When your junior engineer deletes the customer’s sole database and you don’t know if there’s a backup, take a breath and be who you want <em>them</em> to be as they fix it.</p><p>When your roles &amp; responsibilities are changed out from under you (which happens all the time as the company pivots), think how you want your team to feel about it and behave accordingly.</p><p><strong>Be the leader your team wants you to be: supportive, positive, empathetic, challenging.</strong></p><h3>Process is Necessary. Deal with It.</h3><p>Startups famously avoid Process. Yet, as companies grow (which you hope your startup does!) they need to establish processes to so they can repeat successes. It’s one thing to create one whiz-bang software solution, and something entirely different to create two or three. Your Series C investors expect that you have developed a way to repeat successes.</p><p>As a leader, your job is to put frameworks in place to replicate your successes. We adopted the typical agile processes at the team level — standup, retros, planning sessions, and 2-week iterations — but to scale, we adopted quarterly-level planning at the team level and at the division level. We placed responsibility for delivery on the engineering managers. We added bi-weekly demos to keep everyone on track. Our framework allowed us to scale our agile processes our way. Agile is how software gets built, but you must adapt it to your own needs.</p><p><strong>Don’t blindly follow LESS or SAFe. You’ll inevitably confuse process with progress &amp; delivery.</strong></p><h3>Lessons Learned</h3><p>My time at Aware came to an end, but the lessons I learned continue to help me lead software engineering teams:</p><ul><li><strong>The Job of Technology is to Make the Business Succeed</strong></li><li><strong>Be a Builder. Own your Destiny</strong></li><li><strong>Tech Choices Matter for More than you Think</strong></li><li><strong>Find your Internal Kudos</strong></li><li><strong>Lead Yourself to Lead your Team</strong></li><li><strong>Use Frameworks to Scale your Processes</strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eebe7c748324" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Would you bet your bonus on it?”]]></title>
            <link>https://medium.com/@ma_harris1011/would-you-bet-your-bonus-on-it-baa0e872099c?source=rss-8c7c910354a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/baa0e872099c</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mark Harris]]></dc:creator>
            <pubDate>Tue, 07 Feb 2023 17:02:38 GMT</pubDate>
            <atom:updated>2023-02-07T17:02:38.926Z</atom:updated>
            <content:encoded><![CDATA[<p>He stared at me with the intensity of 1000 suns. Every face in the room turned to look at me, and my 30-something self was questioning every decision I ever made to get to that point. This was the Windows 2003 War Room, full to the brim with senior engineers and product managers, each waiting for me to answer.</p><p>I felt the sweat begin to roll down my spine …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vAaB-3AU60EnH3GGVQCrFw.png" /><figcaption>Image courtesy of DALL-E 2 — auto-generated</figcaption></figure><p>I was the test manager for the RPC service that served as the backbone for all interprocess communication in Windows and we had found a <a href="https://www.amazon.com/Show-Stopper-Breakneck-Generation-Microsoft/dp/0029356717">Showstopper</a>. It was a rare condition in the memory manager that affected how RPC worked in high-volume situations, and we wanted to check in the fix.</p><p>The VP was brought in to make the call because we were one week away from shipping RTM — Release to Manufacturing — the final milestone in our 3-year journey.</p><p>I took a deep breath and explained the situation. The bug didn’t happen all the time, but when it did, it was catastrophic. I told him we could tell if the fix worked in a couple of days. The developer told us that the fix was safe, that he had tested it, and that it couldn’t possibly affect other components, but we all knew that was wishful thinking.</p><p>If the developer was right, and his fix addressed the issue and was easy to test, we could be done in a matter of days. More likely, he fixed some other as-yet-unidentified problem thinking it was this one. In that case, a couple days of testing would go for naught, and the problem would recur. We would have delayed for nothing. Third, it was entirely possible the change fixed the issue but caused other problems in the system. Last, his fix could potentially make the memory manager’s performance worse.</p><p>Four possibilities, three of which were bad.</p><p>Just about every team would have to re-run their tests, which could take weeks. That delay would cost the company significant revenue and we would take an immeasurable reputation hit among our partners. The delay of this release might mean that the OEMs we worked with would ship competitors’ systems (e.g. Linux) on servers that year rather than Windows. The risk was that not fixing it would expose Windows Server to crashes when customers started using it.</p><p>“Would you bet your bonus on it?” he asked me again.</p><p>“No,” I said.</p><p>Sometimes I lament that choice. I should have had the courage, I think, to stand up to that VP and his multi-year experience to say “Yes, I would. This is an important issue.” But the truth is it wasn’t that important.</p><p>And his question was a good one. In just a few words, he connected the technology with the realities of our business and our customers, and he did so in a way that didn’t make me feel ashamed or put down. It was simply the truth.</p><p>I wasn’t willing to bet my bonus, my teammates’ time, or my customers’ experience on this fix, our ability to test the change quickly, or on the problem. We shipped Windows Server with that bug and as far as I know, no customer ever hit it.</p><p>That day, the VP demonstrated for me a key tenet: leadership means knowing when and how to ask the right question.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=baa0e872099c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s OK to be Funny at Work … if you’re Careful]]></title>
            <link>https://medium.com/@ma_harris1011/its-ok-to-be-funny-at-work-if-you-re-careful-bc5ce4f471f2?source=rss-8c7c910354a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc5ce4f471f2</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Mark Harris]]></dc:creator>
            <pubDate>Thu, 02 Feb 2023 00:03:04 GMT</pubDate>
            <atom:updated>2023-02-02T00:03:04.412Z</atom:updated>
            <content:encoded><![CDATA[<h3>It’s OK to be Funny at Work … if you’re Careful</h3><p>The year was 2003, and I was 31 years old and early in my career at Microsoft. I found myself participating in the executive review for Windows XP SP2, surrounded by my teammates, everyone in my management chain, and more, all the way to <a href="https://www.linkedin.com/in/jim-allchin-5102ba85/">Jim Allchin</a>, one of the founders of Banyan, a pioneer of networking, and the EVP of the Windows organization. On Jim’s right was the head of Windows product marketing, and on his left, the VP of Windows, <a href="https://news.microsoft.com/2000/02/16/the-motivator-behind-the-windows-2000-development-team/">Brian Valentine</a>. Everyone had a freshly-printed copy of our presentation on the table in front of them.</p><p>Rebecca Norlander led our pitch: a serious description of the state of security on Windows &amp; the work required to address it. Jim listened patiently. As soon as Rebecca finished he asked, “Who is responsible for this?” The product marketing VP turned and spoke up: “Jim, I think we are responsible. I mean, ‘we Microsoft.’ We have to own this security problem for the marketplace as a whole.” Jim looked at him a moment and sighed, “No, I get that. I mean ‘who gets fired if this goes wrong?’ Do I fire Brian?”</p><p>Brian, who had been heads down, studying the PowerPoint print out until this point, looked up at the crowd with sincere pain in his eyes, “<em>Please!</em>”</p><p>The room erupted into laughter. We addressed the question and went on with the meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xUkSmEc_V4RlDuu-" /><figcaption>Photo by <a href="https://unsplash.com/@callmefred?utm_source=medium&amp;utm_medium=referral">Call Me Fred</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Brian was well-known for his antics like riding a motorcycle through the hallway and <a href="https://youtu.be/_9pkVZPYNHk">doing an unreal Tommy Boy scene</a>. He had a way of using humor to defuse the intensity of our daily work that trickled down to the whole organization.</p><p>Over my career, I’ve often tried and failed to be that funny, but I’ve still found using humor to be effective at building relationships, reducing stress, and increasing productivity. I have also found it tricky to navigate, stumbling into culture, experience, and generational hot spots.</p><p>One of the biggest benefits of humor in the workplace is that it can help to build stronger relationships among team members. Laughter is a universal language that helps to break down barriers and create a sense of connection. When people share a laugh together, they feel more connected and are more likely to work together effectively.</p><p>Humor can also be a great stress-buster in the workplace. Laughing can be a great way to diffuse tension and create a more positive atmosphere. When people are feeling stressed (like in a review with your 3-levels-up-boss), a well-timed joke or pun can help to lighten the mood and make everyone feel more relaxed.</p><p>When people are happy and relaxed, they tend to be more focused and motivated. Even during a challenging time in your project, by using humor to create a positive and energizing atmosphere, you can help your team to stay motivated and focused — bringing better performance and more successful outcomes.</p><p>BUT <strong>be careful</strong>! Not everyone has the same sense of humor, and it can be easy to offend someone unintentionally. Here are a few strategies to help you use humor effectively in the workplace:</p><ul><li><strong>Know your audience:</strong> Before you make a joke, think about who you are speaking to and whether or not they are likely to find it funny. Avoid making jokes that could be offensive or hurtful to any members of your team.</li><li><strong>Use self-deprecating humor:</strong> Making fun of yourself is a great way to make others feel more comfortable and to show that you are not above criticism.</li><li><strong>Keep it professional:</strong> Avoid personal or off-color jokes. Stick to jokes and puns that are related to the work at hand.</li><li><strong>Avoid sarcasm:</strong> Sarcasm can be misinterpreted, leading to misunderstandings and hurt feelings.</li><li><strong>Be aware of your tone:</strong> Even if the words you use are not offensive, your tone can make all the difference. Be aware of how you are speaking and make sure that your tone is light and friendly.</li></ul><p>Humor is a powerful tool that can build relationships, reduce stress, and increase productivity in the workplace. You don’t have to be Steve Martin, but with by using humor effectively, you can help to create a positive and energizing atmosphere that will help your team to work together more effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc5ce4f471f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Problem of Tech Debt]]></title>
            <link>https://medium.com/@ma_harris1011/the-problem-of-tech-debt-adee03be8645?source=rss-8c7c910354a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/adee03be8645</guid>
            <category><![CDATA[tech-debt]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Mark Harris]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 15:51:44 GMT</pubDate>
            <atom:updated>2023-01-16T15:51:44.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUedvqIO__oHhjZagCUF0Q.png" /><figcaption>courtesy of DALL-E 2 — spinning your propeller hat</figcaption></figure><p>I’ve been waiting for <a href="https://www.nytimes.com/2022/12/31/opinion/southwest-airlines-computers.html">this article</a>. The news reports about tech debt at Southwest had to lead to this. In modern companies, technology has moved in the value stream from support to the core. Despite what you may have <a href="https://online.hbs.edu/blog/post/what-is-value-chain-analysis">seen in B school</a>, tech is a core piece of the value chain.</p><p>I’m proud to say I’m with a company that recognizes technology in the value chain, and because of that, I can see behind the headlines.</p><p>Software pros: How many times have you seen this in our industry? “<em>there are strong incentives to address any immediate problem by essentially adding a bit of duct tape and wire to what you already have, rather than spending a large amount of money — updating software is costly and difficult — to address the root problem.</em>”</p><p>I can hear the developers reading this: “That’s what I’ve been telling <em>the business</em> all this time!” “See? Southwest Airlines’ trouble is what happens when you ignore us!”</p><p><strong>That’s the lazy response. It’s too easy to blame “the business” for failing to invest.</strong></p><p>Too often, engineers use the phrase “tech debt” to mean “code I don’t understand &amp; didn’t write, so it needs wholesale replaced” or “not written in (my favorite/new-fangled framework), so it needs wholesale replaced” or “this solution is legacy and doesn’t help my career goals.” Our counterparts in corporate planning, HR, sales, marketing, support, finance, accounting, distribution, and procurement are on to us. They have been burned too often by investing &amp; then getting a solution that’s late or doesn’t work as advertised</p><h3>OK, Mark, if you’re so smart, what do I do?</h3><p>As technology professionals, we must safeguard the company’s technology <strong>to keep it relevant</strong>. That means doing your homework, stating your case, and continuing to work until the software <em>surpasses</em> what you need to succeed in your industry. You have to do the work to keep your solutions easy to update so they don’t become tech debt.</p><h4>I wish I could say it’s easy. It’s not, but it starts with speaking the language.</h4><p>Technical debt is software that no longer can be considered a value-add to your organization. What that means is that your technology has become a bottleneck in the company’s core value chain — it’s a liability rather than an asset. Your technology is holding up the delivery of value to your customers.</p><p>As technologists, we’re used to talking in terms of boxes &amp; arrows, technology lifecycles, subsystems, message queues, operating systems, clouds — all the tech stuff. The business doesn’t run that way. Fundamentally, businesses think in terms of return on investment, risk to revenue, and business operations. You have to frame your argument in those terms.</p><h4><strong>Ask Yourself</strong></h4><ul><li>What is the impact to the company goals, both short and long term?</li><li>What is the cost <em>and the benefit</em> in real terms to the company?</li><li>What is the impact to my customers, both internal &amp; external? Do they benefit? How?</li><li>What is the relationship of the cost to the benefit?</li></ul><p>Use those answers to craft your argument for the investment, or else, make the explicit decision not to invest, based on the data you collect. <strong>Either way, you’re making business decisions about your technology.</strong></p><h3>Business == Technology</h3><p>When you realize that technology <strong>is</strong> the business, you can make the right decisions to move your business forward with the technology. You’ll make arguments that your business function peers can understand and will back you in. Understanding what it means that technology is core to your value chain is the first step in keeping your technology relevant.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adee03be8645" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>