<?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 Anders Haugeto on Medium]]></title>
        <description><![CDATA[Stories by Anders Haugeto on Medium]]></description>
        <link>https://medium.com/@haugeto?source=rss-4c414ee3465d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*W7PDXxeFXil3ijr_.jpg</url>
            <title>Stories by Anders Haugeto on Medium</title>
            <link>https://medium.com/@haugeto?source=rss-4c414ee3465d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:23:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@haugeto/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 new AI Paradigm]]></title>
            <link>https://blog.venturemagazine.net/a-new-ai-paradigm-13437da9148f?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/13437da9148f</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 05:03:19 GMT</pubDate>
            <atom:updated>2026-06-03T23:41:20.258Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Mountain, the Logic, and three Parameters</h4><p>“Have you heard about Tsetlin Machines” my friend asked me. At 2600 metres altitude, I was out of breath. He was not. “No. Should I have?”. Last summer, on our annual family EV road trip through Europe, little did I know what this rendezvous in the Pyrenees would bring.</p><p>In the 1960s, the mathematician Michail Tsetlin invented a simple learning algorithm. Half a century later, the researcher Ole-Christoffer Granmo took inspiration from it and showed how it could be used to build a fully functional pattern recognition algorithm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VyVP1stMh_Xb2BTo.jpeg" /></figure><p>It works very differently from how most of us have learned to think about AI. With limited resources, the researcher and a small group around him have been able to show early, but steady progress towards what could become a new paradigm in AI. As versatile as neural nets, but potentially out-competing them on every parameter:</p><ol><li>It uses very low amounts of energy</li><li>It is inherently logical, meaning that it recognises a cat by its fur, whiskers and purr and absence of a mane, rather than a list of abstract numbers</li><li>It’s readable and explainable after training. Every prediction comes with an explanation that humans can verify, and it can continue to learn from mistakes</li><li>It requires much less training data</li><li>It’s fast</li></ol><p>In this post, I’ll explain why these parameters matter to all of us, and how they constitute a new dimension of competition, disruptive to today’s AI paradigms. I’ll show how they show a path forward that’s smarter, more sustainable, and more reliable for everyone. Not just as a technology, but also in its adoption and as a force in the world.</p><p>Today, AI can already do remarkable and impressive things, and it shows that humans are able to build very powerful artificial intelligence. However, current AI systems have some deep, structural problems that are not likely to be solved through continued development of our current regimes.</p><p>Overall, these problems come down to three parameters:</p><ol><li><strong>Energy Use:</strong> Today’s AI uses neural nets that require staggering amounts of compute. Training costs have grown an order of magnitude with each new generation of frontier models, and there is no sign of that curve flattening. Training and running ChatGPT at current scale consumes electricity comparable to the annual consumption of a small nation.</li><li><strong>Data Use:</strong> The same neural nets require vast volumes of data to be trained to a viable level of accuracy and capability. That data comes from everywhere: harvested from any kind of source, often without clear consent or attribution.</li><li><strong>Opacity:</strong> Neural networks may produce a lot of answers, but they cannot explain their own reasoning. Decisions emerge from billions of weighted parameters that no human can trace, audit, change or challenge.</li></ol><p>The first order effects are immediately problematic:</p><p>High energy use makes an energy hungry world even more energy hungry, drives up electricity prices, releases unnaturally warm cooling water into natural ecosystems, and drives CO2 emissions. It’s not sustainable.</p><p>High data use results in high energy use, but it also creates a legal and ethical minefield around copyright, privacy, and ownership that the industry has not resolved, that has the potential to blow up in massive legal battles and public backlash. Moreover, having to train our models on all kinds of data, means we include data that’s not precise, false, opinionated or for other reasons not something we want at the core of an AI that’s scaled up to evaluate, reason and make choices on our behalf.</p><p>Opacity means we cannot trust our models and it limits our understanding of them. If we can’t trace how a system arrives at its conclusions, we’re left guessing at its behavior and reacting to surprises instead of anticipating them. Scaling up the use of an AI we cannot fully trust creates the risk of adding more complexity, more work, more risk and new kinds of trouble to all the larger problems we’re already struggling with.</p><p>As concerning as these issues are, what concerns me even more are the second order effects they create:</p><p>An AI with these characteristics can only be scaled up by centralising its infrastructure: On a physical level, we need very large data centers, with high and reliable access to electricity. It’s expensive. It demands large scale investments that can only be backed by large and powerful companies or governments. This means that as adoption spreads, the substantial economic and strategic interests we all put into our use of AI gets concentrated in a few organisations and the persons controlling them. Such concentration creates an imbalance between supply and demand, where market forces cannot be expected to function. (While a winner-takes-all strategy isn’t new, the moats of today’s big AI companies run much deeper than usual. Airbnb didn’t set out to build their own nuclear power plants in order to scale).</p><p>Any deep concentration of power is a threat to modern, liberal society, and this includes systems and infrastructure that are supposed to be open, contestable, and accountable. When the use of such infrastructure proliferates, they become too big to fail, and this further distorts the mechanics.</p><p>We can illustrate the consequences by contrasting today’s AI with another invention that was scaled up in a very different way, but still had the same level of transformative effect on society. The internet is a technology we all use, it holds great business opportunities, it has been subject to many investments — but nobody owns or controls it. Incidentally, it also paved the way for AI.</p><p>Easily taken for granted, the Internet was designed in an ingenious way that made possible both extreme scalability, widespread adoption, and massive human collaboration. This was all achieved because the Internet is built on a <em>distributed</em> infrastructure. Any exchange of data is facilitated by open and shared protocols designed for resilience: If a router goes down, you won’t even notice it, because your data automatically finds a different route. This design has created a versatile economy and ecosystem that was built on freedom of experimentation, diversity of contribution, low barriers to entry and a lot of voluntary and entrepreneurial creativity.</p><p>Today’s leading AI paradigm, in contrast, has a very different dynamic. Here, a few big AI companies are becoming the de facto platform for innovation where most innovators and entrepreneurs today have no alternative but to become “wrappers”: They innovate around an LLM they don’t own. The underlying technology they depend on could change its behavior, pricing, access, compute power, or capabilities at will, and they would have little or no leverage to push back, and the few alternative platforms they could go to behave in the same way. This lack of sovereignty applies to any system, company or government incorporating such AI into their operations.</p><p>Instead of settling for this, I think we should rather view today’s AI, and all its impressive features, as a <em>stepping stone</em>. In parallel, we should be exploring and developing new architectures that, like the Internet, are more democratic, understandable and sustainable in nature.</p><p>This takes us back to our parameters:</p><p><strong>An AI that uses significantly less energy</strong> doesn’t need centralised compute. Without this, there will be no need for actors that own and control the infrastructure. Instead, it can evolve in tandem with users and stakeholders. (Imagine a generative, agentic AI you could use or integrate in your innovations, where you pay a fixed monthly price no matter how much you use it)</p><p><strong>An AI that uses much less data</strong> and could learn online after its initial training, doesn’t need to be uncritically trained on every bit of data we have, regardless of quality. We could be conscious and selective about what we put in, and scale <em>that</em> up instead.</p><p><strong>An AI that can explain itself</strong> could show both its developers and users why it reaches its answers. We would know immediately when to rely on it and when not to. This trustworthiness is what enables true adoption, the kind where we put it to good use. We would immediately be able to see where we don’t want to apply it, where it isn’t ready, and where human judgement is favorable and superior. And conversely: It might also be more acceptable for us to take its answers seriously when they are inconvenient, but true. (Imagine an AI with a verified value system for safeguarding human interests, advising us on how to create policies and strategies for growing the economy without depleting all our natural resources).</p><p>In sum, when the parameters allow the AI to <em>run anywhere,</em> be trained <em>on the right data,</em> and be <em>transparent and verifiable,</em> we have an AI that can scale beyond hypes, and be used to build strong, long-term businesses and institutional longevity.</p><p>The idea Mikhail Tsetlin had in 1961, that the Norwegian researcher Ole-Christoffer Granmo quietly spent more than a decade developing, was an AI with binary and logical operations that align naturally with digital computer hardware. This explains why energy consumption plummets to roughly four tenths of a percent of a comparable neural network. And it’s the logical nature of the model that allows it to explain itself. Leading practitioners of Tsetlin Machines also point out another thing that makes the algorithm so attractive to them: It’s <em>simplicity</em>. In an already overly complex world, that might just be what we need.</p><p>It struck me on the mountain: Could this be just the parameters we need? I had to find out. Our venture is committed to researching and exploring the full scaling behavior of Tsetlin Machines, and building an AI platform for anyone who wants to use this new AI architecture. At the same time, we hope more researchers and creators will work on either Tsetlin Machines or other new architectures. And beat today’s AI, in all dimensions.</p><p>AI is not going to disappear. We could dismiss it as hype, hope the bubble will burst and bring back the world as we used to know it. This is very unlikely to happen. And if it doesn’t, we will have wasted precious time.</p><p>I think we should view today’s AI as a stepping stone for invention, innovation and opportunity, a prototype of what the future might hold. Hopefully, it’s a future where technology is built to serve our common interest.</p><p>New regimes don’t emerge by themselves. They will only succeed if we step up to find them and build them.</p><p><em>If you’re curious about where this all leads, Iterate with partners is building GreenLogic, a European AI venture for research, product development and commercial scaling of Tsetlin Machines. Our goal is sustainable, sovereign and assured intelligence, for everyone.</em></p><p><em>Thx, Ole Christoffer Granmo, Andreas Hafver, Svein Olaf Olsen, Jørn Knutsen, Kim Leskovsky, Rune Larsen, Julius Telaranta — and all my fellow creators, creatives, builders and entrepreneurs at </em><a href="https://iterate.no/"><em>Iterate</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13437da9148f" width="1" height="1" alt=""><hr><p><a href="https://blog.venturemagazine.net/a-new-ai-paradigm-13437da9148f">A new AI Paradigm</a> was originally published in <a href="https://blog.venturemagazine.net/">Venture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The AI productivity struggle is not about AI]]></title>
            <link>https://blog.venturemagazine.net/the-ai-productivity-struggle-is-not-about-ai-c932c7c76453?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c932c7c76453</guid>
            <category><![CDATA[disruption]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 10:56:26 GMT</pubDate>
            <atom:updated>2025-12-13T14:30:45.940Z</atom:updated>
            <content:encoded><![CDATA[<h4>A primer to Organisational Longevity</h4><p>Imagine you’re in a company experiencing rapid market change, challenged by new competitors with innovative products and business models. You’re at risk of becoming <em>disrupted</em>, unless you innovate yourself.</p><p>You have a choice between two AI projects. Both cost €1 million to implement.</p><ul><li><strong>Project A</strong> will give you a return of €1,1 million</li><li><strong>Project B</strong> will give you a return of €50 million</li></ul><p>Obviously, Project B is the best choice. But what Project will your organisation choose?</p><p>The answer is not as straightforward as you’d think. In this post I’ll show why <a href="https://fortune.com/2025/08/18/mit-report-95-percent-generative-ai-pilots-at-companies-failing-cfo/">the struggle to adopt AI in most organisations</a> doesn’t revolve around AI. It revolves around what projects we choose to implement. I&#39;ll show why so many organisations choose the wrong projects, the deeper thinking that&#39;s at play, and what we can do change our ways.</p><h4>Markets that don’t exist cannot be analysed</h4><p>The term <em>Disruptive Innovation</em> was made famous in <em>The Innovator’s Dilemma</em> published in 1997 by the late Clayton Christensen (Harvard Business School). He analysed why incumbent companies so often fail in competition from new and innovative products, and how the pattern repeats itself over industries and decades, from steel mills, to hydraulic lifters, to harddisks to Gasoline Cars — from the early 1900s up until today.</p><p>Christensen writes he initially thought the companies that got disrupted just had bad management. But he soon discovered this was not the case. On the contrary, management was competent, responsible and acting in accordance with established principles of well managed companies.</p><p>However, when it came to innovation (or lack thereof) that also turned out to be the problem. As he explained:</p><blockquote><em>The best-run companies fail, not because they’re poorly managed, but because they are </em>too well<em> managed to innovate. (Clayton Christensen, Innovator&#39;s Dilemma)</em></blockquote><p>Think about it: Market leaders have a lot at stake. Ran by responsible people, they are drawn towards protecting what they have. Why would they want to pursue high risk endeavours, that on one hand are unpredictable and unlikely to give any meaningful returns, and on the other hand could cause them a lot of trouble? It&#39;s not attractive. Market leaders have instead learned to value stable conditions, efficient operations and tight control.</p><p>As Christensen explains, there is nothing wrong this. Except one thing. It doesn’t work with innovation. Here, we’re supposed to:</p><ul><li>Develop inferior, new products with defects, inefficiencies and lack of functionality, and sell them to our customers.</li><li>Invest in new opportunities that seem small, have no clear market and no track record of success.</li><li>Allocate resources into something unknown and unknowable.</li></ul><p>Of course we don’t. No responsible company would. Right?</p><p>But the world around us changes. It brings about competing products, trends or infrastructures that our current capabilities were never built for. Now, in the age of AI, change goes even faster.</p><p>By doing the right thing, by staying the course, we risk going down the wrong path. We get <em>disrupted</em>, quite possibly in a well-managed way.</p><p>The alternative is to go with the very projects we have learned to avoid. So what do we choose? Go under, or break our principles? This is in essence the Innovator’s Dilemma.</p><p>Is there an other way, where we can stay true to ourselves <em>and</em> succeed with innovation?</p><h3>Building companies that last forever</h3><p>In 2003 the CEO of a successful gaming company pondered what to do, after realising they were losing business to competitors, who had developed products with better performance. Everyone expected him to focus his resources on improving their capabilities — to catch up. But he didn&#39;t. Instead, he started making changes to his products that his customers didn&#39;t care about, to serve a market that barely existed.</p><p>Was he foolish or strategic?</p><p>The gaming company was Nvidia. A backbone of today’s AI infrastructure, they are now one of the world’s most valuable companies. This was not the case back in 2003. Losing badly to competition, CEO Jensen Huang made a crucial architectural decision: Their GPUs would use <a href="https://stratechery.com/2022/an-interview-with-nvidia-ceo-jensen-huang-about-manufacturing-intelligence/">32-bit IEEE compatible floating point</a>, which was not a gaming industry standard, but it was better suited for <em>general-purpose</em> computing.</p><p>It didn’t help them win the gaming war. But it created space for something else: It enabled researchers to use their hardware. The decision seemed odd, because this “data science” and “AI” was all very niche. But Nvidia saw a learning opportunity. They wanted to see where it could lead. Later, when deep learning came, and ChatGPT some years on, they found themselves at at the epicenter of a revolution.</p><p>He was not foolish. He was strategic. About <em>Options</em>.</p><h4>Optimising for renewal</h4><p>When change goes faster and faster, companies have to optimise along two two dimensions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KVaXhDJeWbz2gAVr.png" /><figcaption>Expiry Unknown: We don’t know when our Capabilities go bad</figcaption></figure><ol><li><strong>Capabilities</strong> enable us to be in business: Products, organization, systems, work processes, and IP that deliver value to customers right now. <em>For Nvidia in 2003: Their Gaming GPUs.</em></li><li><strong>Options</strong> enable us to do something different tomorrow: Opportunities within reach given our current constraints, like new markets, adjacent markets, new revenue streams, and substantial productivity gains. <em>For Nvidia: The change to 32 bit floating point, opening up their products for general use.</em></li></ol><p>Both Capabilities and Options work as feedback loops. When a capability starts performing, we optimise it by capturing larger market shares, reducing cost and increasing margins. We allocate resources and build our brand and reputation around it. It becomes self-reinforcing.</p><p>The same goes with Options: When we get good at discovering opportunities, we tend to find even more opportunities. As we experiment, we build skills and confidence in exploring the unknown. We develop networks and relationships that surface new possibilities. The more options we pursue, the better we get at recognising their potential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*STe9BXusyEz974_K.png" /></figure><p>Capabilities and Options are interdependent. Successful development of an option turns it into a capability. But there’s also a reverse relationship: Developing a capability <em>weakens</em> our options.</p><p>This is because capabilities make us accountable: They come with commitments that tie up resources and focus. This narrows down our space of opportunities. We can’t go out and do random things. We have things at stake, and much to lose.</p><p>An organisation can only be good at what it does regularly. In today’s organisations capabilities are the comfort zone. They’re what we’re trained to develop and maintain. Working on options is less common. In most industries companies spend <a href="https://ec.europa.eu/eurostat/statistics-explained/index.php?title=R%26D_expenditure&amp;utm_source=chatgpt.com">less than ~3% of revenue on R&amp;D</a> overall, and far less on true exploration. It means we don’t on a regular basis test and learn, iterate fast, and slice and sequence work into small packages that drive business outcomes, one increment at a time. This lack of innovation know-how further reduces our options.</p><p>However, in a fast changing world, our capabilities can start their decline any time. Hence, we need options to survive. Which leads us back to our two AI projects.</p><h4>Project A or Project B?</h4><p>Most organisations will choose Project A, the project that gives only a 10% return. They choose it, <em>because </em>it has a small margin. They avoid Project B <em>because</em> it’s so valuable. Here’s why:</p><ol><li><strong>Focus: </strong>If Project A slips by just 10% on time or cost, it&#39;s a loss. Hence, it requires tight execution and control, otherwise we shouldn&#39;t do it. The paradox, however, is that the more we focus on the control regimes we need to make such projects successful, the more likely it is that we&#39;re also focusing on such projects.</li><li><strong>Catch-22:</strong> Moreover, tight control regimes often can’t handle high-value projects. They typically kill them from the get-go by demanding upfront answers to questions that can only be found through testing and iteration, which wont happen unless the project is started.</li><li><strong>Mindset:</strong> We’re assume Project B is more risky because it has a higher upside. But innovation doesn’t work like traditional investments. You don’t invest €1 million upfront. You invest €50,000 to explore whether Project B has potential. You talk to users, build prototypes and run experiments. You learn. If it fails, you’ve lost €50,000, not €1 million. Innovation is staged (you can even explore several investments in parallell).</li></ol><p>Wait, we&#39;re not done yet. There is one more reason why so many organisations go with Project A, and it eclipses all the other reasons.</p><p><strong>They primary reason they choose Project A is that they are unaware of the existence of Project B.</strong></p><p>They are unaware of Project B because they don’t explore their options<em>.</em></p><h3>Change the success criteria</h3><p>In capability-optimised organisations, success means delivering predictable results in a controlled, stable and efficient fashion.</p><p>So what about discovering an option, or creating the conditions for the organisation to find its best options? Will that make a board member, manager or employee equally successful?</p><p>In most organisations, the answer is no. The reason is simple: To explore options, we also have to make <em>learning about the unknown</em> an equally legitimate measure of success. If you want innovation to happen on purpose, as an integral part of your strategy, this change needs to come from the top.</p><p>It can be very powerful: When Satya Nadella took over as CEO at Microsoft in February 2014, the company was in serious decline. Microsoft was caught up in old products and systems, unable to respond with the innovations markets wanted. This complacency had created a “know-it-all” culture. Nadella famously stated that Microsoft now has to become a “learn-it-all” company instead.</p><p>He started doing his own experiments, then told his direct reports what he had learned. He expected them to do the same with their direct reports, and so on, until the practice proliferated across the corporation.</p><p>The transformation was remarkable: Microsoft embraced cloud computing with Azure (now generating over $33 billion quarterly), opened its platforms to competitors like Linux and Apple, acquired LinkedIn and GitHub, and partnered with OpenAI to lead in AI. These were innovations that would have been impossible under the old siloed, Windows-centric know-it-all culture.</p><p>Microsoft’s market cap grew from around $300 billion in 2014 to over $3 trillion, surpassing Apple as the world’s most valuable company in January 2024.</p><h3>Getting Started</h3><p>There is also a more practical side to Options. To find and qualify our “Project Bs”, we need to increase the bandwidth of our search. This is what the options loop as all about.</p><p>How do you get full bandwidth? You empower the <em>organisation</em> to explore:</p><ol><li><strong>Pre-authorise learning initiatives:</strong> Enable people to do small-scale, low cost experimentation without having to ask for permission or approval.</li><li><strong>Allow parallell development:</strong> Allow new initiatives to be built on the side of existing systems. Establish policies and guides, but don’t require green light from the functions they will depend on long-term. Provide easy access to resources and data.</li><li><strong>Use Autonomous Teams:</strong> Use cross-functional teams that have the know-how to explore and build without having to ask for help or approval. Provide metered funding, that corresponds to the business value they create.</li></ol><p>It has several advantages:</p><ol><li>People who want a project to happen must first validate key assumption about it. The decision process becomes both educational and, frankly, fun, for everyone.</li><li>Bringing real-life data about proven business impact, gives significantly higher accuracy when deciding on what big bets to go for</li><li>People step up and take more responsibility for value creation, when they’re actually asked to do it.</li></ol><p>It’s the responsibility of management to decide which options to develop further, and which ones to leave behind. By allowing their organisation to do the exploration, to be creative, they get more comprehensive strategic insights, that will help them make much better choices.</p><p>When they do want do double down, they will have a decisive advantage over those new companies trying to disrupt them: Once an option is validated, they can scale up faster and more effectively than any startup. They already have customers, distribution, brand recognition, capital and operational capacity. Startups must prove the concept <em>and</em> build the scaling capability <em>and</em> fundraise <em>and </em>convince the world they are for real. (It begs the question whether today’s incumbents are making it unnecessarily easy for the startups to disrupt them).</p><p>To get started with options we need to learn to use new practices, to work together in new ways, and to see our organisation and the outside the world in new ways. This requires a change in mindset, a <em>cultural change</em>. A fast-track to making this happen is to <strong>mix people and cultures</strong>. Bring in people from a culture that has already done it. Ultimately, you’d like them to have an entrepreneurial background, and <em>also</em> know their way around established organisations. Use such cross-pollination to build your new culture — bottom up.</p><h3>How far could it go?</h3><p>Established companies aren’t just businesses. They are part of the structures that shape how our economy and society function. If they weaken and lose trust, it makes society more brittle.</p><p>AI raises the stakes by challenging the premises of our capabilities faster than ever. In this environment, continuity comes from renewal, not preservation.</p><p>AI won’t save an organisation that can’t renew itself. But an organisation that can will thrive through any technological wave. That’s the real productivity unlock.</p><p>How far could this go if we succeed? Imagine your company is able to renew itself faster than the rate of external change. It can live forever. This is called <em>Organisational Longevity, </em>a larger topic that I will cover in my coming posts.</p><p>In the meantime: Open up. Stay curious. Build options.</p><p><em>Credits: Features / Options: Kent Beck. Project A, Project B: Tom DeMarco</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c932c7c76453" width="1" height="1" alt=""><hr><p><a href="https://blog.venturemagazine.net/the-ai-productivity-struggle-is-not-about-ai-c932c7c76453">The AI productivity struggle is not about AI</a> was originally published in <a href="https://blog.venturemagazine.net/">Venture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Next Nvidia Will Start Without a Vision]]></title>
            <link>https://haugeto.medium.com/the-next-nvidia-will-start-without-a-vision-87d038171ae6?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/87d038171ae6</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Tue, 04 Mar 2025 06:02:38 GMT</pubDate>
            <atom:updated>2025-03-04T06:02:38.899Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Successful Businesses Become Visionary Companies</h4><p>In the late 2000s, many organisations introduced Agile methodologies: Daily stand-up meetings, backlogs, sprints and much more. Inspired by how some super-innovative companies worked, the belief was that the company and its people would become as innovative —if they could follow the method in a “proper” way.</p><p>Then, a post world war II phenomenon from isolated pacific islands showed why this was the wrong focus. It&#39;s know as a <strong>Cargo Cult</strong>, and refers to islanders building bamboo airplanes and control towers, while mimicking the operations of military airfield ground personell.</p><p>Having received gifts and formed connections with soldiers during the war, they had started mimicking their actions, hoping it would bring these benefits back. That copying observed practices would give a desired outcome.</p><figure><img alt="A bamboo airplane from post World War II Cargo Cults of the pacific" src="https://cdn-images-1.medium.com/max/1024/1*5UtPC20OyOIGt4OQpbCPFA.jpeg" /><figcaption>Copying what you see isn’t enough to make it fly</figcaption></figure><p>The islanders were just human. Cargo cults are everywhere. Agile methodologies became the bamboo airplane supposed to summon the company back to its younger, faster and more innovative self. It didn&#39;t fly. The companies that succeeded changed their technology, their organisation and their culture — they went far deeper than superficially copying observed behaviours.</p><p>Today I&#39;d like to discuss another popular methodology: Defining a Vision Statement with the belief it will turn you into a visionary company.</p><h3>Strategy will take you a long way</h3><p>When companies first succeed, it&#39;s because of the right strategy and execution. They use a good market understanding to create a product customers want, grow revenue, hire the right people, and keep the company alive and thriving. This is an achievement in and of itself: Building any kind of business is hard. Very few make it. All hands.</p><p>Many also have vision / mission statements used for communication, in sales, marketing, recruitment, fundraising and so on. They can be used to reach short-term goals, but it’s important to understand that these statements don&#39;t in and of themselves make you visionary. Moreover, when it becomes a trend to communicate like this, when “everybody” has a vision, it becomes diluted.</p><p>What concerns me more is the incentive to jump to conclusions: The moment you embark on an exercise to “define the vision”, you cannot come back without an answer. If would be like stating out loud you have neither direction nor purpose. Hence, you have to return with clarity, conviction and commitment. The exercise becomes a negotiation over words (“can everybody agree to this?”), not a thoughtful dialog about who we are, what we aspire to and what next steps we should take to go in the right direction. Similarly to the feature factories of “agile” organisations, the vision / mission workshops are about outputs, not outcomes.</p><p>The result will at best do no harm, at worst it will limit your ability to communicate who you are and where you&#39;re going.</p><figure><img alt="An innovator on a vision quest in a desert" src="https://cdn-images-1.medium.com/max/1024/1*cOHzMyvSnuBcy9sqNLUyMA.jpeg" /><figcaption>A Vision? Simple: Go on a trip in the desert (Silicon Valley, TV series)</figcaption></figure><h3>Vision: An emerging force</h3><p>Peter Senge, a foundational thinker in modern leadership, describes vision as an <strong>emerging force</strong>. As a researcher at MIT, he studied <em>systems dynamics</em>: How complex systems, like human organizations, evolve over time based on feedback loops and interdependencies.</p><p>In his research he had seen a pattern: Many companies had clear goals, <strong>but their actions were still misaligned</strong>, leading to stagnation or even failure. The problem was a disconnect between leadership’s strategy and the thinking, understanding and aspirations of their employees.</p><p>Senge showed that organizations function more as living systems than structured processes and hierarchies (even when they present themselves as structured hierarchies). A Vision only works when it’s internalized by people at all levels, shaping their decisions and behaviours. It&#39;s not imposed, but <strong>co-created</strong>. It evolves with the people as they collectively gain new insights, through daily work and interactions.</p><p>From his book The Fifth Discipline (2006):</p><blockquote>“A shared vision is not an idea. It is not even an important idea, such as freedom. It is, rather, a force in people’s hearts, a force of impressive power.</blockquote><blockquote>It may be inspired by an idea, but once it goes further — if it is compelling enough to acquire the support of more than one person — then it is no longer an abstraction. People begin to see it as if it exists. (…) When people truly share a vision they are connected, bound together by a common aspiration.</blockquote><p>One of the most counterintuitive aspects of vision is that <strong>leaders don’t have full control over it</strong>. They can shape it and cultivate the right environment for it to emerge, but unlike ideologies (and methodologies) they cannot simply declare it into existence.</p><h3>Nvidia —A Vision 30 years in the making</h3><p>When Rama Akkiraju, VP of Enterprise AI &amp; Automation at Nvidia, took the stage at her 2024 <a href="https://tedai-vienna.ted.com/">TED Talk in Vienna</a>, she was asked how many in the audience might be using Nvidia technology. She didn’t hesitate:</p><p>“You are all using Nvidia.”</p><p>Today, Nvidia is shaping the future of AI but that’s not at all how they started. The company was founded in 1993 with a focus on graphics chips for gaming — a successful strategy that took them all they way to an IPO, but not yet a grand vision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cQ8EKwFybLw23AsB.jpg" /><figcaption>The original NVidia Geforce 256, marketed as “the world’s first GPU”. No one could have predicted how a graphics card company would become the backbone of an AI revolution</figcaption></figure><p>Their breakthrough came when researchers outside the gaming industry started repurposing Nvidia’s GPUs for AI and deep learning. Nvidia embraced the shift, collaborated with the researchers and adapted their technology. Among many other things it played a <a href="https://sloanreview.mit.edu/audio/ai-and-the-covid-19-vaccine-modernas-dave-johnson/">pivotal role in the development of vaccines used to end the COVID-19 pandemic</a> (There’s a fair chance we would still be in lockdown if not for the breakthroughs in protein sequencing and vaccine development, ultimately enabled by high-performance GPUs.)</p><p>By absorbing new impulses rather than confining themselves to an already successful mission, something much grander came into being (and yes, even after DeepSeek, they&#39;re still doing great). Their secret sauce was <a href="https://www.audible.com/pd/The-Nvidia-Way-Audiobook/B0DNRNV83B?source_code=ORGOR69210072400FS&amp;share_location=player_overflow&amp;overrideBaseCountry=true&amp;ipRedirectOverride=true&amp;ref_pageloadid=not_applicable&amp;plink=knbeHDA2MXcJPJ55&amp;pageLoadId=Owl352koYfzHULQs&amp;creativeId=292d6343-f11b-4bbe-a8a5-d4b7272abf61">openness to new ideas, ability to learn, and a relentless drive to eliminate the complacency of past success</a>.</p><p>It’s cool to be inspired by what big companies say — like grand statements about making the world a better place — just remember they often convey their famous statements <em>after</em> they have created visionary things. Steve Jobs infamous quote, “Put a dent in the universe” was formulated 10 years into the journey of Apple (Playboy Magazine, 1985). He had grand ideas all along, but he was able to pick, refine and implement the right ideas because he also was open to see how things evolved. He resisted the urge to define too much too early. It gave him and Apple repeated s<em>trategic success.</em></p><h3>Show, don’t tell</h3><p>When a company allows its vision emerge, they build several strategic advantages that are impossible to copy:</p><ol><li><strong>Connection</strong> — People feel connected to something bigger than themselves. They don’t just work for a paycheck; they work because they believe in something. This is the playground where people perform to the best of their abilities.</li><li><strong>Optionality</strong> — Openness attracts the right kind of people, customers and partnerships. Serendipity plays a major role in visionary companies, and this is becoming an increasingly important asset in an increasingly unpredictable world.</li><li><strong>Cultural Strength</strong> — A vision that emerges through dialogue and shared experiences creates a culture that is authentic, self-correcting and self-sustaining. Such culture also empowers and holds people more accountable to <em>all</em> outcomes of their work, including misuse of the innovation or technology they create.</li></ol><p>You have to own a vision, not just from stage, but in how you think and how you act. In visionary companies, people are collectively willing to take this responsibility. To do the things that are harder, more challenging, and have fewer short-term rewards.</p><p><strong>Start by having conversations</strong>, not exercises or workshops. Ask your people:</p><ul><li>What do they care about? What excites them?</li><li>What do they see as possible?</li><li>What&#39;s a step in the right direction, that they could make right away?</li></ul><p>Encourage everyone to have such conversations. Create an environment where people feel empowered to play, experiment and think big, but also take responsibility for improving what&#39;s around them, on an everyday basis. For building things that work.</p><p>Vision isn’t something you manufacture. By resisting the urge to lock things down too soon, you leave room for real aspirations to take root — not just at the leadership level, but across the entire organisation. Show the world who you are, through what you create.</p><p>In the meantime, focus on your customers: How you make their life easier and better in a way they are willing to pay for. <strong>Be proud of the business you’re building.</strong></p><p><em>Thx, </em><a href="https://medium.com/u/7690808826f"><em>Jonas Feiring</em></a><em> + everyone at </em><a href="https://medium.com/iterate-norway"><em>Iterate Norway</em></a><em> — past, current and future.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87d038171ae6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Value Methodology for innovators and entrepreneurs]]></title>
            <link>https://blog.venturemagazine.net/innovation-exploration-is-all-about-scale-4d7b6bbb7387?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d7b6bbb7387</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[pricing]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 14:48:12 GMT</pubDate>
            <atom:updated>2025-08-28T08:15:50.755Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing Business Canvas and faster learning cycles</h4><blockquote>“We have been missing one scaling train after another”.</blockquote><p>My client was having an epiphany. Torn and excited at the same time, they realised they had become victims of their own early stage success. Sure, they had a grand vision, they had early users, but they lacked the strategy for going above and beyond. They had become tactical beasts, and it was wearing them out.</p><p>It happens to many great innovators: They talk to customers, run fast experiments and build MVPs that validate their idea. Then they start going in circles and never get off the ground. <em>It happens because they have forgotten that early explorations isn’t about validation — it’s about getting to scale.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6xVkHnWBCGi-Gi--" /><figcaption>It looks cool but it&#39;s going nowhere. Photo by <a href="https://unsplash.com/@cdd20?utm_source=medium&amp;utm_medium=referral">愚木混株 cdd20</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Today we talk about the first phase of innovation or entrepreneurship as a discovery phase where we experiment and learn about <em>why</em> an idea is worth building. It&#39;s great for building both insights and connections, but it&#39;s easy to get stuck. My client had fallen in what I call “the concierge trap”, where they had continued for too long doing manual, behind the scenes services that simulated the future, scaled up product. They were all about tactics to learn, as opposed to strategy to scale.</p><p>The foundation of a successful scaling strategy is found in the <em>how much: </em>When you can express the problems you&#39;re solving for your customers in real numbers. How much do the issues you aim to solve cost them in time, money or missed opportunities today? How can you impact those numbers?</p><p><strong>These are the numbers you have to explore, because these are the numbers you are going to scale. </strong>My advice is to start gathering them from the first experiment you run.</p><p>This quantification also helps you nail the commercial model, where you usually will have to deal with an array of questions like:</p><ul><li>How to charge your customers</li><li>How <em>much</em> you should charge</li><li>How you convince customers to spend that money on you, and not someone else</li><li>How to respond when customers complain about the price, or say they have no budget for this, or they have no time for this, or that they will churn on you — even when <em>you just know</em> how much better off they’d be if they would use your solution</li></ul><p>It could also give you an edge over the incumbents: Most mature companies have a lot of data, but they rarely have it down to a level where they understand the value they bring to their customers — in numbers. Somewhere along their way they forgot or they stopped caring. (Meaning that established companies can unlock optimisation potential by re-discovering why customers are really using their products.)</p><p>Below is a simple recipe you can use to avoid the tactical learning traps, and get faster to scale.</p><h3>The Damage and the Value — How to get started</h3><p>To start learning in numbers, focus on two questions:</p><ol><li><strong>What is the damage:</strong> What is this problem costing your customer today in terms of direct costs or lost opportunities?</li><li><strong>What is the value:</strong> How could your solution address that damage? How can you express the value you bring by a function of time, money, risk or other another relevant quantity?</li></ol><p>Here I’ve arrived at a few simple steps that will help you get answers to these questions:</p><h4>1. The Damage: Quantify the Problem</h4><p>Begin by identifying the tangible costs your customers face. Think of this in two categories:</p><p><strong>Operational Costs:</strong> Direct expenses like labor, wasted resources, or inefficiencies.</p><p><em>Example: If your customer spends 30 hours a month processing invoices manually, at an average wage of $30/hour, the operational cost is $900/month.</em></p><p><strong>Opportunity Costs:</strong> Revenue or growth potential they’re losing by not solving this problem.</p><p><em>Example: A customer receives 500 leads per month, but the sales team can only qualify and follow up on 300 leads, leaving 200 leads untouched. On average, 10% of leads convert into paying customers, and each sales generates $5,000 in revenue. With 200 untouched monthly the damage equals 200 * 10% × $5,000 = $100,000/month in lost revenue.</em></p><p>Your solution may not be able to eliminate all costs, or capture all missed opportunities, but don&#39;t worry about that yet. At this stage, you&#39;re simply after what the damage looks like today. The damage can be in absolute numbers, or it can be a function (in the latter example, it would be a function of leads received).</p><h4>Using GenAI to design experiments</h4><p>This is an area where I’ve found Generative AI to be quite useful, by asking about the numbers. As we all know, the LLMs make mistakes, so we still have to experiment. Nevertheless, they are trained on vast amounts of our combined knowledge, and their answers can be an improved starting point for experimentation, because <a href="https://www.reforge.com/blog/ai-native-product-teams">they can ideate and suggest multiple starting points and also help us go more in parallell</a>. (They can also reason on the terms of the customer, or simulate angry customers. It&#39;s fun.)</p><p>Say you have an idea for making customers more productive or efficient. Here’s an example prompt that might give you a hypothesis to test:</p><blockquote>“I’m building a solution for [customer segment], who I believe have issues with [Problem statement]. Who will be impacted by these problems in the customer organisation? How much time do they spend on dealing with these problems every [time unit]?</blockquote><h4>Experiment to Validate Assumptions</h4><p>The next step is to validate your estimates in real-world experiments. The design of these experiments depends on the nature of your value propositions and solutions. Be creative, but make it fast.</p><p>One example can be a pilot study: Temporarily implement your solution, manually or a with an early “duct tape” version of your product, with a pilot group and measure the positive impact it makes. If your solution reduces invoice processing time by some ratio, you can use the Damage Numbers to calculate how much you can save your customer each month.</p><p>You can also ask potential customers questions like “How many hours per week does your team spend on [specific task]?”.</p><p>Calculate what they could save, and ask them for feedback on that calculation. Often, they will come up with more thoughts and problems once they see your back of the envelope numbers. Cross check with other representatives of the same customer. If they give inconsistent answers, don&#39;t stop until you arrive at figures they agree on (at this point, you have most likely also built a lot of trust in you and your mission).</p><h4>2. The Value: Strategise the solution</h4><p>Ideate how your product can impact these numbers. Go extreme first, and pretend your solution would completely eliminate unwanted costs, or fully capture lost opportunities.</p><p>Navigate from there until you reach a number that seems almost within reach. Discuss what this impact could be in the near term and in a scaled up future. Could it increase if you establish network effects? When you get enough data to train an AI? What killer feature could you build soon that would double the impact you&#39;re already creating? And so on.</p><p>Finally, tell potential customers about your new insights.</p><p>“Today, this problem costs you $1,200/month.”</p><p>“Our solution saves you $450/month, plus reduces errors by 100%, saving you an additional $300/month. That’s $750/month in savings.”</p><p>(“Sign here, and here — what&#39;s your invoice address? Hm hm” )</p><p>This method works well for entrepreneurs, but it’s also useful for internal software- or IT-projects. Get faster to business value by establishing these figures as the primary driver of your software development process (the book <a href="https://www.google.com/search?q=Software+by+Numbers+book&amp;rlz=1C5CHFA_enNO987NO987&amp;oq=Software+by+Numbers+book&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIICAEQABgWGB7SAQgxNjg0ajBqMagCALACAA&amp;sourceid=chrome&amp;ie=UTF-8">Software by Numbers</a> is an oldie but goodie).</p><h3>The Business Value Canvas</h3><p>At <a href="https://iterate.no/">Iterate</a>, we have created The Business Value canvas to help ventures and clients nail it before they scale it. We&#39;re now inviting more innovators to use it and give us feedback on how it works and how much impact it creates.</p><p><a href="https://forms.gle/tWuhU3XFPDjtKHSW8">Follow this link to download it (PDF</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odYmVB3gkiHen5U4lI2ydw.png" /><figcaption>Start exploring your business opportunity and scaling strategy today</figcaption></figure><p>Quantifying business value is both a tactic and a mindset. It forces you to focus on what truly matters to your customers and it gives you the tools to turn ideas into strategies. The secret to scaling your idea is to find out how much it is worth.</p><p>This post had a 6 minute reading time. Thank you for the quantified feedback. Oh, and: You can hire me and my co-workers as a coach or advisor to get you going on <a href="/service/mailto:sales@iterate.no">sales@iterate.no</a>.</p><p><em>Thx, Fredrik Pettersen, Sigve Barstad, </em><a href="https://medium.com/u/7690808826f"><em>Jonas Feiring</em></a><em>, </em><a href="https://medium.com/u/15e80a52575a"><em>Stephan Granhaug</em></a><em>, </em><a href="https://medium.com/u/332b040f144e"><em>Kim Ophus Leskovsky</em></a><em> and </em><a href="https://medium.com/u/a8ff3eaa42c"><em>Kent Beck</em></a><em>.</em></p><p><em>Exploration, Expansion and Extraction are the main phases of a product life. Understanding the unique challenges of each stage, and the transitions between them is called </em><a href="https://medium.com/@kentbeck_7670/the-product-development-triathlon-6464e2763c46"><em>3X Thinking</em></a><em>.</em></p><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><ul><li>Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏<strong>️️</strong></li><li>Follow us: <a href="https://x.com/inPlainEngHQ"><strong>X</strong></a> | <a href="https://www.linkedin.com/company/inplainenglish/"><strong>LinkedIn</strong></a> | <a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong>YouTube</strong></a> | <a href="https://newsletter.plainenglish.io/"><strong>Newsletter</strong></a> | <a href="https://open.spotify.com/show/7qxylRWKhvZwMz2WuEoua0"><strong>Podcast</strong></a></li><li><a href="https://cofeed.app/"><strong>Check out CoFeed, the smart way to stay up-to-date with the latest in tech</strong></a> <strong>🧪</strong></li><li><a href="https://differ.blog/"><strong>Start your own free AI-powered blog on Differ</strong></a> 🚀</li><li><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Join our content creators community on Discord</strong></a> 🧑🏻‍💻</li><li>For more content, visit <a href="https://plainenglish.io/"><strong>plainenglish.io</strong></a> + <a href="https://stackademic.com/"><strong>stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d7b6bbb7387" width="1" height="1" alt=""><hr><p><a href="https://blog.venturemagazine.net/innovation-exploration-is-all-about-scale-4d7b6bbb7387">Business Value Methodology for innovators and entrepreneurs</a> was originally published in <a href="https://blog.venturemagazine.net/">Venture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI Workers will Transform Knowledge Workers]]></title>
            <link>https://blog.venturemagazine.net/how-ai-workers-will-transform-knowledge-workers-45c531b6bf89?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/45c531b6bf89</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[knowledge-workers]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Tue, 13 Aug 2024 06:33:33 GMT</pubDate>
            <atom:updated>2024-08-14T19:01:51.284Z</atom:updated>
            <content:encoded><![CDATA[<p>Afraid AI will steal your job as a knowledge worker? It will. But not the way you think.</p><p>First, have you thought about what steals your <em>productivity</em> today? Here’s a trap you’re most likely in already:</p><p>Say you’re building a new product. It’s a success, and your company needs to hire more and more people to keep up with growing demand. It’s exciting to have new co-workers come in and help the climb, but a larger organisation also has its downsides.</p><p>You get more teams, more departments, more rules, hierarchy and bureaucracy, and <em>a lot</em> more meetings. <a href="https://medium.com/@haugeto/scaling-up-the-fight-for-a-product-mindset-2945d83b69fa">Your innovative edge starts to diminish</a>: Dealing with the <em>organisation</em> takes more of your time, and everyone else’s time, leaving less time for everyone to work on the actual <em>product.</em></p><p>Hence<em>, </em>the more success you have — the less productive you become.</p><h4>Organisational complexity</h4><p>It’s not just you. Organisations today are on average<a href="https://www.youtube.com/watch?v=Dzv1s38f6Co"> 35 times more complicated than they were 50 years ago</a>, which far exceeds the corresponding growth of complexity in the economy.<a href="https://sloanreview.mit.edu/article/unpacking-the-ai-productivity-paradox/"> Human productivity is steadily decreasing</a>. Prevailing organisational blueprints and management practices seem unable to turn it around. Why is that?</p><p>There are many forces at play. Here, we’ll take a look at how knowledge workers are increasingly engaging in complex problem solving, which creates an almost indefinite need to stay informed, aligned and coordinated.</p><p>In<a href="https://en.wikipedia.org/wiki/The_Mythical_Man-Month"> The Mythical Man Month</a>, published back in 1975, Fred Brooks pointed out common management fallacies in software engineering projects. When projects were falling behind, the solution all too often was to add more developers, hoping it would speed up progress. Usually, it had the opposite effect.</p><p>Brooks asked himself why, and realised that when adding more people, you also add more communication channels (in software engineering, work cannot be perfectly partitioned into discrete tasks. Directly or indirectly, everyone on the project has a dependency to everyone else).</p><p>It’s called Brooks’s law, and it points out that the number of communication channels in an organisation grows exponentially with the number of people:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9YzHmn4mqaERIiKy" /></figure><p>Hence, even if you grow linearly, hiring the same amount of people every year, knowledge workers will still see an exponential growth in organisational complexity — and a corresponding decline in productivity.</p><p>Hang in there — I believe this is about to change.</p><p>When it does, it will be good news not only for product developers, but for knowledge workers in general. It will also be good news for humanity and the planet. Here’s why:</p><h4>More Productivity for the greater good</h4><p>The global economy is not sustainable and needs to change faster than what we see happening today. A big blocker are old systems and industries that resist change. Here, innovation is a “David and Goliath” power tool that has shown time and time again <a href="https://haugeto.substack.com/p/rethinking-impact-how">how it can overturn even the most invincible giant</a>. New innovations that drive circular economy models, democratisation, renewable energy, socio technological shifts and other disruptions are examples of what ideally all knowledge workers should focus all their time on. (My humble opinion.)</p><p>It boils down to smart people working in the right way on the right things. Speed up knowledge worker productivity, and you will speed up positive change.</p><p>One way we could seriously speed up knowledge worker productivity is to reduce organisational complexity. And what&#39;s the most straightforward way to reduce organisational complexity?</p><p>Reduce the <em>sizes</em> of the organisations themselves.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/jazzfall/status/1636107218859745286%3Fs%3D46&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/39e4facc37508874fd1ab7e41e09e760/href">https://medium.com/media/39e4facc37508874fd1ab7e41e09e760/href</a></iframe><p>Imagine a new and innovative product that needs an organisation of about 2000 people in order to scale up and establish itself as a market leader. According to Brooks’s law, 2000 people result in 1.999.000 communications channels.</p><p>Now, say we found a way to build the same product with <em>half </em>the number of people. That would require a 1000 person organisation, with 499.500 communication channels — one fourth of the original number. Hence, by cutting the organisation in half, we reduce the complexity at least 4 times, giving the people in the organisation a potential to quadruple their productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rxg9LMmruiTN7wdA" /><figcaption>Org charts always look so clean and logical, so I asked DALL-E to illustrate all the hidden communications channels in a company. It might be better depiction of everyday work life</figcaption></figure><p>How would this reduction impact the company and the economy?</p><p>The company would see simpler operations, lower costs of salary, higher profitability, happier and more productive employees — and by extension an even more innovative product. That all adds up to lower risk of building the company, and hence lower risk of innovation.</p><p>Lower risk of innovation, in turn, will have a huge impact on the economy.</p><p>If many companies, eventually <em>all</em> new companies are able to achieve this, it will compound: When innovating and building new companies becomes less risky and more profitable, they will become more attractive as an asset class to invest in (they may also be less dependent on capital, because they have profits that could be reinvested into more research and development).</p><p>The converse effect is perhaps even bigger: The old companies, with their resistance to change, will struggle to keep up, and they can’t necessarily compensate for shortage of innovation by acquisitions, like they do today, because this problem is within. It isn’t with what they’re lacking (what they can buy) but rather deeply entangled with who they are and how they operate. Keeping up will require deep transformations, that in turn will increase their risk profile and make them less attractive for investments.</p><p>Hence, capital will start migrating from preserving the old industries towards building new industries instead. Innovation will still be risky, and startups will still fail, but for new companies, the playing field will become more level than what it is today. More new products and services will emerge, new market opportunities will be created faster, and it will build a foundation for even more new businesses and industries to form.</p><p>That in turn, creates jobs. Hence, those 1000 workers, who were never hired by our example organisation, will see many new opportunities to join other, similarly high productive companies. It could become a virtuous cycle that creates a smarter, innovation-driven economy, that boosts speed of change, to the benefit of everyone.</p><p>The question that remains is how: How can it be possible to slash the need for people in half? Could we reduce it even further?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OA6PC03nGilvz1rb" /><figcaption>A startup <a href="https://x.com/MaxBrodeurUrbas/status/1800621062776074477">had their intern build an invoice processor in 2 hours on Gumloop</a>, an AI agent orchestration platform. Now, they use GPT-4o to analyse receipts sent to their Gmail, extract vendor + amount, categorise it, add it to their database and text their finance admin</figcaption></figure><h4><strong>The AI enabler</strong></h4><p>We’ve all heard about AI and its potential to help or alleviate work that is currently carried out by people. Here, I’d like to shed some light on an emerging field within AI called <em>Guided AI Workers</em> and the productivity gain inherent in this “half machine half man” technology. (By the way: The use of AI is a vast topic that also has its dilemmas with energy use, data infringement and ethical issues, but that’s out of scope for this post.)</p><p>This is how ChatGPT defines them (with some edits from me):</p><blockquote>Guided AI workers are AI systems or agents that assist and augment human workers in performing complex tasks. Operating under human supervision, they provide support in areas like decision-making, process automation, and problem-solving. By handling repetitive and data-intensive tasks, they free up human time and allow humans to focus more on higher-value activities.</blockquote><p>These workers are at an early stage, and have a way to go before we see them everywhere. If you’re in a large organisation, don’t expect to bump into a bunch of them at the office any time soon. However, to understand their potential, we can have a look at how smaller organisations are leveraging them already.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dxo4wA_xs-97f8d1.png" /><figcaption>Another entrepreneur <a href="https://bettermarketing.pub/ai-is-running-my-seo-blog-heres-the-growth-so-far-33d2a436f3a4">used an AI agent to create content for the company blog</a>, building a foundation for organic, search engine optimised traffic to his website</figcaption></figure><p>Take any small business (SMB), in travel, ecommerce, beauty, pets or really whatever category. Apart from the core service offer, these companies also have to engage with social media followers, track competitors, manage search engine optimization, write newsletters, manage invoices, optimise stocks and much more. Today, they can use guided AI workers to do a lot of this work for them, and they don’t have to build and train these workers themselves. They can hire them directly from companies like <a href="https://techcrunch.com/2024/07/09/with-6m-in-seed-funding-enso-plans-to-bring-ai-agents-to-smbs/">Enso</a>, a tech startup that offers industry-specific AI workers trained to help small companies.</p><p>NFX, a venture capital firm, has stretched the AI worker challenge to its extreme, by asking when we will see the first unicorn, a company with revenue of more than $100 million, employing<a href="https://www.nfx.com/post/3-person-unicorn-startup"> only three people</a>? While this may not be a model for every future company, it’s a mental challenge we shouldn’t laugh at. With the current rate of development within the AI field we will see such companies. The question is when.</p><p>In innovation, complexity is both a curse and a blessing. Complexity in a market is a blessing, because it creates opportunities to innovate by streamlining, simplifying or bypassing. Complexity inside a company, however, is a curse, because it degrades productivity and introduces additional operational risks and costs.</p><p>The moment technology like guided AI workers can start alleviating this, by reducing the size of companies, the companies that hire and operationalise them will be the winners. When it happens, we will face more than just a technological upgrade; we will face a paradigm shift in what work looks like and in what humans collaboratively can achieve together.</p><p>We will see smaller, more agile organisations with happier and more productive employees spending more time, perhaps all their time, on the right things. We will see more new ventures, fuelling the right kind of economic change and growth.</p><p>We can even hope to see society transform faster than what we believe to be possible today.</p><h4>.. and the software engineers?</h4><p>So what about the productivity of the software engineers themselves? Do today’s generative AI tools point to any potential for guided AI agents in this field?</p><p>The boost in developer productivity today is not as much as you’d think. While the tools are great, the lack of performance improvement in engineering shouldn’t come as a surprise given what we already have established: Today, boosting the productivity of the software engineers doesn’t revolve as much around the tools. Why? Software developers today spend less than half of their time coding. Most are down to coding just ⅓ of their time. What does the rest of their time go to? It goes to dealing with that increasingly complex organisation.</p><p>Imagine what would happen if it didn’t.</p><p><em>Thx — Mathias Hov, Pernille Wangsholm, Arne Tonning, Sagar Chandna, Martin Sletten, Dag Strømme.</em></p><p><em>Based on learnings from our work at </em><a href="https://iterate.no/"><em>Iterate</em></a>, a<em>n innovation ecosystem.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45c531b6bf89" width="1" height="1" alt=""><hr><p><a href="https://blog.venturemagazine.net/how-ai-workers-will-transform-knowledge-workers-45c531b6bf89">How AI Workers will Transform Knowledge Workers</a> was originally published in <a href="https://blog.venturemagazine.net/">Venture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We’re not telling you how to start a venture]]></title>
            <link>https://blog.venturemagazine.net/were-not-telling-you-how-to-start-a-venture-8205c9de23cc?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8205c9de23cc</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Tue, 25 Jun 2024 07:03:09 GMT</pubDate>
            <atom:updated>2024-11-21T10:56:53.093Z</atom:updated>
            <content:encoded><![CDATA[<h4>It&#39;s common sense</h4><p>Have you ever wondered why balance bikes have become so popular for kids? Whatever happened to training wheels? The answer also answers a question we sometimes get at Iterate: We’re an employee-driven venture builder, but we’re not telling employees how to start a venture. Why?</p><p>In Iterate, employees can spend overhead time between projects to incubate ideas and build venture teams. When they get market traction, we spin them out as founders of their own tech company. Today, after 8 years of venture building we have a portfolio of +30 tech companies, we’re on FastCompany’s list of <a href="https://haugeto.medium.com/how-do-you-build-a-world-class-workplace-for-innovators-524a8f5f99f3">Best Workplace for Innovators</a>, we’ve become co-invested with the world&#39;s best investors and most importantly: We see an investment portfolio that creates growth and positive change.</p><p>Our recipe? It&#39;s not a rigid process. Rather, we&#39;re building what we have learned to be more fundamental success factors for innovation:</p><ol><li><strong>Time to ponder:</strong> There’s a strong mantra in the startup ecosystem to establish focus: But what if a more important problem, or a better solution to that problem is around the corner? What if your understanding of the market opportunity isn’t sufficient enough for you to know the best way to solve it? In short, what if the strong focus you’ve worked so hard to establish turns out to be the wrong focus? Brilliantly described in his classic talk about<a href="https://www.youtube.com/watch?v=Pb5oIIPO62g&amp;ab_channel=VideoArts"> Creativity in Management</a>, John Cleese emphasized the importance of <em>time to ponder</em> with ideas, even stupid ideas, before making a decision. We’ve seen the same: Fast execution is great, but only if we understand the opportunity.</li><li><strong>Time to build a team:</strong> Too many great startups with great products fail because of dysfunctional founding teams. Most startup founders don’t spend time together and don’t get to know each other before they found a company. It easily leads to catastrophic founder breakups. We have seen that when we make it possible for innovators to try out different teams, some will move around before they find their place. Letting people row together before crossing an ocean together is a way to build strong and aligned teams.</li><li><strong>Test of entrepreneurial talent:</strong> Eric Ries has famously said that entrepreneurs are everywhere. But how do you find them? It’s not necessarily about current knowledge or experience. People who are able to create something new and make it work in the real world, need other abilities, such as continually challenging themselves and developing how they see and understand the world. The first test to this entrepreneurial talent is simple: Who takes the initiative to do something with an idea? We have been surprised by the randomness of who rises to the occasion and succeeds to go from play to execution.</li></ol><p>In Iterate, starting a venture is voluntary and the timing is completely up to the employees. The only thing we say is what we’re looking for in the long-term:</p><figure><img alt="Flow Technologies Screenshot from App doing patient followup" src="https://cdn-images-1.medium.com/max/1024/1*NylOgv2ukfAqmsbx2-DfMA.png" /><figcaption>Conceived as an online personal trainer platform, Iterate&#39;s venture <a href="https://en.flowzone.eu/">Flow Technologies</a> found a more important problem to solve: A fast and secure way to follow up and support patients at home</figcaption></figure><ul><li>Strong learnings from users and customers</li><li>Aligned founding team with a shared vision</li><li>Super high ambitions</li></ul><p>We have no documentation, process description, innovation framework, resource pool, Dragons Den or any other requirements, ceremony or help to get them started. Why is this?</p><p>Iterate originally started as an IT consultancy in a world stuck in rigid and complex project management practices. To find our way out of hierarchy, bureaucracy and outdated best practices, and towards real value creation, we looked for contrarian companies that could inspire us. The video conferencing company Tandberg (later acquired by Cisco) matched our criteria: They had world-leading products, despite long standing competition from much larger and more powerful companies.</p><p>Olve Maudal, a senior engineer who had earned the title Minister of Knowledge, told us how he had been surprised by Tandberg&#39;s unexpected ways of working, when he had first started in the company. As an example, he had observed a surprising lack of documentation, far less than what you’d expect from a leading software and hardware company at the time. Soon, however, he made observations about how people interacted and shared knowledge. It made him realize that lack of documentation wasn&#39;t a malpractice — but rather a conscious choice.</p><p>When people needed information in order to do their work, there was no comprehensive document archive or knowledge base for them to read. The only way forward was to engage with co-workers. And those co-workers, in turn, didn’t have a way to dismiss such interactions, because they didn’t have documentation they could tell them to read.</p><p>Hence, lack of documentation, something we’ve been trained to see as a <em>bad</em> thing, had a <em>good</em> side: It facilitated interaction, communication and networking between busy technologists, who otherwise would be inclined to work more in isolation. It helped them build a more dynamic organisation and culture that turned out to be a crucial component in their product development capabilities.</p><p>Over time, Olve identified several unique practices, and today we know them as <a href="https://www.youtube.com/watch?v=34FLhwkrwoQ&amp;t=1606s&amp;pp=ygUQdGhlIHRhbmRiZXJnIHdheQ%3D%3D">The Tandberg Way</a>. He realized something more: The leaders of Tandberg had never been very interested in so-called best practices for how to build and run a company. Instead, they had built a strong culture for using their <em>common sense</em> across the whole organization. The mindset, practices and processes that followed was the secret sauce to their unprecedented innovation capabilities. It was this simple mantra that ultimately had made them a market leader.</p><p><strong>We were deeply inspired.</strong> A decade later, when we started our expansion from consulting to building ventures, we remembered what we had learned at Tandberg. We decided to build ventures without an innovation process. Here&#39;s why:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PchuXFttOrk9-HM2.jpg" /><figcaption>The Iterate Venture <a href="http://vake.ai/">Vake.ai</a> is a space AI startup that started from a masters thesis supposed to collect dust on a book shelf. Acquired in 2024 by KSAT, a world-leading provider of satellite data reception (image: KSAT)</figcaption></figure><p><a href="https://www.leanessays.com/2020/05/whats-wrong-with-training-wheels.html">Mary Poppendieck has used the analogy of teaching children to ride a bicycle</a> to explain the problem we wanted to avoid: She points out how giving organizations <em>recipes</em> for doing something complex (going agile, innovating, transforming) is comparable to giving <em>training wheels</em> to children learning to bike. They will learn the easy part, which is to use the pedals (follow a process), but they will be prevented from learning the hard part, which is to keep their balance (get uncomfortable, learn and transform). Hence, her recommendation is to do the opposite. Give your people a “balance bike”, and they will initially <em>not learn to pedal at all</em>, but instead through trial and failure, they <em>will</em> learn to keep their balance. And, as with children, when they finally do get pedals, they will start using them correctly in an instant.</p><p><strong>This is what we wanted. To have our people play, try and fail until they find their balance and get moving. The first barrier they had to foresee was to <em>get started executing</em> without anyone telling them to do so.</strong></p><p>We still provide support to our innovators by trying to inspire them, helping them network and training them in new skillsets like customer discovery, product development, cross-functional team work and much more. There is however an important difference between mastering such skills and following a process: Skills don’t say anything about what to do or when to do it. Instead, they become like tools in a toolbox.</p><p>It resembles what great chess players do: They know everything about pieces, movements, tactics and strategies, but still every game they play is unique. The best players successfully combine their skills with their creativity to find new ways to win every time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bhdfQzfVpMN1PmxNOGmUbQ.jpeg" /><figcaption>Fantasy Chess is an Iterate Venture that started with our people exploring the world of chess together with Magnus Carlsen. Without any process, they had the first version of the game up and running in six weeks. <a href="https://www.forbes.com/sites/alexkonrad/2024/06/25/fantasy-chess-magnus-carlsen-startup-raises-millions/">A year later, renowned investors, including Peter Thiel, invested</a> (Image: Forbes)</figcaption></figure><p>From time to time employees ask us: Where can I read more about how to start a venture? When it happens, we seize the opportunity to ask a few questions back: Why do you want to know? Are you working on something new? Have you spotted an opportunity? The conversation that follows is an interaction that would easily not have taken place, if they had been able to find quick answers in a process description. It is also an incentive for them to get started trying and failing for real, by finding their balance out there in the real world, that they aim to change. Without a recipe to follow, action and learning is the only progress you can make.</p><p>Innovation is complex and non-repeatable, and every success will take a new path. This is why we’ve skipped the recipes. It took Tandberg to a $3 billion valuation when they were acquired by Cisco in 2009. It propels our venture portfolio forwards, with high performing teams in pursuit of original, scalable and sustainable tech companies. They have no training wheels. They&#39;re powered by common sense.</p><p><em>Thx Olve Maudal, for great feedback.</em></p><h3>Venture</h3><p><em>Thank you for being a part of the community! Before you go:</em></p><ul><li>Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏<strong>️️</strong></li><li>Follow us: <a href="https://twitter.com/inPlainEngHQ"><strong>X</strong></a> | <a href="https://www.linkedin.com/company/inplainenglish/"><strong>LinkedIn</strong></a> | <a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong>YouTube</strong></a> | <a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a> | <a href="https://newsletter.plainenglish.io/"><strong>Newsletter</strong></a></li><li>Visit our platforms: <a href="https://cofeed.app/"><strong>CoFeed</strong></a> | <a href="https://differ.blog/"><strong>Differ</strong></a> | <a href="https://plainenglish.io/"><strong>In Plain English</strong></a> | <a href="https://venturemagazine.net/"><strong>Venture</strong></a> | <a href="https://cubed.run/"><strong>Cubed</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8205c9de23cc" width="1" height="1" alt=""><hr><p><a href="https://blog.venturemagazine.net/were-not-telling-you-how-to-start-a-venture-8205c9de23cc">We’re not telling you how to start a venture</a> was originally published in <a href="https://blog.venturemagazine.net/">Venture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaling up: The fight for a product mindset]]></title>
            <link>https://haugeto.medium.com/scaling-up-the-fight-for-a-product-mindset-2945d83b69fa?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2945d83b69fa</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Mon, 22 May 2023 08:07:24 GMT</pubDate>
            <atom:updated>2023-05-22T09:44:42.442Z</atom:updated>
            <content:encoded><![CDATA[<p>Most successful tech startups fit this description: A visionary, motivated and (usually) cross functional team has been able to iterate quickly, and use what they learned to solve a customer problem in a new and innovative way. A key factor to their success is how they collectively think: They’ve developed a shared mindset that places customers and their needs at the center of all decisions related to what they build and how they build it.</p><p>It’s <em>product mindset</em> — a powerful way to work together on complex problem solving. If you&#39;re oriented towards iteration and learning, it may come naturally to you in the beginning. But to succeed Big Time you need to hang on to it in expansion: You need it to find the best, often unique, growth strategies, that help you go fast while at the same time using only the people and resources you need, while keeping complexity and technical debt at reasonable levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzKOplmKSNzyAPmU6272gQ.png" /><figcaption>In their first period of growth each person who joined product development at Notion had to know how to design, build UX <em>and</em> code. In October 2021 they reached a $10B valuation (still going strong in 2023)</figcaption></figure><p>A product mindset grows strong in companies that have a long term commitment to risk taking, experimentation and learning, and who have a widespread culture for curiosity, creativity and cross functional collaboration. Challenges we face in scaling, however, often steal so much focus from the product being scaled that our product mindset starts to deteriorate. As a consequence, we prematurely start to operate like established companies — before our product has become an established market winner. We loose momentum and stagnate. Here&#39;s how it goes:</p><p>An early version of our product hits the spot: we’re solving an important problem in a new and refreshing way that saves customers time and money. Now, they want more, competitors are around the corner and stakeholders are want to see traction towards exponential growth and beyond. To scale up our product, we have to scale up our organization. We need more capacity in product, design, development, customer success, marketing, sales, and so on. More customers, more features and more people, all at the same time. We probably need a bigger office space too.</p><p>And now we start to get into trouble.</p><p>We start receiving conflicting customer feedback. A few bigger customers start making special demands for product capabilities (it’s hard to say no, but it’s a path to outsourcing product strategy). It&#39;s hard to prioritise. Meanwhile, increased complexity in tech and product slows down speed of development. Back-logs are building up. Conflicts are on the rise between product, design, tech and business development. People are getting frustrated, confused or both. Out of this grows a strong push across the company to establish focus, so that each and every function gets to do more of their things: Sales and key account managers take over customer contact from product and design. Coders code, and stop engaging in product strategy and design work. Marketing runs campaigns by themselves. Customer support handles customer feedback. And everybody tells HR to hire the most experienced candidates, because nobody has time to train new hires.</p><p>Getting things done becomes more important than understanding whether things actually <em>need</em> to be done. Doing <em>my</em> part becomes more important than making <em>all the parts</em> go well together. Delivering becomes more important than iterating. In the silos that emerge, a conservative expertise-based thinking starts to take over from collaboration and learning.</p><p>We start missing out on key insights: What features that customers scream for are <em>really</em> needed, and which could we reject? What new features that <em>nobody</em> has asked for should we prioritize building <em>right away</em>? Are there new, big and shiny customers in the pipeline that we don’t want, or shouldn’t prioritize? What customer segments could get us to fully automated, product-led growth? Are new capabilities in competing products necessary in our product? Do we need more or less publicity? And much more.</p><p>In his book “Blitzscaling”, Ried Hoffman, the founder of LinkedIn, outlines the challenges and opportunities of rapid growth. He argues that <em>speed</em> is often more important than <em>efficiency</em> in the most expansive growth stages of a company, especially in fast-moving industries where competition is fierce. While his particular method isn’t necessarily relevant for every growth company, his thinking is: If you want to grow fast, you have to be careful with efficiency measures. Efficiency is about optimising the parts. If you do that without understanding the whole, it may look like you’re going faster, but that increased speed takes you in the wrong direction. Over time, a high level of efficiency has but one outcome: It solidifies the organisation, the operation and the thinking. Hoffman argues that by valuing speed over efficiency you retain fast decision making, rapid propagation of new learnings, and the agility you need to truly beat the competition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SOSHYM9ECrCA_MO1vC1U8Q.png" /><figcaption>Netflix is known for an uncompromising recruitment strategy hiring the most experienced people only. In Q3 2022, their revenue started to decline for the first time in 10 years.</figcaption></figure><p>So what do you do if you’ve already started to loose your product mindset? In The Hard Thing about Hard Things, Ben Horowizt has an inspiring story about how he solved a long running conflict between two departments: At his company Loudcloud, Sales and professional services had spun into bad dynamics, with sales always promising features that professional services couldn’t deliver, and professional services blaming sales for selling features that didn’t exist yet. Horowitz realized that the problem was with lack of perspectives of what the other department was doing, all the way up to the managers of each department. So he decided to swap them: Overnight, the manager of sales was made manager of professional services, and vice versa. The move was instantly effective in breaking down the silos between the departments and it enabled more collaboration, feedback and cross company learning.</p><p>His story illustrates what it takes to make people focus back on the product: It’s not about my function or my role: It’s about value creation for customers. Get stuck in one role for too long, and you stop seeing that bigger picture. (Or as they say: The first thing you need to do when your down in a hole, is to stop digging.)</p><p>It’s cross-functional work, where people value combined perspectives and new ideas as much as they value experience and deep expertise. It’s overlapping territories, where professionals are both allowed and expected to do work in each others fields. It’s aligned and motivated product and innovation teams.</p><p><strong>It’s culture building. And it needs fuel in the form of fast feedback loops, rapidly flowing learnings and a diversity of perspectives.</strong></p><p>In companies who want to strengthen their product mindset, I first look at how people energise: When people spontaneously come together in high energy conversations or discussions — are they talking about internal affairs (organisational changes, compensation, processes, tools, etc) or are they talking about the outside world (customers, markets, new opportunities)? Here, strong product organisations tend to be more “extroverted”: They care more about how they impact the outside world.</p><p>And speaking of backlogs: Long product backlogs is usually a sign that the product mindset is in distress. They are a symptom of an organisation that spends too much time making promises and speculating about the future. With precision insights on customer outcomes, backlogs tend to shrink, because what becomes the next feature is based on data on how the previous feature performed.</p><p>Below is a non-exhaustive list of other recommendations and suggestions on how to retain and strengthen your product mindset:</p><ul><li><strong>Continually align on the vision:</strong> Remind people why we&#39;re building this product, by emphasising how we are trying to impact our customers. Define strategies not in terms of vision, values and goals, but rather in terms of <a href="https://www.amazon.com/Good-Strategy-Bad-Difference-Matters/dp/0307886239">what obstacles we need to overcome, and how we can make our combined actions coherent and focused</a>. Put people who normally don’t talk to users and customers in front of them, by running <a href="https://www.uxsignals.com/">rapid, online user interviews</a>, spending time at customer service, representing your product at events and so on. Run sprints, like the <a href="http://www.gv.com/sprint/">GV Sprint</a>, on new feature sets and make sure to include all functions in the company on the team. New team for every sprint.</li><li><strong>Always evaluate: Speed or efficiency?</strong> Make this a steadily recurring discussion in management meetings and other arenas where priorities are made and expectations are set. Why are we prioritizing one or the other? What’s the balance between short term benefits over long term consequences? Start the discussion by aligning on where <a href="https://tidyfirst.substack.com/p/appreciating-your-way-to-xp">you&#39;re doing well</a>.</li><li><strong>Build organization, not territories:</strong> Beware of expertise thinking. Embrace the beginners’ mind and curiosity in other people’s fields. Build a rotation program. Always hire a mix of junior and senior people. Name contrian changes in management positions. Postpone individual incentives as long as possible. Keep people in explore mode, even if it means starting up new products and initiatives. And follow the handovers: What happens from discovering a customer need until it has been implemented? How many functions are involved, how much waiting time is involved, and how does each involved function learn how their work impacted customers? And watch the backlogs.</li></ul><p>Many founders say they prefer working in startups, and don’t enjoy the later phases of a company as much. Scale up in the wrong way, and you’ll easily arrive at this conclusion. But if you can scale up without loosing sight of your product, I think most naturally born innovators could thrive in any phase. Ultimately what they want is to work on value creation, and in strong product companies this happens in all phases.</p><p>Over the next decade, I think we will see fundamental changes in how we organise and operate tech companies. We will see more and more examples of learning organisations with strong product focus and drive to innovate in all stages. That in turn could have a fundamental impact on how societes evolve, with more people being allowed to <a href="https://haugeto.substack.com/p/rethinking-impact">build systems and products that are better</a>, more adaptable and more sustainable.</p><p>Founders and leaders who scale up their companies in the right way are at the frontiers of this development. They lead the way and show the rest of us that it’s indeed possible to go big and stay innovative at the same time.</p><p><em>Thx, Christian Møller, Ian Stendera.</em></p><p><em>Based on learnings from my work at </em><a href="https://iterate.no/"><em>Iterate</em></a><em>: An innovation ecosystem helping companies in any phase develop digital products, brands and strategies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2945d83b69fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every startup needs a crazy scientist]]></title>
            <link>https://haugeto.medium.com/every-startup-needs-a-crazy-scientist-52f601a2714f?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/52f601a2714f</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Thu, 08 Dec 2022 12:49:37 GMT</pubDate>
            <atom:updated>2022-12-08T12:49:37.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Dr. Finkelstein" src="https://cdn-images-1.medium.com/max/1024/1*Nuoe_IkNxQyM45humNmnbw.png" /><figcaption>At their most annoying, when you need them the most</figcaption></figure><p>In innovation, hard work alone won&#39;t cut it: To realize the vision of the company we also need to think new, aim high and occasionally go a little crazy.</p><p>It&#39;s true creative work. Not mind maps, brainstorms or “get out of your comfort zone” team building exercises. Nor is it a one-time job: It’s not an onboarding conversation with new employees, a strategy retreat or a board meeting. It’s a continual task, that’s especially important to do when nobody wants it to be done.</p><p>Are we pursuing the right goals? <br>Great traction — but is it the right kind of traction? <br>Do we have enough structure, or is our current structure starting to limit our potential? <br>What’s the craziest viable growth hack that we haven’t tried? (Why haven’t we tried it?) <br>How is the company culture evolving? <br>Are we still a team or are we becoming a group of people working side by side?<br>And when things are getting hard, and everyone feels we’ve ended up in a tough spot, remind us: Why did we start this company in the first place?</p><p>If everyone walked around in the office in circles every day asking themselves these kinds of questions, we wouldn&#39;t get much work done. That&#39;s why we need one or two crazy scientists in the company. Their job is to entertain the ideas, thoughts and ways of thinking they in turn can use to challenge the rest of us. To help us go above and beyond what we can achieve by hard work alone. It&#39;s easier said than done. Being the crazy scientist is a ceaseless struggle. It’s stressful and it’s mentally exhausting.</p><p>Execution work — to design, build, sell and scale — is also fundamental to success. That too is a struggle that’s stressful and exhausting. But it’s a struggle that often takes a very different form. Hard work in execution is about getting up early, getting your sh** together and getting things done. Bugs, outages, angry customers, unpaid bills, unpaid invoices, bad PR, competitors, internal conflicts, external conflicts and so on. When all of this happens (at once), it can be difficult, if not impossible, to recognize the relevance of the crazy scientist, who usually comes across as annoying and out of focus.</p><p>In <a href="https://www.amazon.com/Build-Unorthodox-Guide-Making-Things/dp/0063046067">Build</a>, Tony Fadell tells his stories from being a part of building monumentally innovative products like the iPod, the iPhone, Google Nest and more. A key takeaway from his book is the level of chaos that dominates the companies behind such products. He points out that the closer you get to the top of the organization, the worse it gets. Here, it’s not always a matter of structure and predictability. On the contrary, leaders like Larry Page are known for seemingly random and crazy acts that at times can be very frustrating for the people around them. You could even argue it’s a little too risky, especially for established companies like Apple and Alphabet. But it’s most likely also necessary, at least when you want to keep innovating. Which is what these companies, unlike most big companies, keep on doing.</p><p>The main compass for a crazy scientist on how to spend their time, is to do the things that maximise their creativity. They too have to spend time at the office, to talk to co-workers, customers and partners. If that alone makes them creative — great. But if they need to get a break, to get away from things, even to let things flow a little bit, in order to break through to the next level of creativity — they should go do that thing. It might look like they took the day off sailing, fishing, sleeping or going to another (stupid) conference or whatever it is. It might be tempting to tell them to stay put and do their share of the hard work. And it’s even more tempting to ask them to shut up when they finally come back and start bugging everyone with even more annoying questions.</p><p>If you want to innovate, you have to recognise their work. They are, as much as you are, an indispensable part of the machinery that brings you to success. Moreover: If you want to go beyond pure execution work, you will need the guidance and inspiration of the crazy scientist. In fact, if you see your crazy scientist starting to loose his or her craziness, you should probable ask or even command her to go sing karaoke, climb that wall, brew beer or __________ (fill in the blanks).</p><p>I&#39;ve seen a few crazy scientist in action. Here are some key traits they share:</p><ul><li><strong>Positively good at bad timing</strong> — asking questions when you the least want to hear them</li><li><strong>Doesn’t care about the conventional </strong>— things we should be doing (what others are doing)</li><li><strong>All into the contrarian</strong> — things we could be doing (there are no others)</li><li>Despite the craziness: Stays grounded in reality, and stays grounded in sound ethics and the values of the company</li></ul><p>At times it can be frustrating to be around someone whose job it is to challenge you. First of all, remember that the purpose of the crazy scientist is not to create chaos. It&#39;s to challenge everyone to do their very best (but when they do, it can sometimes feel like chaos). It&#39;s also important to remember the alternative — what work would look like without the crazy scientist: With less chaos and less challenges we would inevitably go into calmer waters, and it would happen sooner than you&#39;d think. We&#39;d start repeating ourselves. We’d start copying others. Ultimately, we’d stop innovating.</p><p>There’s a reason why you’re in innovation. It&#39;s not because you&#39;re seeking calmer waters. You went here because you want to be part of creating something new, awesome and important. You&#39;re on a roller coaster. Don&#39;t fight the G-forces — embrace them.</p><p>Feel a little crazy? Go for it. You might be the next crazy scientist.</p><p><em>Thx to Dan Krister Holst and Kim Leskovsky.</em></p><p><em>Read about using disruptive innovation to build a sustainable future on my (other) blog </em><a href="https://haugeto.substack.com/p/rethinking-impact"><em>Deep Change</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f601a2714f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Stage is Yours]]></title>
            <link>https://haugeto.medium.com/this-stage-is-yours-e060720d7647?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e060720d7647</guid>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[virtual-events]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Tue, 25 May 2021 11:42:23 GMT</pubDate>
            <atom:updated>2021-05-25T11:42:23.638Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ly0Vh0LKCzuZ2Qfz6GYqOw.png" /></figure><p><strong>Anywhere</strong> is helping performers discover and develop their true potential. A new venture from <a href="https://www.iterate.no/">Iterate</a>, we&#39;re getting a lot of questions about what it is and why we&#39;re building it. Here&#39;s from behind the scenes:</p><h3>Why</h3><p>We&#39;re building Anywhere because the world needs more performing arts. Musicians, DJs, rappers, dancers, poets, writers, cooks, geeks or something entirely new that we haven&#39;t even heard of yet — we want to enable more creatives to explore ideas, experiment with audiences and live out their passion. They all deserve an easier, safer and less risky road to success. <em>We</em> all deserve a more diverse and vibrant cultural scene.</p><p>Very few succeed at becoming professional performers. It takes hard work, continual struggle and high risk, that rarely pays off. Most of us are blissfully ignorant about the narrow road our favourite artists have had to go. If there wasn&#39;t for their passion and willingness to sacrifice, the music, shows and art that keep <em>us</em> going wouldn&#39;t be there.</p><p>Imagine what kind of world that would be.</p><p>We tried and we didn&#39;t like what we see. We also realised that we&#39;re missing out: There are many more creative talents out there, that could fly high and could delight and inspire everyone in new ways — if we would only give them a chance. These people are the real value in culture and entertainment, but they are under siege by the industry, big tech and outdated ways of thinking.</p><p>We want to set these people free. They are reason we&#39;re building Anywhere.</p><h3>How</h3><p>Historically, the path to success for a performer has revolved around live shows. First in local venues, later in emerging scenes and ultimately, for a very narrow elite, the “big” industry. The risk of booking a venue and hoping ticket sales would cover the expenses was an obstacle that kept many from trying. On top of that you had inherent limitations in geography: Unless you were already famous, few people would be willing to travel longer distances to attend your show. Hence, performers had to take even bigger risk by going on tours to get the exposure they needed. Now ticket sales was to cover the cost of venues, supporting staff, logistics and more. Once again: It was high risk, that rarely paid off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZU0OoGiLNx98XgeccUk1dQ.jpeg" /></figure><p>Scale this dynamics up and you get to see how the big players work, like the music industry: A premise that almost nobody makes it has shaped the mindset and mechanics of agents, record labels, studios, big venues and media outlets. Over the years it became more and more polarised, with stronger and stronger bias towards boosting the few that are already flying. It’s a winner takes all circus, carefully guarded by gatekeepers who rely heavily on personal judgment and hearsay. The things that make you valuable to your audience, your ideas, creativity and originality, are not important. Instead, it&#39;s about who you know, how you fit in, and how you could be shaped into a cash cow.</p><p>Over the last 10 years, however, digital platforms have started to challenge who is able to perform and who is able to be seen. They have shown that a global and diverse audience can be reached all they way from your living room, and it shows the path to a much more interesting performance landscape: More performers enter the stage, and new types of shows and performances appear, and new audiences find together and connect. Here, we see things that would never have existed if it hadn’t been for digital platforms.</p><p>Still however, today&#39;s digital tools aren&#39;t fit for purpose. Social media platforms are made for the advertisers, not the artist. You get paid for the attention or views you can hold, making the barrier to earning a decent salary very high. On Youtube you will need around 2,100,000 monthly plays just to make a minimum wage. On Spotify the same number is 366,000. This is far, far away from anything sustainable, leaving the vast majority of performers unable to make a living from their craft. Which in turn means the rest of us never get to see them or hear about them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChofLGzc9P3HAgDwm4Pd7A.jpeg" /></figure><p>Other digital tools are made for video conferencing, with limitations in number of viewers and limited support for ticket sales. Some tools are indeed made for live shows, but they are developed for the big players who can afford expensive subscriptions, and have their own supporting staff to run their events. The winner takes all mindset of the old industry has found its way into the digital tools too, it seems. And performers continue facing high risk, low reward.</p><p>We want this to change. We&#39;re building a platform that enables performers to take <em>artistic</em> risk with higher reward. We want them to focus their energy on entering the stage and doing something bold and unique. If they&#39;re going to be nervous about anything, it should be about their ability to delight, move and connect with their audiences. It should not be all about covering expenses, avoiding hustle or being accepted by gatekeepers.</p><h3>What</h3><p>The virtual stage in Anywhere is free to use. You can create one at any time, and you can set up as many events you want. Your upcoming events can be configured and promoted with a ticket goal, a minimum ticket revenue that has to be reached by a certain date for your event to happen.</p><p>We don’t charge money until you make money. 80–85% of the ticket revenue is paid directly to you as an artists. This means you will realising higher earnings a lot quicker than on other platforms. As an example, 40 tickets on Anywhere sold at 15$ each gives you as a performer a $510 income right away (a similar income would require 10,000 views on other platforms if not even more).</p><p>We&#39;ve made it super easy to get started. Log in, and claim your stage. Tell your audience what you want to perform. It&#39;s up to them to choose, and up to you to deliver on it. When the performance is completed, you get paid.</p><p>We’re intentionally building this together with the performers, to understand what they need in order to try out their ideas in the digital space.</p><p>Now, we&#39;re looking for the inventive and experimental performers who want to try out ideas. You could be a total newbie with more passion than fans, or a seasoned performer with an audience ready to be entertained with something new. In any case, our goal is for you to stay creative, live out your passion and to show us your world.</p><p>Own your stage. Go on to <a href="https://app.get-anywhere.com/">login</a>.</p><p><em>Thx to the Anywhere team (special thanks to Chris Sadler for great perspectives and visionary thoughts) and Sean Percival.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOpNR4SysBXTHbpIpTHjkQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e060720d7647" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cheating On Agile]]></title>
            <link>https://haugeto.medium.com/cheating-on-agile-e19ad1da99d2?source=rss-4c414ee3465d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e19ad1da99d2</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Anders Haugeto]]></dc:creator>
            <pubDate>Wed, 30 Sep 2020 06:52:14 GMT</pubDate>
            <atom:updated>2020-09-30T06:52:14.855Z</atom:updated>
            <content:encoded><![CDATA[<h4>What innovation has taught us about agile practices</h4><p>Some years ago my company Iterate pivoted from agile consultancy to venture building. Soon after, we started drifting away from the many agile practices we had spent almost a decade internalising. Nobody around us was doing this — were we setting ourselves up for failure? It felt like cheating. I kept a list, so it would be easier to revert.</p><p>Today, I felt like publishing the list, and confessing to our heresy (and sharing some thoughts on what we learned from it). Looking forward to comments and feedback. 🚀✌️❤️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ct491Nqlsl0gKXh_qKnJTA.png" /><figcaption>In innovation an agile mindset is valuable, but established practices are not</figcaption></figure><h3>Background</h3><p>It doesn’t matter if you’re a startup or an innovation project: The world will only want a new product if the right <em>people</em> build the right <em>idea</em> at the right <em>time</em>. We see this cleary in the startup world, where a few root causes are behind most startup failures:</p><ul><li><a href="https://www.ted.com/talks/bill_gross_the_single_biggest_reason_why_start_ups_succeed">Wrong market timing</a> — usually this means going to market too early</li><li><a href="https://www.cbinsights.com/research/startup-failure-reasons-top/">Dysfunctional founding teams</a> — entrepreneurship is hard, and a team without the right passion, diversity of opinion and grit stands no chance</li><li><a href="https://a16z.com/2019/12/09/product-zeitgeist-fit/">Weak ideas</a> — lack of value makes customers indifferent</li></ul><p>Macro economics and founder/investor dynamics also play a role, but those are for future posts.</p><p>My prophecy: Winners in corporate innovation will be those who aim to <a href="https://medium.com/@hauge2/shocking-rule-for-innovation-get-rid-of-the-shark-tank-78e32deaf7db">solve this struggle</a> — companies who help the right people come together and help them build the right product, at the right time. Most companies don&#39;t however. Instead, they go for the high standard for corporate transformation and digitalisation. They go Agile. Before they know it, they implement practices that could seriously impede innovation. This happens because Agile comes from software development. It&#39;s about <em>building</em>. Innovation, on the other hand, is about <em>creating</em>. Mix those up, and you will easily miss out on the best opportunities ahead.</p><p>Take <em>time</em> as an example. No agile practice tells you it&#39;s valuable to let time go by after you&#39;ve started working on something. In innovation this can be a great idea. Many successful innovators tell stories about how competitors matured their market for them, before they got out of bed and started building on their own. When Google Glasses was launched in 2013, it faced a number of issues, from immature market — few understood what it was supposed to do — to immature technology. It was discontinued after two years of (agile) development. Five years later we&#39;re again seeing similar products emerge, most notably Snapchat&#39;s Spectacles. It remains to be seen if they succeed, but in the meantime they&#39;re clearly building on learning that for Google is nothing but sunk cost. In agile practices, “wasting” calendar time deliberately is heresy. In innovation it can be the single most important factor for success.</p><p>Final warning: If you want to try this, people may get angry with you. Just remember: Learning what works and what doesn&#39;t in <em>your context</em> is what an agile mindset is all about.</p><h3>The list: Agile vs Innovation practices</h3><h4>Time</h4><p><em>Agile: </em>Long time from customer need to working solution leads to waste, increased complexity and lost opportunities. The faster the feedback loop, the better. Minimise lead time. Create flow.</p><p><em>Innovation: </em>The more ripe a market, the better. Run your experiments, but keep them at arms length. Don&#39;t let the desire to build get the better of you. Elapsed calendar time is your best friend. It&#39;s all about market timing. Wait for it.</p><h4>Context Switching</h4><p><em>Agile: </em>The time you spend on context switching is waste. Stay on as few projects / teams as possible — preferably only one at the time.</p><p><em>Innovation: </em>It takes a lot more than skills and experience to qualify people for an innovation journey. Nobody (not even HR) can predict who will form a high performing innovation team. The best way to find one is to let people try lots of different teams and ideas — to allow people to search for true passion.</p><h4>Backlogs and planning</h4><p><em>Agile: </em>Tracking future work, that may not happen, is waste. Keep backlogs short and tight. Don’t plan too far ahead. Prioritise.</p><p><em>Innovation:</em> Bad ideas lead to great ideas. Play around with thousands of them. Build diversity of opinion. Keep track of all ideas. The more ideas the better. Don’t prioritise.</p><h4>Work In Progress</h4><p><em>Agile: </em>As few tasks as possible at a time. Slice work up in smaller packages. Ship right to production. Get things done.</p><p><em>Innovation:</em> Have hundreds of experiments running in parallel. Once a landing page is deployed, just keep it there (perhaps it&#39;ll start converting tomorrow, perhaps in six months). Keep your eyes and your options open.</p><h4>Iterations</h4><p><em>Agile: </em>Start with week-long iterations or longer, but aim for shorter and shorter iterations, until you don&#39;t need them any longer. The most agile teams usually ship right to production when a feature is complete.</p><p><em>Innovation:</em> When fast experiments are inconclusive, you easily get confused. Short iterations incentivise premature conclusions. Separate work rhythm from feedback moments. Allow time to internalise. Then force the discussion: Pivot or persevere? Do we have enough data to know at this point? Are we still waiting for things to play out? (Still need a number? Six weeks at minimum).</p><h4>Focus and goals</h4><p><em>Agile: </em>Work with one thing at the time. Align the team around a small set of long term goals. Find ways to quantify and measure the outcomes you&#39;re trying to achieve. Stay focused.</p><p><em>Innovation: </em>Work in multiple directions at the time. Align the team around a high level vision. Talk to lots of people, also those who don&#39;t seem immediately relevant. Find ways to quickly communicate all insights with the team and surrounding advisors. Create optionality.</p><h4>Feedback</h4><p><em>Agile: </em>As early as possible. Fastest learner wins.</p><p><em>Innovation: </em>Not if it leads to “instant validation gratification”. Make sure you climb the highest mountain. <a href="https://medium.com/@hauge2/does-early-testing-kill-creativity-648dee075ca">Know your vision</a>.</p><p>This is not an exhaustive list. There are many more practices. There are also many that make sense in both worlds: Visual communication, autonomous teams, process and product ownership, continuous improvement and other team empowering practices make sense in either context.</p><h3>Conclusion</h3><p>We never needed the list: We didn&#39;t have to revert our practices. Instead, we ended up with two sets of practices instead of one. A set of practices for early stage innovation, and a set of practices for expansion and growth. Successful ventures at Iterate will transition from one to the other. The whole way they retain a mindset of learning, adapting and challenging their surroundings.</p><p>Transitioning is a topic any serious practitioner should learn to master. This post was inspired by Kent Beck’s <a href="https://medium.com/@kentbeck_7670/fast-slow-in-3x-explore-expand-extract-6d4c94a7539">3x thinking</a> — on how companies go from explore to expand to extract, and how practices and behaviours could change dramatically along the way.</p><p>Still unsure you&#39;ll be able to convince others about this? Don&#39;t discard this post. Put it in your bookmarks instead, and wait for the right timing to pass it around. Our irony is this: We still think of ourselves as agile — perhaps more agile than ever before.</p><p>Innovation is a lonely journey, but time is on your side.</p><p><em>Thx to my extended family at Iterate for being on a quest crazy enough for us to gain these insights. Thx to Kent Beck, for comments and suggestions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e19ad1da99d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>