<?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 Haavard Nord on Medium]]></title>
        <description><![CDATA[Stories by Haavard Nord on Medium]]></description>
        <link>https://medium.com/@haavardnord?source=rss-4365cb76e527------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qjVm26j-5oIcnQMH.</url>
            <title>Stories by Haavard Nord on Medium</title>
            <link>https://medium.com/@haavardnord?source=rss-4365cb76e527------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:02:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@haavardnord/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[Managing Incidents in Slack Teams]]></title>
            <link>https://medium.com/@haavardnord/managing-incidents-in-slack-teams-de0b7b03ca50?source=rss-4365cb76e527------2</link>
            <guid isPermaLink="false">https://medium.com/p/de0b7b03ca50</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Haavard Nord]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 13:47:57 GMT</pubDate>
            <atom:updated>2018-01-30T13:47:57.604Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QUmXFMO6lgFUvsap_FcYKA.png" /></figure><p>Conclude is on a mission to help growing organizations stay nimble. A little over a year ago we released a bot for Slack that helps teams achieve this goal by streamlining their decision-making.</p><p>Conclude quickly became one of the more popular bots for Slack teams and was installed by more than 4,000 organizations worldwide.</p><p>As teams adopted Conclude, we discussed plans to develop the product and reached out for feedback from our users. We quickly found teams were using Conclude for a variety of issues beyond decision-making. One user said:</p><blockquote>“While Conclude is probably great for making better decisions faster, we use it to bring people together to solve urgent issues. My job is to handle things when small and big disasters happen, and make sure the right people get involved in solving them and that we get a quick resolution.”</blockquote><p>Returning to our mission to help growing organizations remain agile, we reconfirmed Slack already provides a fantastic messaging tool that replaces email and shines in addressing daily operational communication. Yet urgent issues are easily lost in the noise of everyday operational chatter.</p><p>Many conversations over the past year gave us a deeper understanding of Conclude user needs on Slack. We decided to make a major change in Conclude. Call it a pivot.</p><p>Maintaining our initial assumptions, we’re taking user feedback to expand Conclude beyond decision-making. We decided to retire /propose and introduce <strong><em>/raise</em></strong> to bring up and tackle any issue that requires special attention.</p><p>Here’s an example: A large customer reports they cannot access your company’s booking service. After confirming the problem, you raise the issue with Conclude in your team’s #devops channel:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*2_Kg0K7pxbUbe1eP_kj4Qg.png" /></figure><p>Your devops colleagues Aaron and Sue will be notified immediately that there’s a message for them in Slack. Conclude points them to a dedicated channel that was created just for this incident. Aaron and Sue use this special channel to find and fix the problem. Sue closes the incident 10 minutes later:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*fqc7II5YcjR9fHHEVbbpYQ.png" /></figure><p>The conclusion is shared in the original #devops channel and the incident channel is archived.</p><p>Conclude is all about raising issues to the attention of your team, creating engagement, and helping the team to drive issues to conclusion. Introducing /raise is a major semantic change of Conclude that will help your team address small and big disasters in addition to decision-making.</p><p>Imagine all the different ways teams use Conclude.</p><p>In development:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*0GMJK0NMIcEKOZ3YWoJ5mw.png" /></figure><p>When closing sales:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*-Q-wCKZ08syuOk5gwD9SWA.png" /></figure><p>In public relations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*KmWA94ekXciC6isgjSHjuQ.png" /></figure><p>And even when exploring space:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*-5X1dnycjEWKyg_BPP9Z_w.png" /></figure><p>Learn more at <a href="http://www.concludebot.com/">concludebot.com</a> and feel free to drop us a line at <a href="/service/mailto:feedback@concludebot.com">feedback@concludebot.com</a> if you have comments or want to share how your team deals with issues and emergencies.</p><p>Happy raising!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de0b7b03ca50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rethinking decision-making]]></title>
            <link>https://medium.com/21st-century-decision-making-for-teams/rethinking-decision-making-e38a15fe6f69?source=rss-4365cb76e527------2</link>
            <guid isPermaLink="false">https://medium.com/p/e38a15fe6f69</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Haavard Nord]]></dc:creator>
            <pubDate>Tue, 27 Dec 2016 21:09:59 GMT</pubDate>
            <atom:updated>2021-11-26T13:22:55.848Z</atom:updated>
            <content:encoded><![CDATA[<p>The secret to improving the efficiency of distributed teams is to rethink how decisions are made and shared.</p><p>I recently shared my <a href="https://medium.com/21st-century-decision-making-for-teams/painful-lessons-from-scaling-a-software-company-1d14ee7f9ab3">personal story</a> about the startup I co-founded, called Trolltech, and our exciting journey before Nokia acquired the company. Along the way we experienced the typical growth pains of scaling a tech company.</p><p>In the early days our company was small and incredibly productive - we got a lot of things done. An industry expert called us “<a href="http://linuxdevices.linuxgizmos.com/trolltech-aims-linux-qtopia-at-mobile-phone-market/">the little engine that could</a>.” With success came funding and growth, and as the company approached 200 employees we had offices on four continents and in five different time zones.</p><p>Over a few years Trolltech turned from a fast and forceful startup into a regular company that takes a long time to make decisions and carry them out. We had lost much of our speed advantage.</p><p>While working with numerous startups and growing companies over the last eight years I have seen the same pattern repeat itself.</p><p>When a company reaches a certain scale it takes a lot of energy to maintain focus and structure. Anthropologist Robin Dunbar suggests that humans can maintain about 150 social relationships (<a href="http://en.wikipedia.org/wiki/Dunbar&#39;s_number">Dunbar’s number</a>) due to our limited cognitive capacity. So when a company outgrows the size of a tribe we invent certain mechanisms and structures to cope.</p><p>One traditional structure is to implement a strict hierarchical organization with management at the top and unskilled workers at the bottom, and a thick layer of middle management to keep the structure together. Decisions are made at the top of the organization and executed at the bottom, while reporting goes the other way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5g8iU8b_UJ1mfloCynsULw.png" /><figcaption>Type 1 Decision System</figcaption></figure><p>These hierarchical organizations tend to be slow at making decisions and have little room for risk-taking or experimentation. This may work for steel producing giants, but most organizations living in the competitive 21st century will be outpaced by the competition if they are rigid and cannot adapt.</p><h4>Type 1 and 2 decisions</h4><p>In the modern organization it is common to organize in autonomous teams consisting of highly educated workers. Decisions are made and carried out by the team members. Jeff Bezos talks about <a href="http://www.businessinsider.com/jeff-bezos-on-type-1-and-type-2-decisions-2016-4">type 1 and type 2 decisions</a> that describe the differences in decision making for large organizations (type 1) and for smaller teams (type 2), and Carl Parker Jones takes the concept further when he talks about <a href="http://medium.com/21st-century-organizational-development/type-2-organizations-df3f1f53c66c">type 1 and type 2 organizations</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJzHQXECiKoQXqHY34CY9w.png" /><figcaption>Type 2 Decision System</figcaption></figure><p>In the team-based organization it is the job of management to orchestrate the teams and pull them in the same direction. Communication between teams is vital for them to stay in sync and work towards the same vision. A great deal of the communication inside the team is about making everyday operational decisions. Inability to make operational decisions impacts execution and slows down the team. Sound familiar?</p><p>We have limited cognitive capacity. Unless a super-pill was invented that made it possible to maintain more than 150 social relationships and keep track of hundreds of concurrent conversations, we will remain challenged and stressed. Unlike the traditional hierarchical organization, the modern organization lacks a clear structure for communication and execution. So we fight to keep our inbox empty and make sure we have no unread Slack messages to catch up with. <a href="http://www.urbandictionary.com/define.php?term=fomo">FOMO</a> has officially entered the workplace.</p><p>We’re always behind and live in a constant state of overload.</p><p>Is it possible to build a distributed company with 300 or even 3000 people, and make it as agile and nimble as a startup? Can we put technology at work to fight the constant overload that makes teams dysfunctional? Email and messaging as we know it create even more noise.</p><h4>Enter Conclude</h4><p>I set out to explore this about a year ago together with serial entrepreneurs Ståle Løvbukten and Ivar Kroghrud. They have a similar story to mine, where they built the companies Questback and Admincontrol to become dominating companies in their respective markets. The three of us have a burning ambition to put passion and fun into work, and let people spend more of their brains on interesting things rather than drown in <a href="https://hbr.org/2016/01/collaborative-overload">collaborative noise</a>.</p><p>So the three of us created the startup <strong>Conclude</strong> last year to solve this big hairy problem. We started out with three decisions:</p><ol><li>Focus on decision-making for distributed teams.</li><li>Not “yet another tool”.</li><li>Keep it simple, stupid.</li></ol><p><strong>Focus on decision-making: </strong>Why focus on decisions/conclusions? Because a decision is the single most important piece of information in the plethora of chatter that is flooding organizations trying to succeed in a type 2 organization reality. It’s the DNA of what’s really going on. We’ll let other tools focus on project management and the TODO list.</p><p><strong>Not “yet another tool”: </strong>We decided to integrate Conclude closely with the popular messaging tool <a href="http://www.slack.com/">Slack</a> in such a way that it becomes a natural part of the team’s workflow. It should take less than 15 minutes to learn and get started with Conclude. After all, we want to reduce noise and make life easier, not introduce “yet another tool” for the teams to learn.</p><p><strong>Keep it simple, stupid:</strong> Conclude is a simple bot that helps facilitate a straightforward process to make a decision and later share the conclusion with the team. You can invite colleagues to give you input (or to anchor the decision with), you can set a deadline, you can later share or export the conclusion. Conclude will gently notify the team members about the discussion and push towards conclusion.</p><h4>Conclude at work</h4><p>Here’s a real life example of how we used Conclude recently. I wrote the following in our Slack marketing channel:</p><blockquote>/propose Should we use Wix or Squarespace for our new web? @ivar @mrleafbay @asbjorn @natalia</blockquote><p>Concludebot created a temporary channel in Slack called <em>marketing-proposal-18</em> where we could discuss the topic, outside the daily marketing team chat.</p><p>A notification was sent to four of my colleagues who needed to be involved. The rest of the team could ignore the discussion and focus on other things.</p><p>We had a fruitful discussion about website builders, and after some time of inactivity Concludebot reminded me it’s time to conclude. I concluded on the matter based on the input from the team and the temporary discussion channel was automatically archived.</p><blockquote>/conclude We’ll use Wix to build the new web; it has everything we need and a few of us have experience with the tool.</blockquote><p>Concludebot shared the conclusion with the rest of the marketing team, and pointed to a <a href="https://app.concludebot.com/app/feed">conclude page</a> for details.</p><h4>What’s next</h4><p>Conclude was recently featured as one of top three apps for Slack and more than a thousand teams have installed Conclude so far. Over the next few months we’re planning to roll out new functionality based on input from our users. Feedback from our early adopters say we’re on to something truly helpful for teams that value agility.</p><p>Check out Conclude for yourself: <a href="http://www.concludebot.com/">www.concludebot.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e38a15fe6f69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/21st-century-decision-making-for-teams/rethinking-decision-making-e38a15fe6f69">Rethinking decision-making</a> was originally published in <a href="https://medium.com/21st-century-decision-making-for-teams">Conclude: Turning conversations into conclusions</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Painful Lessons From Scaling a Software Company]]></title>
            <link>https://medium.com/21st-century-decision-making-for-teams/painful-lessons-from-scaling-a-software-company-1d14ee7f9ab3?source=rss-4365cb76e527------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d14ee7f9ab3</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Haavard Nord]]></dc:creator>
            <pubDate>Wed, 07 Dec 2016 11:25:33 GMT</pubDate>
            <atom:updated>2016-12-07T11:25:33.225Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in the 90s in college I started writing a software development framework called Qt. After graduating I teamed up with my buddy Eirik Chambe-Eng to found the company Trolltech. Our dream was to develop Qt from a tiny college project into a commercial product and make a serious impact in the software development world. We wanted coding to be filled with passion and fun, and not having to deal with obscure toolkits and libraries and spend half a day to write “Hello, World!”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*8Veaw7yAMtMWDxXE1TNCzQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*tYo1sg62GDR3vQ8u_ePPBw.png" /><figcaption>The Trolltech founders in the early days</figcaption></figure><p>Over the years Qt became one of the world leading software development frameworks and is today an industry standard for creating apps across a wide variety of platform (www.qt.io).</p><p>Most startups fail. Why did our company succeed? In addition to having a team of superstar developers at Trolltech, I believe a potent mix of luck and smart decisions helped propel Trolltech and Qt to “world domination”.</p><p>One of the benefits of being a small startup is that you can make decisions fast and start implementing them right away. When we were a handful of developers making Qt we decided to license the product under a commercial as well as an open source license. Helped by this dual licensing business model Qt quickly became the de facto standard for development on Linux. Another great decision was to enter into the embedded device market and turn Qt into a framework for consumer devices and industrial appliances. At the time we made these decisions we were only about 10 people in the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*4rYlDLKhCySB28HXN7sLqA.jpeg" /><figcaption>Christmas party 1997</figcaption></figure><p>In 1999 Trolltech started to get lots of attention among investors and we were fortunate to receive $8 million in funding in early 2000, just before the dot-com bubble burst. The funding took us into another phase of growth. In 2000 we quadrupled the size of the company and soon opened offices on four continents. I brought my family from quiet and comfortable Oslo to Palo Alto and started to hire people and build up sales- and marketing. Until this point we had no sales function and took orders over email or a fax machine.</p><p>As the company grew it became more difficult to make decisions. I’m not talking about large strategic decisions but also everyday operational decisions in sales, marketing, product management or in development.</p><p>Our management team was spread across three continents and many decisions required that we involved people on the US West Coast, Norway and Australia. timeanddate.com’s worldwide meeting planner was our best friend. Our Monday morning call usually started at 6am GMT (= 7am in Oslo, 4pm in Brisbane and 22pm Sunday evening in San Francisco). Goodbye work-life balance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pkHa3dWP_BwiatRwYiBqOw.png" /></figure><p>To collaborate over the oceans we primarily used email, but also Skype, IRC and of course phone calls. Today we probably would have used Slack a lot. A recent <a href="https://hbr.org/2016/01/collaborative-overload">article</a> in Harvard Business Review states that it is common to spend 80% of your time communicating and collaborating with your team, so-called collaborative overload. Based on my own experiences I think this number is fairly accurate.</p><p>A great deal of time was spent making decisions. A decision that earlier had taken minutes to make now took days. When someone needed a decision they typically started an email discussion. The discussion could go on for days until it either died or someone was able to drive the decision to a conclusion. Quite often discussions would resurface a few months after they had gone quiet and we had to start the discussion from scratch.</p><p>If you needed a quick decision it was easier to not involve people in the other offices, even if you knew they had relevant input for the matter you needed to conclude on. Quite often such a shortcut led to conflict and could consume days of cleanup.</p><p>As the organization approached 200 employees we gradually implemented more processes and routines (a.k.a. operational excellence) and made us even slower in making and implementing decisions. Several of the engineers were unhappy that Trolltech had turned into a regular company with pointy haired bosses and ineffective execution. (They quickly forgot this after Nokia acquired Trolltech in 2008 and bureaucracy invaded the company and drove things to a halt.)</p><p>It is very common for growing companies and distributed teams to go through these problems, especially when scaling. The noise level increases and developers can easily spend more time on Slack or email than writing code.</p><p>After my journey with Trolltech and a 10-month short stint at Nokia, I got a lot of time to reflect on building and scaling startup companies. What could we have done different with Trolltech? Is it possible to build a distributed company with 300 or even 3000 people, and make it as agile and nimble as a startup?</p><p>Can software help reduce the noise in collaboration? Slack certainly reduces the amount of email, but it you’re away from your team for a day you come back to 315 messages you should probably read to see what you’ve missed. Can we put deep learning and automation to work to help reduce the noise?</p><p>Stay tuned and I’ll come back to this soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d14ee7f9ab3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/21st-century-decision-making-for-teams/painful-lessons-from-scaling-a-software-company-1d14ee7f9ab3">Painful Lessons From Scaling a Software Company</a> was originally published in <a href="https://medium.com/21st-century-decision-making-for-teams">Conclude: Turning conversations into conclusions</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>