<?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 Hans Magnus Næss Inderberg on Medium]]></title>
        <description><![CDATA[Stories by Hans Magnus Næss Inderberg on Medium]]></description>
        <link>https://medium.com/@hinderberg?source=rss-51099a274601------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ex_Dcif9watCgaLWvddg9w.jpeg</url>
            <title>Stories by Hans Magnus Næss Inderberg on Medium</title>
            <link>https://medium.com/@hinderberg?source=rss-51099a274601------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:53:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hinderberg/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[Both the impressive and the stupid are true at the same time]]></title>
            <link>https://medium.com/@hinderberg/both-the-impressive-and-the-stupid-are-true-at-the-same-time-b3611d39a98a?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3611d39a98a</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Tue, 03 Mar 2026 19:57:40 GMT</pubDate>
            <atom:updated>2026-03-03T20:00:44.906Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y3OcXLdvrcCa92aM" /><figcaption>Photo by <a href="https://unsplash.com/@elimendeinagella?utm_source=medium&amp;utm_medium=referral">Elimende Inagella</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Both the impressive and the stupid are true at the same time.</p><p>That’s what I keep coming back to after years building AI agents in a startup, and now as a product leader at Autodesk. Here’s how I think about what’s actually happening.</p><h3>Follow the money</h3><p>You can think the AI hype is overblown. I think so myself. But most of the capital in the world right now is betting that AI will fundamentally reshape most industries. The bubble will probably burst, and there will be winners and losers, just like every major technology wave. But that doesn’t change what capital does along the way: it creates innovation, draws talent, multiplies research, builds infrastructure, and creates irreversible shifts. We saw it with smartphones, cloud, EVs, SaaS. Each time, the people who dismissed the early, messy versions got caught off guard by how fast things compounded. AI is following that exact pattern, except faster, with even more money to fund the change.</p><h3>What I learned building AI agents</h3><p>When I was running my startup, we built AI agent systems. Every month brought a step change in capability. Something that worked horribly one week could be 10x better the next. That meant I couldn’t trust my own conclusions from the month before. I had to re-test constantly, and accept that what was true yesterday might not be true today.</p><p>I spent weeks designing around a model limitation I’d carefully mapped. By the time we shipped, the limitation was gone. The model had improved, and everything I’d built around the constraint was wasted architecture. That was the moment I realized my learnings had an expiration date ratio I’d never had to deal with before.</p><p>That experience rewired how I think about this. The people who struggle most with AI aren’t the ones who try it and find it lacking. They’re the ones who tried it once, even deeply, concluded it wasn’t good enough, and stopped checking every week. The rate of improvement is the thing to pay attention to, not any single snapshot.</p><h3>Where it’s real and where it’s not (yet)</h3><p>Tools like Lovable and Bolt aren’t for experienced engineers. They’re for the people who couldn’t build before. That’s a massive market: internal apps, CRUD apps, WordPress-level products. A lot of consultancies are going to struggle because of this. People are building real businesses on these tools alone.</p><p>For those who already understand what they need, tools like ChatGPT, Claude, Cursor, and Claude Code are removing the friction between intent and execution. The deeper your understanding, the more leverage you get.</p><p>Does AI solve all complex problems? No. Not yet. But something has fundamentally changed in the last few months. As a concrete example: I built a tool called Loom in about 60 minutes. It orchestrates a full AI product organization, every persona needed to build, market, and sell a product. It plans work from a vision doc, spins up parallel teams in isolated git worktrees, creates PRs, and has an AI reviewer that auto-merges what passes and escalates what doesn’t to me. It builds features for me while I do other work.</p><p>Is it sometimes dumb as hell? Yes. Does it make baffling product, design, and engineering mistakes? Yes. But has it permanently changed how I think about what’s possible? Absolutely. That tool would have been a multi-month side project a year ago, and impossible a few years before that. Now it’s built and I have a decent working product after half a week of vacation mostly spent with my kids and wife.</p><h3>What I fundamentally believe</h3><p>How we work as knowledge workers is changing at an extreme pace. You can choose to be at the frontier or follow from a distance. For me, being at the front is natural. But what you shouldn’t choose is to stop being curious. Dismissing it as “just hype” can be a defense mechanism. There’s also real transformation happening underneath.</p><p>We’ve always been abstractions away from natural language. From assembly to C, to Java, to JavaScript, to TypeScript, to “build me a tool that lets teams track projects.” That distance gets shorter every month now, and the complexity of what you can describe in natural language and actually get done grows every month too. All that knowledge of product taste, design patterns, architecture, and system thinking? It’s becoming your primary interface.</p><p>The people getting the most out of AI tools aren’t the ones writing the best prompts. They’re the ones who can look at what it produced and say “this won’t work, and here’s why.” The ones who understand the deeper abstractions and can direct it where they want to go. The tool does the building. The human designs the system it works within.</p><h3>What you build matters too</h3><p>This isn’t just about how you work. It’s about what you build. If you’re shipping products today without thinking about AI-native capabilities, agent-ready integrations, and machine-readable interfaces, your competitors are. Products that can’t be orchestrated by AI, that don’t expose their value through APIs and protocols like MCP, will feel like websites without mobile support felt in 2015. Not broken, just increasingly irrelevant. The window to build this in from the start is now. If your customer’s AI can’t use your product, they’ll find one it can.</p><h3>What worries me</h3><p>I’m not blindly optimistic here. I’ve been building and using AI systems for years. I get production-grade code out of AI regularly, but once you move beyond CRUD apps into complex, domain-specific territory, it’s still not completely there. It sometimes feels like wasted time, but I still think it’s worth it. The less training material that exists for your problem space, the worse it gets. The gap between what the frontier demos show and where most of us actually are day-to-day is real. If the industry oversells the promise without honestly bridging that gap, we’ll create cynicism instead of adoption.</p><p>I’m also genuinely concerned that we’ll become less personal, less human. Abstraction isn’t always good, and building on things you don’t fully understand carries real risks. The challenge is using AI to make us more human, not less.</p><p>Do I like the direction things are heading? I don’t even know. But things are moving there, and I’d rather shape the direction than watch it happen.</p><h3>What I think matters now</h3><p>The most important skill right now is the willingness to be wrong about what you concluded last week. That’s hard, especially if you’ve built a career on deep, stable expertise. If you’ve spent hours wrestling with AI-generated code that looked right but was subtly wrong, or watched it confidently produce nonsense, your frustration is completely valid. But the tool being bad today and the shift being real are two different things. The instinct is to form a view and hold it. With AI, that instinct will cost you.</p><p>If you’re skeptical, be honestly skeptical and engaged. Say where the tools fall short. That signal is more useful than either blind enthusiasm or silent dismissal. And if you’re not skeptical or excited but just unsure what this means for you: the work is changing shape, and some of what currently fills our days will be automated. But the parts that involve judgment, context, domain expertise, and navigating ambiguity are becoming more valuable, not less. AI makes the thinking more important, not less important.</p><p>I don’t have a tidy conclusion. This is messy, fast, and genuinely uncertain. Stay in the conversation, keep experimenting, and share what you find. What doesn’t work today might work next week.</p><p>Re-test. Every week. Stay uncomfortable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3611d39a98a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding balance through meaning]]></title>
            <link>https://medium.com/@hinderberg/finding-balance-through-meaning-86d9b8b2cd0d?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/86d9b8b2cd0d</guid>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 14:09:33 GMT</pubDate>
            <atom:updated>2025-09-22T14:09:33.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQ2h3MWg_jroSHxHIfOu0A.png" /></figure><p>I recently reflected on a post about hustle culture, work-life balance, and the different ways people approach ambition. What struck me is how complicated we often make this discussion. Should we work fewer hours? Should we slow down? Should we separate work and life more clearly? Should we be more ambitious? Should we suck it up and give it more hours? For me, the real answer is much simpler: it is about meaning.</p><p>I think about balance a lot, but I see it in simpler terms than most. For me, balance is <strong>not</strong> really about how many hours I spend at work or how much time I set aside for life outside of it. It is about whether the things I spend my time on feel meaningful.</p><p>That meaning shows up in different ways. It can be solving a problem at work that has been sitting in the back of my mind for weeks, creating the best possible place for my colleagues to thrive, building a fantastic product for our customers, or contributing to something bigger than myself. It can also be a long run where my head finally clears, or skiing, improving my turns, or going full speed downhill and feeling alive. It is there when I spend time with my family, creating an environment where my kids can grow, or in a moment of laughter with friends or extended family.</p><p>The common thread is that these things matter to me. They give me a sense of mastery, contribution, or growth. They energize me instead of draining me. And when most of my days are filled with this kind of meaning, balance follows naturally. It is less about counting hours and more about balancing the meaningful things so they add up to a full life.</p><p>An important part of this is learning to find meaning in what you already do. Not everything requires a new adventure or a complete change. Often the deeper challenge is to look at the work, the relationships, and the routines you already have and see the value within them or tweak them. Mastery, contribution, and growth can be found there too, if you give them attention.</p><p>That is also why I believe it is worth spending time exploring and figuring out what feels meaningful for you. Because when you look back one day, the questions you will want to be able to answer are not about how many hours you worked or how many hours you rested. The questions will be much simpler:</p><p>Did my life have meaning?</p><p>Did I do what felt right for me?</p><p>Did I find balance?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86d9b8b2cd0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People see your actions, not your feelings]]></title>
            <link>https://medium.com/@hinderberg/people-see-your-actions-not-your-feelings-8920da355a9b?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/8920da355a9b</guid>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Sun, 15 Dec 2024 13:52:22 GMT</pubDate>
            <atom:updated>2024-12-15T13:52:22.262Z</atom:updated>
            <content:encoded><![CDATA[<p>In our daily lives, we often feel a storm of emotions, motivations, and intentions. We care deeply about things — our families, our work, our aspirations. Yet, here’s a simple truth: people don’t experience your feelings. They see your actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yxunyfh93_4pQlDs" /><figcaption>Photo by <a href="https://unsplash.com/@acharki95?utm_source=medium&amp;utm_medium=referral">Aziz Acharki</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>The Reality of Perception</strong></h3><p>No matter how deeply you care or how noble your intentions are, the world judges you by what you do, not by what you feel. This disconnect often leads to misunderstandings. “But I care!” we think, frustrated when someone misreads us. However, actions are the only tangible evidence of our values and priorities.</p><p>If you intend to show care, but your behavior says otherwise — if you’re distracted during conversations, unreliable, or inconsistent — the impression you leave is not of a caring person. People infer what’s in your heart by what’s in your hands.</p><h3><strong>Bridging the Gap: Aligning Feelings with Actions</strong></h3><p>How do you ensure your actions reflect your true intentions?</p><p>1. <strong>Practice Self-Awareness:</strong> Take a moment to understand how your behavior aligns (or doesn’t) with what you feel. If you value a relationship, ask yourself: <em>What actions am I taking to nurture it?</em></p><p>2. <strong>Be Deliberate:</strong> Don’t let good intentions stay as thoughts. Turn them into tangible acts. Send a thoughtful message, show up when it matters, and follow through on commitments.</p><p>3. <strong>Seek Feedback:</strong> Sometimes, there’s a gap we can’t see. Ask trusted people if your actions match your values. Be open to recalibrating.</p><h3><strong>When You Miss the Mark</strong></h3><p>We all have moments when our actions don’t align with our feelings. Perhaps you snapped at a loved one when you were stressed, even though you care deeply.</p><p>The key here is ownership. Apologize when needed, acknowledge the disconnect, and make a conscious effort to do better. People appreciate authenticity and growth.</p><h3><strong>Why This Matters</strong></h3><p>Aligning actions with feelings isn’t just about how others perceive us — it’s about integrity. Living in alignment creates trust, both in relationships and within ourselves. When your actions consistently mirror your values, you build a reputation of reliability and authenticity.</p><h3><strong>Final Thoughts</strong></h3><p>Your feelings are real and valid, but they’re invisible. Your actions, however, are a beacon. Make them intentional, consistent, and reflective of who you truly are.</p><p>In the end, what you <em>do</em> is what matters most!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8920da355a9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Fear of Conflict is Killing Your Company’s Results]]></title>
            <link>https://medium.com/@hinderberg/why-fear-of-conflict-is-killing-your-companys-results-4e746e63c048?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e746e63c048</guid>
            <category><![CDATA[conflict]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Fri, 13 Dec 2024 09:35:21 GMT</pubDate>
            <atom:updated>2025-08-05T05:51:15.629Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SixTa0vfGythqHke" /><figcaption>Photo by <a href="https://unsplash.com/@nbabrams?utm_source=medium&amp;utm_medium=referral">Nick Abrams</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Too many employees, and frankly most leaders, shy away from conflict. It’s uncomfortable. It can be messy. And it often feels easier to avoid it entirely. But this reluctance to confront issues head-on comes at a massive cost to organizations, one that’s often invisible until it’s too late.</p><h3>The Hidden Cost of Avoiding Conflict</h3><p>When employees avoid conflict, they also avert critical conversations. Feedback is watered down, decisions are delayed, and problems fester in silence or corridors. This leads to stagnation, eroded trust, and missed opportunities to improve processes and relationships. Over time, avoidance becomes a cultural norm, a silent killer of organizational effectiveness.</p><p>Here’s the truth: avoiding conflict doesn’t just slow progress, it can stop it dead in its tracks. Teams that fear conflict become paralyzed, unable to make bold moves or take the risks necessary to achieve exceptional results.</p><h3><strong>What You Need Instead: A Culture of Movement and Repair</strong></h3><p>What’s the antidote? It’s not fearlessness. It’s training your employees to <em>dive in</em>, take initiative, and create movement, even if it means making mistakes. The key isn’t perfection. The key is cultivating a culture where people are not only unafraid to act but also <em>excellent at repairing</em> when they act imperfectly.</p><p><strong>Diving In:</strong> Encourage employees to address problems head-on, make decisions quickly, and take ownership of their actions.</p><p><strong>Be humble but not shy: </strong>Train them on not be a know-it-all; but own their truth and create movement.</p><p><strong>Repairing Well:</strong> Mistakes are inevitable, but a strong culture is built on the ability to repair. Train your team to apologize authentically, take corrective action, and rebuild trust.</p><p><strong>Building Regret as a Strength:</strong> Regret isn’t a weakness. It’s a sign of accountability and self-awareness. Use it as a learning tool, not a deterrent.</p><h3><strong>Why Repair Makes Action Less Scary</strong></h3><p>Here’s the secret: when people are skilled at repairing, taking action and creating movement becomes far less intimidating. Why? Because they know that even if they make a mistake, they have the tools to fix it. They stop worrying about avoiding every possible error and start focusing on solving problems.</p><p>Think about the first time you tried to fix something in your home, a leaky faucet, a broken cabinet, or a stuck window. If you’re like most people, it was nerve-wracking. You were scared of making it worse, or maybe you doubted your ability to finish the job. But as you gained experience fixing things, you got better and faster. Over time, you became confident enough to make changes, experiment, and improve. Suddenly, making a repair or even trying something new felt <em>easier</em>.</p><p>The workplace is no different. Employees who know how to repair relationships, processes, and outcomes are less afraid of taking action. They understand that no decision is final, no mistake is fatal, and most problems can be fixed with effort and honesty. This confidence in their ability to repair creates a culture of boldness and movement, exactly what every organization needs to thrive.</p><h3><strong>Why Repair Beats Perfection Every Time</strong></h3><p>Some organizations make the mistake of prioritizing perfection over progress. But perfection is impossible, and striving for it creates a fear of failure that stifles creativity and innovation. On the other hand, teams that are skilled in repair can move faster, fail smarter, and adapt better.</p><p>Imagine an employee who jumps into a conflict with a teammate. They misread the situation, act too aggressively, or make a poor decision. That’s not the end of the story, it’s the beginning of their growth. If they’re trained in repair, they can recognize their misstep, apologize meaningfully, and make things right. Not only does the conflict get resolved, but trust is often strengthened in the process.</p><h3><strong>A New Model: Repair as a Core Competency</strong></h3><p>To truly embrace this approach, organizations need to move beyond merely accepting mistakes. They must actively train employees to handle the aftermath of conflict and missteps with skill and grace. Here’s how:</p><p><strong>Role-Playing Conflict and Repair:</strong> Use real-world scenarios to practice navigating tough conversations and repairing relationships.</p><p><strong>Teach the Language of Repair:</strong> Phrases like “I was wrong,” “I’m sorry,” and “Here’s how I’ll make it right” should be part of your team’s vocabulary.</p><p><strong>Celebrate Repair Stories:</strong> Highlight examples of employees who repaired mistakes effectively, showing that imperfection is not only acceptable but part of the process.</p><p><strong>Reframe Mistakes as Learning Opportunities:</strong> Create a feedback-rich culture where mistakes are expected, discussed openly, and used to improve.</p><h3><strong>The Payoff: Teams That Move Fast and Build Trust</strong></h3><p>When employees learn to dive in and repair well, your organization reaps huge rewards. Decisions happen faster. Problems are addressed before they grow. Trust is built and reinforced through authentic human interactions. And most importantly, your company creates <em>movement, </em>the antidote to stagnation.</p><p>This doesn’t just improve results, it transforms your culture. A team that embraces conflict and masters repair doesn’t fear challenges. They tackle them head-on, knowing they have the skills to make things right when they misstep. And that kind of culture is unstoppable.</p><h3><strong>The Challenge: Start Training Your Repair Skills Today</strong></h3><p>So, here’s the challenge: take a hard look at your organization. Is fear of conflict holding your team back? Are your employees hesitating when they should be diving in?</p><p>If so, the solution isn’t just about encouraging action, it’s about teaching repair. Train your team to own their mistakes, show regret without fear, and rebuild trust. Because in the end, the ability to repair isn’t just a skill. It’s a competitive advantage.</p><p>And just like fixing something in your house gets easier with practice, so does navigating conflict and repairing mistakes at work. Over time, your team will stop fearing missteps and start embracing action, again and again. That’s when real growth happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e746e63c048" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Are All Defined by our self-beliefs]]></title>
            <link>https://medium.com/@hinderberg/we-are-all-defined-by-our-self-beliefs-4ee65ecd0a74?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ee65ecd0a74</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[self-care]]></category>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Mon, 18 Nov 2024 07:12:53 GMT</pubDate>
            <atom:updated>2024-11-18T07:12:53.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DK0r0FlVI2-NCKGH" /><figcaption>Photo by <a href="https://unsplash.com/@fakurian?utm_source=medium&amp;utm_medium=referral">Milad Fakurian</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever caught yourself thinking, <strong>“I could never do that”</strong>? Or heard someone say:</p><p><strong>“How did she achieve that?”</strong></p><p>This comment often implies that the person believes they couldn’t achieve the same thing themselves. Yet, more often than not, that belief simply isn’t true.</p><p><strong>“I’m almost burned out and can’t do anything about it.”</strong></p><p><strong>“That’s easy for you to say!”</strong></p><p>These comments share a common thread: they reflect the limits we place on ourselves through deeply ingrained self-beliefs.</p><p>It took me a while to understand why these statements no longer resonate with me. At first, they only gave me a slight discomfort — a restless itch, if you will. Over time, I realized that discomfort came from recognizing how much of my life had been defined by self-imposed boundaries.</p><p>Growing up, I placed many beliefs on myself: the constraints, limitations, and rules I thought I had to follow. Some were imposed by others, but I accepted them as valid without question. But after years of challenging these assumptions, I’ve come to realize that most of these beliefs were arbitrary. Instead, I’ve learned to focus on a few core beliefs that truly define who I am — beliefs that guide my decisions on a daily basis.</p><p><strong>Let’s Look at Some of My Core Beliefs</strong></p><p><strong>Integrity</strong>: I will always be honest, transparent, and sincere, ensuring that my actions align with my words. To be clear, what is my truth may not be others’.</p><p><strong>Health (= fuel)</strong>: Physical and mental well-being are non-negotiable. They’re the foundation for everything else, and self-care is the essential fuel that keeps me going.</p><p><strong>Commitment to Learning</strong>: No matter where I am in life, I strive to learn something new every day. Continuous improvement is a mindset, and I refuse to settle.</p><p><strong>Accountability</strong>: I take full responsibility for my actions, my choices, and their outcomes.</p><p><strong>Kindness</strong>: Treating others with compassion and respect creates positive relationships and builds a supportive environment.</p><p><strong>Curiosity</strong>: I’m deeply curious about how others see the world and why they do. Asking questions and listening are the shortest paths to understanding and growth.</p><p><strong>Everything is Changeable</strong>: Nearly everything can change if you’re willing to invest the effort, take the risk, and accept the time it takes. It’s all about trade-offs.</p><h3><strong>The “Core Beliefs backpack”</strong></h3><p>I think of my core beliefs as items in a backpack. The fewer items I carry, the freer and more adaptable I am. Everything outside the “core beliefs backpack” should remain open to challenge, reconsideration, or adaptation.</p><p>The more you add to your backpack of unchangeable beliefs, the heavier it becomes. Over time, you might find yourself stuck, unable to move forward. That’s why I regularly reassess what stays inside my backpack and what can be let go.</p><p>This isn’t easy. It takes effort to question long-held assumptions and differentiate between what’s core and what’s simply familiar. But the reward is worth it. When you trust that your core beliefs are solid, everything outside becomes open to adaptation.</p><h3><strong>Why I Challenge Burnout Beliefs</strong></h3><p>I started this by mentioning the discomfort I feel when people say things like, <strong>“I’m almost burned out and can’t do anything about it.”</strong></p><p>I feel empathy for them — burnout is real and painful. But I also want to gently challenge them: <strong>“What small thing can you change today to make tomorrow just a little better?”</strong></p><p>Could it be something as simple as saying, <strong>“No, I can’t take on another task right now”</strong>? Speaking your truth, even when it’s hard, is a courageous step toward reclaiming control over your life.</p><h3>Here’s what I want you to take away from this</h3><p>Work actively to minimize what’s inside your “core beliefs backpack.” Keep it light. Reserve that space for the few things that truly define who you are and how you live.</p><p>Move everything else outside the backpack, where it can be challenged, questioned, and adapted. Doing this opens the door to a growth mindset.</p><p>Think of this as building a muscle: the muscle to question, adjust, and grow — bit by bit, day by day. It won’t happen overnight, but with practice, it gets easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ee65ecd0a74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There Is No Such Thing as a Data-Only Decision]]></title>
            <link>https://medium.com/@hinderberg/there-is-no-such-thing-as-a-data-only-decision-d96117dc0119?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/d96117dc0119</guid>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Thu, 24 Oct 2024 04:54:15 GMT</pubDate>
            <atom:updated>2024-10-24T04:54:15.067Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Introduction</strong></h3><p>In today’s data-driven world, organizations often emphasize the need to make decisions backed by data. We hear terms like “data-driven decision-making” and “let the numbers speak for themselves.” While data is undeniably crucial, the notion of purely data-only decisions is a myth. Every decision, no matter how analytical, involves human judgment, context, and interpretation. In fact, data serves as a way to calibrate our gut feelings rather than replace them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fUxr-dbmRoU7crKJ" /><figcaption>Photo by <a href="https://unsplash.com/@lukechesser?utm_source=medium&amp;utm_medium=referral">Luke Chesser</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>The Role of Data</strong></h3><p>Data provides insights, trends, and facts that can help identify problems, evaluate opportunities, and predict outcomes. In modern business, data is integral to optimizing processes, reducing uncertainty, and guiding investments. Without data, decision-makers would operate in a vacuum of assumptions and guesswork.</p><ul><li><strong>Data as a guide:</strong> Data offers a map, highlighting possible paths and outcomes. For example, in a sales department, data might suggest focusing on a specific customer segment based on historical buying behavior.</li><li><strong>The illusion of objectivity:</strong> Data is often seen as objective. After all, numbers don’t lie, right? However, while data itself is neutral, its collection, interpretation, and usage are influenced by subjective human biases</li><li><strong>Calibrating gut feelings:</strong> Data doesn’t replace instinct — it enhances it. Knowledge-workers often rely on their gut when making decisions, but data can help refine or validate that intuition. For example, if your instinct tells you a new market is promising, data can either support that feeling or caution you to reconsider certain risks. Rather than being at odds, data and intuition work together.</li></ul><h3><strong>The Human Element</strong></h3><p>No decision is made in a vacuum. Even when data is available, how it is interpreted and applied is influenced by human factors like emotions, experience, intuition, and external pressures.</p><ul><li><strong>Context matters:</strong> Numbers are never divorced from their context. Data about market trends, for example, must be considered within the broader social, political, and economic environment. Contextual nuances — such as company culture, customer relationships, or market volatility — impact decisions.</li><li><strong>Bias and interpretation:</strong> Human biases influence how data is interpreted. Confirmation bias, availability bias, and anchoring can skew how we view data. For instance, a knowledge-worker might cherry-pick data that aligns with their pre-existing beliefs or preferences.</li><li><strong>Risk tolerance and ethics:</strong> Decisions are shaped by personal and organizational risk tolerance, as well as ethical considerations. A company might have data suggesting layoffs would increase profitability, but workers may decide against it due to the negative impact on employees and public perception. Here, ethical and emotional judgments interplay with data-driven insights.</li></ul><h3><strong>Data as a Compass for Intuition</strong></h3><p>While gut feeling can be an invaluable decision-making tool, it is prone to being swayed by personal experiences, biases, or emotional responses. Data serves as a compass, ensuring that instinctual decisions are grounded in reality.</p><ul><li><strong>Balancing instinct with facts:</strong> Experienced knowledge-workers often make decisions based on patterns they’ve internalized over the years. They may sense when a business opportunity “feels right,” but data helps to frame that feeling in a broader, more structured context. When intuition and data align, it provides powerful confidence to move forward. When they don’t, it offers a moment to pause and reconsider.</li><li><strong>Avoiding blind spots:</strong> Sometimes, our instincts can be wrong — perhaps because we’re too close to the problem or overly optimistic. Data provides an external check that can reveal blind spots, giving knowledge-workers the chance to recalibrate their feelings before taking action.</li></ul><h3><strong>The Interplay of Data and Judgment</strong></h3><p>Data is one part of a decision-making framework that also includes:</p><ul><li><strong>Experience and intuition:</strong> Experienced knowledge-workers often make decisions that defy data predictions, relying on intuition and pattern recognition. For example, in product development, data might suggest a specific direction, but a worker might use their gut to tweak the approach based on past experience.</li><li><strong>Stakeholder input:</strong> Data doesn’t always capture the human elements of business, such as customer needs, employee morale, or investor expectations. Stakeholders’ insights can shape or alter a data-based course of action.</li><li><strong>Time and urgency:</strong> Decision-makers often face tight deadlines where not all data can be gathered or analyzed. In such cases, decisions may be driven by a combination of partial data and gut feelings or external demands.</li></ul><h3><strong>Real-World Examples</strong></h3><ol><li><strong>Product Development Decisions:</strong> Product development is an ongoing, iterative process where continuous delivery plays a critical role. When teams release features frequently, they’re able to collect real-time feedback from users, allowing them to gather data and adjust their strategy. For example, in software development, a company might feel confident that users will love a new feature based on past feedback or intuition, but after releasing it in a small update (continuous delivery), data shows that users aren’t adopting it as expected. Instead of committing fully to a gut-driven decision or early data, the development team adjusts by analyzing usage data, revisiting user feedback, and tweaking the product. This process of releasing, learning, and iterating not only refines the product but continuously calibrates gut feelings with real-time insights. <strong>Why Continuous Delivery Matters:</strong> Continuous delivery allows teams to course-correct quickly. Decisions about what to build next or how to improve an existing feature are based on live user data, not just assumptions. This minimizes risks and ensures that gut instincts are balanced with actual user behavior and preferences, preventing large, costly mistakes.</li><li><strong>Continuous Improvement of a Business:</strong> Continuous improvement is a core principle in many successful businesses, especially in industries like manufacturing, retail, and service delivery. Take, for instance, a retailer who feels their current supply chain is optimal because it’s been working well for years. However, after reviewing real-time logistics data, they might notice inefficiencies — longer lead times, higher costs, or delays. By introducing incremental changes (lean or agile principles), the retailer can test improvements such as optimizing routes, adjusting inventory levels, or renegotiating with suppliers. Over time, they gather data on which changes have the most significant impact and fine-tune their strategy. This allows them to continuously learn and refine their gut sense of what’s best for the business. <strong>Why Continuous Improvement Matters:</strong> As businesses operate in ever-evolving markets, relying solely on past successes or gut feelings can leave them behind. Continuous improvement enables businesses to adjust their strategies based on up-to-date data while still allowing room for workers’ intuition. It’s a cyclical process: test, learn, improve, and repeat — always keeping gut feelings grounded in actual performance.</li></ol><h3><strong>To Sum It All Up</strong></h3><p>While data is indispensable in modern decision-making, it can never fully replace the human judgment, intuition, and context that shape the final choice. Decisions are rarely as simple as the numbers suggest. Ultimately, data informs and calibrates decisions, but knowledge-workers or AIs make them. Understanding this interplay helps workers avoid over-reliance on numbers and embrace a more holistic approach to decision-making.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d96117dc0119" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transparency in an organization of empowered teams]]></title>
            <link>https://medium.com/@hinderberg/transparency-in-an-organization-of-empowered-teams-fe453869a400?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe453869a400</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[empowered-teams]]></category>
            <category><![CDATA[organizational-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Fri, 07 Oct 2022 08:53:33 GMT</pubDate>
            <atom:updated>2022-10-07T12:32:18.933Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u_IJbjcb8Jz5HNBm" /><figcaption>Photo by <a href="https://unsplash.com/@budhelisson?utm_source=medium&amp;utm_medium=referral">Bud Helisson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>From time to time, I tend to brain-dump things that get stuck in my head and post them into one of our Slack channels at work.</p><p>A while back, I wrote this piece about transparency related to empowered teams, and as this might be relevant to others, I figured I‘ll make a blog post.</p><p>But before we dig into the topic of this post, we need to define what an empowered team is. To me, empowered teams mean that the teams can make aligned, autonomous choices toward solving a problem. Autonomy is an essential driver for individuals and teams at the organization and company levels. It speeds us up, giving us the freedom to make small and big decisions without involving too many stakeholders. But, as with any choice, there are pros and cons. — In this post, I’ll outline how we tackle continuous alignment when teams are empowered.</p><p>Autonomy without alignment is like a guide having many individual thinkers on a ski-touring trip when bad weather comes along. The guide expresses concern and recommends everyone to ski down the mountain. They turn around and slide down the mountain without taking the time to align. Since the individual thinkers on this trip are used to doing what they think is best without aligning with others, everyone ends up skiing down their separate ways, and we can easily imagine the following disaster.</p><p>Alignment is necessary to ensure that everyone moves in the same direction, thereby reducing the risk of people ending up alone and in entirely different places. Unfortunately, I have observed that too many omit the align part when dealing with empowered teams. Aligning on strategy and goals is something I know we are very good at in our organization! In theory, we follow the tight-loose-tight principle by having Planning Weeks every quarter and a more extensive planning every half year to gather and align the whole organization in a top-down-bottom-up process. We discuss everything from our ways of working to where we want to go in the next quarter and the next 2–5 years. We also share strategic context and set goals. Of course, there is always room for improvement, and we look for improvements every time, but I also feel the way we do it works beautifully!</p><p>After we have completed our planning weeks, we move into the loose part. Every team starts building and learning, steering toward an aligned future.</p><h3>If you are not transparent, you diverge</h3><p>Even though our empowered teams are aligned after our planning weeks, and we all move towards the same goals, it’s when we build and learn actual movement happens within the teams. When one learns new things, one needs to adjust. Adjusting rapidly is one of the capabilities empowered teams should have. As a consequence, learning and adjusting happen all over the company, continuously and at a fast pace, without the direct natural involvement of others. The lack of stakeholder involvement increases the chances that teams will diverge. That is why each team needs to invest time in transparency to remain aligned. Updating goals and achievements is part of this, and many have landed on OKRs for this purpose.</p><h3>Being genuinely transparent means much more than updating OKRs</h3><p>In a sizable and global organization, it’s not possible for one person to be involved in every discussion and have all the context. Each day, across time zones, in every corner of the organization, we make decisions where context matters. The more perspectives and context we have from clever heads spread across a company, the better decisions and solutions we will get. If you think about it, you can threat information and decisions in the same way as with your product; the sooner you get something viable and testable out to your customers, the faster you learn and adjust, one small iteration towards a better result. So making information and decisions available, easily accessible, and digestible to get feedback as early as possible is critical to stay aligned.</p><p>It’s essential to know that in an empowered way of working, decisions are just decisions until the team gets more context or better ideas. We work iteratively, and most decisions are possible to adjust. You need culturally to feel that it is more than ok to make decisions, but also share perspectives on decisions made without feeling that you step on anyone’s toes. In an organization like this, decisions are made fast, but it should be possible to change easily!</p><p>To increase the chances of getting perspectives and context, we have made deliberate cultural choices within our organization. One example is reducing the use of email or direct messages on slack or similar chat applications. Instead, we push ourselves to use open channels which others can quickly join.</p><p>We also encourage our employees to use inclusive formats for information sharing and discussions, one of the formats we call PTAS <em>(people talk about stuff)</em>. PTAS was created during covid when everyone was suddenly remote and was trying to simulate random coffee chats or talks happening at the office. The template is one topic, a public zoom link, and a date. Then share it in an appropriate slack channel. Anyone is free to join or listen to the following discussion. Sometimes it is recorded, but we do not require it because we want to keep the bar for creating a PTAS as low as possible. As some employees returned to our offices in person, we saw the random office talks starting to pick up again. At the same time, we noticed the lack of transparency and inclusiveness these talks provide for people not at the office, and we are taking steps to encourage more use of the more inclusive PTAS format again.</p><p>We also have a cultural document describing a goal of “<strong><em>Your ability to participate and contribute at work should not be affected by your preferred working hours or location.”</em></strong> and three simple principles to follow to ensure transparency and inclusiveness.</p><ul><li>Try to reduce the time you spend in meetings, consider other ways of sharing information and ways of working!</li><li>Some communication is best done synchronously, but remember: be inclusive!</li><li>Make decisions in an inclusive way.</li></ul><p>Asynchronous* ways of working encourage transparency in a better way than synchronous* work does, but we need to be able to do both while still ensuring transparency and inclusiveness; this is what the principles are trying to guide. Of course, we also have a ton of other alignment structures, as taking alignment seriously in an empowered teams organization is of utmost importance. Have we nailed this yet? No, working with transparency and alignment is similar to working with product development; you are not done until the company or product is shut down for good. It takes time, repeating, learning, and adjusting- over and over again!</p><h3>What’s my role as a leader in all this?</h3><p>Do you even need leaders in this setup, where the teams are empowered and excellent at continuous alignment by being transparent? The short answer is yes, and I’ll explain why. As pointed out, transparency is not something you can check off and regard as finished. Ensuring that structures are in place to help teams be more transparent is needed, and I focus on this. By design of the system, the empowered teams have a laser focus on their mission, which also means that the gravity towards inward thinking is strong. Slipping on communication outwards and seeking information is something I see many teams need to be reminded of from time to time, and as a leader, I help with this. Primarily by nudging leaders in a team, as nudging when the cultural part is there already is effective. If there are more broken cultural problems, we work with the teams to help them see the why’s and the outcome we are looking for to get them on board. Coaching is an effective way of working with the teams directly, as you need them onboard with the thinking to get them empowered.</p><p>A natural part of the job is observing all sub-organizations and teams. Consequently, I get a broad perspective that makes it easier to see organizational patterns and implement or suggest system changes. Just consuming content and organizational movement takes a lot of time. For example, I follow all team Slack channels and read them daily to get context. To create good strategies, you must have the context that lives inside your organization and teams.</p><p>In addition, I work outwards into the even broader organization and customers, which gives perspectives and context that I can use to inform the directions of the teams. Sharing this context is very important as it improves team decisions. From time to time, I also go into teams and help directly, but in most cases, that is mostly about asking the right questions to help them move forward. I also see myself as responsible for keeping updated on the latest and greatest ways of working. For me having a network of peers in similar organizations and a gang of sparring partners has been truly fruitful. Also, having a link to multiple inspiring startups is a constant reminder that you can innovate on a considerable amount of different things within an organization.</p><p>The principles of servant leadership are often interpreted as you don’t get to have your own opinions or I should be hands-off as the teams are empowered. My interpretation is that you should be more hands-on to understand where you should put your efforts to help out, whether it is with context, direction, structural changes, fixing gaps, coaching, guidance, or other means that create more optimized teams and organizations to create value fast for our customers. In terms of knowing where to help, I like to make a visual example of a surfer who is looking for the waves they should or should not prioritize to tackle, but in this case, the surfer is looking for the worst ones as he has the ability to make them great to surf.</p><h3>To summarize</h3><p>Be aware that others outside your circle could benefit from the information you hold and that you can contribute with questions and different perspectives on contexts shared. Think about how to be transparent so members who cannot attend synchronous meetings or other people can contribute with their perspectives. Think about it when you choose collaboration tools. Think about it when you write summaries; even consider write and share something about a small discussion that happened and is happing all over the organization daily. As a leader, share context, share context, and share context! I truly believe that focusing on transparency in empowered organizations and teams is the key to unlocking even more efficiency, alignment, and user value for our customers!</p><p>*Asynchronous — Describes events that do not happen at the same time. An asynchronous way of working means that collaboration does not happen in real-time but with written documents/videos etc. that are shared and consumed between people.</p><p>*Synchronous — Describes events that happen in real-time. For example, live discussions. Synchronous work does not necessarily mean co-located, it could for example be a meeting on zoom.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe453869a400" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimize ownership, make it somebody else’s problem]]></title>
            <link>https://medium.com/@hinderberg/minimize-ownership-make-it-somebody-elses-problem-a1b1c59ab00c?source=rss-51099a274601------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1b1c59ab00c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[timetovalue]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Hans Magnus Næss Inderberg]]></dc:creator>
            <pubDate>Fri, 04 Jun 2021 08:14:17 GMT</pubDate>
            <atom:updated>2021-06-04T09:12:25.550Z</atom:updated>
            <content:encoded><![CDATA[<p>In Spacemaker, we have a set of core beliefs. They are our guiding statements for time to value; speed, quality, reliability, and agility. We use them for alignment and guidance when discussions get heated about some choice we need to make in a stressful situation. I have for some time intended to create a couple of blog posts elaborating on a few of them, and finally, I have started! Who knows, maybe all of them will get some elaboration over time?</p><p>But, before we dig deeper, how did we end up with these core beliefs? In Spacemaker, we have many people with previous experience from different companies, with various tech, culture, and leadership structures, both as employees and consultants. One recurring theme for companies is that they tend to build up massive organizational overhead and debt. Debt can be both organizational, tech, and product-based, and more often than not, these are tied together. Why is that? And what has changed in the last decade or two that makes us believe it is possible to build a more robust company that reduces the debt you take on over the years to come? We asked ourselves these questions when we developed our core beliefs.</p><p>The first one I felt like writing more about is <a href="https://github.com/spacemakerai/spacemaker-tech-core-beliefs#minimize-ownership-make-it-somebody-elses-problem">Minimize ownership, make it somebody else’s problem</a>.</p><blockquote><em>Inventing and caring about a thing has a huge hidden cost — you have to build/configure it, maintain it, it spreads focus, broadens competence needs, takes time in maintenance, increases the potential for technical debt, etc. All in all, it dramatically increases time to value (in a non-transparent way). It also increases time spent on non-critical tasks. Since our most expensive resource is hours spent by our employees, most hours should be spent building the unique stuff only we have — our business logic and user interaction.</em></blockquote><blockquote><em>So, suppose an existing, well-designed, maintained software lib or managed service can do 70% of the job or fits only 70% unless you redefine your problem. In that case, you should work hard to reduce your problem to fit into this slot before you even consider doing it yourself. AWS Lambdas are an excellent example of something that has significant constraints on runtime, environment, and resources but should almost always be favored for its ease of use and reliability. Another example would be product support. If that is not your main product, why would you ever try to build a support platform yourself when you have SaaS like Intercom? You shouldn’t; these SaaS tools’ main mission is to solve support the best way possible, pouring millions into that goal. Let somebody else build it, and focus instead on building what is strategic to your product.</em></blockquote><blockquote><em>And if you ever consider building it, be aware that what we build WILL have lower Quality of Service than what you can get “off the shelf” — others have spent thousands of hours iterating over the existing service. The more our business grows and the more users we have that rely on our services every day, our QoS requirements will grow. Be humble and thankful to the sacrifices of all those engineers solving problems that we have as parts of our total product delivery. :)</em></blockquote><blockquote><em>So, start every day looking for stuff we could throw away and replace with something somebody else owns for us — and accept owning more stuff only when you are desperate :)</em></blockquote><blockquote><em>Own as little as possible, and build the things you own so that others don’t need to know or care how it works. This reduces time to value dramatically, as you can move forward independently of both the services you consume and of your consumers.</em></blockquote><h3>Why is this easier to accomplish now than before?</h3><p>There are many reasons why this core belief is easier to adhere to today than ten years ago. With services like Github, npm, Docker, and others, the open-source community has exploded. People have a place to share, collaborate, and easily build upon each other’s work and ideas. Previously, this kind of sharing and collaboration was happening primarily in the Linux community. Now, sharing has also become a commodity for software companies and developers in every industry. There’s been a seismic shift in the number of software libraries and frameworks available for everyone to use as part of their product development.</p><p>However, the most significant shift is the explosion of companies building products and services, solving problems for other companies delivered as digital services running in the cloud — also called Software-as-a-Service, Platform-as-a-Service, and Infrastructure-as-a-Service, or SaaS, PaaS, and IaaS, respectively. This ecosystem has gone from just having a couple of choices to becoming a candy store with products, services, and libraries solving almost every problem out there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AIulgKW3joyk7kzL" /><figcaption>Photo by <a href="https://unsplash.com/@5thsun?utm_source=medium&amp;utm_medium=referral">Luis Aguila</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When new companies emerge, they can build upon these products to solve the main problem they have set out to solve instead of building everything from the ground up. Learning to take advantage and pick from that big pool of candy is essential to reduce both organizational, technical, and product debt over time.</p><h3>Adapting your problem to a solution will often be worth it</h3><p>An argument in favor of DIY is that you get to build a solution tailored to your needs. Either because the offering you are considering does not match the problem you are solving or simply because the API is cumbersome to work with. Here is where our core belief gets pretty brutal: <em>“If an existing, well-designed, maintained software lib or managed service can do 70% of the job or fits only 70% unless you redefine your problem. In that case, you should work hard to reduce your problem to fit into this slot before you even consider doing it yourself.”.</em></p><p>The benefits of using software libraries and SaaS are so great that we are willing to let the available offerings define how we build our product. We often choose not to tailor a solution to our needs but instead say that we are happy to build something within the constraints and boundaries set by the SaaS product we are buying or library we are using. Because in the end, the maintained SaaS or library is likely more invested in solving that problem than we would be. Therefore: fewer bugs, faster fixes, and better scalability.</p><p>We use SaaS and libraries to solve many of the sub-problems we have. That gives us more time to focus on the complexities of the main problem we’re trying to solve: building our product. Which drastically decreases the time to value for our users.</p><h3>Exploiting the SaaS ecosystem</h3><p>If you don’t know your way around the candy store, it is easy to resort to DIY. I still hear about companies that pour resources into building systems for monitoring their products. Why? Because they didn’t find that one product that solved all their needs.</p><p>Checkly is an excellent example of a monitoring SaaS tool we use in Spacemaker. It lets us monitor our services E2E and build tests that ensure we get notified if we break our product’s core value. If we were to make something like Checkly, it would take years and many resources, and it would not take us closer to solving what our product is supposed to solve. Checkly solves a sub-problem for us, but it lacks in-depth logging tools. However, many other companies out there are experts on building in-depth logging tools that we can utilize.</p><p>An excellent thing about the candy store of SaaS tools is that they fit together. They are incentivized to integrate with other SaaS because it elevates the value proposition of their own product, making these products a part of a total monitoring ecosystem of SaaS. These integrations allow the customers to tailor the overall monitoring platform based on multiple tools that solve different problems inside that domain.</p><h3>On-premise should not be an option</h3><p>When discussing this with established businesses, I hear arguments like “using SaaS tools is not as secure”, “let’s build something on our own”, or “having it on-premise is better”.</p><p>It’s not! The only way it could be more secure is to guarantee with 100% certainty that your tool/service/system is never accessible through the internet. And in 2021, you most likely want that.</p><p>If it is accessible, the chances are that you’re running an outdated and insecure lib, runtime, or OS. Solving that issue by adding a VPN on top of it is not solving the actual problem. At best, it is a band-aid, securing something with something else. At the same time, you are increasing the overhead and complexity, and therefore time-to-value for everyone in the company.</p><p>On the other hand, a SaaS with millions of users would very likely have dedicated teams to keep their service secure. Not only are they a target for hackers, but their reputation and business are also on the line. No one would want to use a service where security is not taken seriously, and a service provider definitely doesn’t want to be held responsible for security breaches. This is a massive incentive for making sure it happens as few times as possible.</p><p>It is naïve to believe that you can do better than what’s already out there, and even though you can, why would that take you faster towards solving your main business problem?</p><h3>Don’t fall for the standardization trap</h3><p>Another hidden cost of running these services on your own, or building some lib from scratch, is that you have limited resources for maintaining the service because it’s not your primary business. That triggers standardization; fit into the same box. Standardization in a world that innovates at the pace that our world does is organizational debt that you sometimes need. However, it would be best if you avoided it as long as you can. One size fits no one!</p><p>Why does it trigger standardization? As a simplified example, say you have 50 teams running on your on-premise service. When would it be best for your server team to support a new version of something? You would upgrade when the last team is ready for it. Because maintaining two versions for a long time is too heavy for your team, or creating the abstraction to handle it is too costly.</p><p>In the meantime, the other teams that are ready for the upgrades have to wait for new capabilities that potentially could reduce time to value for the teams. <strong>You will never be faster than the slowest team</strong>! And since teams need to optimize for different things, you can’t say that the slowest team is prioritizing wrong because they might have more critical issues than getting ready for the new capabilities that the upgrade gives.</p><p>Making teams dependent on each other in this way will, over time, make companies, teams, and people <strong>slow</strong>. And what are the benefits left with trying to solve a problem that someone else has more resources and focus on solving than you have? It only makes sense if your business’s primary goal is to solve the same problem in a better way and be a competitor.</p><p>This is why we in Spacemaker focus on creating teams that own their domain from top to bottom. It helps them be autonomous both organizationally, product and tech-wise, and they are therefore <strong>optimized for time to value</strong>. Having a candy store of products, libraries and services enable that vertical thinking.</p><h3>Final words</h3><p>Building upon each other’s learnings has been one of the main drivers for human evolution, and now you can do the same with products and services accessible from everywhere! Of course, you should seize the opportunity to <em>minimize ownership and make it somebody else’s problem</em>! If you want to create products customers love, at the quality and speed they demand, is there really any alternative?</p><p>Want to read our tech core beliefs? <a href="https://github.com/spacemakerai/spacemaker-tech-core-beliefs">https://github.com/spacemakerai/spacemaker-tech-core-beliefs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b1c59ab00c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>