<?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 Adam Haeger on Medium]]></title>
        <description><![CDATA[Stories by Adam Haeger on Medium]]></description>
        <link>https://medium.com/@adam.haeger?source=rss-364be09e36ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RFTOzVDJkbFHOgCxDiQ6Dw.jpeg</url>
            <title>Stories by Adam Haeger on Medium</title>
            <link>https://medium.com/@adam.haeger?source=rss-364be09e36ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:14:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adam.haeger/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[The 3 main ingredients for turning around a doomed IT project.]]></title>
            <link>https://medium.com/@adam.haeger/the-3-main-ingredients-for-turning-around-a-doomed-it-project-13728224f1ee?source=rss-364be09e36ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/13728224f1ee</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Adam Haeger]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 18:57:48 GMT</pubDate>
            <atom:updated>2019-02-07T10:16:31.546Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to save your doomed IT project.</h3><p>In my <a href="https://medium.com/@adam.haeger/why-im-passionate-about-doomed-it-projects-f2e3e3339eef">previous post</a>, I told you all about the gems to be harvested from failed IT projects. Now I will break down for you how this can be done, starting at a birds-eye view in this post and drilling down further in the future.</p><h4>1. The Mission: Start with why</h4><p>If you find yourself in the midst of a doomed project, the first thing to figure out is why you should even bother saving it. Indeed, in some cases, the best course of action is to cut your losses and abandon the project all together.</p><p>Now if you find that this project is worth the investment to save (and you really have to dig deep to actually believe this yourself), it is of critical importance that each team member understands why this decision has been made.</p><p>As Jocko Willink lays out in the stellar leadership book <em>Extreme Ownership</em>, <strong><em>you have to</em></strong> <strong><em>make sure everyone believes in the “why,” understands the “why,” and then pursues the “what.”</em></strong></p><p>The consequences of ignoring this can be catastrophic. If people don&#39;t understand why they are being put through this ordeal, they will do all kinds of detrimental things. This includes actively working against the project, doing a half-assed job, badmouthing the project, the client and management, quit their job or refuse to work on the project. These things sound harsh. I have seen all of these things happen.</p><p>Now the thing is that they don&#39;t do this to be mean. They do it because they think it&#39;s the right thing to do. And if management either haven&#39;t found a good enough reason to soldier on, or if they&#39;ve done a poor job of communicating it, they may think it is their duty to stop the madness before it goes too far.</p><p>If you are a project member in the midst of a project gone haywire, you need to take responsibility for understanding why the project is worth saving. And don&#39;t stop until you get a satisfactory answer. This is your life, don&#39;t sell it cheaply.</p><h4><strong>2. The Vision: Figure out the success criteria</strong></h4><p>In the military, we had to walk. A lot. Sometimes we knew where we were going, sometimes we had no idea where or for how long. The psychological stress of not knowing for how long you are walking is terrible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CwhiWeFlbPjApxeCGxbunQ.jpeg" /><figcaption>If you have to climb a mountain, it helps to see the summit.</figcaption></figure><p>The people tasked with saving the project need to know exactly what goal they are working against. They need to know that there is a light in the end of the tunnel, and that they wont be stuck in the abyss forever. If the end is a long way away, break it down into milestones. Also make it clear to them that this work is very important and much appreciated. When milestones are reached, celebrate the victory. This helps increase ownership and will knit the team even tighter together.</p><h4><strong>3. The Values: Never, <em>ever</em> undermine the integrity of your team.</strong></h4><p>No matter our level of consciousness of it, we are all driven by virtues and values. These are the principles that we live after. Both as a leader and a team member, you should be very conscious of what you stand for.</p><p>As a leader, you should not allow any shortcuts or dishonesty to creep into your project. This will infest the project and create a culture of shortcuts. No matter what has happened in the past, now is the time to own up to mistakes, and set new standards for going forward.</p><p>If the team is forced to do things that conflict with their values, they will loose respect for their managers, and loose ownership over the project. These are exactly the kinds of things that makes team members look for other jobs (and rightly so).</p><p>As a team member you should never ever do anything that conflicts with your values. This undermines your personal and professional integrity.</p><p>If you as a team member feel you are being forced to do things that conflict with your values, now is the time to dig out your companies&#39; values. Most companies have these written down, very few use them actively, but they are there for a reason. Ask your managers how the decision in question align with their corporate values, and don&#39;t accept half assed answers.</p><p>There are no situations that are so bad that you are forced to lie or cheat your way out of. Consult with your team and find the right decision that you can all get behind. Honesty and hard work will prevail no matter what, and if you violate this you will be found out, or the consequences will not be worth it.</p><p>These topics boil down to three things, Mission, Vision and Values. They will keep you on track to turn the project around. The Mission is why you are doing this, the Vision is where you are going, and the Values is the moral integrity that you will deploy going forward.</p><p>If you can get these three things down, you are already on your way to successfully turning the project around. As I said, this is a birds-eye overview, I will break down each of these into concrete steps in the following posts so stay tuned, follow, like and share and I&#39;ll be back soon!</p><p>Cheers, Adam</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13728224f1ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I’m passionate about doomed IT projects.]]></title>
            <link>https://medium.com/@adam.haeger/why-im-passionate-about-doomed-it-projects-f2e3e3339eef?source=rss-364be09e36ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2e3e3339eef</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Adam Haeger]]></dc:creator>
            <pubDate>Sun, 03 Feb 2019 12:20:49 GMT</pubDate>
            <atom:updated>2019-02-07T10:15:48.944Z</atom:updated>
            <content:encoded><![CDATA[<p>The past 6 years I have been working as an IT consultant, which is a fancy way of saying that I’m a programmer for hire.</p><p>During this time I have seen my fair share of either failed or terribly underperforming projects, and the financial and personal consequences that follow. The most heartbreaking of those are the personal.</p><p>During the worst of these projects, I have seen working relationships blow up, people quitting, people being removed from projects and untold amounts of backbiting and resentment rise up in its wake. A doomed project is like a maelstrom that sucks people and resources into its shadowy void and, unless something is done, it can spread through an organisation like a disease. Alliances form, distrust of leadership arises and, most crucially in my opinion, people’s lives and their families suffer. In terms of money, I have seen millions, not to speak of the value of reputations and professional relationships.</p><p>And yet, these doomed projects are the ones that I’m the most proud of having been part of, and the ones I have learned the most from.</p><p>The reason? I had to learn, out of sheer necessity, the tools to create unity and direction for teams. This is a skill that is so powerful and fascinating it eclipses all my technical skills. With unified, goal oriented teams, anything is possible. Such teams allowed us to send people to the moon and form countries. And the silver linings of doomed projects are invaluable, if you manage to turn them around. And you can&#39;t afford not to.</p><h4>These are 3 of the priceless bounties of a doomed project turned around:</h4><h4>1. Extremely unified and high performing teams.</h4><p>Many of the team members from my doomed projects that was turned around are now very close friends of mine. These are people that I spent the majority of my waking hours with for periods of up to two years, and during this time they proved themselves as the most skilled, professional and trustworthy people that I’ve had the honour of working with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZPfGKnb6754ELJFIWAXGg.jpeg" /><figcaption>The best teams are the ones that have done the hardest work together.</figcaption></figure><p>These are people that I would truly cherish the opportunity to work with again. I know that they are rock solid and that if we ever worked together again, we would make an extremely effective team right off the bat.</p><p>Now, if you are a manager reading this and manage to turn around a project properly, you will end up with one of these teams as well. Just make sure you reward them properly so they stick around, these people are now highly prized assets on the job market.</p><h4>2. Massive amounts of learning.</h4><p>When you are in a doomed project, you are basically in a startup in the sense that you just have to solve the problems in front of you because time and human resources are usually extremely scarce.</p><p>That means you quickly have to adapt to new technologies and solve problems that are way out of your comfort zone. In one of my doomed projects, I had to learn how to deploy and manage a Kubernetes cluster serving production traffic for one of Norway’s most popular sites in a matter of weeks. I also had to step up from doing mostly developer tasks to doing way more high level architecture work. Last, but certainly not least, I had to figure out how to create a motivated team simply because that’s what the project needed.</p><p>These are skills that have accelerated my professional career and given me opportunities that would probably take me years to gain otherwise.</p><h4>3. Sense of accomplishment and meaning</h4><p>We all search for meaning in our lives, and in the technology sector it is not always easy to see the greater meaning in our work. But helping to turn around something that seems absolutely doomed into something that is thriving and still delivering value to people and customers to this day is something truly special. And the contrast of seeing a team that is completely disunited and one that is thriving and joyful at work every day is also something deeply meaningful.</p><p>So thats why Im very passionate about doomed IT projects, and maybe you should be too. Maybe embrace them as an opportunity to set something right in the world.</p><p>If you want to find out the three main ingredients to turn around a doomed project, check out my next post <a href="https://medium.com/@adam.haeger/the-3-main-ingredients-for-turning-around-a-doomed-it-project-13728224f1ee">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2e3e3339eef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>